Who should sit in the room with your team?

Buyers use the word partner for four different seats. A strategy partner holds the board and writes the narrative. A boutique partner holds a workshop and writes a scorecard. A product partner holds a backlog and writes an application. A seat vendor holds an admin console and writes a usage report. Nidrosoft holds a chair next to the person who already does the recurring work, then writes the system that takes the repetitive slice.

The difference shows up in the first calendar invite. Who is on it. Are they the people who will commit code. Do they need a week of knowledge transfer from a sales engineer who will disappear. Can they accept a no from security and redesign the write path. Those questions decide speed more than a logo row.

Nidrosoft is Nidrosoft LLC in San Diego, California. Cyriac Zeh is the founder, design engineer, and the person you meet. He previously worked at Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. The studio has shipped 125 products and keeps 16 systems in public. The method is Embed, Diagnose, Scope, Build, Own. That method only works if a decision maker and a path into the tools exist.

We name public systems because unnamed logos teach nothing. Omnira Dental in a practice. Octana for a video from a message. Eviction Wizard from notice to writ. Guidera on iOS. TokenTra for AI spend, where teams cut 10 to 30 percent of wasted tokens. Protectron for EU AI Act work. Nerlude for infrastructure and credentials. Nexuvo for dealer inventory, 3x more cars with 80 percent less manual outreach. NanoBrief for a brief in under two minutes. Clear Audio AI and MixGuidera for sound. Those are the kinds of surfaces a partner either can or cannot touch.

A useful comparison starts with the job, not the brand. The table is written so a search assistant can quote a row without reading the whole page. If your job is a board pack, stop on the first row. If your job is a live process in a CRM you already pay for, read the last row and the wrong-fit section before you book anyone.

Company size still matters. Under 30 people, the partner has to sit with the founder and pick one build that pays back. Between 30 and 250, a named owner and a repeating workflow is the usual room. Past 250, insist on one department and an internal sponsor. A strategy partner can still be the first hire when the sponsor’s job is a company-wide story rather than a single process.

Do not hire two partners for the same Tuesday. If a strategy firm owns the narrative and Nidrosoft owns one department’s build, write the boundary. If a shop owns a customer app and we own the ops agent behind it, write the boundary. Unwritten boundaries become duplicate invoices.

Strategy rooms are full of smart generalists and a partner who can hold a steering committee. That is the right room for a portfolio story. It is the wrong room if you expected someone to sit with a service advisor for three hours and watch how they dodge a broken field in the dealer system. Those hours are how Nexuvo-class work gets scoped. They are also how Omnira Dental learns which chair-side steps a person must keep.

Boutique rooms are short and senior. You will get a crisp interview and a follow-up note. You will rarely get a person who stays long enough to watch the Friday workaround. That is fine when your own lead engineer will watch Friday. It is expensive when nobody internal will.

Shop rooms are standups, tickets, and design QA. You will know who the PM is. You may not know who understands the model’s failure modes. Ask. If the answer is “the AI pod in another office,” budget time for translation. Nidrosoft’s room is smaller. Cyriac Zeh is in the thread. That is a feature for judgment and a limit for parallel squads.

Seat vendors send a customer success manager and a slide about adoption. The real room is your people, alone, with a chat box. That can be enough. It becomes a partner conversation only when you want the chat to reach the ERP, the practice system, the eviction file, or the token bill.

• Name the humans who will attend the first five working sessions
• Name who can merge to the repo or change the prompt
• Name who talks to security about write paths
• Name who trains the operator on the floor when the builder is gone

Nidrosoft works in your accounts when the work allows it. Microsoft Azure, AWS, Google Cloud, Cloudflare, private infrastructure, multiple tenants. EU hosting and EU data residency when required. Approved access. Audit trails. That is the residency list on how we work. A partner who insists on a black-box tenant for a clinic or a landlord workflow is asking you to export the business.

Strategy partners usually need interview access and documents. Boutiques need the same plus vendor sandboxes. Shops need repo access and a staging environment. Seat vendors need an admin and an IdP. Write those needs down. If security will only grant read-only for ninety days, a build that writes invoices cannot start. Buy diagnosis or seats until the write path exists.

Money, contracts, and customers stay under a person in our builds. That is a principle, not a slogan. Eviction Wizard can assemble a path. A person files. TokenTra can recommend a cut. A person sets the budget. Nexuvo can reach a seller. A person buys the car. If another partner offers a fully automatic customer email with no approval, ask who eats the bad send.

Protectron is our public example of paperwork that still needs a human owner. Risk classification and generated documents help a team move. They do not replace counsel. A partner who blurs that line is selling comfort. Keep counsel. Keep the software for the trail.

Everyone claims fast. The honest version is a table of what “done” means. A strategy partner is done when the board pack lands. A boutique is done when the shortlist is agreed. A shop is done when a release hits the environment in the spec. A seat vendor is done when licenses assign. Nidrosoft is done with the first slice when a ranked map exists and, if you continue, when a scoped process runs in your tools with an operator who can explain it.

The how-we-work page lists a common implementation window after audit and plan, often weeks five through ten for the first build. That is a planning shape, not a guarantee. A dealer outreach flow that already has CRM access moves sooner than a clinic integration waiting on a vendor API. We would rather slip a date than ship a demo that dies when the builder leaves.

If you need a board date in four weeks and no system access, hire the strategy partner or write the pack internally. If you need seats before a leadership offsite, buy seats. Do not hire Nidrosoft to manufacture a date we cannot keep.

A strategy partner leaves language you can reuse with investors and regulators. That language has value. It does not move a listing from Craigslist into a dealer’s inventory board. A boutique leaves a sequence of pilots. Your staff still has to staff them. A shop leaves software. Read whether the prompts, eval notes, and third-party keys are included. Seat vendors leave an invoice and a habit, if people formed one.

Nidrosoft leaves the map from Diagnose even if you stop. If you continue, we leave the running process, the prompts, the runbooks, and a person on your side who saw the build. NanoBrief is a reminder that a brief can be an asset you generate in minutes. The client equivalent is a runbook your operator can open without us on the call.

Nerlude exists because founders lose keys in Slack. A partner who stores production secrets in a personal password manager is a risk. Ask where credentials live. Ask who can revoke them. Ask what happens to logs. Those questions belong in the first audit, not the last week.

Octana, Guidera, Clear Audio AI, and MixGuidera are products with edges you can see. A partner comparison should be equally visible. If a firm will not show a system, ask for a working session in your stack instead of another case-study reel.

A bench wins when you need parallel streams, coverage across time zones, and a replacement if one engineer is out. Nidrosoft is a studio. The thread from first constraint to live system can sit with one person. That is why design, architecture, and production code stay aligned. It is also why we will refuse a program that needs four squads in month one.

Transformation at Nidrosoft still goes team by team. We do not boil the company. A department gets a map, a build, and training. Then the next department uses people who already saw the method. That is slower than a slide that says “enterprise rollout.” It is how ownership survives the first vacation.

If you want a rented senior engineer inside standups on a monthly seat, read the rent-an-AI-engineer page. That offer is an embed with a clear seat. This compare page is the wider choice among partner types. Do not treat a monthly embed as a published price for every audit and build. Book the audit. Scope the seat or the project from the map.

Twelve-plus years of shipping, 125 products, 16 public systems. Those numbers describe range. They do not describe a factory. If a procurement sheet requires twenty named CVs, we will fail that sheet. Hire the shop. Keep us for the process that has no spec yet.

Strategy consultancy wins

The board needs a transformation story, a risk model, and org language before anyone is allowed to write to production. Two divisions still fight over data. Investors asked for a plan, not a bot. Hire the firm that lives in that room.

Boutique AI consultancy wins

You want a bake-off and a ranked pilot list. Your engineers will build. You do not want a studio in Slack for a quarter. Hire the boutique. Staff the winner internally.

Product shop wins

The objects are known, the screens are drawn, and you need a bench. Or you are building a consumer or SaaS product that is not an operations workflow. Hire the shop. Put ownership of prompts and evals in the contract.

Seat vendor wins

People need to draft and summarize faster. You are measuring adoption, not a write to the ERP. Buy ChatGPT or Copilot. Add Nidrosoft training later if the leadership team wants practice on real files. Skip a custom build until a process repeats.

We are a poor partner for a legal-only EU AI Act opinion. Protectron helps teams produce and track artifacts. Counsel still signs. We are a poor partner for a tool-only rollout with no process owner. We are a poor partner for a confidential-logo theater. If you need a wall of unnamed banks, look elsewhere.

We are a poor partner if the process happens once. Annual planning can use NanoBrief-style speed for documents. It does not need an overnight agent. We are a poor partner if nobody can name the system of record. “Put AI on it” is not a brief.

Remote work is normal. Cyriac Zeh lives in San Diego. Teams across the United States and abroad already book the studio. We will not claim a staffed office in your city. If you require a local badge every day, hire a local firm. If you can work in shared tools with scheduled embed days, we can partner.

If the audit finds that seats or a boutique map are enough, we will say so. A partner who cannot lose a deal on the merits is a vendor. Be suspicious of that energy.

• System runs in accounts we control (cloud, tenant, or approved private infrastructure)
• Source we can build without the partner on the call
• Prompts and eval notes in a place we can edit
• Runbooks for the named operator
• Keys stored in our vault, revocable
• Logs we can keep for audit
• Human approval on money, contracts, and customer sends
• A ranked map delivered even if we stop after Diagnose

Nidrosoft treats that list as the definition of Own. Strategy and boutique partners should initial the items they can meet and strike the rest. Honesty there is worth more than a shared vocabulary about “enablement.”

Training belongs on the same list. Corporate AI training at Nidrosoft is a sprint on your tools with a playbook you keep. It pairs with a build when the operators need practice. It replaces a build when practice was the whole job.

Book the free audit on the public calendar or write cyriac@nidrosoft.com. Bring the tools, the owner, and one painful process. If you already have a strategy pack, bring page numbers. We will mark which items are partner work for a studio and which items should stay with the firm that wrote them.

The first two weeks produce the map. Hours, feasibility, payback. You can stop. You can buy training. You can scope a build. You can take the map to a shop. The map is yours. That is the cleanest way we know to compare partners without a theater of proposals.

We will not invent a retainer or a euro figure on this page. Stacks differ. Access differs. A clinic is not a fund. A dealer desk is not a SaaS billing team. Scope after the map, or you are buying a guess.