An AI implementation partner San Diego shop should spend week one with the people who already close Friday, not with a kickoff deck. The partner watches the unofficial path, lists the systems those jobs touch, and costs the hours. 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 production write in the first morning is a software-as-a-service (SaaS) signup, which you can buy without a partner.
Key takeaways
- Week one is Embed: interview notes, unofficial-stack list, paste history, and a named owner of the system of record. It is not a live agent.
- The partner who will merge should be in the room or on the link. A sales engineer who disappears fails the partner test.
- Fit is usually 30-250 people, or a smaller shop if one workflow is already clear. Workshops have been run in La Mesa.
- Bring leftovers: Copilot usage, a Rosie or FrontDesk trial, a prior deck, model invoices if spend is the story.
- Public texture you can compare includes Omnira Dental, Eviction Wizard, TokenTra, and published results on Nexuvo, TokenTra, and NanoBrief.
- Book a free audit if you want week one to produce a map you can stop after.
Contents
- What week one is for
- Who sits in the working sessions
- The unofficial stack
- Access, counsel, and leftovers
- A day-by-day shape you can copy
- What week one is not
- How Nidrosoft handles this
- County rooms in week one
- Frequently asked questions
- Leave week one with notes, not a demo
What week one is for
Week one of a serious partnership is Embed. The partner sits with the people who do the repeating jobs. Intake, outreach, scheduling, reconciliation, notice prep, inventory hunt, ticket grooming, after-hours capture. The official standard operating procedure (SOP) is useful and incomplete. The unofficial path is usually where the hours are. If leadership only allows the SOP tour, the partner should say the week is unfinished rather than invent hours.
The artifacts you can hold on Friday of week one are interview notes, a list of systems and side systems, ChatGPT or Microsoft Copilot paste history, a first pass at who owns each system of record, and a calendar for week two. You do not hold a live receptionist. You do not hold a production write. Anyone who promises those in the first morning is selling a product dashboard, not a partnership.
Week two is Diagnose and the first pass of Scope: hours, feasibility, payback, and an outcome paragraph. A common calendar after the map is plan in the following window, then implement and train in a later stretch often listed as weeks five through ten for the first system. Dates move with access and vendor application programming interfaces (APIs). Week one exists so those later weeks do not guess.
The county operating guide for the full sequence is AI implementation for San Diego small businesses. The leftover table across firm types is AI consulting alternatives. This page stays on the first five working days.
Who sits in the working sessions
The partner who will merge should attend. If the first name on the invite does not match the Git author you will see later, you hired a logo. A sales engineer can join for logistics. They should not be the only person who hears the unofficial path.
The operator who already does the job should attend. That person is rarely the vice president who booked the call. It is the hygiene coordinator who works a recall report between check-ins, the inventory buyer who still opens Facebook Marketplace at 6 a.m., the listing coordinator who pastes remarks into the multiple listing service (MLS), or the office manager who rebuilds the same spreadsheet every Friday. If that person is "too busy," week one will lie.
The system-of-record owner should attend at least once. Someone must be able to request a time-boxed role with logging in the customer relationship management (CRM) system, practice management system (PMS), dealer board, inbox, or phone vendor. Security can join that session. Counsel can join the session that names what text may leave the building. Those people do not need every interview. They need the session that would otherwise stall week two.
The inheritor should be named even if they only listen. Own fails on the last Friday if nobody internal will pair. If you cannot name the inheritor in week one, the honest next step may be a job posting, seats, or a stop after the map. Write that down. Do not wait until week eight to discover it.
Fit still matters. About 30-250 people is the usual room. Under 30, one later build must be able to pay for itself. Past 250, pick one department before week one starts. A steering committee that cannot name the coordinator is the wrong room.
The unofficial stack
The unofficial stack is the Sheet named "recall this week," the group text for the wait list, the Facebook Marketplace tabs the buyer will not close, the voicemail box nobody returns before the next El Cajon contractor picks up, the clipboard in the truck, the Copilot chats that already hold customer text. Week one treats those objects as data.
Ask the operator to share screen on a real Monday, not on a sanitized demo. Watch the broken field. Watch the double entry. Watch the moment they leave the official system to finish the job. Write the field names they already use. RecallDueOn. LastAttemptAt. SourceUrl. AskPrice. JobType. Zip. LanguagePref. DoNotContact. A partner who leaves week one with "patient engagement" and no columns failed Embed.
ChatGPT paste history is not embarrassment. It is a prototype. If the coordinator already pastes a recall list into a prompt every Thursday, Diagnose can cost those hours in week two. If the buyer already asks a model to rewrite listing remarks, the MLS path is already in scope. Forbidding that evidence is how partners ship a chatbot nobody wanted.
Side systems are often the hours. Insurance eligibility may sit in a second login the biller already pays for. Confirmations may sit in a text vendor. The PMS or CRM is still the record. A partner who offers to replace Open Dental, Dentrix, HubSpot, or the dealer CRM in week one is selling a conversion, not an embed.
Access, counsel, and leftovers
Access in week one is a list, not a write. Name the systems. Name the owners. Name the role you will request in week two or in the plan window. Cyriac asks for a time-boxed role with logging, not a personal admin account he will keep forever. If security cannot issue that role later, Diagnose must mark feasibility as blocked. Pretending otherwise is how week six stalls.
Counsel in week one is a sentence. What text may leave the building. What recording disclosure the phone line needs. What Telephone Consumer Protection Act (TCPA) rule applies to missed-call texts. This page is not legal advice. California is a two-party consent state for recording. A vendor checkbox is not an opinion. If counsel has not spoken, write "blocked pending counsel" rather than invent a path.
Leftovers in week one are the tools you already pay for. Copilot seats. ChatGPT Enterprise. A Rosie, FrontDesk, Goodcall, Smith.ai, DentalAssist, or Voksha trial. A prior strategy pack. A product-shop repo. Model invoices if "we already use AI" is part of the brief. TokenTra at tokentra.io is the public product for spend by feature. You do not have to buy it. The partner should look at invoices if spend is the story. An embed that ignores leftovers will duplicate spend.
Write the boundary in the same notes. Which calls the SaaS receptionist already owns. Which screens the product shop already shipped. Which recommendations the deck already made. Unwritten boundaries become duplicate invoices.
| Week-one object | You should leave with | Fail |
|---|---|---|
| Operator interviews | Names, unofficial path, field names | SOP-only tour |
| Systems list | CRM, PMS, inbox, phone, Sheets, group texts | "We'll figure out the stack later" |
| Access list | Owner, requested role, expiry plan | Personal admin forever |
| Counsel line | Allowed text, or "blocked pending counsel" | Guessing a HIPAA certificate |
| Leftovers | Copilot, SaaS, deck, repo, invoices | Rip-and-replace speech |
| Inheritor | First name | "The team will own it" |
A day-by-day shape you can copy
Copy this shape. Move days when access slips. Do not skip the operator.
-
Day one, kickoff in writing. Confirm the repeating job, the system of record, and the owner. Confirm who merges. Confirm remote versus a room in San Diego, La Mesa, or elsewhere in Southern California. Confirm that unofficial workarounds are in scope. No production write.
-
Day one or two, operator session one. Ninety minutes with the person who does the job. Screen share. Watch ten real tasks if you can. Write field names. Write the unofficial path. Ask what ChatGPT or Copilot already ate.
-
Day two, systems walk. PMS, CRM, inbox, dealer board, phone vendor, text vendor. Who owns each login. What exports exist. What APIs exist. What is a clipboard.
-
Day three, leftovers and counsel. Bring the deck, the SaaS trial, the invoices. Write the boundary. Get the sentence on text leaving the building, or write the block.
-
Day three or four, second operator or adjacent role. The biller, the on-call technician, the bilingual coordinator, the service advisor. Adjacent roles hide transfer graphs and
DoNotContactrules. -
Day four, sponsor readout of notes, not recommendations. Read back what you saw. Let them correct the unofficial path. Do not rank yet. Ranking is week two.
-
Day five, week-two calendar and access requests. Submit the time-boxed role request. Book Diagnose sessions. Name the inheritor again. Send the notes packet the company can keep if they fire the partner on Friday.
That last line is the partner test. If the notes are only useful inside the vendor's tenant, week one failed Own in advance.
| Week-one artifact | Audit week one | Build week one (map already exists) | Fail version |
|---|---|---|---|
| Access log | Time-boxed role, logging on | Same, plus deploy path | Personal admin, standing key |
| People list | Operator, system owner, inheritor, sponsor | Same, inheritor on the pull request | Directors only |
| Floor notes | Unofficial path, skip reasons, paste history | Delta if the floor changed | SOP reprint |
| Systems map draft | Official plus unofficial, field names | Confirmed write path | Logo diagram |
| Leftovers list | Seats, SaaS, decks, invoices | Boundary written | "We will replace everything" |
| Risk notes | Data that cannot move, missing counsel sentence | Gates copied into the ticket | "The model handles it" |
| Open questions | API, vendor, access gaps | Blockers that slip the calendar | Hidden until month two |
| Outcome paragraph | First pass at the end of week two, not day one | Ticket description | "Add AI" |
| Fallback note | Usually later | Same week as happy path | Hope |
| Revoke plan | Date on the calendar | Guest expiry set | Forever access |
| Production send | None | Only if Scope already said so | Patient text on Tuesday |
What week one is not
Week one is not a SaaS signup. FrontDesk, DentalAssist, Rosie, Goodcall, Smith.ai, and Voksha can start the same day. Praise that speed. If coverage tonight is the constraint, buy the product and measure missed calls for thirty days. A partner can still run week one on the leftover. They should not pretend the dashboard is their embed.
Week one is not a 40-slide opportunity landscape. If the partner needs a week to produce adjectives, you bought a deck. AI consulting alternatives exists so you can keep that leftover on a different invoice.
Week one is not a HIPAA certificate. The studio does not publish a Health Insurance Portability and Accountability Act certification on this page. Ask for the written status. Do not treat a kickoff sentence as a certificate.
Week one is not a price list. Stacks differ. A two-chair practice is not a 200-person software company. Any number on another firm's site is theirs.
Week one is not five agents. A company that wants five agents in month one is buying theater. Transformation starts after one department has a live process and a measured thirty days.
Week one is not a confidential case study. Open public URLs. Omnira Dental at omnira.dental. Eviction Wizard at evictionwizard.ai. TokenTra at tokentra.io. Octana at octana.one. Protectron at protectron.ai. Nerlude at nerlude.com. Guidera on iOS. Nexuvo dealers acquire 3x more inventory with 80% less manual outreach. TokenTra teams cut 10-30% of wasted spend. NanoBrief briefs in under 2 minutes versus 3+ hours. Those are texture. They are not a promise your first system will be a clone. We will not invent a San Diego client logo to fill the gap.
How Nidrosoft handles this
Nidrosoft handles week one by putting Cyriac Zeh in the sessions. Formerly Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. 12+ years, 125 products shipped, 16 public. There is no junior bench behind a partner. That is good for judgment. It is a hard limit if you wanted four squads.
The commercial start is an audit. Week one is Embed. Week two is Diagnose and the first pass of Scope. You can stop after the packet. Many teams should. Details live on AI audits. How we work is the five words in calendar form.
We will not take a week one that forbids the unofficial stack. We will not take a week one that is only a board conversation with no operator. We will not take a brief that is only "make us AI native" with no department and no repo. We will not promise a receptionist on morning one of the audit.
Human gates stay in the notes even before Scope is finished. Money, filings, clinical facts, and customer sends stay under a named human. Nexuvo can hunt. A person buys. Eviction Wizard can assemble. A person files. TokenTra can flag. A person sets the budget. Omnira Dental can draft. A coordinator sends.
Book a free audit if you want this week-one shape. Write cyriac@nidrosoft.com if a calendar slot does not fit. The about page is the person. The work page is the archive.
County rooms in week one
San Diego is the studio city. A working session in La Mesa is a different drive than a screen share into an Oceanside yard. Remote is normal when systems are reachable. In-room days help when the unofficial stack is a clipboard or a phone the coordinator will not mirror. Say which you want when you book. Workshops have been run in La Mesa. That is a training fact. Week one of a partnership can still be a link.
North County clinics along Coast Highway in Encinitas and Del Mar should put the coordinator who sends confirmation texts in the first session. South Bay shops in Chula Vista should put the bilingual person who already takes "buenas tardes" calls in the first session. East County trades in El Cajon and La Mesa should put the person who rebuilds the estimate inbox at night in the first session. Kearny Mesa lots should put the buyer who still opens classifieds after dinner in the first session. Carlsbad and Oceanside contractors should put the person who works the Friday surge in the first session. La Jolla and University Town Center (UTC) companies should put the department owner, not the campus tour, in the first session. Downtown Gaslamp hospitality should put the person who fights no-shows in the first session.
Military families move on orders. Week one should ask how DoNotContact and Transferred get marked today. If the answer is "we remember," write that as a risk.
Other locals can run a better week one for a given leftover. SideGuy in Encinitas can start on a spec you already wrote. Parsons AI and Applied Intelligence publish consulting and automation. San Diego AI under James Schlauch is educator and consultant shaped. AI Upside Group is consulting shaped. Christian Johnston's "Your AI Guy" brand is his. If their week one matches the leftover you want, hire them. The partners page keeps those rows honest.
Frequently asked questions
Will we have a live system at the end of week one?
No. Week one produces notes, a systems list, an access list, and a week-two calendar. A live number this week is a SaaS signup. Buy FrontDesk, DentalAssist, Rosie, Goodcall, Smith.ai, or Voksha if coverage tonight is the constraint.
Who has to be in the sessions?
The person who will merge, the operator who does the job, and at least one meeting with the system-of-record owner. Counsel and security join the sessions that would otherwise stall access. The inheritor should be named even if they only listen.
What should we pack?
The repeating job, the system of record, the owner, leftovers, and field names if you have them. Last-30-day missed-call or inbox counts help if you already keep them. Do not invent a number. The packing-list essay on this site is the free-audit page.
Can we stop after week one?
You can stop after the two-week audit. Week one alone is incomplete Diagnose. If you must stop on Friday of week one, keep the notes. They are yours. A serious partner will not hide them in a tenant you cannot export.
Do you publish a price for week one?
No. Prices wait for stack and access. Any number on another firm's site is theirs. Book a free audit or write cyriac@nidrosoft.com.
Will you come to our office in week one?
The studio is in San Diego. In-room days in Southern California are possible when you say so at booking. Remote is normal. There is no published network of suburban offices. If you need a body in the building every Tuesday, hire that staffing model.
Leave week one with notes, not a demo
An implementation partner in San Diego earns week one by watching Friday, writing field names, and leaving a packet you could take to someone else. The production write comes after Diagnose and Scope. If you want that order, Book a free audit and bring the unofficial stack on day one.