Codebase rewrites, founder salaries, and the stair-step method

Executive overview

Technical founders routinely face three recurring dilemmas: whether to rewrite code for an acquirer, how to balance salary against growth, and how to prioritise engineering versus marketing. Each has a clear answer once framed correctly.

Rewriting a codebase to chase a higher exit multiple is cargo-cult management — tech stack almost never affects acquisition price.

Rewriting your codebase for a future sale

• Acquirers care about the business, not whether it runs on Django, Rails, or PHP Laravel.
• The only edge case: a stack so obscure or deprecated that finding developers is genuinely hard.
• Classic ASP (circa 1998) warranted a rewrite; standard modern stacks do not.
• If a buyer already has a team skilled in your stack, that's a minor bonus — but you can't predict who will acquire you years from now.
• Cargo-cult thinking often comes from executives who've only worked in large enterprises, not startups.

Founder salary vs. growth reinvestment

• A bootstrapped founder at $1–1.5M ARR can take home more than a VC-backed CEO on $300–400K.
• Every dollar left in the company compounds: $1K MRR added equals roughly $60K in exit value at a 5× ARR multiple.
• Reinvesting instead of extracting is the same logic as compound interest — pulling cash today trades future equity for present comfort.
• Paying yourself enough to feel financially secure is the right floor; maximising extraction is the wrong ceiling.
• Lifestyle businesses optimised for cash-out are valid — just don't confuse them with the long-term equity-building play.

The stair-step method and step one products

• The original stair-step (Bangkok, 2014) included e-books, courses, and simple software as step one — not just SaaS.
• Writing blog content and turning it into a course is a legitimate step one move.
• Building a Zapier-style integration between niche tools (e.g., Xero + time tracking) is a strong step one business:
  • Traffic comes from platform app stores, so marketing demand is lower.
  • Revenue is real, even if capped well below millions.
  • APIs between a few apps are low-effort to build for a developer.
• Step one teaches revenue generation, product support, and audience building — skills that make step two far easier.
• A no-code MVP (actual Zapier) can validate demand before writing any code.

Engineering vs. marketing as a solo founder

• Technical founders are psychologically pulled toward building; that pull needs conscious resistance.
• Marketing, sales, and onboarding are what grow the business; code is the product that makes the business possible.
• Over-building and endless redesigns are the visible symptoms — a year later, MRR hasn't moved.
• For teams with multiple developers, a common heuristic: dedicate one sprint in four (or ~20% of time) to technical debt.
• Solo founders carrying both roles face compounded difficulty — step one products or early funding exist partly to eliminate this tension.
• Funding is a tool: use it when the job requires it, not by default or dogma.