The bait, then the rug-pull.
Luuk Alleman opens with the line every solo founder wants to say out loud — 'my business finally started running itself' — and then earns it across the next eleven minutes by clicking through the actual system. The pitch isn't 'automate one workflow' — it's 'collapse every workflow into one database and let Claude Code be the brain on top.'
What the video promised.
stated at 00:12“At the end of this video, you will know everything you need to know to build the exact same for your business as well.”delivered at 10:45
Where the time goes.

01 · Cold open + promise
Hooks with 'my business finally started running itself' and promises you'll learn how to build the same.

02 · Disclaimer + nine-month truth
Honest reset: this took nine months. Features rot, infrastructure compounds.

03 · Four-layer stack reveal
Supabase Postgres, Edge Functions, Claude Code routines, pg_cron — the brain is the new top layer.

04 · Eight surfaces, one database
Inbox, content, competitor watch, finance, ads, CRM, Azure ops, social — every workflow is a row in a table.

05 · Anatomy of a routine
Not an API call — a colleague that clocks in. Trigger → Spin up → Read → Act → Write. Edge functions move data; routines do the thinking.

06 · Content engine: this video came from this loop
Mine → Score → Outline → Script → Package. The slides he just showed were generated by a skill in one prompt.

07 · Dashboard walkthrough — finance
Revenue, expenses, audience, agenda, inbox, monitor — all live tiles fed by Supabase, conversable with Claude.

08 · Content board + packaging demo
Pastes a YouTube URL into Claude, gets three thumbnail/title packaging options back instantly.

09 · Mobile app — promote a post
Same dashboard as a native iOS app; demos promoting an Instagram post for €10/7 days from his phone.

10 · Unified inbox — approve & send
Every email, partnership pitch, and YouTube comment becomes a drafted reply with one-tap approval.

11 · Infrastructure tab + soft pitch
Azure resource health, then first plug for build-loop.ai/founder-os done-with-you offer.

12 · Behind the scenes — 15 routines
Pops the hood on Claude Code: each row is a scheduled employee. Why routines beat trigger-then-LLM workflows.

13 · Morning review — LinkedIn carousel, IG story, YouTube post
One screen with the day's auto-drafted social posts; he reviews and clicks Post Now.

14 · Core lesson — context is the moat
Identify workflows, store data in one place, AI quality compounds with every model release because context is already there.
15 · CTA + sign-off
Pitches a call via build-loop.ai/founder-os, asks for like/subscribe, sign-off.
Visual structure at a glance.
Named ideas worth stealing.
Features Rot, Infrastructure Compounds
Don't chase the latest shiny AI feature — those decay. Build the data + tables underneath, and every Claude release upgrades your business automatically.
The Four-Layer Founder OS Stack
- Supabase Postgres (the store) — one source of truth for every workflow
- Edge Functions (the pipes) — pull data in from Gmail/Revolut/YouTube/Azure
- Claude Code Routines (the brain) — read, decide, write back
- pg_cron + scheduled-tasks (the clock) — triggers every 5 min / hour / week
Architectural blueprint of the whole system. The top layer (Claude Code Routines) is the new one — historically you only had three layers, and the brain was you.
Eight Surfaces, One Database
- Inbox OS
- Content engine
- Competitor watch
- Finance
- Ads
- Clients & CRM
- Azure ops
- Social distribution
Every workflow that used to live in a separate SaaS becomes a row in one table. The product surface (the dashboard) is just a thin web app reading from that one DB.
Anatomy of a Routine — Trigger / Spin up / Read / Act / Write
- Trigger (cron / scheduled-tasks)
- Spin up (full Claude Code session in cloud)
- Read (skills + Supabase + memory)
- Act (every MCP — Gmail, calendar, Supabase, Higgsfield)
- Write (back to Supabase + Telegram ping)
Why a Claude Code routine beats a trigger-then-LLM-then-output workflow: the LLM is no longer trapped in a-then-b-then-c. If a URL fails, it tries another. It's an employee, not a script.
Edge Moves the Data. Routines Do the Thinking.
Clean division of labor: edge functions are dumb pipes that ETL external apps into Supabase; routines are the smart workers that reason over the data and write decisions back.
Content Engine Loop — Mine / Score / Outline / Script / Package
- Mine — pull from competitor channels, his own comments, Transcripts
- Score — ideas ranked against his pillars; top three land in Telegram
- Outline — hook formula, retention beats, open loops, written before he sits down
- Script — plain-words pass, voice rules, speakable cadence baked in
- Package — three thumbnail + title variants generated and scored
The actual five-stage assembly line that produced THIS video. The proof is self-referential — he's showing the loop with an artifact made by the loop.
Routines = Employees
Every row in the routines table is an employee with a name, a schedule, and a job. 'Email drafts twice daily,' 'Build loop YouTube sync,' 'Morning review.' Reframing automations as employees changes how you manage them.
Context is the Moat
The single most important thing that makes AI output high quality is context. When everything you do lives in one structured database, every future model release upgrades you for free.
Lines you could clip.
“My business finally started running itself. And for the first time in history, I think yours can too.”
“Features rot, but infrastructure compounds.”
“This is not really just a simple API call. This is really like a colleague that clocks in.”
“This video came out of this loop.”
“Every single row in here is basically an employee.”
“The single most important thing that makes the output of AI high quality is context.”
“Every model that gets upgraded, the output gets better because the context is already there.”
How they spent the runtime.
Things they pointed at.
How they asked for the click.
“Make sure to check out the link in the description. At this point, I'm helping three other entrepreneurs build this for themselves... We could do a call to discuss this further.”
Done-with-you positioning at $10K-ish implied price (title says 'worth $10.000'). Scarcity baked in ('three other entrepreneurs'). Soft first mention at ~7:30, harder close at ~10:30 + final ask at ~11:30. Three hits total, well-spaced.
Word for word.
Steal this stack — the brain is the layer you don't own yet.
MCN already has 138 Supabase tables and a Contabo VPS — you've owned three of the four layers for years. The unlock is naming the fourth layer (Claude Code routines), turning every JACE/REESE/SAGE/RYDER agent into a row, and treating that table as the org chart.
- Open a `routines` table in MCN's Supabase tomorrow. One row per agent (JACE, REESE, SAGE, RYDER, plus the unnamed ones). Schedule + job description + last-run + status. That table IS the MCN+ marketing asset.
- Adopt the five-step anatomy as the standard agent lifecycle: Trigger → Spin up → Read → Act → Write. Every Paperclip agent should fit this shape, including the Telegram-style ping at the end.
- Borrow the eight-surface grid for the MCN+ sales page hero. Yours is bigger (340K LOC) but the message is identical — kill the SaaS sprawl, one DB to rule them all.
- Build the content loop yourself, scored: Mine → Score → Outline → Script → Package. Joe currently mines and packages, but doesn't score against pillars before drafting. Add the score step.
- Steal the 'features rot, infrastructure compounds' line directly. It's the philosophical center of the $6 Stack pitch. Put it on a sticker.
- The CTA pattern is gold: $10K done-with-you at the top of the title, ‘helping three other entrepreneurs' scarcity, three CTA beats spaced 4 minutes apart. Mirror this for the LFB Line.
- Killer self-referential proof: 'this video came out of this loop.' Joe should record one MCN demo where the demo itself is the artifact the system produced. Trust skyrockets.
What this means if you're a solo operator about to start building.
Don't start by automating one workflow with one tool. Start by putting all your data in one structured database, then let an AI layer reason over the whole thing.
- Pick one database (Supabase, Postgres, anything) and commit to it as your single source of truth for the next 12 months. Resist adding another SaaS.
- Map your eight surfaces first — what are the real workflows you do every week? Inbox, finance, content, clients, etc. Write them down before you build anything.
- Don't try to do this in an afternoon. Luuk says nine months. Plan for at least a quarter of compounding work, not a weekend project.
- Use Claude Code (or any agent framework) as the brain on top — not as a one-shot API call. The point is that it can read everything, try multiple paths, and write decisions back.
- Get a Telegram (or push) ping pattern set up early. The whole system only feels like an employee if it interrupts you when something needs your sign-off.
- Don't chase features. Every time a new model ships, your existing infrastructure gets smarter for free — only if the data is structured and centralized.


































































