Corporate · Program 3 · Teams · Can my team work this way?

Build your AI-native employees in Claude. Twenty working employees are the proof.

You leave with: One AI-native employee per participant, running in Claude on the function's real work, with a shared department brain behind them.

Three days with a working team. Every participant hires, briefs and deploys an AI employee on the function's real work, under the standard set in program two.

Starts with the free intro: Applied AI for Everyone

Scoped with youfrom $30,000 per cohort

3 days. Up to 20 seats. On your own systems and data. per cohort, never per seat. Travel and venue excluded. The scoping call fixes the figure before anything is signed.

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

Tax invoice with trade licence and TRN. 50 percent on signature, 50 percent at Demo Day. NDA on request.

3 days
Format
Up to 20
Seats
from $30,000 per cohort
Per cohort, never per seat
How it works

The part of Claude you build.

One AI-native employeeHired, briefed and put to work on real tasks before the session ends
Brainyour context, your standards
Skillsthe jobs it does, written down
Toolsthe systems it may touch
Memorywhat it carries forward
Guardrailsapprovals and limits
Scoreboardthe output you check

Every employee is these six things, or it is a prompt

The build

10 assets, block by block.

10 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. 01Day 1Brain

    The function's work as jobs a machine can hold, and the department brain

    • The function's work mapped into jobs a machine can hold
    • The department brain: standards, templates, exceptions
    • Every seat set up as an operator on the team's own systems

    3 of 10 assets built

  2. 02Day 2Employee

    One employee per person, built live

    • One AI-native employee per participant, hired, briefed and put to work
    • Skills: the jobs it does, written down and tested on live work
    • Tools: the systems it may touch, with approvals and limits
    • The scoreboard: the output each person checks

    7 of 10 assets built

  3. 03Day 3Cockpit

    Handover, and what actually came off the team's plate

    • Handover: how work moves between human and employee
    • Measuring what actually came off the team's plate
    • Demo Day in front of your executives, and 30 days of supervised use after

    10 of 10 assets built

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

What your finance team will ask for.

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

Ship or retake: if the capstone does not pass the Demo Day gate, the cohort reruns at no charge. Score gates before every block, and a Demo Day your executives attend.

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

What this feeds

This program feeds The Revenue Operating System build, $7,500 per process. 100 percent of the program fee is credited toward it, 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 The Revenue Operating System build
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
Gulf conversion vendorPublished case studyLive KSA contact centre vendorPublished case studyLive US AI scale-up entering MENAPublished case studyLive

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 runs the room

Mamoun Alamouri

Sixteen years working with AI, from speech and conversational systems inside Google, Cisco, Avaya and Uniphore 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.

I spent 14 years building AI before AI had a brain. The moment it got one, I rebuilt everything around it.
Built
20+ software products built AI-native, and 100+ operating systems created and deployed with AI.
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
Owns a marketing agency built on the model that replaces agencies: systems clients own, not retainers.

Registered member of the Claude Partner Network. Master NLP certified, with a focus on driving innovation and change inside organisations.

After you ask

Three steps, one business day to the first.

01

You ask

Name the program and your organisation. No deck, no call booked yet.

02

We reply within one business day

A short brief: what the program builds for you, the seats, the from-price, the dates we can hold.

03

One scoping call, thirty minutes

Room, language, on site or remote, and the number, fixed. Then a tax invoice, 50 percent on signature.

FAQ

Questions, answered.

Do we need program two first?

It helps, because the employees are built under the standard your managers set there. If you have not run it, the first morning sets a working standard for the room and we note what the managers still need to decide.

Whose accounts and data does it run on?

Yours. Every seat is set up on the team's own tools and files from day one, with access and permissions agreed with your IT before the room opens. Nobody builds in a sandbox, so nothing has to be rebuilt afterwards.

What if a team member cannot attend all three days?

The seat is for one named person for the whole cohort, because the employee they build is theirs to run. A company may reassign a seat between cohorts on request; mid-cohort swaps do not work, and we say so up front.

What does the team need before day one?

Claude accounts on your own workspace, the function's real documents (the ones the job is actually done from), and one manager who will own the department brain afterwards. A one-page setup checklist goes out at signature.

Who maintains the employees after the three days?

Your team. Each employee is documented as it is built, the shared department brain lives in your account, and Demo Day is where every one of them is shown running. Nothing depends on SMOrchestra staying.

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.

Where to go next