Build a dev department inside Claude. Two tools in production are the proof.
You leave with: An AI-native dev department you own inside Claude: three directors, one OS, two tools live.
- 8 weeks
- One live 3-hour session a week
- Live on Microsoft Teams
- In English
- $12,000
Eight weeks, one live 3-hour co-build session a week. Three directors trained on Claude, one operating system installed on your repositories, two internal tools live. Directed by people, run by Claude.
Your dev department, built in 8 weekly sessions across Brain, Skills, Tools, Employee, 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 AI-Native Dev Department Inside Claude
$12,000
8 weeks, one live 3-hour co-build session a week, company-only sprint. 20 seats included, $400 per extra seat. Waiting list open.
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
- 24 assets handed over across the weeks
- Every session recorded
Built for one kind of operator. They leave owning the system.
Built for
CEO, COO or CTO with between zero and ten engineers
What you leave with
An AI-native dev department you own inside Claude: three directors, one OS, two tools live.
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 department on paper
Ships: A company tooling audit and your backlog scored
What ships (2)
- A company-wide subscription and tooling audit
- Your backlog scored on what a department could actually clear
Week 2Brain
The roadmap and the charter
Ships: A 12-month replacement roadmap and the department charter
What ships (2)
- A 12-month replacement roadmap with sequencing
- The department charter: roles, gates and the autonomy dial
Week 3Skills
Install the factory and the architect
Ships: The factory and architect systems on your repositories
What ships (2)
- The factory system installed on your repositories
- The architect system, so a spec exists before code
Week 4Skills
Engineering and security systems
Ships: Your review gates encoded, and security running before any merge
What ships (2)
- The engineering system, with your review gates encoded
- The security system, running before anything merges
Week 5Tools
Tool one, spec to skeleton
Ships: Tool one as a live skeleton, with the directors' first gates passed
What ships (4)
- Tool one taken from spec to a live skeleton
- Your pipeline and workspace wired into the department
- The three directors passing their first real gates
- The escalation path when a gate fails
Week 6Employee
Tool one live, tool two specced
Ships: Tool one in production with security sign-off
What ships (4)
- Tool one in production with security sign-off
- Tool two specced by your Product Director, without the instructor
- The review record that proves the gates were used
- Cycle time measured on both tools
Week 7Cockpit
Tool two live, and the SOP book
Ships: Tool two live and the operating procedures adapted to you
What ships (4)
- Tool two live on your own hosting
- The operating procedures adapted to your company, not ours
- The adoption playbook run on tool one
- A named owner per system, with a deputy
Week 8Cockpit
Demo Day, and the hiring plan reversed
Ships: Both tools demoed, and a plan for what to hire instead
What ships (4)
- Both tools demoed to the chief executive
- Savings and cycle time on the scoreboard
- The reversed hiring plan: what to hire instead of a dev team
- The next six months of backlog, sequenced by the department
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.
Software used to need a team. Now it needs three people.
SMOrchestra AI-Native Dev framework, 2026. Percentages are the share of the seat's output the operating system produces, not a headcount cut.
Five systems and the factory that makes them.
Named, versioned, and yours. This is the same machinery behind the Entrepreneurs Oasis dev organization.
Dev Brainstorm and Roadmap Factory
Idea and gap finder, scoring and roadmapping: turns what should we build into a scored, sequenced roadmap
Architect OS
Interview to requirements, data model, flows and screens, spec and handover file, scored at a gate before anything is coded
Engineering Dev OS
More than 40 development skills and 20 operating procedures: spec-driven build, tests, review, refactor, release, documentation
Production and Security OS
Production skeleton with authentication, roles, multi-tenant, billing and audit log, plus security procedures for secrets, backups, checks and access reviews
Launching Pad optional
Distribution and monetization: landing, onboarding, pricing, first customers
Meta OS
The factory: interview, generate context files, skills and templates, lint and score
SMOrchestra AI-Native Dev framework, 2026. The same machinery running the Entrepreneurs Oasis dev organization.
What are you renting?
Three subscriptions, your seats, and your backlog. The figures update as you type.
Why no is the expensive answer.
- $12,000 is about two months of one mid-level engineer's fully loaded cost in Dubai or Riyadh.
- Two internal tools ship inside the program, so the first savings land before the program ends.
- The chief executive sees the demo, not a slide.
Bring the real work: your repositories, your backlog, the subscriptions you want gone. 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.
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.
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.




