What to bring to a free AI audit in San Diego

Nidrosoft is the San Diego studio of Cyriac Zeh, a design engineer who implements AI for small and mid-size businesses: audits, custom builds, phone and receptionist agents, training, and systems the team can own. A free AI audit San Diego owners should treat as a working session, not a product tour. Bring the people who answer the phone, the name of the customer relationship management (CRM) or practice management system (PMS), after-hours rules, whether Spanish is required on the line, and one painful repeating workflow. Volume from the last 30 days of missed calls or inbox backlog helps if you already keep it. Do not invent a number for the meeting.

Key takeaways

• A useful audit costs hours on a named process. A tool directory is a different purchase.
• The first artifact to pack is an org chart of who picks up, who texts back, and who owns the system of record.
• Last-30-day missed-call or inbox counts are optional evidence. If you do not have them, say so. Do not guess a county average.
• Write the CRM or PMS name, after-hours rules, and Spanish need before anyone talks about agents.
• You can stop after the map and take it to seats, a boutique, or another builder. The packet is yours.
• Book a free audit when a decision maker can grant calendar and system access the same week.

Contents

• What the free session is actually for
• Numbered packing list
• Draw the org chart of who answers the phone
• Last 30 days of volume, only if you already have it
• Name the CRM or PMS and the unofficial stack
• After-hours rules, Spanish, and one painful workflow
• How to run the first working hour
• How Nidrosoft handles this
• What you leave with, and what you can refuse
• Frequently asked questions
• Bring the owner and the ugly queue

What the free session is actually for

The free audit on this site is the door into that work. It is not a lunch-and-learn about models. It is not a blessing for a homepage chatbot you already promised a board. It is two people looking at how work already moves through a Kearny Mesa lot, a La Mesa front desk, a Chula Vista contractor office, or a North County clinic, then ranking where a later build would pay back.

Cyriac Zeh founded the studio after design and engineering roles at Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. The studio has shipped 125 products and keeps 16 systems public. Those numbers describe range. They do not describe your hours. Omnira Dental, Eviction Wizard, Nexuvo, TokenTra, and NanoBrief are reference systems you can open. Your first session may point at something quieter: a shared inbox, a recall list, a missed-call text that nobody owns.

Fit is usually companies roughly 30 to 250 people, plus smaller shops if the workflow is clear. Under 30, one later build has to pay for itself. Past 250, pick one department before anyone books the calendar. A 4,000-person health system that wants a county-wide vision and no PMS login should hire a strategy firm. A 12-person HVAC shop in Oceanside with a named dispatcher and a repeating after-hours path can still sit down.

The session needs a decision maker. The person who can grant CRM or PMS access, approve a write path later, and say no to a pet chatbot belongs on the invite. If only a vendor-relations intern can attend, wait. AI implementation for San Diego small businesses starts the same way: one repeating process, one owner, one system of record.

San Diego texture matters because the unofficial stack changes by zip. A South Bay office that takes Spanish-first callers on the mobile will waste an hour if the audit assumes English-only scripts. A Del Mar medspa that books on Coast Highway walk-ins will waste an hour if the audit assumes every appointment starts on a form. Bring the truth of the desk, not the brochure.

Numbered packing list

Print this or paste it into the calendar invite. Each item has a field name you can fill before the call. Empty is allowed. Fiction is not.

1. DecisionMakerName and DecisionMakerRole. Who can grant system access and stop a bad scope. Owner, office manager, or department lead. Not a student project, not a logo hunter.
2. LocationsAndDesks. Street-level truth: Encinitas front desk, El Cajon yard, La Jolla suite, Chula Vista warehouse. One line per site that answers the phone or the inbox.
3. PhoneOrgChart. Names, not titles only. Who answers during business hours. Who covers lunch. Who owns the mobile that still rings at 7 p.m. Who is allowed to book, quote, or take a card.
4. MissedCallCountLast30Days. Fill only if your carrier, voice over Internet protocol (VoIP) portal, or answering app already shows it. Label the source: RingCentral export, Nextiva dashboard, iPhone Recents screenshot, FrontDesk log. If you do not have a count, write unknown and bring the login so someone can look together.
5. InboxBacklogLast30Days. Unread count or oldest open thread in the shared mailbox, patient portal, or CRM activity view. Again, only if the screen already shows it.
6. SystemOfRecordName. CRM or PMS product name and edition if you know it. HubSpot, Salesforce, ServiceTitan, Jobber, Open Dental, Dentrix, EagleSoft, AppFolio, or the spreadsheet that still closes Friday.
7. UnofficialStack. WhatsApp group, personal Gmail rules, paper recall column, Facebook Marketplace tab, after-hours cell. One line each.
8. AfterHoursRules. Hours the live person stops. What the greeting says. Whether a human is on call. Whether Spanish is required after 5 p.m. Whether emergencies go to a mobile or to voicemail.
9. SpanishNeed. Required on first greeting, required for a subset of callers, or English-only by policy. South Bay and many Kearny Mesa and El Cajon lines are not English-only even when the website is.
10. OnePainfulWorkflow. A single repeating path with a start and an end. Missed-call text-back. Hygiene recall. Estimate follow-up. Notice-to-file prep. Inventory outreach. Name the person who does it on Tuesday.
11. ApprovalGates. What a system must never do without a person: take a card, change a chart, file a legal notice, send a customer email, quote a price that binds the company.
12. AlreadyTried. ChatGPT seats, Copilot, a Rosie or Goodcall trial, a Smith.ai month, a FrontDesk or DentalAssist signup, a Voksha demo. Say what you kept and what you turned off.
13. AccessNote. Can an owner share a screen of the CRM or PMS the same week. Is there a sandbox. Has security already said no write path this half.
14. PriorDeck. If a strategy firm already wrote a pack, bring page numbers. The audit will mark which items are a live process and which items stay with the firm that wrote the deck.

That list is enough for a first hour. Do not add a 40-page request for proposal (RFP) unless procurement already requires it. Do not add invented win rates. Do not add a competitor’s case study with the logo blurred.

If two rows are empty besides volume, reschedule. The map will lie.

Draw the org chart of who answers the phone

Most San Diego shops think they already know this. The first screen share usually proves they do not. The website lists a main number. The Google Business Profile lists a mobile. The front desk in La Mesa forwards to a coordinator who is also running hygiene confirmations. The owner in Carlsbad still answers from the truck. The bilingual cousin in Chula Vista takes overflow on WhatsApp and never logs it.

Draw boxes for people, not for software. Software comes second.

Start with the live interval. Who sits at the desk from open to close. Name them. Write the hours. Write which number rings their headset. Write whether they can book in the PMS or only take a message. Write whether they can speak Spanish on the first greeting without transferring.

Then draw lunch and breaks. Many missed-call spikes in service businesses are 12:00 to 1:30, not midnight. If the “receptionist” is also the biller, the phone is already an overflow problem during claims hour.

Then draw after hours. California evenings are when HVAC, dental pain, and property emergencies arrive. Who owns the mobile. Is there a paid on-call. Does the greeting promise a callback that nobody measures. Does the Spanish greeting exist only on the English voicemail tree.

Then draw walk-ins. A Coast Highway medspa and a Baltimore Drive dental office still get bodies at the counter. The person who looks up from the clipboard is part of the phone org chart because they cannot pick up while they check in a patient. An agent that books over that person without a rule will double-book the chair.

Then draw transfers. Who is allowed to take a clinical question. Who is allowed to quote a job. Who is allowed to take a card. If those names are blank, the later agent will either stall on every interesting call or invent authority it does not have.

Bring this as a one-page sketch. Boxes and arrows are enough. A polished org chart from human resources is usually the official story. The unofficial story is the one that costs hours.

If you have more than one location, draw one chart per desk. A North County clinic and a South Bay clinic that share a brand rarely share a lunch cover or a Spanish script. Treating them as one box is how an audit recommends a single greeting that fails on both lines.

Last 30 days of volume, only if you already have it

Volume is useful when it is real. It is harmful when it is a story.

If your VoIP portal, carrier bill, or answering product already shows inbound, answered, missed, and voicemail for the last 30 days, export it. Label the date range. Label the number. A Kearny Mesa dealer and a Chula Vista contractor on the same brand may not share a trunk. Bring both exports if both lines hurt.

If the shared inbox or CRM activity view already shows open threads, unread count, or oldest waiting item, screenshot the filter. Name the mailbox. info@, scheduling@, and the owner’s personal Gmail are different queues.

If you do not have those numbers, write unknown. That is a complete answer. The first working session can open the portal together and read what is there. Guessing “we probably miss 40 calls a week” teaches the map a fiction. This studio will not treat a guessed figure as a Nidrosoft statistic, and you should not treat it as yours either.

Do not paste a blog’s “typical dental office misses X calls” into the invite. Those posts invent or recycle numbers to rank on search. They are not your desk. They are not this studio’s archive. Nexuvo’s public dealer result (3x more inventory with 80 percent less manual outreach) and TokenTra’s public spend range (teams cut 10 to 30 percent of wasted AI spend) are named-product results. They are not a missed-call benchmark for a La Jolla suite.

If you already run Rosie, Goodcall, Smith.ai, FrontDesk, DentalAssist, or Voksha, bring that product’s call log for the same 30 days. Those products are good at same-day start. Their logs are often the cleanest volume you have. Bring the log as evidence of what the subscription already catches, not as a reason to hide the unofficial mobile that still rings the owner.

If the only volume you have is a feeling (“Fridays are bad”), write the feeling as a hypothesis and pick a week to measure after the session. The audit can still rank a workflow without a perfect count. It cannot rank a workflow against a number you made up in the parking lot.

Name the CRM or PMS and the unofficial stack

Write the product name. Edition if you know it. Hosted or on-prem if you know it. Who holds the admin login. Whether an application programming interface (API) or an export exists. Whether a prior vendor already burned the office manager on a failed sync.

Dental and clinic desks in Encinitas, La Mesa, and Chula Vista usually live in Open Dental, Dentrix, or EagleSoft. Contractor desks in Oceanside and El Cajon often live in ServiceTitan, Jobber, or a spreadsheet named jobs-final-v7. Property teams may live in AppFolio or Buildium. Software teams near UTC may live in Linear and HubSpot and still run renewals in a Sheet. The audit needs the name because feasibility is API reality, not a slide about agents.

Then write the unofficial stack. The hours hide there. The WhatsApp group that takes South Bay overflow. The paper column for hygiene recall. The Facebook Marketplace tab a dealer still types into the CRM at night. The personal cell that gets the after-hours HVAC call because the main greeting dumps to voicemail. Nexuvo exists as a public product because that night of retyping was the job. Your unofficial stack may be smaller. Name it anyway.

If you already pay model providers, bring the invoice or the admin usage view. TokenTra is the studio’s public product for spend by feature. You do not have to buy it. The audit does need to see whether “we already use AI” means a useful write path or a second copy of a chat seat you already waste.

Credentials belong on the risk list, not in the chat thread. Nerlude exists in the public archive because founders lose keys in Slack. Write where production secrets live today. If they live in a personal password manager, write that. Do not paste the keys into the calendar notes.

After-hours rules, Spanish, and one painful workflow

After-hours rules are a script, not a vibe. Write the clock. San Diego service shops often close the live desk at 5 p.m. while the county still has two hours of daylight and a full evening of emergency calls. Write what the greeting currently says, word for word. Write whether a human is on call, and for which event types. Write whether the promise is “we will call you tomorrow” or “someone will call you tonight.” Those are different builds.

Spanish need is a first-greeting question, not a website footer. South Bay callers, many Kearny Mesa industrial lines, and a large share of El Cajon and Chula Vista traffic will start in Spanish even when the owner’s email is English. Write whether the live person can answer in Spanish. Write whether the current voicemail tree has a Spanish option that actually routes. Write whether booking, estimates, and medical intake have approved Spanish copy. An agent that improvises clinical or price language in a second language is a risk, not a feature.

One painful workflow is the heart of the session. Pick one. Repeating. Named owner. Start and end.

Good examples, written as outcomes:

• Missed-call text-back: inbound missed on the main trunk, outbound short message, CRM or PMS note, human follow-up if the caller replies with a booking or a clinical question.
• Hygiene recall: PMS report rows, owner column, draft message from an approved script, coordinator send, reason code for do-not-call.
• Estimate follow-up: Jobber or ServiceTitan estimate sitting past N days, draft follow-up, dispatcher send, no silent price change.
• After-hours HVAC: greeting, emergency keyword path, on-call mobile transfer, morning summary in the board.
• Inbox triage: shared mailbox, draft reply, human send, no autonomous customer email.

Bad examples: “AI strategy.” “Make the office modern.” “A chatbot on the homepage.” Those can be later rows on a map. They are a poor first hour because they have no Tuesday owner.

Write the approval gates next to the workflow. Money, contracts, charts, legal filings, and customer-facing sends stay under a person in any later Nidrosoft build. If you want an agent that charges a card or files a notice with no click, say so now so the studio can decline. Another vendor will take that scope. You will own the error.

How to run the first working hour

Use this sequence on the call or in the room. Field names match the packing list.

1. Confirm DecisionMakerName is present and can grant a screen share of SystemOfRecordName this week.
2. Walk PhoneOrgChart out loud. Correct names. Add the unofficial mobile.
3. Open volume only if MissedCallCountLast30Days or InboxBacklogLast30Days is not unknown. Read the source, not a memory.
4. Open SystemOfRecordName. Show the record a new lead or patient creates. Show the fields a person currently types: FirstName, LastName, CallbackNumber, Source, AppointmentType or JobType, LanguagePreference if it exists.
5. Show UnofficialStack without apology. The workaround is data.
6. Read AfterHoursRules and SpanishNeed as they are, including the greeting text.
7. Walk OnePainfulWorkflow from first trigger to done. Time one real example if a recording or a thread exists.
8. Write ApprovalGates on a shared note. Read them back.
9. List AlreadyTried and what you turned off. A cancelled Rosie trial is information.
10. End with three candidate ranks: hours, feasibility, payback. No vendor shortlist yet unless that was the only job you wanted. If you only wanted a shortlist, hire a boutique from the AI consulting alternatives page and staff the build yourself.

Keep the hour on one workflow. A second location can be a second hour. A board narrative is a different meeting. Workshops have already been run in La Mesa for operators who brought their own files. The same rule applies here. If the recall report or the missed-call log cannot be opened, you bought a conversation.

Remote is normal. Cyriac Zeh lives in San Diego. A screen share from Carlsbad or Chula Vista is enough when the system is reachable. Ask for an on-site hour if the unofficial stack is paper on a counter. Say that when you Book a free audit.

How Nidrosoft handles this

The AI audits service is two weeks in the work when you continue past the free door. Week one is mostly Embed: sit with the people who do the job, watch the unofficial path, ask what ChatGPT or Copilot already ate. Week two is mostly Diagnose and the first pass of Scope: hours, feasibility, payback, and a first outcome written in plain sentences.

You own the ranked map, the risk notes, and the recommended next purchase even if you stop. That next purchase might be seats and corporate training. It might be a scoped build in your accounts. It might be nothing from this studio. The last option is a valid audit.

The method is Embed, Diagnose, Scope, Build, Own. Build happens in your cloud or your SaaS tenant when the work allows it: Azure, AWS, Google Cloud, Cloudflare, or private infrastructure, with EU hosting and EU data residency when a policy needs it. Approved access. Audit trails. Money, contracts, and customers stay under a human. Training uses tomorrow’s list, not a toy clinic.

Public reference systems stay named: Omnira Dental at omnira.dental, Octana, Eviction Wizard, Guidera, TokenTra, Protectron, Nerlude, Nexuvo, NanoBrief. Sixteen public systems. No confidential logo wall. If a later builder pretends your open questions vanished, you still have the list from Diagnose.

Cyriac Zeh is the person in the thread. That is a feature for judgment and a limit for parallel squads. If you need a fifty-person delivery floor, hire a shop. If you need a board pack with no path to a write, hire a strategy firm. If you need a same-day receptionist subscription, start with Rosie, Goodcall, Smith.ai, FrontDesk, DentalAssist, or Voksha and come back when the PMS rules do not fit the template.

How we work lists a common shape after the map: plan in the following weeks, first implementation often described as weeks five through ten. Access delays move the calendar. The free session does not invent a monthly rate. Stacks differ. A two-chair practice is not a 200-person software company.

What you leave with, and what you can refuse

A finished free session should leave you with a filled packing list, a corrected phone org chart, and a one-page note that names the first workflow, the system it touches, the human gate, and the open questions (missing API, missing Spanish copy, security delay). If you continue into the two-week audit, you leave with the ranked table the stand-up can read aloud.

You can refuse a build. You can take the packet to another firm. You can buy seats. You can do nothing until the owner of the CRM is back from leave. Those are clean outcomes.

Refuse a session that wants you to invent volume. Refuse a session that will not look at the unofficial mobile. Refuse a session that starts with a homepage bot. Refuse a session that asks you to sign a statement of work before anyone has seen SystemOfRecordName.

If the honest next step is a strategy deck for a board that will not grant production access, use the alternatives page and hire that shape. If the honest next step is a specified application with a bench, hire a product shop and put ownership of prompts in the contract. If the honest next step is a live process in tools you already pay for, stay on the audit path.

Email cyriac@nidrosoft.com with the packing list if the public calendar is full. The calendar is https://calendar.app.google/GCtfuTx3Ms6K7d579. Bring the owner and the ugly queue. Leave the invented averages in the parking lot.

Frequently asked questions

What should I bring to a free AI audit in San Diego? Bring a decision maker, a phone org chart with names, the CRM or PMS product name, after-hours rules, Spanish need, and one painful repeating workflow. Add last-30-day missed-call or inbox volume only if a portal already shows it. Write unknown rather than guessing. Book a free audit when those fields are ready.

Do I need 30 days of call data before I book? No. Volume helps when it is real. If the VoIP or inbox screen is blank, say unknown and open the login together. Invented county averages will distort the rank. The audit can still cost a named workflow by walking one real thread.

Can a 10-person shop in Chula Vista or Oceanside book this? Yes when the workflow is clear and one later build can pay for itself. Fit on the site is usually 30 to 250 people, plus smaller shops with a named owner and a repeating path. A shop with no system of record and no Tuesday owner should wait.

Will the audit push a phone agent on day one? Only if hours, access, and gates support it. Many first maps rank missed-call text-back, recall, or inbox draft-and-send above a voice agent. Same-day subscriptions already exist for simple answering. A custom agent waits on PMS or CRM rules you can name.

What if we already paid a strategy firm? Bring the deck and page numbers. The session will mark which items are a live process in your stack and which items stay with the firm that wrote the narrative. Nidrosoft will not rewrite a board pack for sport.

Is the free audit the same as the two-week paid audit? The free session is the door: packing list, screen share, first rank. The AI audits service is two weeks of Embed and Diagnose when you continue. You own the map either way. You do not own a production integration unless you buy a build.

Bring the owner and the ugly queue

A free AI audit in San Diego is a working hour on a named desk, not a tour of model vendors. Pack the phone org chart, the CRM or PMS name, after-hours and Spanish rules, and one workflow that already repeats. Bring last-30-day volume only when a screen already shows it. Book a free audit when the decision maker can open the system the same week. The map is yours even if you hire someone else to build.