Do you need a workshop or an implementation?

Workshops and implementations get bundled because both use the word AI. They are different purchases. A workshop changes what people can do with tools they already have. An implementation changes what the system does while people sleep, drive, or sit with a patient. Buying the first when you need the second produces a burst of energy and the same inbox. Buying the second when you need the first produces software nobody asked to operate.

Nidrosoft’s training offer is a focused sprint. Leadership or engineers work on their own tools and their own tasks. They leave with a playbook. The San Diego and Southern California rooms, including sessions such as AI for the Rest of Us and the Executive Roundtable, are the public face of that teaching. They do not replace a build in a dealer CRM or a dental stack.

Nidrosoft’s build offer follows Embed, Diagnose, Scope, Build, Own. We sit with the people doing the work, rank payback, define what runs and what a person approves, ship into your accounts, and leave operators who can run it. Public systems show the shape: Omnira Dental, Octana, Eviction Wizard, Guidera, TokenTra, Protectron, Nerlude, Nexuvo, NanoBrief, Clear Audio AI, MixGuidera.

You can buy them in sequence. Many teams should. A workshop that surfaces three repeating workflows is a cheaper Diagnose than a full audit if the company has never practiced together. An audit is the right next buy when the workshop notes point at a system of record and an owner. Implementation is the buy when that owner can grant access.

A product shop is missing from the first table because shops rarely sell workshops as the main offer. They sell builds against a spec. If you already have a spec and need an application, skip this page and read the alternatives guide. If you are trying to decide whether people need practice or whether the company needs a connector, stay here.

Transformation is the longer path that includes audit, builds, training, and rollout. It is not a synonym for workshop. Teams that buy “transformation” and receive three Zoom classes were sold a label. Nidrosoft will not use that label for a single afternoon.

Corporate AI training at Nidrosoft is built around the work already on someone’s laptop. Leadership sessions aim at judgment: where a model helps, where a person must stay, what a department can measure. Engineer sessions aim at a small build on the stack you already pay for. Both leave a playbook. Neither pretends the playbook files a notice, buys a car, or closes a chair-side loop.

Cyriac Zeh has sat on the San Diego Executive Roundtable with regional corporate leaders, on Southern California executive rooms, and in public sessions such as AI for the Rest of Us. Those rooms are teaching and conversation. They are proof that the studio will stand in front of operators. They are not attendance theater. We do not publish headcounts for those events on this page.

A workshop wins when the company lacks a shared picture. Finance thinks AI means the chatbot on the website. Ops thinks it means a robot on the floor. Legal thinks it means a ban. A few hours with real tasks lowers the volume. People leave able to reject a bad vendor demo. That skill is worth money even if you never hire us to build.

A workshop also wins when the only data you will share is a copy of a spreadsheet on a laptop. Implementation needs accounts, policies, and a write path. If those are months away, buy practice. Buy seats. Come back when security can say yes.

Implementation starts with Embed. We watch the recurring work. Diagnose scores hours, feasibility, and payback. Scope writes what the machine does, what a person approves, and what you will measure. Build ships into the CRM, inbox, ERP, practice system, or lot tools. Own means the code, prompts, and runbooks stay with you.

Nexuvo is the public picture of overnight work: dealers acquire 3x more inventory with 80 percent less manual outreach. TokenTra is the public picture of a bill you can finally read: teams cut 10 to 30 percent of wasted AI spend. NanoBrief is the public picture of a document job collapsing from three-plus hours to under two minutes. Your build will not be those products unless you license them. Your build should be that concrete.

Implementation wins when a workflow repeats, an owner exists, and the system of record can be reached. A landlord path through Eviction Wizard is a process. A practice path through Omnira Dental is a process. A founder’s keys and renewals in Nerlude is a process. If you describe the job as “make us more innovative,” you are still in workshop territory.

Implementation loses when the spec is already a product with screens and a release train. A shop may be faster. Implementation loses when the board wants a pack and no one may touch production. A strategy firm wins. Implementation loses when people only needed Copilot. Buy the seats.

Buy a workshop first when the leadership team cannot yet name three processes. Use the room to write those names on a wall. If the names are vague, stop. If the names point at systems you already pay for, book the audit. The audit is more thorough than a workshop because it costs the hours and ranks payback. The workshop is faster at creating permission to do that work.

Buy implementation first when the process is already obvious and painful. A dealer who already spends nights on Marketplace does not need a half-day to learn that outreach is the job. They need access, a scope, and a build. Add training during Build so the desk can run the new path without a Slack thread to San Diego.

Buy transformation when you want the sequence funded as a program: audit, builds, training, rollout, next team. Still start in one department if you are past 250 people. Still require a founder in the room if you are under 30 and betting the quarter on one build.

Do not buy a workshop as a consolation prize after a build stalls. Fix access or stop. A room cannot unblock a vendor API. Do not buy a build as a souvenir after a fun afternoon. Fun is not a scope.

Typical speed is honest only if you keep the artifacts straight. A workshop can happen as soon as calendars and a file set exist. An implementation cannot start its build phase until Diagnose and Scope have something true to say. Seats are faster than both for drafting. Strategy rooms are slower than a workshop and still faster than a build if the only output is paper.

Price stays off this page. A half-day and a multi-week build are not the same invoice. Anyone who quotes both as one “AI package” without a map is selling a bundle you will regret. Use the audit to split the line items.

A McKinsey or BCG style offsite wins when the artifact must look like a corporate transformation pack. Our rooms look like work. That is a compliment in an ops meeting and a problem in a board that asked for a named firm. Hire the named firm. Invite us later for a department build.

A boutique’s generic lab wins when you cannot bring real files. Some companies will not let customer data into any room. A synthetic lab is then the only legal teaching. Our bias is your files. If you cannot bring them, a generic lab is cleaner than a fake “custom” session.

Vendor enablement wins when you already bought a platform and need adoption. Salesforce, Microsoft, and others will teach their own surfaces. Pay them for that. Pay Nidrosoft when the work crosses tools or sits in a gap the platform does not cover.

A product shop’s kickoff workshop wins when the build is already sold and the workshop is really discovery for screens. That is project inception, not corporate training. Keep the labels honest so finance can see what it bought.

After a Nidrosoft workshop you should hold a playbook, the prompts the group wrote, and the notes from the exercises. After a Nidrosoft implementation you should hold those plus the running system, the repo or tenant objects, eval notes, and the operator runbook. After a strategy room you hold a pack. After seats you hold an admin console.

If a workshop vendor keeps the playbook in their portal and charges you to look at it later, you rented a PDF. If an implementation vendor keeps the prompts on their laptop, you rented a person. Nidrosoft’s Own step exists to prevent both. Ask us to show where the files will live before the sprint or the build starts.

Clear Audio AI and MixGuidera are reminders that some work is media, not chat. A workshop can teach a producer how to brief a tool. An implementation can hang that tool on a catalog pipeline. Own the brief either way. Own the pipeline if you paid for the pipeline.

• Workshop: playbook, prompts, exercise files
• Implementation: code, prompts, evals, runbooks, accounts
• Strategy room: pack and recommendations
• Seats: tenant, policies, leftover chats

A two-hour inspiration talk sold as implementation. An implementation sold to a company that has never opened ChatGPT. A transformation program with no department owner. A workshop that uses only the vendor’s demo data and then claims custom. A build with no human on customer send. We will walk away from those shapes.

A workshop for a process that happens once a year. An implementation for a process nobody can show us. Seats for a clinic that needs Omnira-class operations. A strategy pack for a 20-person company that needed one automation. Size the artifact to the company.

San Diego proximity does not change the mix. A La Mesa operator and a remote fund get the same question: playbook or system. Local rooms are easier to book. They are not a different methodology.

Cyriac Zeh is in San Diego. Teams in San Diego, La Mesa, and the rest of Southern California can ask for a room. Teams elsewhere can ask for the same workshop on a video link with the same rule: your tools, your tasks. Implementation follows the systems, not the airport.

If you searched for San Diego workshops, there is a dedicated explore page. This compare page will not repeat a calendar of events. Public formats you can name today include the Executive Roundtable and AI for the Rest of Us. Book an audit or a training sprint if you want a private room for your company.

We do not invent attendance numbers. We do not invent a second office. If a local firm can teach your stack in person every week and that is the constraint, hire them. If you want the person who also ships Omnira Dental and TokenTra, book us.

Book time on the public calendar or write cyriac@nidrosoft.com. Say whether you think you need a room, a build, or you cannot tell. Bring one process and the tool it lives in. If you already bought seats, bring two examples of useful chats and two examples of failure. That pair is a better brief than a vision slide.

The audit may say: stay on seats, run a leadership sprint, then stop. Or: skip the room, scope a build. Or: do both in that order. We will write the recommendation in plain sentences. You can take that page to another vendor.

No monthly implementation price lives here. No invented euro retainer. Scope follows the map because a playbook and a dealer integration are not the same object.