For Owners Doing $500K–$50M

Build the AI-First Business That Runs Without You.

Two days. We rebuild your company around AI so it scales while you step out of the middle of it.

In Person · Brisbane · Aug 31 + Sep 1

From Ben Simkin — 30 years building systems, over $3.1B in tracked client revenue.

Let's see if it's a fit

Book a 20-minute call · founding cohort

First Name *

Email *

Phone *

Company *

Annual Revenue *

Where are you the bottleneck most? *

We'll reply within 24 hours to set up a call.

What this is.

AI First Foundations is a 2-day, in-person workshop in Brisbane (August 31 + September 1) for established owners — you plus one operator each. We take your actual business apart on the whiteboard and rebuild it around what AI can do today.

The goal is one number: drive your Owner Dependency as close to zero as possible — so the business runs and scales without you holding the centre together with both hands.

You leave with a 90-day plan. And you keep the Operator's Beta™ software that measures the number live and keeps score for the 12 weeks after — a two-minute weekly check-in re-scores your beta as the work lands.

What you walk out holding.

Not notes. A build spec and a dated plan — what to delete, what to automate, what to rebuild, and who owns each.

Your Owner Dependency measured on two axes — your effort, and what has to happen live
Three lists: keep, redesign, eliminate — every part of the business sorted
A tech-stack audit: what's load-bearing, what's cosmetic, what's blocking AI
A build spec for the first department you rebuild
A 90-day plan: milestones, owners, definitions of done, dates
One public commitment, made in front of the other founders
The Operator's Beta software to keep — your number, live, week after week
Twelve weeks of running it with the software keeping score — your beta re-scored as the work lands

Let's TalkFounding cohort · just a conversation

Who This Is For

This is for you if:

You own a business doing $500K – $50M+
You have customers, an offer, and revenue (not idea-stage)
You can feel yourself as the bottleneck
You're willing to eliminate before you rebuild
You can bring one operator who'll run the install

Not for you if:

Pre-revenue, no offer yet
Want done-for-you implementation from day one
Looking for LinkedIn content about AI
Already know you're not going to delete anything

Who's running it.

30 years building production systems

First company at 20, sold at 24 for $1.2M

Over $3.1B in tracked client revenue

Helped Kerwin Rae scale past $100M

Canterbury Services: $35M to $180M

Builds production-grade AI systems daily

I build production-grade AI systems. I also run real businesses. The workshop is what happens when those two rooms are the same room.

The 12-week guarantee.

Do the work — run your snapshot, take the moves your 90-day plan gives you, and do the two-minute weekly check-in inside the software. Follow the system for 12 weeks and your dependence on the business, and the hours it needs from you, will measurably fall.

If you do the work and those numbers haven't dropped by week 12, email us with your record and we refund your investment in full. The only condition is that you actually followed it.

The risk is on us. The measurement is on your screen.

From the room.

Founders on what changed. In their own words.

Let's Talk About AI First Foundations™

Tell us about your business — we'll set up a quick call to see if it's a fit.

First Name *

Email *

Phone *

Company Name *

Annual Revenue *

Where are you the bottleneck most? *

The next step is a quick call to see if it's the right room for you.

Ben

P.S. Your business can't scale past you — not because you're not good enough, but because it was built to depend on you, and nobody told you that dependency was the ceiling. Two days is how we start breaking it.

Let's TalkA quick call to see if it's a fit

For Owners Doing $500K–$50M

Build the AI-First Business That Runs Without You.

Two days. We rebuild your company around AI so it scales while you step out of the middle of it.

In Person · Brisbane · Aug 31 + Sep 1

Let's TalkFounding cohort · just a conversation

First — who's running it.

The rest of this page asks you to rethink how your business is built. It's fair you know who's making the argument.

30 years building production systems

First code at 13; six languages by 16

First company at 20, sold at 24 for $1.2M

Over $3.1B in tracked client revenue

Helped Kerwin Rae scale past $100M

Canterbury Services: $35M to $180M

I build production-grade AI systems. I also run real businesses. The workshop is what happens when those two rooms are the same room.

Here's the promise, up front.

If you do the work and those numbers haven't dropped by week 12, email us with your record and we refund your investment in full. The only condition is that you actually followed it — the system cannot move a number you never touched.

The risk is on us. The measurement is on your screen.

You already know more than enough. That's not what's missing.

Product-market fit. Systems. Sales. Leadership. You could fill a book about growing a business.

So why isn't it 10x bigger? Not "grown." Scaled.

Here's the test. Picture next Monday. 10x the orders. 10x the inquiries. 10x the work hitting your team's desks.

Could the business absorb it — deliver without you holding the centre together with both hands?

For almost every owner doing $1M, $5M, $10M, even $25M, the honest answer is: the wheels come off in week one.

That's not a capacity problem. It's an architecture problem.

You built something that scales with your hours. Then you ran out of hours. Then you hired people and discovered it now scales with your management of other people's hours. The constraint moved. The dependency didn't.

Owner-dependency is the ceiling. Not the market. Not the offer. Not the team. You. The business's structural dependency on you is the binding constraint on everything else.

I measure this now. Precisely.

Same markets. Same access to capital. Same calibre of operator. Wildly different outcomes. Across years of working with owners at every scale, the variable was never strategy, grit, or talent.

It was a single structural property: how much of the business required the owner to function.

As an engineer, if I can't measure it, I can't move it. So I built a number for it.

Operator's Beta™

β Reading	What It Means
≈ 0	Business runs independent of you
≈ 0.5	You are roughly half the engine
→ 1	Output tracks your personal involvement directly
> 1	Output collapses faster than you withdraw

And here's what surprises people: beta isn't one number. It's two.

Effort Beta (βE): how much of the total human work runs on you personally. Your load.

Presence Beta (βP): how much of that work must happen live. Real-time. On calls. "Only I can decide this right now."

Two owners carry the same workload. One disappears for a month and nothing slows down. The other can't take Wednesday afternoon without three Slack pings. Same effort. Opposite freedom.

Both numbers go on the whiteboard on Day 1.

The ceiling is mathematical, not motivational.

You cannot scale exponentially when your beta is locked above a specific threshold.

Not with more capital. Not with a stronger team. Not with longer hours. Not with better tools. Above that threshold, the math doesn't bend.

Freedom wants near-zero beta because time is finite, non-renewable, and the only resource you can't buy back. Scale requires near-zero beta because human hours are capped and cannot multiply. Both roads converge on the same structural redesign.

Owner-dependency heatmap before — This isn't a diagram. It's beta on a real account inside **Operator's Beta**, the software you keep after the workshop, so the number stays live week after week.

Owner-dependency heatmap after — This isn't a diagram. It's beta on a real account inside **Operator's Beta**, the software you keep after the workshop, so the number stays live week after week.

Let's TalkFounding cohort · just a conversation

Why now. Why AI changes the equation.

Owner-dependency has always been the ceiling. What's new is that for the first time in history, the tools exist to dismantle it without $50M in venture capital.

Before AI, reducing owner-dependency meant one thing: people. Hire an ops manager. Hire a GM. Staff your way out.

That worked if you had the margins. Most owners doing $500K to $10M don't. They're stuck in the gap between "too much work for me" and "not enough margin to hire the team that replaces me."

AI collapsed that gap.

This isn't about productivity. Productivity is a team-level metric. This is about dependency — the structural question of what still requires you.

Two types of owner right now.

Retrofitters bolt AI onto the existing business. ChatGPT for content. Zapier for reminders. Copilot for dev. The org chart stays the same. The offer stays the same. Beta hasn't moved a decimal point.

AI-First Builders asked a different question: If I were starting this company today, knowing what AI can do, what would I build?

Then they built that.

The test: if you removed every AI tool from your business tomorrow, would it still operate in basically the same shape? If yes, you're a retrofitter. The AI is cosmetic, not structural.

The productivity trap.

AI, as pitched to owners, is a productivity tool. Faster emails. Faster content. Faster reports. That's the right frame for your team.

But productivity is not the founder's job. The founder's job is to design the system that produces the work without them in the middle of it. Productivity tools don't touch that.

A faster wheel doesn't free the hamster. It just spins harder.

The AI that changes a founder's week isn't productivity AI. It's architecture AI. Same tools. Different question. Different outcome entirely.

What happens in the room.

We take your business apart on paper. Area by area. Team. Offer. Delivery. Marketing. Sales. Operations.

For each one, the same question: Would I build it this way if I started today?

First pass, everyone's generous. Yeah, that's mostly fine. Second pass is where the real answers live.

~30%

Well-designed.
Keep it.

~50%

Legacy architecture.
Re-engineer it.

~20%

Shouldn't exist.
Delete it.

You leave with three lists: Keep. Redesign. Eliminate. And the sequence you move through them is the whole game:

01 Delete

02 Automate

03 Outsource

04 Delegate

05 Do (last resort)

Every task earns its way down that ladder. Most beta-reduction fails because the owner skipped elimination and automated something that should have been killed. You don't speed up what shouldn't exist.

The Two Days

Day 01

Diagnose

Measure your beta, both axes, live on your actual business. Run area-by-area on each company in the room. Score your team seats on three pillars: self-management, reliability, initiative. Find the wrapper-systems you've built around weak hires and stopped seeing.

Day 02

Design, Plan & Commit

Tech stack audit. Every load-bearing tool: keep, redesign, replace, rebuild. The path decision: full model rebuild AI-first, or start with one department. Build spec drafted, then the 90-day plan. Public commitment in front of the other founders. The act, the owner, the date. Your beta tracked live in the software as the work lands.

What you walk out holding.

Both beta numbers (effort and presence) measured on your real business
The three lists: keep, redesign, eliminate
An honest read on your team. Which seats are real, which are wrapper-systems around weak hires
A tech stack audit: what's load-bearing, what's cosmetic, what's blocking AI
A path decision: full rebuild or department-first
A build spec for the part you're starting with
A 90-day plan: milestones, owners, definitions of done, dates
One public commitment. The act. The owner. The date.
The Operator's Beta software to keep: your beta measured and tracked live, so the number stays honest week after week long after the room

Your own business, diagnosed. With an architecture for the version that scales without you in the centre of it.

The first 12 weeks.

The workshop sets the plan. Then you run it, with the software keeping score: the two-minute weekly check-in re-scores your beta as the work lands, so the number stays honest instead of drifting. Here's what the curve typically looks like.

Owner Dependency (β) Over 12 Weeks

Week 0 is when you walk in. Week 12 is when you become the case study.

Bring the person who's going to run it.

Your seat includes you plus one team member. Pick the operator whose name will be on the 90-day plan. Ops lead. Sales lead. Delivery lead. Whoever runs the department you're redesigning first.

They helped build the plan. They own the plan. Don't walk back to a team that wasn't in the room and spend the next month re-selling a framework they didn't experience.

Who This Is For

This is for you if:

You own a business doing $500K – $50M+
You have customers, an offer, and revenue (not idea-stage)
You can feel yourself as the bottleneck
You're willing to eliminate before you rebuild
You can bring one operator who'll run the install

Not for you if:

Pre-revenue, no offer yet
Want done-for-you implementation from day one
Looking for LinkedIn content about AI
Already know you're not going to delete anything

From the room.

Founders on what changed. In their own words.

Founding Cohort

Three Access Tiers

One-time investment, not a subscription. The tier that fits you — and the exact number — is walked through in the chat or on the 20-minute call.

Brisbane · Aug 31 + Sep 1 · applications open

Let's TalkA call to see if it's a fit

This is the founding cohort. You become a named case study at week 12: beta-before, beta-after, one shipped install. Apply below and we'll talk to make sure it's the right fit, both ways.

What Happens After You Apply

You complete the form

Tell us about your business and what you're looking to change.

We review it

To make sure the room is the right fit.

We schedule a call

20 minutes to discuss your business.

If it's a fit

We lock your seat and send everything you need.

Applying doesn't commit you to anything.

Let's Talk About AI First Foundations™

Two quick steps, then a call to see if it's a fit.

Email *

Annual Revenue *

First Name *

Phone *

Company Name *

Where are you the bottleneck most? *

The next step is a quick call to see if it's the right room for you.

Ben

P.S. Your business can't scale past you. Not because you're not good enough. Because it was built to depend on you, and nobody told you that dependency was the ceiling. The whole goal of these two days is to drive your Owner Dependency as close to zero as possible. That's what breaks the ceiling.

P.P.S. Skip-to-the-end version. Two days. Brisbane, August 31 + September 1. You + one operator. Walk out with: beta on both axes, three lists, build spec, 90-day plan, one public commitment. Founding cohort, applications close once it's full.

Let's TalkScroll to the form