Do Things That Don't Scale

Activate when: an early founder is over-automating or waiting for growth to be 'efficient'; 'this won't scale', recruiting first users, delivering early service manually; concierge/white-glove starts. Do NOT activate when: the motion is already validated and the task is genuinely to scale it (then systemize/automate).

Overview

Paul Graham's counterintuitive rule: early on, the unscalable is exactly what you should do. Startups don't take off by themselves — founders recruit users manually, deliver an over-the-top experience by hand, and learn things automation would hide. Worrying about scale too early is a form of avoidance; the manual phase is where you earn insight and love that later become your moat.

The Process

1. Recruit the first users by hand — go to them individually; don't wait for a funnel. Gate: "it won't scale" used to avoid direct outreach = you're hiding from the work that matters now.
2. Deliver a delightfully unscalable experience — concierge/white-glove; do manually what the product will later automate.
3. Insert yourself into the value delivery — the friction you feel is the product spec.
4. Learn from doing, not dashboards — hand-delivery surfaces needs analytics miss.
5. Use the unscalable to create early love — a small number of users who love you beats many who are indifferent.
6. Systemize only what's validated — automate a step after manual delivery proves it matters. Gate: automating before validation locks in the wrong process (and becomes an agent doing the wrong thing well).

When to Use

• Pre-PMF user acquisition and delivery
• Tempted to build automation before demand is proven
• Early service businesses deciding manual vs systemized

Applying It Well

• Manual now buys the insight that makes later automation correct.
• The best unscalable move is usually direct, personal, and generous.
• Feeds systemization later — do it by hand, then write the SOP (see sop-systemization).

Red Flags

• Building automation/funnels before anyone loves the manual version.
• "Won't scale" as an excuse to avoid sales/support.
• Optimizing efficiency before validating the motion.

Verification

• First users recruited personally
• Early delivery done manually/concierge
• Insights captured from hands-on delivery
• Automation deferred until the step is validated

---

Part of deciqAI Knowledge Skills — 223 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/c/do-things-that-dont-scale · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.