Do Things That Don't Scale to Feel Magical
Manually deliver a magical outcome behind a one-button experience to win a commoditized market before automating
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 92%
When a technical, high-friction step blocks adoption, don't wait to automate it — put humans behind a single magical button so users experience the outcome instantly, even though it's manual on the back end. Packaging matters: the same result delivered as 'we'll email you in 3 days' feels ordinary, while 'push a button, be live in 24 hours' feels insane and drives word-of-mouth in a commoditized category.
Origin
An explicit Anchor early-days principle ('build things that don't scale'), a well-known startup maxim popularized by Paul Graham; Maya credits Anchor CEO Mike Mignano's team for executing it on podcast distribution.
Core principles
- 01Obsess over reducing friction as a constant battle
- 02Packaging the same outcome changes whether it feels magical or mundane
- 03Humor 'stupid' ideas and 'yes-and' them rather than killing them with 'that can't work because'
- 04Unscalable manual delivery is a temporary hack to win share, then you automate
How to run it
- 1
Find the high-friction step users can't clear
Identify the technically painful barrier (for Anchor: Apple Podcasts submission requiring an Apple ID, RSS ownership proof, 301 redirects) that stops non-savvy users.
Pro tip Target friction that competitors treat as unavoidable — that's where the magical gap is biggest.
- 2
Put a single magical button in front of manual labor
Let the user press one button; have humans (Anchor hired paid college interns) do the tedious manual work behind the scenes so it feels automatic.
Pro tip Compress the visible turnaround (button → live in ~24h) so it reads as automation, not a support ticket.
Watch out Don't expose the manual seams — 'a team member will get back to you in 3 days' kills the magic even if the work is identical.
- 3
Ride the word-of-mouth, then automate
The remarkable experience makes users tell friends, winning share in a commoditized market; retire the manual hack once it stops scaling.
Pro tip Make something so remarkable it knocks users' socks off — that's the real driver of word-of-mouth growth.
Watch out It genuinely won't scale and will create technical and relationship complications (e.g. with Apple) — plan the automation exit.
In the wild
Anchor hired paid college interns to create Apple Podcast accounts and manually submit podcasts behind a one-button 'distribute' experience. Users assumed Anchor had a secret backdoor deal with Apple.
→ Delivered a huge benefit over commoditized competitors and was a major reason Anchor gained hosting market share so quickly; one intern later became a full-time PM on Maya's team.
Common mistakes
Exposing the manual process as a slow support flow
Framing it as 'request distribution and we'll get back to you in 3 days' removes the time-saving magic even though the underlying work is the same.
Killing silly ideas with 'that can't work because'
Refusing to humor unscalable ideas means you never discover the differentiators competitors are too afraid to try.
Is it for you?
Best for
Early-stage startups fighting for share in a commoditized market with a painful technical onboarding step
Not ideal for
Mature products at scale, or steps where manual handling risks security, compliance, or data integrity
From the transcript
“build things that don't scale”
“we just had college students making apple podcast (31:30) accounts and then submitting like hundreds of thousands of podcasts through these accounts”
“if all you see as a user is you're hitting a button and then 24 hours later you're somehow magically on Apple podcast like that…”
From the episode
Building Anchor, selling to Spotify, and lessons learned
Maya Prohovnik (Spotify’s Head of Podcast Product)