5 · The whole department, directed by three people.

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.

Six weeks. Three directors trained on Claude, one operating system installed on your repositories, two internal tools live. Directed by people, run by Claude.

Next cohort$12,000, up to 20 seats

6 weeks, company-only cohort. Up to 20 seats, $400 per extra seat.

This cohort is scoped to your company, so it starts with a conversation.

Corporate invoice available. Two-instalment card option on request.

I acknowledge that course access and digital assets are provided immediately, waiving statutory withdrawal periods. Academy terms

Company-only cohort
Format
6 weeks
Duration
$12,000
One time, no subscription
How it works

Six hats, one repository, one quality bar inside Claude.

A department is not a pile of prompts. It is roles with a repository between them and an operating system underneath, which is why the second diagram belongs on this page too.

The operating system between your command and Claude's output: context files, settings, workspace, templates, skills, plugins, MCPs and CLIs
The operating system between your command and Claude's output: context files, settings, workspace, templates, skills, plugins, MCPs and CLIs

Diagrams from Mamoun Alamouri's published explainer series. They are the same model this program teaches you to build against.

The build

24 assets, block by block.

24 assets in 6 weeks. Every one is a file, a connection or a running system on your own account, and you keep all of it.

  1. 01Week 1Brain

    The department on paper

    • A company-wide subscription and tooling audit
    • Your backlog scored on what a department could actually clear
    • A 12-month replacement roadmap with sequencing
    • The department charter: roles, gates and the autonomy dial

    4 of 24 assets built

  2. 02Week 2Skills

    Install the operating system

    • The factory system installed on your repositories
    • The architect system, so a spec exists before code
    • The engineering system, with your review gates encoded
    • The security system, running before anything merges

    8 of 24 assets built

  3. 03Week 3Tools

    Tool one, spec to skeleton

    • 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

    12 of 24 assets built

  4. 04Week 4Employee

    Tool one live, tool two specced

    • 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

    16 of 24 assets built

  5. 05Week 5Cockpit

    Tool two live, the SOP book

    • 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

    20 of 24 assets built

  6. 06Week 6Cockpit

    Demo Day, and the hiring plan reversed

    • 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

    24 of 24 assets built

The 6 blocks of Build Your AI-Native Dev Department Inside Claude, each showing the layer of Claude it installs and the assets it hands over
All 24 assets of Build Your AI-Native Dev Department Inside Claude, and the layer of Claude each block installs. Swipe across the board.
Receipts

Not a mockup. A screenshot.

An organization chart of AI agents: a chief executive, a marketing lead, a VP of engineering, a quality lead and six engineers, each a running agent rather than a chat session
An organization chart of AI agents: a chief executive, a marketing lead, a VP of engineering, a quality lead and six engineers, each a running agent rather than a chat session
An agent closing a ticket and acquiring an environment lease beside a human's own activity, with success rate and task charts
An agent closing a ticket and acquiring an environment lease beside a human's own activity, with success rate and task charts

Built on the same operating systems you install in this program. Mamoun Alamouri's workspace, August 2026. Not graduate work.

The seats

Software used to need a team. Now it needs three people.

100% Business analyst What the human keeps: Says yes or no to the scope
90% Architect What the human keeps: Signs the architecture and the data model
90% UX What the human keeps: Picks between rendered options
90% Engineering What the human keeps: Reviews at gates, decides the 10 percent that touches money or security
80% QA What the human keeps: Accepts the release
90% Product owner What the human keeps: Owns the roadmap decision, not its production

SMOrchestra AI-Native Dev framework, 2026. Percentages are the share of the seat's output the operating system produces, not a headcount cut.

The stack

Five systems and the factory that makes them.

Named, versioned, and yours. This is the same machinery behind the Entrepreneurs Oasis dev organization.

1

Dev Brainstorm and Roadmap Factory

Idea and gap finder, scoring and roadmapping: turns what should we build into a scored, sequenced roadmap

Replaces: Business analyst, product owner

You own: Every rented tool and every request scored on fit, cost, data ownership and workflow mismatch, with a 12-month replacement roadmap

2

Architect OS

Interview to requirements, data model, flows and screens, spec and handover file, scored at a gate before anything is coded

Replaces: Business analyst, architect, UX

You own: Your context files, security and data conventions and brand system baked in, so every spec passes a gate before it reaches the build

3

Engineering Dev OS

More than 40 development skills and 20 operating procedures: spec-driven build, tests, review, refactor, release, documentation

Replaces: 90 percent of engineering, 80 percent of QA

You own: Installed on your repositories and your pipeline, with the procedures defining how the department works so it survives any individual

4

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

Replaces: The operations and security baseline

You own: Every internal tool starts at production grade rather than at demo, and security sign-off is a checklist a non-engineer can run

5

Launching Pad optional

Distribution and monetization: landing, onboarding, pricing, first customers

Replaces: Growth

You own: An internal adoption playbook, or, if a tool is good enough, sell it to peers as a MicroSaaS and turn a cost centre into a product

6

Meta OS

The factory: interview, generate context files, skills and templates, lint and score

Replaces: The systems engineer

You own: Generates the operating system for every new build, so the company owns the means of production

SMOrchestra AI-Native Dev framework, 2026. The same machinery running the Entrepreneurs Oasis dev organization.

The number

What are you renting?

Three subscriptions, your seats, and your backlog. The figures update as you type.

0Yearly rent
0Estimated owned run cost, yearly
0Payback
0Backlog cleared at AI-native speed

Owned run cost is an estimate, not a quote. It uses the GreenLeaf pattern as its basis: $100,000 a year to $300 a month for a 55-person deployment. Source: GreenLeaf, SMOrchestra client.

The arithmetic

Why no is the expensive answer.

Bring the real thing. Real subscription, real pipeline, real backlog. Nobody builds a demo.

Ship-or-retake guarantee

If you attend all scheduled sessions, submit the milestone artifacts, and do not deploy a working system through the Demo Day quality gate, you receive free enrollment in the next cohort plus two hours of private technical remediation.

No open money-back guarantee. Full terms: Academy terms

Fee credit

Your $12,000 comes off AI-Native Dev Department, built and transferred at Scoped after the AI Audit, in full, if you sign within 90 days of Demo Day.

The credit runs 90 days from Demo Day and applies once, to one build. It is separate from the audit credit, which runs 60 days. Academy terms

See AI-Native Dev Department, built and transferred
Proof

Systems that actually run.

Services firm, 55 people, no software teamOwned software replacing a rented system$100,000 a year to $300 a monthrented software replaced by owned software, 55 people, no software teamSource: GreenLeaf, SMOrchestra clientLive
Domain experts building their first productLaunched MicroSaaS products18 experts, 8 launched, 5 payingunder two weeks from idea to productSource: Entrepreneurs Oasis, wave 1Live
Expert-led business, DubaiA revenue engine wired to live channels20 deliverables in 8 weeksand more than 500 contacts reachedSource: Dubai coach engagement, SMOrchestraLive

Every number above is an outcome from a named engagement, with its source on the card. Client names appear only where the client agreed to be named.

Who teaches it

Mamoun Alamouri

Mamoun Alamouri builds AI-native revenue engines for B2B and expert-led businesses across the Gulf, and has sat in the enterprise seats these systems now hold. The academy teaches the same machinery SMOrchestra installs for clients, on your own accounts instead of theirs.

I have sat in every seat this engine replaces.

Registered member of the Claude Partner Network.

FAQ

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 week two, 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 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.

How do we start?

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.

The other door

Rather have us build it?

Start with the Revenue and AI Audit. One day, $1,500, credited in full against any build.

See the two audits
Where to go next