Every question, answered once.

No. Every step is scripted and every prompt is provided on screen. A person who has never typed anything into an AI tool can follow along and get the same result.

The recording is included with every seat. The capstone is a build you run yourself, so it works from the recording, and the next cohort is open to you at no cost if you want the live room.

Yes. 100 percent of the $297 is credited toward any SMOrchestra build signed within 90 days of the session. The credit terms are on the academy terms page.

Both, as separate cohorts. The Arabic cohort runs in Arabic with the same curriculum and the same capstone. Pick your language at enrollment.

You get one AI employee running on your own Claude account, on a job you do every week. A certificate is issued only after it passes the quality gate, because the working employee is the proof and the certificate is not.

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 three evenings walk you up that ladder on your own work.

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. Many people take this first because the OS is what the employees stand on, but neither depends on the other.

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.

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 cohort, and it starts with a scoping call.

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.

You need somewhere your leads already live. A spreadsheet is enough for day one. The employees are wired to SalesMfast during the program, and a trial workspace comes with your seat.

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 day two.

Only if you decide it should. The default is an approval gate: the employee drafts, you release. Teams usually move to unattended sending on the follow-up sequence once they have watched it for a week.

The ship-or-retake guarantee applies. Attend every day, submit the milestone artifacts, and if you have not deployed a working employee through the Demo Day gate, you retake the next cohort free, with two hours of private remediation.

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.

Because the three steps aren't the same thing sold three times. Step one teaches you the operator skill. Step two builds the hands and the tools, the skills, plugins and MCP connections every employee runs on. Step three assembles the employees, live, on your own accounts. Pricing them the same would hide that each one hands you more than the last. Buy one step at a time, or buy all three as a bundle at the early-bird price through November 3, either way you pay for what that step actually gives you.

After step one: the employee brain file, the context and rules layer every employee you build afterward has to obey, and the skill of operating Claude yourself. After step two: the skills and plugins built, and the MCP connections wired to your own tools, Gmail, Chrome, Exa and Firecrawl among them. After step three: two of the three employees built live on your own accounts, the third's foundation completed through the guided path, and the session recordings, yours to keep. You keep what steps one and two gave you even if you stop there.

Four weeks of session recordings come with step three, starting when your cohort's step-three sessions run. That's the window to rewatch anything you want to run again, or catch a detail you missed live. Full terms live on the Academy terms page, the same terms that cover every guarantee and credit on this site.

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

No, but you need channels you control. The inbound specialist publishes where you already are. If you have no channel at all, start at Hire Your First AI Employee in Claude and build that channel first.

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

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.

The same ship-or-retake terms as every rung. Attend, submit the artifacts, and if no specialist is live through the Demo Day gate you retake free with two hours of private remediation.

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 week five real.

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

No. GreenLeaf, a client build by SMOrchestra, replaced $100,000 a year of rented software with $300 a month of owned software at 55 people and no software team. You need someone who knows the workflow and will be in the room.

Hosting and API usage, which is where the $300 a month figure in the GreenLeaf case comes from. Your own numbers depend on your usage; the calculator on this page estimates them from your inputs and shows the assumption it used.

For one system, yes, because the scope is one subscription and the architecture is scored at a gate before any code is written. The guarantee covers you if it is not: attend, submit the artifacts, and retake free with two hours of private remediation.

Who holds the keyboard. At $6,500 you build it with guidance across twelve weeks. 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.

No. The diagnostic routes you to the one or two that fit your product, your readiness and your history. Building all thirteen is how teams stay busy without producing pipeline.

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.

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. Founders who arrive with nothing to sell are the ones we route elsewhere at the quiz.

Yes, 100 percent toward any SMOrchestra build signed within 90 days of Demo Day, and graduates skip Phase 0 because the diagnostic has already run. The terms are on the academy terms page.

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.

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.

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

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

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

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.

The room decides it: a board of six in one city costs less to run than a regional executive committee of fifteen with pre-reads in two languages. The scoping call fixes the number before anything is signed.

The oversight model is yours, and it becomes the standard every later program builds under. Most boards send their managers to Hire AI Safely next, so the rule the board wrote is the rule the managers apply.

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.

Yes. The full session fee is credited toward the AI Audit or any build signed within 90 days. The oversight model you leave with is the first document that audit reads.

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

Two live days, the 30-day follow-through, the materials and recordings, and one delegated job left running. Travel and venue are excluded, which is why the price is 'from'. Pricing is per cohort, never per seat, and the scoping call fixes the figure before you sign.

It produces the part of it that is usually missing: 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.

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 cohort than half in this one. Recordings support the room; they do not replace it.

Yes, as two cohorts, not one larger room. Twenty is where every manager still gets a delegated job reviewed in front of the group; above that, the decision rule turns into a lecture.

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.

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.

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

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.

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.

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.

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.

The 13-motion diagnostic you ran in the program is Phase 0 of the B2B Revenue Engine build, so graduates skip it, and 100 percent of the program fee is credited toward that build within 90 days of Demo Day.

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 cohort never shares a workspace with another company.

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.

The one with a mandate, a deadline and repeated work that already has a baseline. Operations, finance, service and sales operations go first most often. The scoping call picks it on evidence, not on who asked loudest.

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.

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 stays inside the organisation from the first day, and the fee is credited toward the next department if you want us to build that one.

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.

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.

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, a non-disclosure agreement and the KHDA or TVTC pathway are available where a subsidised budget requires them.

Because a curriculum 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.

The diagnostic day, the curriculum design, 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.

Yes. The program is scheduled on your calendar, on site or remote, and the materials can be handed to your learning team with train-the-trainer, so the second run does not need us.

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.