Build your Claude business OS. Close to thirty working skills are the proof.
You leave with: A Claude business OS you own: a router, close to thirty skills, and a gate before anything acts.
- 8 weeks
- One live 3-hour session a week
- Live on Microsoft Teams
- In English
- $1,750
Eight weeks, one live 3-hour co-build session a week. You master the operator layer, you package what you build into a plugin your team can run, then you assemble the operating system itself: close to thirty skills across money, customers, sales, marketing and the week, behind one plain-English front door and an approval gate.
Your Claude business OS, built in 8 weekly sessions across Brain, Skills, Tools, Cockpit.
Join the waiting list. Dates reach the list first.
No dates are set for this program yet. The price and the build below are final; the first sprint is dated from the list, and the list hears before anyone else.
Build Your Claude Business OS
$1,750
8 weeks, one live 3-hour co-build session a week, in English. Waiting list open. Arabic training for individuals runs at Entrepreneurs Oasis.
The waiting list is open. Dates go to the list first, before they are published.
- 8 live co-build sessions, one a week, 3 hours each
- Built on your own accounts, so it is yours the day it runs
- 12 assets handed over across the weeks
- Every session recorded
Built for one kind of operator. They leave owning the system.
Built for
Owners and operators running a whole business out of a chat window
What you leave with
A Claude business OS you own: a router, close to thirty skills, and a gate before anything acts.
8 weeks. One live session a week.
We build it together in one 3-hour co-build session a week, on your own accounts. Each week names what you build and what ships before you leave the session.
Week 1Brain
The project brain
Ships: Your rules, voice and definitions in one project brain
What ships (2)
- The project brain: your rules, your voice, your definitions
- Your operating vocabulary, so a term means one thing every time
Week 2Brain
Context, in the right order
Ships: Context files Claude reads in order, and a measured before-and-after
What ships (2)
- Context files structured so Claude reads them in the right order
- A before-and-after on the same request, measured
Week 3Skills
Skills, one job at a time
Ships: Your first skills, each doing one thing well
What ships (1)
- Skills authored one job at a time, each doing one thing well
Week 4Skills
The plugin that carries them
Ships: A versioned plugin your team can install
What ships (1)
- The plugin that carries them, versioned and installable by your team
Week 5Tools
Connections, and the gate
Ships: Connections with permissions set first, and the scoring gate
What ships (2)
- The connections your skills need, with permissions set before anything runs
- The scoring gate that stops a bad output before anyone sees it
Week 6Cockpit
Onboarding and the router
Ships: Your business context captured once, and a plain-English front door
What ships (2)
- The onboarding skill that captures your business context once, not every session
- The router that turns plain English into the right workflow: say the problem, get the skill
Week 7Cockpit
The skill roster
Ships: Close to thirty skills across the business
What ships (1)
- Close to thirty skills across money, customers, sales, marketing, the week, and people
Week 8Cockpit
The capstone: the Gulf week built in
Ships: Your SME OS assembled and running, with the Gulf week built in
What ships (1)
- The Gulf week built in: your working week (Monday to Friday in the UAE, Sunday to Thursday in Saudi Arabia), VAT and zakat, Arabic first, WhatsApp as a channel
Not a mockup. The system, running.
Screens from our own workspace, where the same system runs SMOrchestra.
Yours is built on your own accounts, with your data, during the weeks above. Open any screen to see it full size.
Why no is the expensive answer.
- The OS you build in class is the kind of system we build for clients as an AI-Native Revenue Operating System, at $7,500 a process. You build the first one yourself.
- A prompt library does not survive contact with a team. An operating system does, and that is the difference you are buying.
Bring the real work: your own accounts, your pipeline, your backlog. Nobody builds a toy example.
Systems that actually run.
Where a card shows a number, its source is on the card. Clients appear by name only where they agreed to be named; external cases cite their public source.
Mamoun Alamouri
22 years in technology, 14 of them inside Google, Cisco, Avaya and Uniphore, and 16 working with AI, from speech and conversational systems to the agentic systems his team ships today. Founder and CEO of SMOrchestra.ai and founder of Entrepreneurs Oasis, an SMOrchestra company. MBA, University of Leicester; BEng Computer Engineering, University of Jordan. He teaches the room himself.
The moment AI got a brain, I rebuilt everything around it.
- Built
- 11 MicroSaaS products shipped, and 100+ operating systems created and deployed.
- Track record
- Grew an AI company's MEA business from zero to $12M in two years.
- Revenue
- Autonomous inbound, outbound and agentic sales, running on live pipeline.
- Practitioner
- Runs his own agency on the model he sells: systems clients own, not retainers.
Master Practitioner of Neuro-Linguistic Programming, focused on leading change inside organisations.
SMOrchestra is a registered member of the Claude Partner Network (see the proof).
Questions, answered.
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.
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.




