The Stack You Sell

Where this comes from

This is season two of the AI Auto Base classes. Season one, The Brain That Runs a Company, built a brain for your own business. This one builds the business: a self-hosted stack on a box you control, solid enough to hand to somebody else, and a price list that survives contact with a reseller. Version 2 turns the summary guide into thirty prompts, one per service, with the exact commands inside each one, written for someone who has never rented a server, and adds SERVICES.md: the fourteen services an AI agency commonly sells, each mapped to the apps and the prompts that deliver it, and honest about which ones are human work. The nine per-layer install packs from the agency track ship in the zip unchanged, with their verify scripts, as the reference behind the prompts.

What you build

Prompts 00 to 03 run in Claude Code on your laptop: the constitution, the Hostinger purchase, the first login, the hardening. Prompt 04 puts Claude Code on the box, and from there every prompt is pasted on the server itself, where the errors are. Docker and Coolify, the domain on Cloudflare, backups with a restore drill that deletes a volume on purpose, Uptime Kuma and Vaultwarden, one Postgres for every service that can use it, n8n with the timezone and encryption key set before the first workflow, ERPNext with the CRM in the same bench, Umami, Cal.com, Listmonk, the loop that turns a form into a lead and a booking, email that passes SPF, DKIM and DMARC before it warms, a one-page site with Payload, video on a CDN, Stripe in test mode until the duplicate test passes, and then, when a client pays, Chatwoot with WhatsApp, Typebot, the AI layer on pgvector, Docmost with the runbook, and a second box stood up from the same prompts with a timer running. Prompts 25 to 29 add the services on top once a client pays for them: Metabase dashboards, integrations with the tools the client already uses, a content pipeline with a human gate, evals and guardrails instead of fine-tuning, and a voice receptionist built on the pattern.

Each prompt explains its commands one line at a time, stops on the first error, and ends with a proof you can see without reading code: a refused password login, a file named RESTORE-PROVEN.txt, a timezone printed from a running container, three PASS lines in an email header, one Payment Entry after two identical events.

The one thing it deliberately does not do: promise an income. The guide's pricing section gives ranges and the reasoning behind each, and the rule that keeps them honest, and stops there.

Do you need this? Be honest first

If you have not yet built one automation that runs while you are asleep, start with season one. This pack assumes you can open a terminal, read an error, and paste it back into Claude Code. It is for the freelancer, the career-switcher, and the one-person agency who wants to sell a system the client owns rather than rent one from a platform, and for the agency owner who wants to resell that build under their own name. If you want a template shop or a hosted funnel builder, this is more machine than you need. If you plan to sell an ERP implementation as your first project, read the guide's section called what not to sell yet before you quote anything.

What you need

• A laptop with a terminal, an SSH key and Claude Code (Pro, Max or Team). The three setup paths (Windows with WSL2, Mac, Linux) start from a clean machine and end at the Claude Code prompt in about half an hour. Nothing else installs on the laptop.
• A Hostinger account and one KVM 2 VPS to start (8 GB); a KVM 4 (16 GB) once ERPNext, Chatwoot or a client lands. Promo and renewal prices as read on 2026-09-03 are in COSTS.md; check the live page before you buy and budget the renewal.
• A domain, a free Cloudflare account, a Backblaze B2 or R2 bucket, an email relay account, a GitHub account, and a Stripe account, each opened by the prompt that needs it. An LLM provider key only for prompt 22.
• The time: an evening to read, a weekend for layers 0 to 4 on your own box, and sixty to ninety days running your own business on it before you sell it.

What is in the zip

the-stack-you-sell/
  README.md                     the lesson: what you build, the paths, hosting, accounts
  SERVICES.md                   the fourteen services, the apps and prompts behind each
  index.html                    the clickable guide with the services map and all 30 prompts (same as the browser link above)
  COSTS.md                      every cost, with the date it was read
  CREDITS.md                    as-is notice, what was verified, terms
  agency-build-guide.pdf        the guide: services, stack, domain, banks by market, pricing
  paths/                        one README per platform: Windows WSL2, Mac Apple Silicon, Linux Omarchy
  prompts/                      00-project-brief ... 24-handover-and-the-second-box, then 25-metabase ... 29-voice-receptionist
  packs/                        the nine L0 to L8 install packs with verify.sh and TROUBLESHOOT.md
  assets/                       the cover art

What was verified and what was not

This pack is distributed as is, as a proof of concept. The guide was opened in a real browser and driven by a script on 2026-09-03: the three platform tabs, the progress bar, the checkboxes, the saved progress, and the copy buttons for commands and prompts all work, including from a downloaded file where the modern clipboard API silently fails and the guide falls back to the older method. Every text file was scanned for keys, private addresses, personal mailboxes and placeholders before the zip was built. The nine layer packs were rebuilt by their own builder the same day, which refuses to write a zip when a required file is missing, a script fails to parse, or a file carries a secret.

The thirty prompts were written from install runbooks that exist and were read by a second model for contradictions and missing steps, and have not been run as a sequence on a fresh Hostinger box. Coolify's catalogue entries and their variable names move between releases; each prompt says what to do when a field is not where it says. The bank list in the guide is names only, fees unverified. If a prompt breaks on your box, paste the full error into Claude Code and ask it to fix it, then post what broke and the plan you are on in the community.

Read the prompt before you run it

Hand each prompt to Claude first and ask what it plans to do. Compare that to the numbered steps. A prompt costs a minute to read. A locked-out box costs an evening, and prompt 03 says exactly which session to keep open so that never happens.