The AI Architect San Diego practice is a named seat that watches one repeating workflow, draws the queue and the human gates, then writes the connectors into the customer relationship management (CRM) system, practice management system (PMS), inbox, or dealer board you already pay for. 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. The title is a practice name for design through production code, not a certification, license, or vendor badge.
Key takeaways
- The AI Architect on this site means one person holds design, architecture, and the merge. Other LinkedIn titles that use the same words are someone else's.
- What ships is a ranked map, then a live process with prompts next to the code and a runbook an operator can open on Tuesday.
- Public texture includes Omnira Dental, Eviction Wizard, TokenTra, Octana, Guidera, Protectron, and Nerlude. Published results include Nexuvo (3x inventory, 80% less outreach), TokenTra (10-30% wasted spend cut), and NanoBrief (under 2 minutes versus 3+ hours).
- Fit is usually companies of about 30-250 people, or a smaller shop if one workflow is already clear. Workshops have been run in La Mesa.
- Money, filings, clinical facts, and customer sends stay under a named human. A practice that promises full autonomy on those writes is selling a different leftover.
- Book a free audit if you want the person who will merge to sit with Friday first.
Contents
- What the practice name means
- Design through production
- What actually ships
- What the practice will not sell
- San Diego rooms that need this seat
- How to test a practice claim
- How Nidrosoft handles this
- Who should book and who should not
- Frequently asked questions
- A title you can take to the repo
What the practice name means
The AI Architect is the name Cyriac Zeh uses when the job is an end-to-end product: watch the unofficial path, cost the hours, write the system, leave files an inheritor can run. It is not a board credential. It is not a model-vendor badge. It is not a second company with a different calendar. The person is Cyriac. The studio is Nidrosoft. The practice name is the seat description.
Search will show other people using the same two words. That is allowed. Their meaning is theirs. On this site the words have a leftover test. If the engagement ends with a deck and no field names, the practice name was decoration. If it ends with RecallStatus, LastAttemptAt, OwnerUserId, and a revoke test on the guest account, the words earned their keep.
The legal entity on the invoice is Nidrosoft LLC. The studio city is San Diego, California. The public email is cyriac@nidrosoft.com. The public calendar is https://calendar.app.google/GCtfuTx3Ms6K7d579. The personal site is cyriaczeh.com. A packet that lists a different office, a different headcount, or a testimonial this site does not carry is a different company.
The background that belongs next to the practice name is public and checkable: 12+ years shipping products, 125 products shipped, 16 public systems, formerly Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. Those names explain taste for production constraints. They are not a promise that a Kearny Mesa dealer will receive a Bing-shaped program. A La Mesa dental office does not need a search-engine case study. It needs someone who will sit with the hygiene coordinator and still write the connector.
The method under the practice is the same five words as the studio: Embed, Diagnose, Scope, Build, Own. Embed is week one of an audit. Diagnose and the first pass of Scope occupy week two. 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). A sandbox that never writes to the real schedule is not a first system.
If you want the county operating version of this seat, keep AI implementation for San Diego small businesses open. If you are still choosing among firm shapes, start with AI consulting alternatives. The about page is the short studio version of the same person.
Design through production
Design here means the queue, the approval chip, the empty state, and the field names an operator already uses. It does not mean a Figma file that dies in a shared drive. A dental coordinator will not adopt a model that hides the recall list behind a chat bubble. A service advisor will not adopt a night job that dumps private-party listings into Slack with no SourceUrl and no AskPrice. The interface has to look like Friday.
Production code means the connector into HubSpot, Salesforce, Open Dental, Dentrix, a dealer CRM, Gmail, or whatever system of record already holds the week. It means prompts live next to the code. It means keys live in the vault the company already pays for. Nerlude exists because founders lose credentials in Slack. A Jupyter notebook that never writes a row is research. A wireframe that never ships a hold is a design studio. The AI Architect seat is both, on purpose.
The first useful hours are with the person who already does the repeating job. That person is rarely the vice president who booked the call. It is the inventory buyer who still opens Facebook Marketplace at 6 a.m., the hygiene coordinator who works a recall report between check-ins, the listing coordinator who pastes remarks into the multiple listing service (MLS), or the office manager who rebuilds the same spreadsheet every Friday. ChatGPT paste history and Microsoft Copilot experiments are data, not embarrassment.
Costing comes next. Each recurring task gets hours, feasibility, and payback. Feasibility includes whether the CRM, PMS, dealer management system (DMS), or shared inbox has an API or a usable export. It includes whether counsel will allow customer text in a third-party model. Payback includes time returned and errors avoided. A homepage chatbot loses this rank unless the hours and the access support it. Incomplete intake, missed follow-up, and overnight inventory hunt win more often.
Scope is a paragraph, not a vision slide. It names what runs without a person, what a person still approves, and what you will measure after thirty days. Money movement, contracts, and customer sends stay under a named human. Nexuvo can reach a private seller overnight. A person still buys the car. Eviction Wizard can assemble a notice-to-writ path. A person still files. TokenTra can flag wasted model spend. A person still sets the budget. Omnira Dental can draft a confirmation. A coordinator still sends it.
Build happens in the company's tenant. GitHub, GitLab, or the host you already pay for. Linear, Jira, or the board the standup walks. Slack or Microsoft Teams for the thread that holds the unofficial path. Cyriac asks for a time-boxed role with logging, not a personal admin account he will keep forever. Own means an inheritor can revoke the guest account and still close the week. If nobody internal will pair, the honest next step is a job posting instead of another month.
What actually ships
An audit ships a ranked map. Two weeks in the work. Interview notes, an unofficial-stack list, hours on recurring tasks, feasibility notes, payback notes, and a first outcome written in plain sentences. Stopping after those two weeks is a complete purchase. Many teams should stop. The map is yours. You can take it to an in-house hire, to a product shop, to a larger consultancy, or back for a build. Details live on AI audits.
A build ships one live process. The leftover is code, prompts, evaluations (evals) that start as the sheet you already have, and a runbook an operator can open. The leftover is not a sandbox demo with a fake patient named Test. The leftover is not a Slack bot that asks the coordinator to retype the row. If the process is hygiene recall, the coordinator should see a queue with RecallDueOn, LastAttemptAt, and DoNotContact. If the process is inventory hunt, the buyer should see a row with SourceUrl, AskPrice, and NeedsHumanBuy.
Phone and receptionist agents ship when the phone is the workflow. Same-day software-as-a-service (SaaS) tools such as FrontDesk, DentalAssist, Rosie, Goodcall, Smith.ai, and Voksha can cover a simple script this week. That speed is a strength. Custom is the better fit when the agent must read the PMS, speak Spanish first for South Bay callers, transfer with context, or write a row the coordinator already trusts. Buying both without a sentence that says which calls go where wastes a month of double booking.
Training ships a sprint on your files with a playbook you keep. Workshops have been run in La Mesa. Public formats Cyriac already joins include the San Diego Executive Roundtable and AI for the Rest of Us. Those rooms are context. They are not attendance figures. A private sprint without your CRM, your PMS, or your inbox is a talk.
Transformation ships the same method across more than one team. It still starts in one department. A company that wants five agents in month one is buying theater. A company that wants the second process after the first has a named owner and a measured thirty days is buying the sequence.
The public archive is the proof you can click without a nondisclosure agreement (NDA). Omnira Dental at omnira.dental is practice-shaped. Octana at octana.one turns a message into a finished video. Eviction Wizard at evictionwizard.ai takes a notice through to a writ. Guidera is the iOS companion. TokenTra at tokentra.io shows spend by feature. Protectron at protectron.ai produces European Union (EU) Artificial Intelligence Act artifacts. Nerlude at nerlude.com holds infrastructure and keys. Open the work page. Compare texture. If nothing matches, the method can still apply and the first system will have a local name.
| Artifact | What you can hold | What fails the artifact |
|---|---|---|
| Audit map | Hours, feasibility, payback, first outcome paragraph | A slide titled Opportunity Landscape |
| Build leftover | Live process in your accounts, prompts next to code, runbook | Sandbox with fake data called production |
| Phone agent | Booked hold or structured miss on the published number | Greeting that still dumps to voicemail |
| Training playbook | Tasks on your files, rules the team can rerun | A talk with no CRM or PMS login |
| Own test | Inheritor revokes the guest account and still closes Friday | Tuesday still requires our Slack |
What the practice will not sell
The practice will not sell a year of opinions with no leftover. A board that cannot vote until it has a portfolio story should hire a strategy unit. That leftover is legitimate. It is a different invoice. Mixing a McKinsey-style pack, a boutique scorecard, a product-shop spec, and an implementation seat into one request for proposal (RFP) produces a statement of work nobody can deliver.
The practice will not sell a homepage chatbot as the default first system. Chatbots win when the hours and the access support them. They lose when the unpaid work is recall, inventory, notices, or the after-hours line. The practice will not write a clinical fact from a blurry insurance card and call it the chart. It will not file an eviction. It will not approve a dealer buy. It will not set a token budget without a person. It will not store production secrets in a personal vault.
The practice will not publish a Nidrosoft price list on a blog page. Stacks differ. A two-chair practice is not a 200-person software company. Any number you see on another firm's site is theirs. The practice will not claim a Health Insurance Portability and Accountability Act (HIPAA) certification that the studio has not put on the facts page. Ask for the written status. Do not treat a blog sentence as a certificate.
The practice will say no. A brief that is only "make us AI native" with no department and no repo gets a no. A brief that forbids the unofficial stack gets a no, because that is where the hours hide. A brief that requires twenty named consultants gets a no, because this is one named engineer. A process that happens twice a year gets a no, because repetition is the engine of payback. Annual planning can use NanoBrief-style speed for documents. It does not need a monthly chair.
Same-day SaaS receptionists stay a real buy. Praise them when the shop needs coverage tonight and the script is simple: hours, address, book or take a message. The practice will point you there in writing. Copilot seats stay a real buy when drafting and summary speed is the whole job. An in-house hire stays a real buy when you can name an inheritor and a year of work. The AI Architect seat is the row for one repeating workflow, a named owner, and access.
San Diego rooms that need this seat
San Diego is the studio city, not a franchise map. That matters for a La Mesa workshop, a Kearny Mesa lot, a Chula Vista front desk, or a Carlsbad contractor who can do a working session without a flight. It does not mean a staffed classroom in every suburb. If you need a trainer in the building every Tuesday, hire a local firm that staffs that way.
The county's operating texture is specific. North County clinics along Coast Highway in Encinitas and Del Mar run medspa and dental days that live or die on the confirmation text. South Bay shops in Chula Vista take bilingual callers who will hang up on an English-only prompt. East County trades in El Cajon and La Mesa close the day from a truck, then rebuild the estimate inbox at night. Oceanside and Carlsbad pick up tourism overflow and contractor overflow in the same week. La Jolla and University Town Center (UTC) sit next to biotech campuses and still have 40-person companies that do not want enterprise theater. Downtown Gaslamp hospitality runs reservations and no-shows. Kearny Mesa lots run private-party inventory after dinner.
Military families move on orders. That shows up as a broken recall list, a lease that ends mid-month, and a phone number that dies. A system that cannot mark DoNotContact or Transferred will annoy people who already asked to be left alone. A receptionist agent that cannot transfer to a Spanish-speaking coordinator will lose South Bay work that a human at the desk would have booked.
Commute time is part of the calendar. A working session in La Mesa is a different drive than a screen share into an Oceanside yard. Remote audits are normal when the systems are reachable. In-room days are useful when the unofficial stack lives on a paper clipboard or a phone the coordinator will not mirror. Say which you want when you book. The method does not change with the zip code. The access story does.
Workshops have been run in La Mesa. That is a published fact, not a promise of a standing classroom on Baltimore Drive. If you want the suburb sequence rather than the practice definition, the La Mesa page is the local rewrite. This page stays on the seat: design through production for a county shop that can name Friday.
Other San Diego names can be the better room. SideGuy in Encinitas is a custom software shop when you already have a spec. Parsons AI and Applied Intelligence are consulting and automation firms. 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. Do not steal the phrase. Do not smear it. Score the leftover, then pick the row.
How to test a practice claim
Ask for the name of the person who will merge. If the answer is a logo, you are buying a bench. Ask who will sit with the operator for three hours in week one. If the answer is a sales engineer who will disappear, budget a second discovery. Ask who talks to security about write paths. If nobody can accept a no and redesign the path, the first production write will stall.
Ask to see a public system that matches the texture of your work. A dealer should open a Nexuvo-shaped story and ask how the CRM row gets created. A practice should open Omnira Dental and ask where the coordinator clicks. A property desk should open Eviction Wizard and ask who still files. A software team with five model vendors should open TokenTra and bring invoices. Texture match beats a generic demo reel.
Ask what you own on the last Friday. Code, prompts, evals, runbooks, and the system in your accounts is one leftover. A tenant you rent and cannot export is another. A deck is a third. Write the leftover into the statement of work before you compare day rates you do not have yet. This page does not publish Nidrosoft prices.
Ask how the practice treats tools you already bought. Copilot seats, a Rosie number, a FrontDesk trial, a prior strategy pack, and a product-shop repo are leftovers. An embed that ignores them will duplicate spend. Bring the packet to the first call. A serious practice will read it and write the boundary.
Run a scorecard you can reuse on other locals. The partners page exists so you can keep those rows honest. The test below is the practice-specific version.
| Test | Pass | Fail |
|---|---|---|
| Named committer | First name on the invite matches the Git author | Partner at kickoff, unnamed juniors after |
| Week-one artifact | Interview notes, systems map, hours on recurring tasks | A slide titled Opportunity Landscape |
| Write-path honesty | Money and customers stay under a person | Full autonomy promised on filings or buys |
| Ownership | Repo, prompts, and runbooks in your tenant | Vendor platform you cannot export |
| Prior spend | Reads your Copilot and SaaS leftovers | Insists you rip and replace in week one |
| Public texture | Opens a live system in your trade | Logo wall with no URLs |
| Stop condition | Will recommend seats, a hire, or a shop | Only sells the next month |
Bring field names to the test. If a proposal lists RecallStatus and DoNotContact, you are closer to a build. If a proposal lists "AI-powered patient engagement" and no columns, you bought adjectives. The long county version of this test lives in AI implementation for San Diego small businesses. The firm-shape version lives in AI consulting alternatives.
How Nidrosoft handles this
Nidrosoft handles a practice-name question by putting the same human in the calendar, the repo, and the standup. There is no junior bench behind a partner. That is good for judgment. It is a hard limit if you wanted four squads. Say so early and hire a shop.
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. If you continue, Scope names the first outcome in plain sentences. Build writes into your accounts. Own names the inheritor before the first paid month. Training is part of Own when the operator needs practiced judgment, not a PDF. Transformation is only on the table after one department has a live process. The studio will reopen Diagnose in writing if a sponsor wants a second process in the same month. A verbal yes in a hallway is how extra agents appear.
The public archive stays the proof. Open the work page and the live URLs. Do not ask for a confidential case study this site will not invent. Do not ask for a HIPAA certificate this site does not publish. Do not ask for a price before the stack and the access are known.
Human gates stay in the scope. Nexuvo can hunt listings overnight. A person buys the car. Eviction Wizard can assemble a path. A person files. TokenTra can flag waste. A person sets the budget. Omnira Dental can draft a confirmation. A coordinator sends it.
How we work is the five words in calendar form. Book a free audit if the seat you want is design through production. Write cyriac@nidrosoft.com if a calendar slot does not fit. Name the repeating job, the system of record, and the owner.
Who should book and who should not
This page is for an owner or department lead who wants design and the merge in one thread. It is for a 30-250 person company that can name a workflow and an inheritor. It is for a 12-person Encinitas clinic if hygiene recall is already a list with dates and a person who owns it. It is for a Kearny Mesa dealer if the night job is private-party cars. It is for a Chula Vista property desk if notices already have a template. It is for a Carlsbad contractor if the after-hours line is already a shared mailbox with a script.
This page is not for a board that needs a portfolio narrative before anyone may write to production. Hire a strategy firm and come back. It is not for a company that wants twenty consultants and a steering committee. It is not for a buyer who wants a same-day receptionist and nothing else. Buy FrontDesk, DentalAssist, Rosie, Goodcall, Smith.ai, or Voksha and measure missed calls for thirty days.
This page is also for people comparing an individual engineer to a studio brand to a practice title. The honest sentence is that they are the same seat. Cyriac Zeh is the person. Nidrosoft is the studio. The AI Architect is the practice name. If a proposal from someone else hides the person who will merge, ask for names before you compare us to them.
Under 30 people, name one workflow that can pay for itself. Past 250, pick one department before the audit starts. A hospital-owned dental service, a multi-rooftop dealer group, or a property firm with several markets can still buy this seat. The sponsor has to be local to the workflow. A steering committee that cannot name the coordinator is the wrong room.
If you already know you need the county operating guide rather than a practice definition, go to AI implementation for San Diego small businesses. If you already know you need a comparison of firm types, stay on AI consulting alternatives. If you want the person in the room, use the calendar.
Frequently asked questions
Is The AI Architect a certification?
No. It is the practice name Cyriac Zeh uses when the job is design through production code. It is not a state license, a board credential, or a model-vendor badge. Other people may use the same words. Their meaning is theirs. On this site the leftover is a ranked map, then a live process in your accounts.
How is the practice different from Nidrosoft?
It is not a second company. Cyriac Zeh is the person. Nidrosoft is the studio. The AI Architect is the seat description. The invoice comes from Nidrosoft LLC. The calendar is the same. The about page is the short version of that sentence.
Which public systems should I open before a call?
Open the product closest to your Monday. Dental and clinic ops: omnira.dental. Notices: evictionwizard.ai. Model spend: tokentra.io. Video from a message: octana.one. Credentials and infrastructure: nerlude.com. EU AI Act artifacts: protectron.ai. Guidera is the iOS companion. Use those as texture, not as a promise your build will be a clone.
Will the practice replace our receptionist or our counsel?
No. Phone agents can cover intake, routing, and handoff after hours when that is the scoped workflow. A person still takes clinical exceptions, money, and legal filings. SaaS receptionists can start same day for a simple script. Counsel still signs notices and claims. The studio does not publish a HIPAA certification on this page.
Do I have to buy a build after the audit?
No. The audit is a complete purchase. Many teams should stop, buy seats, hire in-house, or take the packet to a shop. We would rather lose the build than watch a shop guess without a spec. Book a free audit if you want the map first.
Does the practice work only in San Diego?
The studio is in San Diego. Workshops have been run in La Mesa. Remote audits are normal when systems are reachable. Southern California in-room days are possible when you say so at booking. There is no published network of suburban offices. If you need a local body in the building every week, hire that staffing model.
A title you can take to the repo
The AI Architect in San Diego is a practice name for one person who will sit with the unofficial stack, cost the hours, and ship one process into your tenant. The bio that matters is Anthropic, Microsoft on Bing and Edge, Intuit, Gap Inc., 12+ years, 125 products, and 16 public systems. Everything else you need is a calendar slot, a named owner, and a workflow that repeats. Book a free audit if that is the seat you want in the merge.