FAQ

Build Sprints FAQ: every question, answered once.

Fees and credits, sprint dates and languages, recordings, prerequisites, transfers and invoicing.

FAQ

Every question, by program.

General questions

How does a build sprint work for one founder?

A fixed, dated block of live sessions in which you build working AI employees on your own work and your own accounts, with us in the room: seventy percent building, thirty percent teaching, and a quality gate before each step. You leave with the system, not a certificate.

Will I learn Claude?

Yes, by building with it. Every session ends with something running on your own accounts, and that working system is what you keep.

What credits apply?

One, inside the sprints. Master Claude's $297 counts toward all four weeks if you upgrade before 10pm GST on the day of the Week 1 session. Sprint fees do not credit against a build. The one-day audits are a separate service; their 60-day credit is on the audits page.

Which programs run in Arabic?

Every corporate program can be delivered in Arabic. The public builder sprints are taught in English; Arabic builder sprints run at Entrepreneurs Oasis, an SMOrchestra company.

What happens in Week 1 if I only buy Master Claude?

You leave with your business brain, your voice file and one working skill. If you want the employees, upgrade before 10pm GST the same day; your $297 counts.

Are there prerequisites?

For the builder sprints: a Claude Pro or Max account (Max recommended from Week 3), a laptop, a Gmail or Outlook inbox and calendar you can connect, and one real weekly job to hand over. Master Claude assumes you already use Claude or ChatGPT every day. Corporate programs send a setup checklist at signature.

Do I get a certificate?

No. We do not issue certificates. Your work passes a quality gate instead: the Week 1 gate for Master Claude, Demo Day for the longer programs. The work is the proof; a certificate for attendance is what these programs exist to replace.

What is an AI build sprint?

A fixed, dated block of live sessions in which your people build a working AI employee or operating system on their own work, with us in the room: seventy percent building, thirty percent teaching, a quality gate before each step, and a Demo Day on the longer sprints. You leave with the system, not a certificate. If it is not running on the job by day 30, the sprint did not work.

Will my team learn Claude?

Yes, by building with it. Every session ends with something running on your own systems, and that working system is what your team keeps.

What does 'starting at $15,000' mean?

It is the floor for one program: one sprint of up to 20, one department or one custom group. Scope sets the final figure: the number of functions, the delivery language, on site or remote. Prices are per program, never per seat, and exclude travel and venue. The scoping call fixes the figure before anything is signed, and the number on the invoice is the number on the call.

Do you invoice with VAT, and what are the terms?

Yes: VAT appears on each tax invoice at the applicable rate. 60% of the fee follows proof. A tax invoice carrying our trade licence and TRN is issued at each milestone: 40% on signature, 40% when your named sponsor accepts the outcome, 20% at close-out. A non-disclosure agreement is available on request, signed before the scoping call if you prefer.

On site or remote?

Either. On site in the UAE, Saudi Arabia and Jordan, or remote for the rest. In the UAE and Saudi Arabia, on-site training is contracted and delivered with a licensed local training partner, named in your proposal. The sprint is private in both cases, so the schedule is built around your team, not a public calendar.

Is Arabic delivery available?

For every corporate program, as Arabic delivery with bilingual artifacts, or the reverse. Mixed rooms work; you choose at scoping.

What if we have more than 20 people?

Run two sprints, or scope a custom program. Twenty is the size at which every seat still builds something in the room; above it, the room stops being a room.

What happens after we request a proposal?

A reply within one business day with a short brief, then one scoping call that fixes room, language, format and the number. Then a tax invoice. No deck, no sequence of discovery calls.

Is the training accredited?

No, and we do not issue certificates: what you get is AI running in your organisation, checked at a quality gate. If your budget depends on a subsidy or a licensing rule (HRDF in Saudi Arabia, KHDA in Dubai), tell us at scoping and we say plainly what we can support and what we cannot. We do not claim an accreditation we do not hold.

We already pay for Microsoft Copilot. Why Claude?

Keep Copilot. It drafts inside Office. These programs build the operating system around the work: the brain, the skills, the tool keys and the gate. We teach on Claude because that is where we build and run 100+ operating systems ourselves. The decision rule, the job description and the oversight sheet are yours whatever model you run.

Who pays for the Claude licences?

You do, directly with Anthropic; they are not in our fee. Each participant from the managers' program (C2) up needs a seat on your organisation's Claude Team or Enterprise plan; the board session needs none. Anthropic lists Team at $25 a seat a month, or $20 billed annually (claude.com/pricing); Enterprise is quoted by Anthropic. The setup checklist sent at signature names the plan and the number of seats.

Is our data used to train the model?

Not on Claude Team or Enterprise: Anthropic's commercial terms exclude your inputs and outputs from model training by default. Residency and data-protection rules (PDPL, your sector's) are reviewed with your IT and legal at scoping, before any of your data enters a session.

Who Signs Off When Claude Is Wrong? $5,000 per session

Is this a technical session?

No. It is a governance session. Nobody opens a terminal. You leave with a written oversight model, the questions to ask your teams, and a clear view of what should reach the board quarterly and what should reach it immediately.

What does the $5,000 session include?

Half a day with your board or executive committee, up to 15 people, the pre-read, and the written oversight model delivered after the session. Travel and venue are excluded, as on every corporate program, and the scoping call fixes the date and the room before you sign.

What happens after the session?

The oversight model is yours. It becomes the standard every later program builds under, and it is the first document the AI Automation Audit reads if you take one. The next step on the ladder is Hire AI-Native Employees Safely, so the rule the board wrote is the rule the managers apply.

Can it run in Arabic, or for a mixed board?

Yes. The session runs in Arabic or English, and a mixed board gets bilingual materials, with the oversight model written in the language your minutes are kept in. On site in the UAE, Saudi Arabia and Jordan, or remote.

Who should be in the room for the board session?

The directors who approve AI decisions, and the executive who will own the oversight model afterwards.

Hire AI-Native Employees Safely and Consciously in Claude $12,000 per sprint

Which managers should we send?

The people who answer for output quality: department heads and team managers in operations, HR, finance, service and delivery. Up to twenty per sprint. If your board has not set an oversight model yet, the board session (C1) comes first and takes half a day.

What does $12,000 per sprint include?

Two live days, the 30-day follow-through, the materials and recordings, and, where the readiness score allows, one AI employee in delegate mode left running under a signed oversight sheet. Travel and venue are excluded. Pricing is per sprint, never per seat, and the scoping call fixes the dates before you sign.

Does this replace our AI policy?

It produces the part of it that is usually missing: a readiness score, a signed job description and a decision rule per task type that a manager can actually apply, with the approval gates and the kill switch wired in Claude rather than described in a document.

What if a manager cannot attend both days?

The two days are consecutive and the 30-day follow-through assumes both. Tell us at scoping: a manager who cannot make both days is better placed in the next sprint than half in this one. Recordings support the room; they do not replace it.

Can we run it for more than 20 managers?

Yes, as two sprints, not one larger room. Twenty is where every manager's job description still gets reviewed in front of the group; above that, the method turns into a lecture.

How do you decide whether a department is ready?

A 12-factor readiness score, taken on Day 1. 0 to 17: not ready, and the program tells you what to fix first. 18 to 27: hire in delegate mode (it does the work, a person approves each run). 28 to 36: ready for more autonomy; the program still onboards in delegate mode, and the 30-day follow-through decides whether it moves up.

What stops an AI employee from acting alone?

The leash: approvals, logging, evaluation, a kill switch, and personal data handled under PDPL. Every employee has a named supervisor on a signed oversight sheet. No name, no autonomy.

Where does the first AI employee go to work?

Into work nobody on the team does today, never into someone's job. We start from four questions: what does your team keep postponing, what do you wish someone did, where do you pay an outside firm, and where is AI simply better? Then four checks before it runs further: is it reversible, can it be checked, is it bounded, and who signs? One no, and it stays in delegate mode.

Build AI-Native Employees for Teams in Claude Starting at $15,000 per sprint

Do we need the managers' program, Hire AI-Native Employees Safely (C2), first?

It helps, because the employees are built under the standard your managers set there. If you have not run it, the first morning sets a working standard for the room and we note what the managers still need to decide.

Whose accounts and data does it run on?

Yours. Every seat is set up on the team's own tools and files from day one, with access and permissions agreed with your IT before the room opens. Nobody builds in a sandbox, so nothing has to be rebuilt afterwards.

What if a team member cannot attend all three days?

The seat is for one named person for the whole sprint, because the employee they build is theirs to run. A company may reassign a seat between sprints on request; mid-sprint swaps do not work, and we say so up front.

What does the team need before day one?

Claude accounts on your own workspace, the function's real documents (the ones the job is actually done from), and one manager who will own the department brain afterwards. A one-page setup checklist goes out at signature.

Who maintains the employees after the three days?

Your team. Each employee is documented as it is built, the shared department brain lives in your account, and Demo Day is where every one of them is shown running. Nothing depends on SMOrchestra staying.

What does 'starting at $15,000' cover for a team sprint?

The program as described for one sprint of up to 20, with the materials, the recordings and the 30-day follow-through. The number of functions, the delivery language and on site or remote set the final figure, which the scoping call fixes before anything is signed. Travel and venue are excluded.

Build an AI-Native Revenue Engine for Teams in Claude Starting at $15,000 per sprint

Which CRM does it need?

The one you run. The engine is built on your own stack, and SalesMfast, our own CRM and marketing automation platform, is available if you would rather start clean. Either way the accounts are loaded and the first campaigns run before Demo Day.

Who should be in the room for the revenue engine?

The people who carry the number and the people who do the work: the CRO or head of sales, marketing, sales operations, and the two or three people who actually run outbound and follow-up today. Up to twenty seats.

What if we want SMOrchestra to build the full engine afterwards?

The build starts from the diagnostic you already ran. It is priced as published; program fees do not credit against it.

Is our data safe in the room?

The engine is built on your CRM and your accounts, under your own access controls. An NDA is available before scoping and standard once CRM data is in the room, no lead lists leave your systems, and a sprint never shares a workspace with another company.

How is progress measured after the four days?

By the number that was on the wall on day one: meetings booked from the campaigns wired during the program, read from the reporting the program builds inside your CRM, not from a survey.

What does 'starting at $15,000' cover for the revenue engine?

The program as described for one sprint of up to 20, with the materials, the recordings and the 30-day follow-through. The number of functions, the delivery language and on site or remote set the final figure, which the scoping call fixes before anything is signed. Travel and venue are excluded.

Build Your Agentic Operating System in Claude Starting at $15,000 per department

Which department should go first?

The one with a mandate, a deadline and repeated work that already has a baseline. Operations, finance, service and sales operations are the usual candidates. The scoping call picks it on evidence, not on who asked loudest.

Four weeks or six?

Four when the department's processes are documented and the tools are already connected. Six when the mapping has to be done from scratch or the controls need a risk sign-off before anything runs. The scoping call says which, and the price follows it.

How is this different from having SMOrchestra build it for us?

Same machinery, different hands. In a Build-Operate-Transfer engagement we build and operate it, then hand it over. Here your team builds it with us from week two, so the capability is inside the organisation before handover, not after it.

What does the department keep when the engagement ends?

The running operating system on its own infrastructure, the documentation, the controls the audit function signed, and the people who built it. There is no licence and no monthly fee to SMOrchestra afterwards.

Does it need our IT team?

For one week of it, yes: accounts, access and the connections to your systems are set up with IT in week one, under IT's own approval. After that the department runs it, not IT.

What does 'starting at $15,000' cover for one department?

The program as described for one department, with the materials, the recordings and the 30-day follow-through. The number of functions, the delivery language and on site or remote set the final figure, which the scoping call fixes before anything is signed. Travel and venue are excluded.

Built For Your Organisation, in Claude Starting at $15,000 per engagement

Can you deliver to a government entity or a university?

Yes. Training is the format both already procure, and this program is designed on their processes, regulations and language. A tax invoice with our trade licence and TRN, and a non-disclosure agreement are available, and any subsidy or licensing rule your budget depends on is checked with you at scoping.

Why does it start with a diagnostic?

Because a build plan designed on a guess trains people for work they do not do. One day inside your operation names the functions, the constraints and the regulator, and the program is written from that, not from a brochure.

What does 'starting at $15,000' cover for a custom program?

The diagnostic day, the build plan, the delivery and the 30-day follow-through for one group. Several functions, train-the-trainer or more than one language are scoped on top, and the figure is fixed before anything is signed.

Can you deliver on our LMS or inside our training calendar?

Yes. It runs on your calendar, on site or remote, and the materials are handed over in formats your learning team can load into its own platform. Add train-the-trainer at scoping and the second run does not need us.

How long from the first call to the first session?

Typically four to six weeks: a scoping call, the diagnostic, a proposal with a fixed price, then delivery. Government and university procurement cycles are the usual variable, and we work inside them.

Build Your Claude Business OS $1,750

What is the difference between a prompt, a skill and a plugin?

A prompt is a request you type once. A skill is that request saved, so it repeats with precision. A skill plus connections reaches your actual tools. A plugin, skills and tools and instructions together, holds a whole job. The eight weekly sessions walk you up that ladder on your own work.

Is this the same as the AI employee programs?

No. This builds the operating system underneath: the router, the skill roster and the gate that the whole business runs through. The employee programs staff one function on top of it. Take this first if you want the OS under the employees; neither depends on the other.

Do I need to be technical to build the OS?

No. You need to be the person who knows how the work actually gets done. The connections are configured with permissions and a checklist, not with code, and every step is run on screen before you run it yourself.

Can I buy seats for a team?

Yes, seats are per person. If you want a private delivery built on your company's own stack, that is the corporate track, priced per sprint, and it starts with a scoping call.

What do I actually leave with?

A working operating system on your own files and tools: an onboarding skill that holds your business context, a plain-English router, close to thirty skills across money, customers, sales, marketing and the week, and a gate before anything acts. Not notes, and not a certificate.

Build Your AI-Native Employees in Claude Was $1,750 Now $1,297

What do I need before Week 1?

A Claude Pro or Max account (Max recommended from Week 3) that you already use every day, a laptop, a Gmail or Outlook inbox and calendar you can connect, one real weekly job to hand over, and someone who knows your writing (a colleague, a partner or a friend) for the Week 1 voice blind test.

Will I be taught, or will I build?

You build. Each week ends with something running on your own Claude account, not with a lesson plan. What you learn is a by-product of building the employees, and the foundation, the gates and the recordings stay with you after Week 4, so you can keep building.

Do I need to be technical to build my AI employees?

No. You need to know how your own work gets done. Each employee is configured with permissions and a checklist, not with code, and every step is run on screen before you run it on your own account.

What if I miss a weekly session?

Every weekly session is recorded and stays available for 90 days from Week 1, so you catch up before the next session. The build runs on your own account, so you follow the recording step by step.

Do I need a CRM before I start?

You need somewhere your leads already live. A spreadsheet is enough to start; the Sales Nurture Specialist reads it in Week 3. The employees can be wired to SalesMfast or to the CRM you already run.

Will it write in Arabic the way my customers speak?

Yes. The follow-up specialist is built on your own past messages, so it carries your register rather than a translated one. Arabic and English run side by side from Week 3, when it is built.

Does it send without me seeing it first?

No. The employee drafts, you release. Autonomy is earned per channel, after clean approvals, never by default.

What if my employee is not finished by Week 4?

All three are designed to run by the end of Week 4. If one needs more work, you have 4 weeks of async support after Week 4 and the recordings for 90 days to finish it.

Is this the same as the marketing department program?

No. This one fills three founder seats: the assistant, the follow-up and the posting. The marketing program builds a department of three specialists who hand work to each other, which is a different thing and priced differently. Same method, different shape.

Why isn't this one price?

Because Week 1 stands on its own. Some people want the brain and the first skill; others want the employees.

What do I actually walk away with after each week?

After Week 1: your business brain, your voice file and one working skill. After Week 2: connectors to your own inbox and calendar, your first plugin, and the Founder's Personal Assistant, built and customised end to end, producing your morning brief. After Week 3: the foundation installed and the Sales Nurture Specialist running, with one scheduled run. After Week 4: the Social Media Specialist running, a signed permissions sheet per employee, Demo Day and your own 20-step map.

What happens to the recordings, and for how long?

Every weekly session is recorded, and the recordings stay available for 90 days from Week 1. That is the window to rewatch anything you want to run again. Full terms live on the Sprint terms page.

Can I cancel the four weeks?

Yes. Within 7 days of booking you can cancel for a full refund, as long as you have not accessed the program's digital materials or attended a live session. The full rule is section 3 of the sprint terms.

Build Your AI-Native Marketing Department Inside Claude $2,750

Why is this program on a waitlist?

The first sprint is dated against real demand rather than a guess. Join the waitlist and the date is set from what the list asks for. The build plan and the price are final either way.

Do I need an audience already?

No, but you need channels you control. The inbound specialist publishes where you already are. If you have no channel at all, open one first; Master Claude is the right start while you do.

Does it publish without my approval?

Not by default. Every draft stops at your gate. You can open the gate per channel once you trust the output, and the method opens one channel first.

Why does this cost more than the founders' program?

Because three specialists are not three of the same thing. Each is built for a job the others do not do, and what you own is the work that passes between them: the outbound specialist finds the signal, the strategist turns it into a brief, the inbound specialist publishes against it. The handoffs are the department, and they are what you are buying.

What if a specialist is not live by the last week?

The method opens one channel first, so you finish that channel before you add the next, and every specialist follows the same build.

Build Your MicroSaaS in Claude $3,500

What if I cannot name a subscription to cancel?

Then this is not your rung yet. Take the two-minute quiz; it usually routes people in that position to Build Your OS first. The entry rule exists because the savings baseline is what makes the last week real.

Who owns the software at the end?

You do, completely. It is deployed to your own repository and your own hosting from week five, and the operating system that produced it is packaged and handed to you in week eight so you can retire the next tool alone.

Do I need engineers on my team?

No. You need someone who knows the workflow and will be in the room; Claude Code writes the code inside the program's review gates.

What does it cost to run afterwards?

Hosting and API usage. The calculator above assumes about $300 a month per deployment for a small team: an SMOrchestra estimate, not a quote, shown beside the result. Your own numbers depend on your usage.

Is eight weeks really enough?

For one system, yes, because the scope is one subscription and the architecture is scored at a gate before any code is written.

Build Your AI-Native Revenue Engine in Claude Was $6,500 Now $5,700

How is this different from the $39,000 build?

Who holds the keyboard. At $5,700 you build it yourself in twelve weekly co-build sessions. At $39,000 SMOrchestra builds it, operates it with your team and transfers it, with up to three channels wired and both languages production ready.

Do I build all thirteen motions?

No. You build one: the diagnostic routes you to the motion that fits your product, your readiness and your history, and may name a second for later. Building all thirteen is how teams stay busy without producing pipeline.

What do I need before the first session?

Your own Claude plan (Max is recommended for this program), access to the tools your motion will run on, such as your CRM and your sending channels, and one product you sell today. The weekly sessions run on Microsoft Teams, and week 8 connects your tools so Claude executes rather than advises.

Why only ten seats?

Because weeks nine to twelve are hot seats on your own pipeline, and a room larger than ten stops being a hot seat. One room, twelve weeks, all build and no filler.

What if my pipeline is not ready in week one?

That is what weeks one and two are for. The diagnostic runs on what you have, and the 72-hour plan is the readiness work. If you have nothing to sell yet, take the 2-minute quiz before you book; it routes you to the right rung.

Does the program shorten a later build?

It shortens the start, not the price. The diagnostic has already run on your business, and sprint fees do not credit against a build.

Can I cancel the revenue engine program?

Yes. Within 7 days of booking you can cancel for a full refund, as long as you have not accessed the program's digital materials or attended a live session. The full rule is section 3 of the sprint terms.

How much of my time do the twelve weeks take?

One live 3-hour co-build session a week, plus about three hours of building on your own accounts between sessions. Each session builds one part of the engine on your real pipeline.

Build Your AI-Native Dev Department Inside Claude $12,000

Which three people should we send as directors?

The person who decides what gets built, the person who owns delivery, and the person who says a release is acceptable. Titles vary; those three decisions do not. The other seats are for the team that will request, review and adopt.

Does this replace our engineers?

It changes what they do. The seats the operating system holds are the production of specs, code, tests and documentation. The humans keep the decisions: scope, architecture, the ten percent that touches money or security, and acceptance.

Do the tools run on our own infrastructure?

Yes. The operating system is installed on your repositories and your pipeline in weeks three and four, and both tools deploy to hosting you own. Nothing you build here lives on our accounts.

What about security sign-off?

It is a checklist a non-engineer can run, and it is a gate in week six rather than a review at the end. Secrets handling, backups, access review and an audit log are part of the skeleton, not an afterthought.

How do we start?

With a scoping conversation, because this is a company-only sprint built on your stack. Book fifteen minutes and we scope the seats, the two tools and the dates.

The other door

Rather have us build it?

Start with a one-day audit, Revenue & GTM or AI. $1,500 each, credited in full against the matching build signed within 60 days.