Workshops on your tools, with a playbook you keep

Workshops are one of five Nidrosoft services, next to audit and strategy, product, AI systems, and transformation. The room exists for teams that need shared language and hands-on reps before anyone talks about a connector. It also exists for teams in the middle of a build who need a wider group than the single operator. The artifact is a playbook you keep. Embed and Diagnose still show up, compressed: we look at the work, then we practice on it. People who searched corporate AI training San Diego land here.

Leadership sprints aim at decisions. Which processes are even candidates. What a human must approve. How to read a vendor demo. How to tell a workshop from an implementation when a salesperson bundles them. Engineer sprints aim at a small, honest build on your stack: a prompt with eval notes, a draft connector to a safe copy, a checklist for keys. Mixed rooms are possible. They need a tighter agenda so executives do not sit through an API hour they will never use.

Cyriac Zeh teaches the room. He founded Nidrosoft in San Diego after Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. He also sits in public Southern California rooms such as the Executive Roundtable and AI for the Rest of Us. Those public formats are not this service. This service is your company, your tools, your tasks. We do not publish attendance numbers for public sessions, and we will not invent a headcount to make a private sprint look famous.

Before the room we ask for three real tasks and the tools they live in. If you cannot share any file, say so. A synthetic lab may be safer, and a boutique that sells generic labs may be the better buy. Our bias is your work. NanoBrief-shaped exercises use your brief questions. Token-shaped exercises use a redacted invoice. Inbox exercises use a week of real threads with names removed if counsel requires it.

The day (or the short series) moves from a shared picture to practice to a written playbook. People fail in the room on purpose. A bad customer email, a wrong inventory match, a clause the model invented. We treat those failures as the curriculum. A talk that only shows success teaches people to trust a demo.

We will use ChatGPT, Copilot, Claude, or whatever you already pay for. Training is a poor excuse to force a new vendor. If you have no seats yet, we will say whether seats should come first. Rolling licenses after a good sprint is common. Rolling licenses instead of a sprint is also common, and sometimes enough.

San Diego and La Mesa teams can ask for an in-person room. Southern California companies can do the same. Everyone else can work on video with the same file rule. Geography changes catering, not the playbook.

We will send a pre-read that is short on purpose. Long pre-reads do not get read. The pre-read names the three tasks, the tools, and the rule for customer data. If someone arrives without opening it, they can still join, and they will spend the first hour catching up while others practice. That cost belongs to the company, not to a longer lecture from us.

Homework is part of the sprint when the calendar is a series rather than a single block. A leadership group might rewrite one vendor email with the new approval rule. An engineering group might move a key out of chat. We review the homework in the next session. If nobody did it, we stop adding new material. Practice that never leaves the room is entertainment.

Interpreters and accessibility needs should be named when you book. We will not assume every room is English-only or that everyone can use the same laptop setup. The playbook should still be readable by someone who missed the day.

• Agenda tied to named tasks
• Practice on approved files
• Written rules for approvals
• Prompts the group authored
• Playbook in a place you control
• Recommended next buy: seats, audit, build, or stop

After a leadership sprint, a director should be able to reject a bundled “AI day plus platform” email. They should be able to say whether they need a playbook, a map, or a live process. They should be able to name one metric they already believe. They should know that Nexuvo-class overnight work still needs a person on the offer, that Eviction Wizard-class paths still need a person on the filing, and that TokenTra-class bills still need a person on the budget.

They should also know when a McKinsey or BCG style firm is the right next spend. If the board asked for a transformation pack, our playbook will not satisfy that audience. We will say so in the room. Hiring the strategy firm is a success if that was the real job.

Risk conversation stays concrete. Customer text. Money movement. Medical or legal language. EU AI Act trails via a product like Protectron versus a letter from counsel. We do not turn the sprint into a fear seminar. We do mark the processes that must not go to an unsupervised model.

Under 30 people, the founder should attend. Between 30 and 250, the department leads who own the tools should attend. Past 250, pick one department’s leaders. A 40-person all-hands with no shared tools becomes a show.

Engineer sprints end with something in a repo or a tenant they control: a prompt file, an eval note, a thin connector to a copy of the CRM, a key stored in the vault rather than chat. Nerlude exists because teams lose infrastructure details. We will treat secret hygiene as part of training, not an appendix.

We will not spend the day on model trivia that expires. We will spend it on the failure modes of your workflow. Wrong field. Stale export. Hallucinated clause. Token waste. Those are the same failure modes a later Nidrosoft build would write evals for. If you staff the build internally, you just saved a month of discovery.

If the engineers already have a spec and need a bench, send them to a product shop. Training will frustrate a team that wanted tickets, not judgment. If they have never sat with an operator, pair the sprint with an afternoon on the floor. Embed is still the first method word, even in a class.

Engineers often want a stack lecture. We will give a short one and then return to the workflow. A perfect local setup that never reads the CRM field the operator uses is a science fair. The playbook should include the boring parts: where prompts live, who can edit them, how to revert, how to record a failure. Those lines are what a later hire will thank you for.

If your engineers are staffed by a shop, invite the shop lead. Shared language between a studio trainer and a delivery bench prevents a later argument about who owns evals. If the shop refuses to discuss prompts, write that down. It will matter in the contract.

You own the playbook, the prompts authored in the room, and the exercise notes. You own recordings only if you asked and counsel agreed. You do not own a production integration. You do not own Nidrosoft products such as Omnira Dental or TokenTra unless you separately license them. You can take the playbook to another trainer or to a shop.

If a vendor locks the playbook in a portal and charges you to reopen it, you rented a PDF. We put the file in your drive. If we used a shared board during the day, we export it before we leave.

Octana, Guidera, Clear Audio AI, and MixGuidera may appear as examples of product edges (media, travel, audio). They are illustrations. The playbook should still speak in your nouns: claims, chairs, lots, funds, SKUs.

• Playbook in your drive
• Prompt file the group wrote
• Approval rules in writing
• Recommended next step

Skip this service if you needed a build last month and the process is already obvious. Skip it if you wanted a famous keynote brand and a thousand-person livestream. Skip it if you cannot bring any representation of the work. Skip it if the success metric is “everyone got a certificate.” Skip it if you needed counsel to sign an EU AI Act opinion.

Skip it if the only goal is rolling Copilot and the vendor already included enablement. Pay the vendor. Skip it if a strategy offsite was what the board booked. Let that firm run their format. Our rooms look like work sessions. That can be the wrong costume.

Skip it if you wanted us to implement during a half day and call it training. That mix is how companies get a fragile demo and no playbook. Read implementation versus workshops. Buy the artifact you need.

Training first when leaders cannot name processes or when engineers have never practiced on the real stack. Audit first when the processes are named and you need hours and payback. Build first when the owner and the access already exist and a room would only delay the operator. Transformation when you want that sequence funded as a program, still team by team.

A sprint can produce a short list that makes the audit faster. An audit can produce a playbook outline that makes the sprint sharper. A build should include operator training even if you never buy this service for the whole department. Do not pay twice for the same hour without saying why.

If the sprint reveals that seats are enough, stop. If it reveals that a shop should take a specified app, stop and hire the shop. Twelve-plus years and 125 shipped products do not obligate you to keep paying Nidrosoft.

Nidrosoft wins the first row. We lose the others on purpose. If procurement tries to score all five as “training,” the cheapest generic lab will win and you will learn nothing about your CRM.

The San Diego Executive Roundtable is an invite-style conversation with regional corporate leaders. AI for the Rest of Us is a working session for operators who need the technology in the business. Cyriac has also appeared in Southern California executive panels. Those appearances show that the studio will stand in a room. They are not a substitute for your playbook, and they are not a lead-gen stunt with invented crowd sizes.

If you want a public-style session for your company, say so. We will still require your tasks. If you want tickets to a community event, watch the channels Cyriac already uses. This page sells the private sprint.

The explore pages for workshops and for San Diego workshops repeat the local facts for people who searched those phrases. The rules stay the same: your files, your playbook, no fake attendance.

We teach from systems that exist. Omnira Dental, Octana, Eviction Wizard, Guidera, TokenTra, Protectron, Nerlude, Nexuvo, NanoBrief, Clear Audio AI, MixGuidera. Sixteen public. One hundred twenty-five shipped. When we say a brief can take under two minutes, that number comes from NanoBrief. When we say dealers can acquire 3x inventory with 80 percent less manual outreach, that number comes from Nexuvo. When we say teams cut 10 to 30 percent of wasted tokens, that number comes from TokenTra. We will not invent a fourth number for your slide.

Your playbook will not copy those products. It will copy the discipline: name the user, name the approval, name the measure, name what you own.

Book the calendar or write cyriac@nidrosoft.com. List leadership or engineers, location (San Diego, elsewhere, or remote), and three tasks. If you already bought seats, say which ones. If you already have a strategy pack, say which page the room must respect or challenge.

We will reply with a proposed agenda or with a no. A no usually means you need an audit or a build instead, or a vendor’s own enablement. That no is part of the service.

Scope sets the fee. This page will not invent one. A half-day leadership room and a multi-session engineering sprint are different objects.

If two departments want to share a room, say so early. Shared rooms work when the tasks overlap. They fail when finance sits through a dealer outreach lab. We would rather run two shorter sprints than one confused day. Transformation can fund both. This service does not require the banner.

Send the names of tools, not a list of model brands you saw in a keynote. We will match the agenda to HubSpot, a practice manager, a dealer DMS, or a shared inbox. If the only tool is chat, the agenda is seats and judgment. That is still a valid sprint. It is a different sprint from a CRM lab.

After the room, give the playbook a week to be used. If nobody opened it, do not book a build to fix a reading problem. Book a shorter follow-up or stop. Software cannot repair a playbook that sits closed. We will ask what people tried before we talk about connectors.

A sprint can be the entire purchase. Write that option into the confirmation. The pressure to add software because the day went well is how unused agents start. We will recommend a build only when a process, an owner, and access showed up in the room.