Everything I've learned building an AI company alone — from stack selection to fundraising, unit economics to App Store rejections. No theory. All practice.
Hero: Solo founder at desk — split-screen restaurant kitchen / code editor
One person. Two worlds. Same operating system.
Author photo: Shaen Hawkins
Former McKinsey · Mexico City
I'm a former McKinsey consultant who moved to Mexico City and decided to build an AI company. Not an AI wrapper — a real product with 60+ AI characters across five languages, a mobile app in both app stores, and a content production pipeline that would normally require a team of ten.
I did it alone. Not because I'm particularly gifted technically — I'm not a traditional engineer. I did it because the tools available right now make it possible.
This document is not about my product. It's about the operating system I built to create it.
The multi-chat AI workflow. The sandbox-first philosophy. The documentation that compounds. The content pipeline that generates cinematic video from text prompts. Every chapter = something I learned by doing it wrong first.
Diagram: The multi-chat workflow
Strategy → Brief → Execution → Review
You know some code but not enough to ship alone. You want the AI workflow that multiplies what one person can build.
Never written code. You have taste, opinions, and a product idea that won't leave you alone. This guide starts from zero.
No co-founder yet, or you want to get further first. You want the real playbook from someone who shipped — not the hype.
Each chapter has two layers. The core text is the philosophy — how I think, the mistakes that shaped those opinions. The appendices are the tactics — exact configurations, code patterns, step-by-step workflows.
Read chapters for thinking. Reference appendices when building.
Philosophy, opinions, real mistakes. Read for the thinking.
Configs, code, step-by-step. Reference when building.
Every example uses a restaurant analogy. Building software is like opening a restaurant — you don't grow vegetables or build ovens. You assemble the right suppliers, equipment, and recipes. That's what this guide teaches. Not farming. Cooking.
17 chapters across four layout types.
Ch 1 · Why This Exists
Ch 5 · Vibe Coding
Ch 17 · Lessons
Ch 4 · AI Team
Ch 6 · Docs
Ch 7 · Sandbox
Ch 8 · Edge Functions
Ch 11 · Mobile
Ch 14 · Automation
Ch 2 · Stack
Ch 12 · Payments
Ch 13 · Content
Ch 15 · Unit Econ
Ch 3 · APIs & Keys
Ch 9 · Database
Ch 10 · Design
Ch 16 · Fundraising
Illustration: Restaurant cross-section mapped to software architecture
Kitchen = backend · Dining room = mobile app · Menu = marketing site · Cash register = payments
The tools exist right now for one person to build what used to take a funded team of twenty. This is the operating system — not the product, the process.