SaaS Playbook hits 29,000 sales: channels, royalties, and book lessons

Executive overview

Self-published books live or die by word of mouth, not audience size. Rob Walling's SaaS Playbook reached 29,000 copies with no marketing engine — just readers sharing it repeatedly across Twitter, Reddit, and podcasts.

Amazon and Audible together control 60% of sales volume but extract punishing margins. Selling direct is a small slice but yields dramatically better economics.

The book that keeps selling is one worth sharing — not one ghostwritten for a LinkedIn credit.

SaaS Playbook sales breakdown

• 29,000 copies sold in under a year; top-line revenue just under $400k, ~$275k paid out
• Amazon: 35% of volume (paperback ~$15 net, Kindle ~$7 net), split roughly 50/50 between formats
• Audible: 26% of volume; keeps 75% of each sale — drops to 60% only if you grant exclusivity
• Kickstarter: 25% of volume (more than the "3–4k" estimate from launch)
• Direct (sasplaybook.com): 11% of volume; only 3% Stripe fee vs. Audible's 75%
• Apple Books: 1% — barely worth the conversion effort
• Format mix: 43% audiobook, 29% print, 28% ebook
• Recurring monthly sales driven entirely by readers recommending it organically

Lessons for self-published authors

• Audience size predicts early sales (6–8k copies); word of mouth drives everything after
• Amazon and Audible have a stranglehold — they can delist, suppress rankings, or reprice
• Ghostwritten books pumped at launch and then forgotten are a poor use of time
• Direct sales channel is small but worth maintaining for margin alone
• Writing a genuinely useful book is the only durable marketing strategy

Information vs. motivation to learn

• Access to coding tutorials, boot camps, and AI tutors is now essentially free and ubiquitous
• The bottleneck was never information — it was always desire and disposition
• People who don't learn to code aren't unmotivated in general; they simply have different proclivities
• No-code and AI lower the floor but don't eliminate the need for skilled developers
• Democratising information does not mean everyone will act on it — true across any discipline
• Hot takes ("AI means no one will need to code") confuse availability with adoption

Hiring people who already know how to run fast

• A top track coach's insight: "At this level, you don't teach him how to run fast. You teach him how to run fast better."
• Hiring junior people at a bootstrapped startup means the founder becomes the trainer
• Early at Drip, hiring junior local staff cost significant founder time that was already scarce
• If you're building the parachute mid-air, you can't also be teaching the person next to you
• Exceptions: once you have senior staff who can absorb the training load, junior hires work fine

Making your first level last

• John Romero (co-creator of Doom) always designs the first game level last — by then he knows the full aesthetic and can put his best work at the entry point
• Applied to SaaS: build the app first, then architect onboarding once you understand the complete user journey
• Onboarding built last reflects the full gestalt of the product; built first, it misaligns as the product evolves
• Alternative approach: write marketing copy first as a forcing function to clarify what you're building, then revise it at launch once you know the real product
• Both approaches converge: the customer-facing surface gets your most refined thinking