Activate when: user says 'founder mindset' or 'founder mode'; asks 'default alive or default dead'; says 'do things that don't scale'; says 'am I avoiding th...
Coding
Do Things That Don't Scale
Try itActivate when: an early founder is over-automating or waiting for growth to be 'efficient'; 'this won't scale', recruiting first users, delivering early serv...
What it does
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). More: deciqai.com/c/do-things-that-dont-scale
The skill document
Do Things That Don't Scale
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
- 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.
- Deliver a delightfully unscalable experience — concierge/white-glove; do manually what the product will later automate.
- Insert yourself into the value delivery — the friction you feel is the product spec.
- Learn from doing, not dashboards — hand-delivery surfaces needs analytics miss.
- Use the unscalable to create early love — a small number of users who love you beats many who are indifferent.
- 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 — 227 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.
Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/do-things-that-dont-scale.json
Related skills
Activate when: a founder says they're hitting a ceiling despite working harder; a founding team keeps fighting about who makes decisions; someone asks 'why d...
Activate when: an early founder needs revenue but wants to hire a salesperson or 'automate' sales too soon; 'I hate selling', 'when should I hire sales?', fi...
Surfaces founder axioms for ambiguous startup decisions — hiring, fundraising, product, sales, and cash.
Activate when: a founder is deciding whether/what to hire first; 'should I hire now', 'what's my first hire', feeling overloaded, sequencing early roles; hir...
Activate when: a founder is the bottleneck on repetitive work, or wants to delegate/automate to people or AI agents; 'everything depends on me', 'how do I do...