2a · Rung two. Where you stop operating Claude and start employing it.

Employ Claude, do not operate it. Three working employees are the proof.

You leave with: Three AI-native employees you own, working inside Claude: your day, your follow-up, your feed.

A car needs someone behind the wheel every mile. A plane needs someone who set the heading and can trust the systems to hold it. Three days, one skill pattern built once, three employees assembled from it, and you make that switch on your own accounts.

1$290

Master Claude, build the brain

You leave running Claude like an operator instead of guessing at it, with the one context file every employee you build next has to obey already written.

Enrollment opens when this cohort is dated.

2$390

Build the hands and the tools

You leave with Claude's skills and plugins built, and the MCP connections wired to your own accounts, Gmail, Chrome, Exa and Firecrawl among them, so it can act on your real tools instead of only talking about them.

Enrollment opens when this cohort is dated.

3$1,290

Assemble all three, two live

You leave with the plugin foundation from step two assembled into three employees, one by one: two built live with us in the room, the third finished through the guided path, plus four weeks of every session recorded.

Enrollment opens when this cohort is dated.

Or, the bundle$1,970$1,290

All three steps individually run $1,970. Buy them together and save $680.

First cohort: October 6 to 8, 2026. Early bird through September 20, then $1,750.

Enrollment opens when this cohort is dated.

3 hours a day for 3 days
Format
3 days
Duration
$1,750
One time, no subscription
How it works

Three hires. You build all three in Claude.

An advisor decides, an operator executes, an assistant sits beside you. Confuse them and you hire an advisor, then rage that it did not execute. These three steps build all three shapes, and the second diagram is the six layers each one is made of.

The six layers of an AI-native employee, from the model as the mind to the command you type, with the brain, skills and tool keys as the layers you build
The six layers of an AI-native employee, from the model as the mind to the command you type, with the brain, skills and tool keys as the layers you build

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

The build

13 assets, block by block.

13 assets in 3 days. Every one is a file, a connection or a running system on your own account, and you keep all of it.

  1. 01Step 1 · $290Brain

    The three seats, and the brain they share

    • Your day, your pipeline and your channels mapped as three distinct jobs
    • The context file every employee obeys: offers, objections, tone
    • Your CRM and calendar connected and reading live records
    • Each seat named, with what it is allowed to do without asking

    4 of 13 assets built

  2. 02Step 2 · $390Tools

    The hands and the tools: skills, plugins and MCP

    • The four-part pattern every Claude skill runs on: interview, gather, produce, check
    • How skills bundle into one plugin, versioned and installable by your team
    • MCP and the CLI, explained plainly: the two ways Claude reaches outside the chat
    • The MCP connections wired to your own accounts: Gmail, Chrome, Exa and Firecrawl, whichever your employees need

    8 of 13 assets built

  3. 03Step 3 · $1,290Employee

    The plugin foundation, and the employees built on it, one by one

    • The plugin foundation and the workspace it runs in, ready to assemble into a real employee
    • The first employee, assembled from that foundation and built live on your own accounts
    • The second employee, assembled the same way, one by one rather than all at once
    • The third employee's foundation completed through the guided path afterward
    • The approval gate each employee passes before anything reaches a customer, plus four weeks of every session recorded

    13 of 13 assets built

The 3 blocks of Build Three AI-Native Employees in Claude, each showing the layer of Claude it installs and the assets it hands over
All 13 assets of Build Three AI-Native Employees in Claude, and the layer of Claude each block installs. Swipe across the board.
The platform

You build on what we run.

The employees run on SalesMfast, our own SME CRM and marketing automation platform. You can wire them to a CRM you already run instead; the program works either way, and the subscription is separate from the fee whichever you choose.

Receipts

Not a mockup. A screenshot.

What you build, shown running in our own workspace, grouped by which step it proves.

The three employees, built on one pattern

The employee marketplace showing all three foundation employees, the personal assistant, the sales nurture specialist and the social media specialist, as installable plugin cards under SMOrchestra
The three employees, one Directory. The Personal Assistant, the Sales Nurture Specialist and the Social Media Specialist, published as three named plugins under SMOrchestra, ready to install. Swipe across the shot.
The Personal Assistant plugin detail page: reads the whole inbox each morning, gives three priorities and a decision list, and reports weekly with every figure traced to its source
Employee 1, Founder's Personal Assistant. Your inbox, read and triaged before you're at your desk.
The Sales Nurture Specialist plugin detail page: every lead bucketed cold, warm or hot, follow-up drafted, nothing sent until the founder confirms
Employee 2, Sales Nurture Specialist. No lead goes cold without you deciding it should.
The Social Media Specialist plugin detail page: a publish-ready week in brand and voice, creatives sized per channel, copy past an anti-AI writing gate
Employee 3, Social Media Specialist. A publish-ready week, in your brand, in your voice.

All four drawn from the Social Media Specialist, the representative walkthrough: all three employees run this same pattern underneath.

The hire skill: five questions with ready answers, and the foundation becomes a plugin carrying the owner's own name. Runs once, never ships with the employee
Build step 1, The Interview. Five questions, and the foundation becomes an employee.
The collect skill: gathers every input the run needs and marks every gap, and produces nothing yet
Build step 2, The Eye. It gathers everything first, and produces nothing yet.
The produce skill: turns what the eye gathered into the complete deliverable in one pass
Build step 3, The Hand. One hand, one output: the whole publish-ready week.
The check skill: grades the run against its own checklist, and sends anything under nine out of ten back before the owner sees it
Build step 4, The Scale. It grades its own work, and sends itself back if it fails.

The cadence that keeps a live employee safe

The guide command: one status line naming exactly where the week stands, ready or not, with the missing pieces and the next command to run
Command, the status check. One line tells you exactly where the week stands.
The start command: the one door into the employee, running it stage by stage, waiting for the owner's go-ahead before the next stage
Command, the one door in. One command runs the whole employee, stage by stage.

Mamoun Alamouri's own Claude desktop, August 2026. The build sequence is shown once, from the Social Media Specialist; all three employees run the same four skills underneath.

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

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.

Do I need a CRM before I start?

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.

Will it write in Arabic the way my customers speak?

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.

Does it send without me seeing it first?

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.

What happens if I do not ship all three?

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.

Is this the same as the marketing department program?

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.

Why isn't this just one price?

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 September 20, either way you pay for what that step actually gives you.

What do I actually walk away with after each step?

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 four weeks of session recordings. You keep what steps one and two gave you even if you stop there.

What happens to the recordings, and for how long?

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