Sep 29, 2020 · 40m · startups-for-the-rest-of-us
Episode 516 | When to Re-write Your SaaS Codebase
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this episode of Startups for the Rest of Us, host Rob Walling interviews Summit founder Matt Wensing about the strategic decision, execution, and commercial impact of completely rewriting his SaaS application codebase. Through candid reflections on customer persona misalignments, architectural overhauls, and subsequent revenue growth, the discussion delivers actionable frameworks for founders evaluating high-risk product transformations.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Rob holds 42.7% of the talking time here. How this is scored →
Rob as informed peer 4.7 Guest teaching 4.1 Guest disagreement 1.3 Rob pushing back 1.7
speaking balance: gold is Rob, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 28:15 Matt rejects the blank slate critique initially
Matt acknowledges pushing back against Rob's initial feedback, thinking Rob 'did not get it' before eventually realizing preloaded templates were necessary.
Hardest push from Rob ▶ 18:10 Rob questions developer justification for code rewritesRob invokes Joel Spolsky and his portfolio experience to challenge whether Matt was succumbing to classic engineer bias rather than sound business logic.
Biggest teaching moment ▶ 15:30 Matt breaks down competing against ExcelMatt explains the realization that users did not just want specific extra features, but required open-ended canvas flexibility equivalent to a spreadsheet.
Rob holds their own ▶ 29:20 Rob illustrates onboarding friction using Drip blueprintsRob draws on building Drip's visual workflow builder to explain how power features paralyze non-expert users without pre-built templates.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Rob as informed peer | Guest teaching | Guest disagreement | Rob pushing back | Why |
|---|---|---|---|---|---|---|
| Update on Co-Host Mike Tabor's Temporary Hiatus | 0 | 0 | 0 | 0 | Solo host intro covering housekeeping regarding Mike Tabor's hiatus and the TinySeed fund thesis. Since this is a monologue, all conversational dynamics are scored at zero. | |
| Welcoming Matt Wensing and Setting Episode Context | 5 | 2 | 0 | 1 | Rob welcomes Matt back and frames Summit's value proposition relative to backwards-looking analytics tools like Baremetrics. The tone is highly collaborative and warm. | |
| Diagnosing the Problem: Persona Misalignment and Product Inflexibility | 3 | 6 | 1 | 1 | Matt educates Rob on diagnosing the target persona failure of Summit v1, explaining how earliest-stage founders outgrew the rigid v1 interface and demanded deeper flexibility. | |
| Strategic Timing and Opportunity for a Major Pivot | 4 | 5 | 1 | 1 | Matt outlines how securing fresh runway right at the onset of the pandemic allowed him to make a high-risk strategic pivot rather than burning runway on incremental tweaks. | |
| Redesigning Summit: Competing with the Flexibility of Excel | 4 | 6 | 2 | 1 | Rob offers the 'jobs to be done' framework, which Matt adopts to explain that competing against Microsoft Excel requires delivering an open-ended canvas rather than a vending machine. | |
| Justifying the Rewrite: Business Strategy Versus Developer Bias | 8 | 4 | 2 | 6 | Rob brings heavy founder/investor expertise, invoking Joel Spolsky's classic warning against rewrites and pressing whether Matt fell into developer bias. Matt clarifies he made a sales-driven executive call. | |
| The 70-Day Sprint and Building Maintainable Foundations | 4 | 5 | 1 | 1 | Matt discusses executing a disciplined 70-day sprint of daily commits to construct maintainable infrastructure that future contract developers could step into. | |
| Launching V2, Revenue Uptick, and Persona Validation | 7 | 5 | 3 | 3 | Matt details his revenue rebound upon launching v2 and admits he initially resisted Rob's advice regarding the blank slate problem until realizing template blueprints were essential, which Rob validates with his Drip onboarding experience. | |
| Practical Financial Modeling Scenarios for Bootstrapped Founders | 6 | 4 | 1 | 1 | Rob and Matt compare notes on concrete modeling scenarios for bootstrappers, such as calculating ad payback periods and cash flow thresholds for new hires. | |
| The Ultra-Minimalist Homepage Strategy and High-Intent Funnels | 6 | 4 | 2 | 2 | Rob interrogates Matt's radical 16-word homepage. Matt defends it as a high-intent qualification filter inspired by Hiten Shah, while Rob connects it to his own past curiosity-driven landing page for HitTail. |
Statements from this episode (17)
Walling: Early-stage independent B2B SaaS yields amazing investor returns
“We believe investing broadly into the earliest stages of B to B SaaS companies, and specifically it's the B to B SaaS companies who are not necessarily reliant on traditional venture capital, right? It's the startups for the rest of us, the micro-conf type com…”
Walling: TinySeed is raising Fund Two to fund independent SaaS startups
“We're in the process of raising Fund Two so that we can continue to help and support and mentor and guide and fund hundreds and hundreds more independent SaaS companies.”
Walling: Dharmesh Shah, Rand Fishkin, and Patrick McKenzie are TinySeed LPs
“If you decide to invest, you'll be joining folks like Dharmesh Shah, co-founder of HubSpot, Rand Fishkin, Founder of SparkToro, Steli Efti, co-founder of Close.com, and Patrick McKenzie, who many of you know as PatioEleven on the internet.”
Wensing: Early Summit struggled with poor free user retention and conversion
“So my retention, even my free retention, because it's a freemium product, free retention wasn't good. You know, I didn't like the direction it was going. People would have these experiences, but then they weren't engaging frequently enough to turn them into a …”
Wensing: Founders have a bias toward confirming, complimentary feedback
“I think we're always looking as founders for validation... And so when people say things that are complimentary, they just tend to really, I wanted to say weigh on us, but that sounds bad, but they really put wind in our sails, you know, pick your metaphor. Li…”
Wensing: Competing with spreadsheets is difficult because they are endlessly flexible
“The difficult thing about competing against a spreadsheet, and probably other products like that, is that a spreadsheet is just endlessly flexible. Right? There's nothing you can't do in a spreadsheet.”
Walling: Five of his 35 portfolio startups requested full codebase rewrites
“I'm 35 angel invest, you know, angel and tiny seed investments in, and I've had at least, I'll say four, four or five of the startups that I kind of advise or interact with say, I want to rewrite, we need to rewrite our code base.”
Walling: Founders must evaluate codebase rewrites through a CEO, not technical, lens
“If you're a single founder or a two founder team and you are thinking about rewriting, put on your sales and marketing hat, you know, put on your CEO hat and not your CTO or not your developer hat.”
Walling: Codebases justifying full rewrites are far rarer than developers claim
“Not that there's never a reason, you know, I mean, you can have code that is so bad that you can't add features and it takes you a month to do a days worth of work or whatever. Of course that happens, but it's a lot less frequent than I think developers tend t…”
Wensing: Summit codebase rewrite took 70 days with daily commits
“I think, 70 days of coding. Essentially with a commit and push every day.”
Wensing: Summit V2 rewrite immediately converted target-persona founders into customers
“So I think the short answer is yes, but I'll qualify that by saying I took it then to the customers that I was essentially targeting with this rewrite, right? I took it to them basically as soon as it was ready. And I said, aha, here's the flexibility you've b…”
Wensing: Summit V1 would have sold subscriptions but attracted the wrong persona
“Who knows what the old version, I'm pretty sure I would have sold some subscriptions as well. But again, back to the personas, it wouldn't have been to these people. Right. It would have been to those other people, and that was not what I ultimately wanted to …”
Walling: Drip required workflow blueprints to successfully onboard mid-level marketers
“It wasn't until we got the blueprints built that people, and you could just one click import, you know, a blueprint that we really started getting the mid-level and the lower end marketers.”
Wensing: Summit's rewrite alienated early users who preferred the simpler original
“There's a group of users of the first product that I essentially alienated, right? They came to the new one and basically said, what have you done? You know, like you took away the one I liked and you replaced it with this power tool that she's, I don't know w…”
Wensing: Founders struggle with spreadsheets but easily model their business descriptively
“What's nice about a model approach instead of a spreadsheet is, you set a founder in front of a spreadsheet and you say, put your business in here. And there's kind of an immediate thought of, okay, I need a revenue row, I guess, and I also need a, Expenses ro…”
Wensing: Summit gets 2 to 20 daily signups via ultra-minimalist homepage
“So I'm getting through that homepage, I'm still getting anywhere, depends on the day, but I'm getting anywhere from on a very, very slow day. Maybe it's a Sunday holiday or something like that. Two to three signups on a busy day, 10, 12, 15, 20 signups through…”