AI consulting that ends in a system you can run

Type AI consulting into a search box and you will get strategy units, boutique diagnosticians, offshore benches, seat resellers, and a few studios that actually write connectors. They all use the same noun. They leave different files. Nidrosoft is the last shape: Embed, Diagnose, Scope, Build, Own. We will still use the word consulting on this URL because that is what buyers type. We will not let the word erase the leftover.

The leftover we sell is a ranked map and, if you continue, a process running in your accounts with prompts and runbooks your people can edit. The leftover a strategy firm sells is a pack the board can vote on. The leftover a boutique sells is a scorecard. The leftover a shop sells is an application against a spec. The leftover a seat vendor sells is a tenant. Mixing those leftovers in one RFP produces a statement of work that cannot be delivered.

Cyriac Zeh founded Nidrosoft LLC in San Diego 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. Consulting here is not a junior bench behind a partner who flies in for the kickoff. It is also not a factory. If you need a factory, read the alternatives page and hire a shop.

Public work keeps the claim specific. Omnira Dental is live for practices. Octana turns a message into a finished video. Eviction Wizard takes a notice through to a writ. Guidera is an iOS companion. TokenTra shows spend by feature so teams can cut 10 to 30 percent of wasted tokens. Protectron produces EU AI Act artifacts. Nerlude holds infrastructure and keys. Nexuvo dealers acquire 3x more inventory with 80 percent less manual outreach. NanoBrief writes a brief in under two minutes instead of three or more hours. Clear Audio AI and MixGuidera work on sound. Consulting that cannot point at a system is a conversation.

AI audits are two weeks in the work. We cost recurring tasks and leave a ranked roadmap of systems, workflows, data, and risks. AI builds take a scoped outcome and put it in your stack. Corporate AI training is a sprint on your tools with a playbook you keep. AI transformation funds the sequence across more than one team, still starting in one department. Consulting is the umbrella search. Those four are the line items.

A first conversation often sounds like consulting and ends as an audit. That is the right collapse. You cannot staff a six-month consulting program if nobody has watched Friday. You also cannot honestly price a build from a vision slide. The calendar books time. The map decides the rest.

Some buyers want a sounding board with no path to a write. We can do a short advisory block after an audit if the map says seats and patience. We will not sell a year of opinions as consulting. Opinions without a leftover are how retainers rot.

Renting an AI engineer is a related seat: a senior person in your standups. It is still scoped from a map. It is not a published consulting rate. If a page you read elsewhere lists euros per month for a different firm, that number is theirs. Ours waits for your stack.

• Audit: map and recommended next buy
• Build: live process, code, prompts, runbooks
• Training: playbook and practiced judgment
• Transformation: the sequence, team by team
• Engineer seat: embed after the outcome is named

Embed means we sit with the people who do the job. We watch the unofficial path. We do not accept a polished SOP as the whole truth. Diagnose means hours, feasibility, and payback. Scope means you buy a result: what runs, what a person approves, what you measure. Build means the system goes live in your accounts while someone in-house learns it. Own means the files stay with you and Tuesday does not require our Slack.

How-we-work gives a common calendar: audit in weeks one and two, plan after that, implement in a later stretch often listed as weeks five through ten for the first system. Consulting engagements that skip Diagnose produce pretty agents that miss the hours. Engagements that skip Own produce a contractor you cannot fire.

Human approval on money, contracts, and customers is part of Scope. Nexuvo can hunt listings overnight. A person still buys the car. Eviction Wizard can assemble a path. A person still files. TokenTra can flag waste. A person still sets the budget. Consulting that sells full autonomy on those actions is selling a story we will not sign.

Infrastructure follows your constraints. Azure, AWS, Google Cloud, Cloudflare, private infrastructure, EU hosting and residency when required, approved access, audit trails. San Diego is the studio city. It is not a requirement that your data live in California.

The usual fit is 30 to 250 people, a named owner, and a workflow that repeats. Under 30, one later build must pay for itself and the founder should be in the audit. Past 250, one department goes first with an internal sponsor. Software teams, clinics, dealers, funds, landlords, factories, and retailers all appear. The industry pages exist so those searches have a home. The method does not change.

Decision makers who cannot grant any environment should buy training or seats first. Consulting that pretends to implement without a write path becomes a series of workshops with a consulting invoice. We will redirect you rather than take that invoice.

If your buyer is a board that asked for a famous strategy logo, hire that logo. We can sit later in one department when the pack names a process. If your buyer is a product lead with screens already drawn, hire a shop. If your buyer is an IT admin rolling Copilot, buy Copilot.

Remote work is default. On-site days are available, including San Diego, La Mesa, and the rest of Southern California. We do not invent a consulting office in your city to win a search. The regions pages say the same thing for teams outside the United States.

After an audit you own the packet. After a build you own the running system, the code you accepted, the prompts, the eval notes, and the operator runbook. After training you own the playbook. After transformation you own an index of processes, operators, and measures. You do not own Nidrosoft products unless you license them. You can take every leftover to another firm.

Compare that to a consulting pack you cannot execute, or a portal you must keep paying to read. We put files in your drive and systems in your tenant. Nerlude is a public reminder that credentials and renewals need a home. Your consulting leftover should have a home too.

Ownership includes the right to stop. A map that says buy seats is a complete consulting engagement. A build that you pause after the first outcome is complete. We will not redefine stop as failure to keep a retainer alive.

• Ranked map from Diagnose
• Code and prompts from Build
• Playbook from Training
• Index from Transformation
• Keys in your vault
• Human names on approvals

A strategy consultancy wins when the board needs governance language, org design, and a multi-year narrative before anyone may write to production. That is AI consulting in their catalog. It is a different leftover. Hire them for the pack.

A boutique AI consultancy wins when you want a vendor bake-off and your engineers will build. Hire them for the scorecard. A product shop wins when the application is specified and you need a bench. Hire them for the repo. ChatGPT or Copilot wins when the job is drafting. Buy the seats.

A legal firm wins when you need an opinion. Protectron can help a team produce artifacts. It is not counsel. A compliance consulting arm that only writes paper may still be the right first hire if no software should exist yet.

Price is missing because it would be fiction. Strategy projects are large. Boutiques bill days. Shops bill sprints. Seats have list prices that change. Nidrosoft scopes after an audit. If you need a number for a budget committee this week, book the calendar and say the date. We will not invent euros to look complete.

The compare guides go deeper on alternatives, on who sits in the room, and on workshops versus implementation. Use those URLs when the search is more specific. This page is for the generic consulting query.

We will not take a brief that is only “make us AI native” with no department. We will not take a brief that forbids looking at the unofficial stack. We will not take a brief that requires twenty named consultants. We will not take a brief that wants a confidential logo wall. We will not take a brief whose only metric is a press release.

We will not take a process that happens once a year and call it automation. We will not take a legal opinion. We will not take a greenfield consumer social app that needs a shop. We will not take a company that already promised a board a chatbot and wants us to retroactively bless it without an audit.

We will take a messy intake queue, a dealer night shift, a notice file, a token invoice, a brief that takes three hours, a renewal calendar, a mix that needs notes. Those are consulting problems because they are operations problems. They match the public archive.

Omnira Dental, Octana, Eviction Wizard, Guidera, TokenTra, Protectron, Nerlude, Nexuvo, NanoBrief, Clear Audio AI, MixGuidera. Those names are on this site for a reason. Consulting claims that cannot survive a click are decoration. Click them. See whether the texture matches the work you want done.

Numbers we can repeat: Nexuvo’s 3x inventory and 80 percent less manual outreach. TokenTra’s 10 to 30 percent wasted spend. NanoBrief’s under two minutes versus three-plus hours. One hundred twenty-five products shipped. Twelve-plus years of making software. We will not add a consulting-specific ROI invented for this paragraph.

The AI Architect is the practice name. Nidrosoft is the studio. Cyriac Zeh is the person. If a proposal you received from someone else hides the person, ask for names before you compare us to them.

Week one, we watch. Week two, we rank. You receive a packet. Some companies stop and run seats for a quarter. Some book training so leaders share a language. Some scope a build. Some take the packet to a shop. All of those are valid uses of consulting time.

If you already have a strategy pack, we read it and mark the pages that are processes. If you already have Copilot, we read the useful and failed chats. If you already have a shop, we ask who owns prompts. Consulting that ignores prior spend will duplicate it.

If the first month reveals that you needed a workshop more than a consultant, we will say so. The implementation versus workshops page exists for that fork. If it reveals that you needed a partner comparison, use the partners page. Keep the searches separate so the next vendor cannot mash them.

Use the public calendar or cyriac@nidrosoft.com. Name the department, the tool, the weekly pain, and the owner. Say if you think you need consulting, training, or a build. We will answer with a recommended first service or with a no.

Cyriac Zeh is in San Diego. The work ships wherever the systems run. We will travel when the floor requires it. We will not invent an office to look global.

Scope sets commercial terms after we understand access and volume. That is why this explore page, like the service pages, refuses a fake price. A 40-person clinic and a 200-person software company are not the same consulting object.

If you were compared against three other consulting firms already, send their leftovers, not their logos. We will say which leftover we also sell and which leftover we will lose. A bake-off that scores all four firms on the same twenty rows is how a strategy pack and a CRM connector get averaged into mush.

Bring the unofficial path. The export. The night someone retypes a listing. The personal inbox rules. Consulting that only sees the official SOP will recommend a chatbot on the homepage because that is what official SOPs mention. The hours are usually elsewhere. Nexuvo, Eviction Wizard, and NanoBrief exist because those hours were concrete enough to ship.

If you only have budget for seats, say that in the first note. We will not stretch a consulting invoice over a license problem. Buy ChatGPT or Copilot. Add a short room if people need practice. Come back when a process repeats behind a login. That sequence is consulting advice. It does not require a six-month program.

If you already hired a shop for a specified app, keep them. Ask us only about the operations path the spec ignored. Two partners with a written boundary beat one mashed consulting SOW. Write the boundary before the first standup so the shop and the studio do not rebuild the same queue.