Built to Run · Self-paced course

Build a business that needs a little less of you every month.

Set up AI systems that handle the repeating work, so you can focus on growth. Start today and go at your own pace.

Robert Sanberg. Founder of AIIMN, Owner of WindRider.
lessons in 8 sections
46
downloadable kits
20
department playbooks
5
of AIIMN Community included
6 mo

Proof · What this system did at WindRider, my own business

organic sales growth
≈5X
net margin, same headcount
2X
software expense replaced
$5,000+/mo

My numbers at my company. The course teaches you the same system, built for yours.

The week you actually have

Get back the hours the business takes from you.

Monday morning.

Shopify, then the ad account, then the spreadsheet. Half the morning's gone before you've decided anything.

The uploading.

The idea's yours. The downloading, re-uploading and pasting into three tools still eats hours every week.

Everything waits on you.

Questions that aren't yours to answer land in your inbox, and nothing moves until you get to them.

The laptop at dinner.

Nothing's on fire. There's just always 1 more thing, and you're the one who answers.

What changes first

Start Monday with a finished report, not a pile of tabs.

You build this exact routine for your own business in the course’s opening section. Here it is before and after.

BeforeMonday, the manual way

  • Open the store, the ad account and the spreadsheet.
  • Compare this week to last by eye.
  • Chase anything that looks wrong.
  • Nothing happens until you start.

AfterMonday, built to run

  • The system gathers the numbers from your sources.
  • It compares them to last week and flags what moved.
  • It drafts the summary and queues it for your review.
  • You read a finished report and make the calls that need you.

Proof · Real course screens

The finished weekly advertising review: a table comparing week 1 and week 2 for the Prospecting campaign, with cost per purchase rising from $50 to $75 and each figure cited to its source line.
After
A raw weekly ad export open in a text editor: rows of comma-separated campaign numbers for the fictional Example Outdoor Shop, with the Prospecting row highlighted.
Before
The saved scheduled task for the weekly advertising review, switched on, set to repeat every Monday, with its next run shown.
Every Monday

Set once, repeats every Monday. Screens from Example Outdoor Shop, the course’s fictional demo business.

Why it didn’t stick last time

Get a system that remembers your business and runs on schedule.

If AI faded on you after two weeks, it wasn’t a lack of effort. You were handed prompts, and a prompt gives you one good answer, once.

A system remembers your business, runs on a schedule and waits for your yes. It’s built from five pieces:

  1. Business Brain.What you know about the business, written down once so you stop being the only copy.
  2. Workflows.Small, real, repeating jobs, handed over one at a time.
  3. Agent Team.A drafter, a checker and a researcher, each with a narrow job.
  4. Gates.Nothing ships, spends or sends without your yes.
  5. Operating Rhythm.It all runs on a schedule and gets a little better every week.

Proof · The course diagram for each piece

Show the course diagram for

Business Brain

What you know about the business, written down once so you stop being the only copy.

Shared, current and restricted business information follow different paths into a task. Restricted information passes only if allowed, and only information loaded for the run reaches the task workspace.

Workflows

Small, real, repeating jobs, handed over one at a time.

A saved instruction that runs the weekly job again without the setup conversation

Agent Team

A drafter, a checker and a researcher, each with a narrow job.

Original sources feed a researcher and a checker. The researcher passes evidence notes to the drafter, the drafter passes a draft to the checker, and the checker sends a checked version to owner review, with one correction loop from checker back to drafter.

Gates

Nothing ships, spends or sends without your yes.

Two versions of a weekly brief. Version 1 is approved for one named action. An edit creates version 2, which goes back for a new decision instead of inheriting the old approval.

Operating Rhythm

It all runs on a schedule and gets a little better every week.

A scheduler, a saved instruction, and refreshed sources feed a runner, which loads the instruction and sources and performs the job with set tools, permissions, and limits. The run ends in either a dated result and run record saved for review, or a visible reason it stopped with a named person who can investigate, stop, or restore the job.

It took me two years of getting it wrong to find the order this course follows.

Start here, then six builds

Have one more job off your plate after every build.

This is hands-on building on your own business. Each build leaves something running that wasn’t running before. Take them as a six-week rhythm, or go slower.

Start here · Lessons 0.1 to 0.7

One job off your plate.

Running after this: a weekly job you already do, like your ad review, checked and scheduled to come back with fresh numbers.

Milestone The first time it works on your business.

Get one recurring job off your plate

  1. 0.1Take one recurring job off your plate
  2. 0.2Set up a place where the work can happen
  3. 0.3Explain the job and find the right sources
  4. 0.4Build the prompt together and run your real job
  5. 0.5Check the claims that could change your decision
  6. 0.6Use the result in your business
  7. 0.7Have the next result waiting for you

Where 0.7 leaves you: the job saved, scheduled and checked on its first run.

Section 0’s seven lessons, as titled in the course. You build each one on your own business.
  1. Build 1

    Business Brain

    Running after this: your offer, customers, voice, processes and key numbers in one place, so the job stops guessing about your company.

  2. Build 2

    Repeating Workflow

    Running after this: a saved instruction that runs the job again without the setup conversation. You also open your first Claude Code project.

  3. Build 3

    Three-Lane Agent Team

    Running after this: a drafter, a checker that can send work back and a researcher that shows its sources.

    Milestone You stop running every step. The team works the job while you're doing something else.

  4. Build 4

    Safe Operating Rhythm

    Running after this: approval wherever money, sending or publishing is involved, and your edits turned into lasting corrections.

    Milestone You trust what it's allowed to do.

  5. Build 5

    Two Department Playbooks

    Running after this: the method at work in the two parts of the business that eat most of your week.

    Proof · What one playbook did at WindRider

    Ad creative cost, from about $10 an ad
    Under $0.50
    Ads per week at peak, from about 40, by one operator
    100 to 150
  6. Build 6

    Capstone Business OS

    Running after this: one documented operating system a new hire could read, so it keeps running when you're on vacation.

Every section comes with working files from the 20 kits, so you never start from a blank page.

The full curriculum: 46 lessons in 8 sections
Section 0 · Start hereGet one recurring job off your plate 7 lessons
  1. 0.1Take one recurring job off your plate
  2. 0.2Set up a place where the work can happen
  3. 0.3Explain the job and find the right sources
  4. 0.4Build the prompt together and run your real job
  5. 0.5Check the claims that could change your decision
  6. 0.6Use the result in your business
  7. 0.7Have the next result waiting for you
Section 1 · Build 1Start with your business and its information 5 lessons
  1. 1.1Start with the operation you actually run
  2. 1.2Give the AI the information this job needs
  3. 1.3Build a Business Brain from your real information
  4. 1.4Make the context available on the next run
  5. 1.5See whether the context changes the work
Section 2 · Build 2Make the job dependable 6 lessons
  1. 2.1Give the job a clear start and finish
  2. 2.2Use the right tool for each part of the job
  3. 2.3Make the existing job dependable
  4. 2.4Run it again without the setup conversation
  5. 2.5Diagnose an answer that looks good but does not help
  6. 2.6Make fresh information easier to supply
Section 3 · Build 3Design useful roles and procedures 6 lessons
  1. 3.1Understand roles, agents, and reusable procedures
  2. 3.2Give each agent a lane
  3. 3.3Build a drafter that produces usable work
  4. 3.4Build a checker that can return the work
  5. 3.5Build a researcher that shows where its answer came from
  6. 3.6Run the team and decide what earns its place
Section 4 · Build 4Keep decisions and authority clear 5 lessons
  1. 4.1Put approval where the consequences change
  2. 4.2Make the decision easy to review properly
  3. 4.3Give waiting work a place you actually check
  4. 4.4Check what actually happened at the destination
  5. 4.5Keep the authority and stop controls clear
Section 5 · Build 4, continuedOperate, learn, and improve 5 lessons
  1. 5.1Turn an edit into a useful correction
  2. 5.2Keep a correction from creating another problem
  3. 5.3Decide whether your routine needs a different runner
  4. 5.4Give the system more freedom deliberately
  5. 5.5Review whether the system is helping
Section 6 · Build 5Put two department playbooks to work 7 lessons
  1. 6.0Put the method to work in another part of the business
  2. 6.1Marketing: turn performance into the next useful brief
  3. 6.2Sales: prepare the follow-up without inventing a commitment
  4. 6.3Operations: surface the exception before it becomes a surprise
  5. 6.4Finance: prepare a clear review from current records
  6. 6.5Admin: arrive prepared and keep accepted work visible
  7. 6.6Check the two jobs you have put to work
Section 7 · Build 6Own the system and its continuing value 5 lessons
  1. 7.1Make the work understandable without your original chat
  2. 7.2Bring your Business OS together and demonstrate it
  3. 7.3What carries over from WindRider
  4. 7.4Choose the next improvement and make room to use it
  5. 7.5Show what you can now operate
Take the first job off my plate

Self-paced, and you’re inside the same day.

From the Built to Run pilot

Get your Monday morning back.

A Built to Run pilot member, in his own words.

The moment this paid for itself was Week 5. Got to the office Monday morning to find our competitor analysis and weekly KPI summary fully drafted and waiting for me. That used to eat up my entire Monday morning. Now it just gets done and is ready for me.

David K. Partner, Consulting Firm · Pilot member

What you get

Get every file you need to build it.

46lessons 8sections 20downloadable kits 84resources inside them
46 self-paced lessons.
One recurring job off your plate first, then six builds that add up to one operating system you keep.
20 kits, 84 resources.
Prompts, working records, guides, agent roles and an optional tested runner.
5 department playbooks.
Marketing, sales, operations, finance and admin, so the relief reaches the whole company.
A Safe Operating Rhythm.
Approval gates, a correction loop and scheduled work that gets checked afterward.
Six months of AIIMN membership.
Included from enrollment, with no automatic paid continuation. Compare notes with owners doing the same work, and ask them when you're stuck.

Proof · What you download

  • prompts/20 filesAdaptation prompts, from choosing your first job to choosing the next improvement.
  • workspace/21 filesYour Business Brain, source map, run record, decision and value records.
  • guides/10 filesSetup, tool choice, diagnosis, review queue, and choosing a runner.
  • code/5 filesProject instructions, three installable agent roles, and a skill.
  • departments/20 filesFive playbooks, each with a guide, a run prompt, and a worked example.
  • runner/6 filesAn optional, tested read-only runner for when you want your own schedule.
The real kit folders, with the one-line description each carries on the course page. 84 resources in all.
Robert Sanberg, smiling, head and shoulders
Robert Sanberg, Founder of AIIMN, Owner of WindRider.

Who’s teaching you

Learn from an owner who built it in his own business first.

I run WindRider, a multi-million-dollar apparel business, wholesale and direct to consumer. I built this system there first, on my own money and my own margin.

Proof · What runs at WindRider today

scheduled jobs running the repeating work across the whole business
75
coordinating system over all of them
1
I approve what matters
Sign-off

The course teaches you the same system, built smaller, for your business.

Read how it started

A few years ago WindRider had me cornered. Tariffs were squeezing the margin on nearly everything we sell, and Meta wanted more ad creative every week than I could make by hand.

Hiring my way out didn't add up. So I started handing real jobs to systems that run on a schedule and wait for my sign-off.

It took a couple of years, and plenty broke before it held. I sorted most of it out alone, and alone is a slow way to learn anything.

What moved me forward were conversations with other owners doing the same work. You get that room too, for six months, with no automatic paid continuation.

What still breaks

Catch problems before they cost you.

Things still break, in my business too. The builds teach you to catch them.

Proof · What broke at WindRider: wrong premise

What happened
An agent read revenue from the wrong source and decided a product line's pages were broken. It queued fixes for the web team.
What caught it
An approval gate at the end of the chain. Nothing shipped.
Where you build it
Build 4, Safe Operating Rhythm.

Proof · What broke at WindRider: silent failure

What happened
A system posting our ads stopped showing the ad copy for close to 3 weeks. The platform kept reporting success.
What caught it
Performance dropped, and I went looking for why.
What you take from it
Check that the work got done, not just that the system says it did.

Permissions, in two lines

Your instructions shape what a system does. The permissions you grant in each platform decide what it can do at all, and the course teaches you to set both.

Every course screen on this page uses Example Outdoor Shop, a fictional demo business, so you see the work without anyone’s private numbers.

Fit

Know in a minute if it fits your business.

This is for you if

  • You run a small business, or you're the operator who gets handed every problem.
  • You've used AI in pieces and want it wired into something that keeps running.
  • You want less of your week on work that doesn't need your judgment.
  • You'll build on your own business, not just read about it.

It isn’t for you if

  • You want a prompt pack or a list of tools.
  • You want someone to build it for you.
  • You don't have a real business to point it at yet.

What it takes

Build time
Exercises run 15 to 90 minutes. Scheduled work comes back for a check later.
Computer
Mac or Windows. You start in Cowork in the Claude app and add Claude Code in Build 2, so you'll need permission to install it.
Claude plan
A paid plan. Scheduled tasks and Claude Code run on it, and it's separate from the course fee.
Your info
Real business information. A manual export works fine.
Coding
None. Claude takes instructions in plain English.

Your price

Get the whole system for $495, backed by the 10x Guarantee.

Built to Run · self-paced

$495 one payment

46 lessons · 20 kits · 5 department playbooks · six months of AIIMN membership, with no automatic paid continuation

Take the first job off my plate

7-day no-questions refund, then the 10x Guarantee. Self-paced, and you’re inside the same day.

The course fee covers the course. The paid Claude plan and other software are separate. Taxes and the final total show at checkout.

The 10x Guarantee: two ways to get your money back.

First 7 days
Full refund, no questions asked.
Months 1 to 12
Do the six builds and keep your value record.
At 12 months
Under $4,950 of documented value? Send it in for a full refund.

Read the full Built to Run guarantee terms

A Built to Run pilot member, on what it replaced.

We were about to spend $4,000/month on a part-time operations assistant just to handle data entry and content handoffs. Built to Run gave us the system to automate 70% of that workload safely. This course saved us $40k+ in payroll.

Elena R. Owner, Professional Services · Pilot member

Before you decide

Get straight answers before you start.

I don't have time for a course right now.

That's the reason to look at it. A weekly job leaves your plate in the opening section, and each build takes on more. Exercises run 15 to 90 minutes, at your own pace.

My business is too different.

The first four builds teach the machinery every business needs. Build 5 applies it to the two departments that cost you the most time. I've put marketing, sales, operations, finance and admin at WindRider through the same system.

Is this just a chatbot with extra steps?

No. A chat window answers and stops. A system runs at 6 in the morning, checks its own work and waits for your sign-off before anything goes out.

I'm not technical. Will I keep up?

Yes. No coding is assumed or taught. You start in the Claude app, and the course walks you through adding Claude Code in Build 2.

What breaks, and what happens when it does?

Real things break: a wrong source, an unclear instruction, a process that reports success without doing the job. The builds add checkers, approval gates and readbacks, so a break shows up before it costs you.

What if it doesn't pay off for me?

Ask within 7 days for a full refund, no questions. After that, do the six builds and keep the value record, and if it shows under $4,950 of value at 12 months, I refund every dollar. A refund ends the included membership, and the published terms govern.

Stop being the one everything waits on.

Next Monday you’ll pull the numbers again, and the laptop will open after dinner again. Built to Run hands that work off, one job at a time, until it comes back to you finished.

You keep the judgment and the sign-off.

$495, one payment, with six months of AIIMN membership included. 7-day no-questions refund, then the 10x Guarantee.