The $400/mo One-Person Unicorn Stack: 30-Day Postmortem

The pitch is everywhere: a solo founder did $400M with zero employees, so you can run your agency with Claude, n8n, and a stack of agents that costs less than a junior hire’s lunch budget. I bought the pitch. I rebuilt my ops at Alington Media on a roughly $400/month stack. Thirty days in, here’s the unvarnished version.

Three things worked. Three things broke. One I had to hand back to a human.

The actual stack (and what each piece costs)

  • Claude (Pro + API): ~$[100]/mo. SOP drafting, voice agents, summarization.
  • n8n (self-hosted on Hetzner): ~$[15]/mo. Glue layer for every workflow.
  • Vapi: ~$[80]/mo. Inbound voice for qualification.
  • Twilio + OpenAI: ~$[120]/mo combined. SMS follow-up and embeddings.
  • Cal.com + Notion + Airtable: ~$[60]/mo. Calendar, docs, ops database.
  • Loom + Otter: ~$[25]/mo. Recordings into transcripts for SOPs.

Total: roughly $400/month. No employees, no contractors on retainer, just me and a folder full of agents.

What worked

1. Claude drafting SOPs from Loom transcripts

Every time I did a task manually, I recorded a Loom. Otter pushed the transcript into a Google Drive folder. An n8n workflow watched that folder, sent the transcript to Claude with a prompt template (“Convert this into a numbered SOP with prerequisites, steps, and a ‘done when’ check”), and dropped a draft into Notion. I edited about 20% of each draft. In 30 days I went from [3] documented SOPs to [27]. This is the single biggest unlock of the stack.

2. n8n pulling usage data into one sheet

I had no idea what my real cost per client was. I built an n8n flow that hits the Vapi, Twilio, and OpenAI APIs every morning, attributes usage by client tag, and writes it to one Google Sheet with a daily Slack summary. The first week I found a client whose voice agent was burning [4x] what they paid. I fixed it that day. Without the pipeline, I’d have caught it at month-end, if at all.

3. The invoice sub-agent

A small Claude agent reads the weekly usage sheet plus my Notion “work log” and drafts invoices with line items including the small stuff I always used to forget: extra calls, integration changes, urgent requests. I review and send. Revenue per client went up because I stopped underbilling myself.

What broke

1. The voice-match writing agent drifted

Week one it sounded like me. By week two it sounded like a LinkedIn ghostwriter on melatonin: more em-dashes, more “in a world where,” zero edges. The problem wasn’t the model. It was that I kept giving it feedback in chat instead of updating the system prompt and the few-shot examples. Each new conversation started from a slightly stale baseline. Fix: I now version the prompt in Git and require new examples (good + bad) every Friday. It’s better. It’s still not me.

2. The support agent invented a refund policy

A client asked about refunds. The agent confidently quoted a 14-day policy. We don’t have a 14-day policy. We don’t have any refund policy written down, which is the actual root cause. The agent filled the vacuum with plausible nonsense. Lesson: agents amplify whatever’s missing in your documentation. I pulled it offline until I’d written the real policy and grounded the agent in a retrieval doc with a hard “if not in source, escalate” rule.

3. The scheduler double-booked me

The auto-scheduler tried to be helpful by holding tentative slots across two calendars. It double-booked me [4] times in two weeks, including once on a paying client call. I killed it. Cal.com with one round-robin link and a manual buffer rule is now doing 95% of the job at zero risk.

What I had to take back

Client strategy calls. I tried to use an agent to prep a strategy doc, run a partial discovery via async video, then have me only join for the close. Clients hated it. They didn’t pay me for a workflow, they paid me for the judgment in the room. The async layer was extracted to a pre-call intake form. The call itself is mine again.

The real lesson

The stack is real. It’s just not a team. It’s an extremely fast intern with no taste, no memory, and no skin in the game. That framing changes how you design the system:

  • Give it bounded tasks with a clear “done when” and a source of truth to ground in.
  • Review everything that touches a client for the first 60 days, minimum.
  • Document before you automate. Agents amplify the doc; if the doc doesn’t exist, they invent.
  • Keep judgment work human. Strategy, pricing, hard conversations, anything where being wrong is expensive.

Your job didn’t disappear. It moved. From doing the work to catching where the work goes wrong. That’s the actual one-person unicorn skill, and nobody’s selling a course on it yet.

Discover more from Alington Media

Subscribe now to keep reading and get access to the full archive.

Continue reading