You leave with: A running department operating system in Claude on your infrastructure, operated by your own people, with the documentation and controls behind it.
Four to six weeks turning one department's way of working into an operating system that runs, with your people supervising instead of executing. The same machinery behind our Build-Operate-Transfer engagements; here your team builds it with us.
4 to 6 weeks, guided build. One department. Your people, your infrastructure. per department. 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.
Same model in both cases. The box in the middle is the difference.
9 assets in 4 to 6 weeks. Every one is a file, a connection or a running system on your own account, and you keep all of it.
3 of 9 assets built
6 of 9 assets built
9 of 9 assets built
Bring the real thing. Real subscription, real pipeline, real backlog. Nobody builds a demo.
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
This program feeds Build-Operate-Transfer: the next department, built with you, from $16,000. 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 Build-Operate-Transfer: the next department, built with youEvery 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.
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.
Registered member of the Claude Partner Network. Master NLP certified, with a focus on driving innovation and change inside organisations.
Name the program and your organisation. No deck, no call booked yet.
A short brief: what the program builds for you, the seats, the from-price, the dates we can hold.
Room, language, on site or remote, and the number, fixed. Then a tax invoice, 50 percent on signature.
The one with a mandate, a deadline and repeated work that already has a baseline. Operations, finance, service and sales operations go first most often. The scoping call picks it on evidence, not on who asked loudest.
Four when the department's processes are documented and the tools are already connected. Six when the mapping has to be done from scratch or the controls need a risk sign-off before anything runs. The scoping call says which, and the price follows it.
Same machinery, different hands. In a Build-Operate-Transfer engagement we build and operate it, then hand it over. Here your team builds it with us from week two, so the capability stays inside the organisation from the first day, and the fee is credited toward the next department if you want us to build that one.
The running operating system on its own infrastructure, the documentation, the controls the audit function signed, and the people who built it. There is no licence and no monthly fee to SMOrchestra afterwards.
For one week of it, yes: accounts, access and the connections to your systems are set up with IT in week one, under IT's own approval. After that the department runs it, not IT.
Start with the Revenue and AI Audit. One day, $1,500, credited in full against any build.