Workshops and training that use your files

Workshop and training are two words buyers use for the same job: get people practicing together before or beside a build. Nidrosoft treats them as one service with two common audiences. Leadership rooms aim at judgment. Engineer rooms aim at a small, honest artifact on your stack. Mixed rooms need a tighter agenda. Public community sessions such as AI for the Rest of Us and the Executive Roundtable are related teaching, not this private sprint, and we do not publish attendance numbers for them.

The service page for training is the product description. This explore page exists because people type the pair. If you already know you need a live process, skip to builds or to implementation versus workshops. If you already know you need a San Diego room, there is a local page. Stay here if you are still separating a class from a system.

Cyriac Zeh founded Nidrosoft after Anthropic, Microsoft on Bing and Edge, Intuit, and Gap Inc. He teaches the room himself. One hundred twenty-five products shipped and sixteen public systems keep the examples from drifting into folklore. We will still use your nouns in the playbook.

Before the room we ask for three tasks and the tools they live in. Inbox threads with names removed. A redacted invoice. A brief questionnaire. A listing the desk already lost. If you cannot bring any representation of the work, say so. A boutique’s generic lab may be cleaner. Our bias is your files.

The sprint moves from a shared picture to practice to writing. People fail on purpose. A bad customer send. A wrong inventory match. A clause the model invented. Those failures become rules in the playbook. A workshop that only shows success trains people to trust demos.

We use the seats you already pay for when we can. ChatGPT, Copilot, Claude, or a hosted model. Training is a poor reason to force a new vendor. If you have no seats, we will say whether licenses should come first. Rolling seats after a good room is common. Rolling seats instead of a room is also common.

Homework appears when the sprint is a series. Rewrite one vendor email with the new approval rule. Move a key out of chat. If nobody does the homework, we stop adding material. Practice that never leaves the room is entertainment.

• Agenda tied to named tasks
• Practice on approved files
• Approval rules in writing
• Prompts the group authored
• Playbook in your drive
• Recommended next buy

After a leadership workshop, a director should reject a bundled “AI day plus platform” email. They should tell a strategy offsite from a working session. They should name a 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 know when a McKinsey or BCG style firm is the correct next spend. If the board asked for a transformation pack, our playbook will not satisfy that audience. Saying so in the room is part of the teaching.

Risk stays concrete. Customer text. Money. Medical or legal language. EU AI Act trails versus a letter from counsel. Protectron can help a team produce artifacts. It is not a law firm. We will not turn the day into a fear seminar. We will mark the processes that must not go unsupervised.

Under 30 people, the founder should attend. Between 30 and 250, the leads who own the tools should attend. Past 250, one department’s leaders. A giant all-hands with no shared tools is a show. Buy a keynote brand if a show was the brief.

Engineer training ends with something in a repo or tenant they control. A prompt file. Eval notes. A thin connector to a copy of the CRM. A key in the vault. Nerlude exists because teams lose infrastructure details. Secret hygiene is curriculum, not an appendix.

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

If engineers already have a spec and need a bench, send them to a shop. Invite the shop lead if they will stay on the account. Shared language about who owns prompts prevents a later contract fight. If the shop will not discuss prompts, write that down during the sprint.

Pair the room with time on the floor if the builders have never watched the operator. Embed is still the first method word, even when the invoice says training.

Nidrosoft wins the first row. Implementation is on the table so you do not buy a room when you needed a system. The other rows win for the reasons in the Best for column. Procurement should not score all six as training. The cheapest generic lab will win that scorecard and you will learn nothing about your CRM.

You own the playbook, the prompts authored in the room, and the notes. You own recordings only if you asked and counsel agreed. You do not own a production integration. You do not own Omnira Dental, TokenTra, or any other Nidrosoft product unless you license it. You can take the playbook to another trainer.

If a vendor locks the playbook in a portal, you rented a PDF. We put the file in your drive and export any board we used. Octana, Guidera, Clear Audio AI, and MixGuidera may appear as product edges. The playbook still uses your nouns.

Ownership includes the recommended next buy. Seats. Audit. Build. Stop. A workshop that refuses to recommend stop is selling the next room in advance.

Room first when leaders cannot name processes or engineers have never practiced on the real stack. Audit first when the processes are named and you need hours. Build first when the owner and access already exist. Training during a build for the operator is included in builds. This explore page is the wider room.

Transformation funds rooms and builds as a program, still team by team. Do not print that banner if you only needed one afternoon. The compare page on implementation versus workshops exists so those line items stay honest.

If the room reveals that seats are enough, stop. If it reveals a shop should take a specified app, hire the shop. Twelve-plus years of shipping does not obligate you to keep paying Nidrosoft.

We will not run a half-day implementation and call it training. We will not run a certificate mill. We will not run a thousand-person livestream as this service. We will not run a room with no representation of the work if a generic lab would be safer. We will not run a legal-opinion seminar.

We will not run a room whose only goal is rolling Copilot if the vendor already included enablement. Pay the vendor. We will not run a strategy offsite costume. Our rooms look like work. That can be the wrong look for a board that booked a famous firm.

When we say a brief can take under two minutes, that is NanoBrief versus three-plus hours. When we say dealers can acquire 3x inventory with 80 percent less manual outreach, that is Nexuvo. When we say teams cut 10 to 30 percent of wasted tokens, that is TokenTra. We will not invent a fourth statistic for your slide.

Omnira Dental, Octana, Eviction Wizard, Guidera, Protectron, Nerlude, Clear Audio AI, and MixGuidera keep other edges visible: practice operations, media, legal ops, travel, compliance artifacts, infrastructure, audio. 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.

The AI Architect is the practice name. Cyriac Zeh is the teacher. Nidrosoft is the studio in San Diego.

Private sprints can be in San Diego, La Mesa, and Southern California, or on a video link. The local explore page lists community formats. This page will not repeat a calendar of events. If you need tickets to a public session, watch the channels Cyriac already uses. If you need a private room, book here.

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

We do not invent attendance. We do not invent a second office. If a local trainer can be in your building every week and that is the constraint, hire them. If you want the person who also ships the public archive, book us.

Use the public calendar or cyriac@nidrosoft.com. Say leadership or engineers, location, and three tasks. Name seats you already bought. Attach a strategy pack if the room must respect or challenge a page.

A no usually means you need an audit or a build, or a vendor’s own enablement. That no is part of the work. Scope sets the fee. A half-day leadership room and a multi-session engineering sprint are different objects. No invented currency on this page.

Bring the ugly workflow. Pretty decks waste the first hour. The playbook should still make sense on Monday when nobody is performing.

If two time zones share the room, say so. We will not run a single block that wastes half the group. Two shorter sessions beat one heroic afternoon. Southern California mornings and European afternoons are a real constraint. So are night-shift ops leads. Name the constraint when you book.

Send the last vendor workshop you attended, if you have notes. We will not repeat their labs for sport. If they already taught Copilot adoption, we will skip that hour and spend it on the unofficial path. Paying twice for the same lunch-and-learn is how training budgets vanish.

Ask us to write the leftover into the confirmation email: playbook, prompts, notes, recommended next buy. If a later invoice tries to call the day an implementation, you have the email. The compare page on implementation versus workshops exists for the same reason. Keep the artifacts named.

After the sprint, pick one rule from the playbook and use it for a week. Approval on customer send. Keys out of chat. A saved prompt for intake. If nobody used a rule, do not book a build to hide that fact. Book a short follow-up or stop. Software cannot repair a closed file.

NanoBrief, TokenTra, and Nexuvo may appear as timed examples (under two minutes versus three-plus hours, 10 to 30 percent wasted spend, 3x inventory with 80 percent less manual outreach). They are timed because those products exist. Your playbook still needs your measure. Do not copy a number that is not yours onto a slide for the board.

If counsel forbids customer text in any model, say so before we design exercises. We can work on internal drafts, redacted files, or we can send you to a generic lab. Pretending the rule does not exist until 10am on the day is how rooms stall. We would rather redesign the agenda than perform a forbidden paste.

A workshop can be the entire purchase. Many companies should stop there. Leadership shares a language. Engineers store a prompt file. Seats get used on purpose. That is a complete leftover. The pressure to add a build because the room went well is how unused agents start. We will write stop when stop is the right next buy.

If you already scheduled an implementation and want a room in the same month, tell us the date of the write path. We will aim the playbook at the operator who will run that path. A generic inspiration day the week before a CRM integration is a wasted calendar slot. Sequence the artifacts.

If the room is for engineers employed by a shop, send the SOW. We will aim the playbook at whoever will own prompts after the shop leaves. A training day that ignores the contract will produce files nobody is allowed to edit. That is a wasted sprint.

If you only needed Copilot adoption, pay that vendor for their own enablement program. Invite us later when the work crosses tools the vendor will not touch. A room that repeats the vendor slide deck is a wasted morning for everyone who already sat through the license kickoff.