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 Demo Day. 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 a published website. A certificate is issued only after the artifact passes the quality gate, because the artifact is the proof and the certificate is not.

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

Yes. The follow-up employee 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 evening 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 evening, submit the milestone artifacts, and if you have not deployed a working employee through the Demo Day gate, you retake the next cohort free plus two hours of private remediation.

No. This one staffs the revenue seat: follow-up, qualification, reactivation. The marketing program staffs the content and campaign seats. Same method, different employees, and each is priced on its own.

The first cohort is dated against real demand rather than a guess. Join the waitlist with your language and your role, 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 Content OS publishes where you already are. If you have no channel at all, start at Claude for Everyone and publish a site 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.

It is optional and built in evening three if your cohort wants it. It reads campaign performance and reports; it does not spend money, and it never touches a budget without a human release.

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

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

No. This builds the operating system underneath. 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 is a prerequisite for 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 Cohort, and it starts with a scoping call.

A working operating system on your own files and tools: a project brain, at least one skill, one live connection, and a scoring gate. Not notes, and not a certificate.

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

Yes, in the UAE and Saudi, and remote for the rest. The cohort is private either way, so the schedule is built around your team rather than a public calendar.

Either, or both. Mixed rooms are common: the delivery is Arabic and the artifacts are bilingual, or the reverse. You choose at scoping.

A tax invoice, our trade licence and TRN, and a non-disclosure agreement if you want one. Terms are 50 percent on signature and 50 percent at Demo Day.

CPD accreditation is in progress, and KHDA or TVTC pathways are available on request where a subsidized budget requires them. We do not claim an accreditation we do not hold.

You keep it and it keeps running, because it was built on your stack from week two. If you want us to extend it across every function, that conversation starts at the Enterprise Engine.