How to implement AI in a 10-person San Diego company without hiring a team

To implement AI small business San Diego work in a 10-person company, pick one repeating workflow, write the field names the operator already uses, buy seats or a same-day product if that leftover wins, and only then wire a write path into the system you already pay for. You do not hire a department. You name an inheritor. 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.

Key takeaways

• Under 30 people, one later build must be able to pay for itself. Fit on this site is usually 30-250, plus smaller shops if the workflow is clear. A 10-person shop qualifies only with a named owner and a repeating job.
• Numbered steps beat a vision offsite. Field names beat "make us AI native."
• Copilot or ChatGPT seats and a Rosie-class receptionist are honest first buys when drafting or pickup is the job.
• Custom work waits until a customer relationship management (CRM) system, practice management system (PMS), inbox, or phone board needs a row the template cannot write.
• Workshops have been run in La Mesa. A room is a leftover. It is not a write path.
• Book a free audit if you want the map before you spend a year of evenings on a chatbot.

Contents

• What a 10-person shop can own
• Step-by-step implementation
• Field names you should write on day one
• San Diego clocks for a small crew
• When seats or SaaS should win
• What you must not automate yet
• How Nidrosoft handles this
• A 30-day calendar you can print
• Where a thin crew still wastes a quarter
• Frequently asked questions
• One workflow, one inheritor

What a 10-person shop can own

A 10-person San Diego company already has an unofficial stack. The estimator's camera roll. The coordinator's Sheet. The founder's ChatGPT history. The after-hours cell. That stack is the product surface. An implementation that forbids it will miss the hours. An implementation that tries to replace the whole stack in a month will miss Friday.

You can own a ranked list of recurring jobs, a first system in accounts you already pay for, and a runbook the Tuesday person can follow when the founder is in Oceanside traffic. You cannot own a center of excellence. You cannot own five agents. You cannot own a Health Insurance Portability and Accountability Act (HIPAA) badge this studio does not publish. You cannot own a Nidrosoft price list. This page does not publish prices. Cost drivers live on the companion cost article if it is live: access, integrations, training, after-hours coverage.

AI implementation for San Diego small businesses is the county pillar. This page is the small-crew cut. AI consulting alternatives keeps seats, shops, and studios in different columns. How we work is Embed, Diagnose, Scope, Build, Own. You can run a thin version of those five words without hiring us. You can also stop after a two-week audit and take the packet to SideGuy in Encinitas, to an intern who will stay, or to a SaaS signup.

Public texture you can open: Omnira Dental, Eviction Wizard, TokenTra (10-30% wasted spend when you can see the bill), Nexuvo (3x inventory, 80% less outreach), NanoBrief (under 2 minutes versus 3+ hours), Octana, Protectron, Nerlude, Guidera. Those are patterns. They are not a promise your first system is a clone. A 10-person shop should steal the gate, not the product name.

Step-by-step implementation

1. Write WorkflowName in one sentence. Example: "Missed calls become a text and a Jobber row." Example: "Hygiene recall list gets a drafted text the coordinator sends." Example: "Estimates sent last month get a day-2 and day-5 follow-up." If you cannot write the sentence, you are not implementing. You are browsing.

2. Write WeeklyVolume and HoursPerWeek the operator already spends. Time three Fridays if you do not know. Invented hours produce invented software.

3. Write SystemOfRecordName: HubSpot, Salesforce, Open Dental, Dentrix, Jobber, Housecall Pro, ServiceTitan, Gmail, AppFolio, OpenTable, a Sheet. Write AdminOwner. If there is no admin, the first job is access, not a model.

4. Write OperatorName (who does the job today) and InheritorName (who will run it if the operator is in a truck). If inheritor is "none yet," stop. Assign it. A 10-person shop that cannot name a second person should buy seats, not a custom agent.

5. Write HumanGates: money, filings, clinical notes, customer sends, dispatch. The model drafts. A person clicks.

6. Write AlreadyTried: Copilot, ChatGPT, Rosie, FrontDesk, a prior intern, a prior deck. An embed that ignores leftovers duplicates spend.

7. Write CounselSentence if it exists: customer text in a third-party model, recording, texts. If you record calls, California is widely reported as two-party consent. Identify as AI. This is not legal advice. Read the consent article on this site.

8. Rank three leftover types. Seats if the job is drafting. Same-day software-as-a-service (SaaS) if the job is pickup (FrontDesk, DentalAssist, Rosie, Goodcall, Smith.ai, Voksha). Custom if the job is a trusted row the template cannot write.

9. If seats win: buy the licenses, run a La Mesa-style working session on your files (workshops have been run there), keep a playbook in your Drive. Stop.

10. If SaaS wins: forward the number, write GreetingApproved, run seven days, export VendorCallLog7Days. Stop or continue based on retype time into the system of record.

11. If custom wins: buy an audit or run the two-week map yourself. Scope one outcome paragraph. Build in your tenant. Keys in your vault. Nerlude exists because keys still land in Slack.

12. Measure the metric you already track for 30 days. Do not invent a dashboard to declare victory. Reopen Diagnose only in writing.

Do these in order. Skipping to step 11 because a vendor demo was exciting is how a 10-person Encinitas shop spends a quarter on a homepage chatbot while the Sheet still runs Friday.

Field names you should write on day one

Print the table. If a row is blank, that is the first homework. Adjectives such as "engagement layer" do not belong on this sheet.

Dental-shaped shops add PatientName, NextDueDate, InsuranceCarrier as a label. Trades add JobType, ZipCode, PriorityFlag. Property desks add UnitId, PropertyId. Restaurants add PartySize, CoversSat. Software teams add FeatureName, InputTokens. Use the nouns you already shout across the room.

San Diego clocks for a small crew

A 10-person crew feels commute and coverage more than a 200-person company. A La Mesa shop loses the estimator to the Interstate 8 drive. A Kearny Mesa lot stays loud through dinner. A Chula Vista front desk takes Spanish-first callers after a border-schedule shift. A Carlsbad or Oceanside yard picks up tourism overflow on the same Friday the technician is on a roof. An Encinitas or Del Mar clinic on Coast Highway takes walk-ins at 11:40 a.m. that steal the last consult. A Gaslamp restaurant runs no-shows on a four-top. A UTC or La Jolla 10-person product company sits next to biotech and does not need enterprise theater.

Write coverage before you write prompts. Who answers when the operator is in El Cajon traffic. Who honors STOP. Who pages on no-heat. Who sends the recall text. If the answer is "whoever is free," you do not have an inheritor. You have hope.

Remote implementation is normal when HubSpot or Open Dental is reachable. In-room days help when the unofficial stack is a clipboard in a La Mesa suite or a Marketplace phone that will not screen-share. Workshops have been run in La Mesa. Say which you want. There is no published Nidrosoft neighborhood office grid.

Military families move on orders. Mark DoNotContact and Transferred. A 10-person shop that keeps texting a dead number will spend its thin goodwill faster than a large group.

When seats or SaaS should win

Seats win when the painful job is drafting: emails, listing remarks, a BEO, a job description, a first-pass estimate narrative the estimator still prices. Buy ChatGPT or Copilot. Save the prompts next to the files. Train on tomorrow's list. NanoBrief-shaped speed is the pattern for a brief someone asked for. A brief nobody asked for is waste.

SaaS receptionists win when the painful job is a dead line and the script is short: hours, address, book or take a message. Praise same-day start. Measure missed calls for 30 days. Custom starts when writeback, Spanish-first South Bay routing, or a two-location lock is the product.

A product shop (SideGuy in Encinitas is the public local example of specified glue) wins when you already have screens and a spec. Do not hire a studio to re-diagnose a finished spec. A strategy pack wins when a parent needs a vote and you have no write path. You probably do not need that pack at 10 people. If you do, buy it separately.

Local names without smearing: Parsons AI, Applied Intelligence, San Diego AI / James Schlauch, AI Upside Group, Christian Johnston's "Your AI Guy" brand. Score leftovers. Do not steal the phrase.

What you must not automate yet

Do not automate money movement. Do not file a notice. Do not buy a car. Do not chart a clinical fact from a photo. Do not quote an unpublished price. Do not diagnose a rash. Do not tell a tenant they will be evicted. Do not set a token budget without a person. Eviction Wizard, Nexuvo, Omnira, and TokenTra all keep a person on the consequential click. Copy the gate.

Do not automate a process that happens twice a year. Do not automate the homepage until intake is complete. Do not launch two agents in the same month. Do not record calls until counsel writes the sentence. Do not store production keys in a personal vault.

Do not fire the receptionist or the coordinator on the back of a demo. Coverage first. The replacement article on this site stays on that question.

How Nidrosoft handles this

Nidrosoft handles a 10-person brief by testing whether the workflow can pay for itself. If it cannot, we will say buy seats or SaaS. If it can, the audit is two weeks: Embed, then Diagnose and a first Scope. You can stop. Cyriac Zeh is the named person. 12+ years, 125 products shipped, 16 public. Formerly Anthropic, Microsoft on Bing and Edge, Intuit, Gap Inc. No junior bench. That is a limit if you wanted a department. You do not want a department.

We will not take "make us AI native." We will not publish prices or a HIPAA certification. We will praise Rosie when Rosie wins. AI audits are the packet. Book a free audit, cyriac@nidrosoft.com, https://calendar.app.google/GCtfuTx3Ms6K7d579. Bring the field table. Name the inheritor.

A 30-day calendar you can print

Days 1-2: write the field table. Days 3-4: time the hours. Days 5-7: decide seats, SaaS, or custom. Days 8-14: if seats or SaaS, implement and train; if custom, run or buy the map. Days 15-21: one write path or one forward, not both unless a lock exists. Days 22-30: measure MetricAlreadyTracked. Friday of day 30: keep, stop, or write a new Diagnose. Do not add a second workflow because a hallway said so.

If you want a room in that month, use a working session on your files. Workshops have been run in La Mesa. Implementation versus workshops is the split. A playbook you keep is a complete leftover. A queue in Jobber is a different leftover.

Where a thin crew still wastes a quarter

Ten people have fewer hiding places than a 200-person company and they still waste a quarter. The usual leak is a second project that starts because a hallway demo was pretty. The first workflow is half-wired. Someone saw a voice agent. Someone promised a website chatbot. Someone bought a second ChatGPT workspace because the first one felt “personal.” Friday still runs on the Sheet. The inheritor is now angry at two tools.

Write a freeze. From day 8 to day 30, no new leftover. If a partner, a spouse, or a vendor sends a link, park it in a note titled LaterQueue. Do not open a second tenant. Do not forward a second number. Do not hire an intern “just to explore models.” Exploration is seats on tomorrow’s real list, not a side quest.

The second leak is access theater. The owner says HubSpot is ready. The admin login sits with a former bookkeeper in Arizona. The PMS vendor wants a ticket that takes three weeks. The unofficial path is still a Gmail label. Implementation that pretends the official system is live will build against a ghost. Days 1 and 2 of the calendar exist to catch this. If AdminOwner is blank, the whole month is access, seats, and a playbook. That is still implementation. It is not a custom agent.

The third leak is language and hours treated as settings. A 10-person Chula Vista desk that greets in Spanish cannot buy an English night script and call the month done. A 10-person Oceanside yard that dies on harbor Saturdays cannot buy a weekday-only forward. A 10-person Encinitas clinic that shares a book with Del Mar cannot hide LocationId. Write those constraints on day 1 next to WorkflowName. They are cheaper than a rebuild in week six.

The fourth leak is keys. A founder pastes an API key into a group chat so “the nephew can try something.” Nerlude exists because that pattern is common. Put KeyLocation on the table. If you cannot name a vault, you are not ready for a write path. You are ready for seats.

The fifth leak is vanity metrics. A 10-person shop does not need a dashboard that counts tokens for fun. Count the metric you already use: chairs, jobs booked, estimates answered, inbox age, no-shows. If that number is quiet on day 30, pause send. Keep drafts. Own includes the right to stop. A thin crew that keeps a quiet agent running will spend more hours explaining it than they spent on the old Sheet.

Bring the field table to any vendor, including this studio. If they will not sit with InheritorName and HumanGate, they are selling a department you cannot staff. Compare partners if you are choosing who sits in the room. A product shop is fair when you already have a spec. A SaaS receptionist is fair when the trunk is dead. A studio is fair when one row must land and someone on payroll will mark it.

Frequently asked questions

Can a 10-person San Diego company implement AI without hiring an engineer?

Yes if the leftover is seats, a playbook, or a same-day receptionist. Custom writeback still needs someone who can merge. That someone can be a studio, a shop, or a person you already employ. You do not need a team of four.

What is the first workflow most shops should pick?

Missed-call text-back, estimate follow-up, recall drafts, or invoice attribution. Rank hours. Favorite chatbots go last unless they win.

Do we need a HIPAA-certified vendor?

If you handle protected health information, ask counsel and ask for a business associate agreement. This studio does not publish a HIPAA certification. A blog badge is not your paper.

Will you work at our size?

If the workflow is clear and an inheritor exists, yes. If you cannot name the job, buy seats and come back. Fit is usually 30-250, plus smaller shops with a clear path.

How do we start this week?

Write WorkflowName, SystemOfRecordName, and InheritorName. Book a free audit if you want the map. Or buy the seats tonight if drafting is the job.

What if we already use ChatGPT every day?

Bring the paste history. That is data. The next step is a trusted row or a stop, not a second consumer account.

What if two owners disagree on the first workflow?

Write both sentences. Time both for one week. Rank hours. The louder owner loses if their job happens twice a year. If they still disagree, buy a La Mesa-style room on the files, not two agents.

Who holds the keys on a ten-person crew?

The admin of the system of record, not a nephew and not a personal vault. Put KeyLocation on the field table. If you cannot name it, stay on seats until you can.

One workflow, one inheritor

A 10-person San Diego company implements AI by writing field names, picking seats or one queue, and naming the Tuesday person. You do not hire a department. You do not launch five agents. If the crew sits in Chula Vista, write Spanish on day one. If it sits in Encinitas, write LocationId before a walk-in steals the last slot. If it sits in Oceanside, write Saturday. Book a free audit if you want that map before the unofficial Sheet becomes a second job. Keep AI implementation for San Diego small businesses open so week two does not invent a hallway agent.