Revenue vs. profit multiples, pricing cuts, and cap table basics

Executive overview

Bootstrapped SaaS founders often face competing pressures: grow top line fast, stay profitable, or protect equity. The right answer depends on where you are in the journey.

Below ~$1.5M ARR, buyers value you on net profit. Above that threshold, growth and revenue dominate valuations. Cap table mistakes compound over time and are hard to undo.

Build for revenue and growth first; protect equity from day one.

When buyers use revenue vs. profit multiples

• Sub-~$1.5M ARR: most buyers value on net profit, not revenue
• Above ~$1.5M ARR: strategics and larger PE firms shift to revenue multiples weighted by growth
• Growth is the top valuation driver; revenue is second; churn is third
• Value buyers (micro PE) will push for profit multiples at any stage to lower the price
• Exceptions exist — a founder at $80K ARR sold for 10x revenue when the price made walking away worthwhile
• If your goal is exit, reinvesting everything to accelerate growth is rational pre-$1.5M ARR

When lowering prices is warranted

• Price cuts are rare — Rob can recall only ~2–4 cases across thousands of companies
• Two clear signals: sustained churn to cheaper competitors, and consistent price objections causing lost deals
• Some price complaints are normal; if you get none, the price is too low
• Low switching costs amplify the pressure to cut — customers leave more easily
• Commodity positioning = price sensitivity; strong brand = pricing power (Salesforce, HubSpot)
• Tactical option: lower published entry-level tiers to reach price parity, keep higher tiers priced on value delivered

Competing against well-funded incumbents

• Don't compete pound for pound — exploit structural weaknesses of large competitors
• Large players: slow to move, poor developer/designer talent, unresponsive to customers, locked-in contracts
• Advantages to press: faster iteration, easier UX, flexible pricing, no long-term contracts
• Recruit "refugees" — customers who hate the incumbent and are actively looking to leave
• Cheap is not the core value proposition, but being noticeably cheaper is part of the package early on

Build vs. hire for your MVP

• If making steady progress on your own, keep building — no strong reason to bring in a developer
• If the code won't scale or you're teaching yourself as you go, assess honestly whether it's good enough for a first client demo
• Non-technical founders frequently hire bad developers because they can't evaluate code quality
• If budget is tight, take longer — don't take on bad code to move faster
• The question is whether your current output can credibly transition to a scalable solution

Cap table rules of thumb

• Cap table = who owns what percentage of the company (starts as a simple spreadsheet)
• Gets complicated when you add investors, option pools, SAFEs, or convertible notes

Rule 1 — everyone vests, including founders

• Standard: four-year vest with a one-year cliff
• Without vesting, a co-founder who leaves after six months keeps their full equity stake
• Unvested departures make the company unfundable

Rule 2 — don't sell more than 10–20% in a single round

• Tiny Seed gets cautious if founders own less than 80% at application; below 70% is a red flag
• Selling 50–70% early to a single investor can make the remaining work feel like it lines their pockets
• Bootstrapper/indie rounds: aim for 10–15% dilution per raise

Rule 3 — understand your SAFEs and convertible notes before you sign

• A SAFE is a promise of future equity at a specified valuation cap — it converts later, not now
• A convertible note is a loan that converts to equity at a trigger event (next round, time-based)
• Founders repeatedly underestimate post-conversion dilution and discover too late they own far less than assumed
• Don't DIY legal on funding instruments — get a lawyer

Recommended resources for bootstrapping beginners

• Blog: search "stair-step method of entrepreneurship" (Rob Walling)
• Book (entry): Start Small, Stay Small — dated on tactics but strong on founder mindset
• Book (preferred): The SaaS Playbook — more current, broader coverage
• Video: microconf.com/youtube → "Building Your First SaaS: The Ultimate Crash Course" playlist
• Podcast: startsupsfortherestofus.com → Greatest Hits tab, especially episode 222 (stair-step approach)

Career stability vs. job change for side-project builders

• Changing jobs likely pays off long-term: new network, new codebase exposure, probable pay rise
• The real cost is months of lost side-project momentum while re-establishing trust and learning the new environment
• Decision hinges on your personal timeline — how many years do you have before you need to replace your income?
• If timeline is loose (3–5 years), lean toward the move; if tight, preserve current flexibility