425 | Product-Market Fit Starts with Understanding the User | Erin Rollenhagen

Erin Rollenhagen learned the most expensive lesson in product development the hard way: she spent years building software without ever talking to a single end user—and people took early retirement to avoid using it. That failure launched a 20-year career spanning 200+ tech launches across healthcare, finance, and regulated industries, and her book *Love At First Launch*. In this conversation, Erin and Jeff cover what an MVP actually needs (the "good boots" analogy), the peak-end psychological effect applied to software, finding emotional peaks in B2B workflows, critical mistakes when turning internal tools into commercial SaaS, and the one question almost no founder is asking—but should be.

Key Takeaways

[4:30] Erin's government project failure—building for two years without meeting a single user

[6:10] Client requests are signals, not specifications—"the big blue button" analogy

[9:18] Don't replace high-touch experiences with chatbots

[11:55] Chatbot satisfaction data: 88% for simple queries, 31% for complex

13:21] Security and multi-tenancy: the first things to fix going from internal to commercial

[16:00] "Just don't click that button" doesn't work with paying customers

[20:48] The 15-steps trap: founders see the roadmap, users only see today

[23:58] "Good Boots": the MVP analogy every founder needs

[27:14] The peak-end effect applied to software design

[30:25] Finding emotional peaks in B2B products through user interviews

[32:45] Transitioning from builder to visionary: recruit people to your cause

[34:00] Erin experiences her own founder insecurity launching her own product

[38:30] Revisit old features, don't just chase new ones

[39:25] Don't match competitors feature-for-feature

[40:05] Differentiate on experience, not feature count

[41:52] The one question founders aren't asking: "How will your users find you?"[insert timestamps]

Tweetable Quotes

"The stated order for what they want is a signal for the need or the problem they're trying to solve, but it's not necessarily the ultimate answer." — Erin Rollenhagen [8:19]

"If their claim to fame is being high touch, we don't want to put tech in there and take them from high touch to low touch." — Erin Rollenhagen [9:52]

"Simple queries have an 88% user satisfaction rate. Complex ones have 31%. That's a very clear dividing line." — Erin Rollenhagen [12:04]

"You can't train your way out of problems when it's an external audience." — Erin Rollenhagen [18:20]

"Your vision is so big—15 steps down the road. But the audience hasn't seen your grand vision. They're just judging it on what they see today." — Erin Rollenhagen [21:35]

"Your army needs good boots. In software, that's login, billing, security—the basic stuff that has to be there." — Erin Rollenhagen [24:00]

"Nail the emotional peak, nail the end of the experience, people will be happy." — Erin Rollenhagen [30:05]

"When it's our own stuff, I don't know where the bar is. I can't see it. The bar is invisible." — Erin Rollenhagen [36:10]

"How are your users going to find you? That's the one question almost no founder is asking." — Erin Rollenhagen [41:52]

SaaS Leadership Lessons

1. Talk to users before the product is ready.

Proximity to users is the single biggest determinant of whether what you build gets used. No interview, no insight.

2. Treat client requests as signals, not specifications.

Dig behind what they ask for to find what they actually need. The request describes a solution in terms the client understands—your job is to keep peeling.

3. Build "good boots" before anything exciting.

Login, billing, security, and core infrastructure are unsexy but non-negotiable. The constraint they create forces focus on the 2-3 features that matter.

4. Don't let external validation inflate your scope.

Cramming features before a big debut is almost always insecurity, not necessity. Ship what you have.

5. Make iteration on existing features part of your roadmap.

Revisiting what you shipped last quarter with real feedback is just as important as building the next thing.

6. Differentiate on experience, not feature count.

Feature parity is easy to copy. A seamless, low-friction experience isn't. Reduce steps, remove configuration, make the path effortless.