Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Customer Interviews to Validate Pricing
Transcript
- Lucas: You know, one of the biggest mistakes bootstrapped founders make isn't building the wrong feature — it's pricing the thing wrong from day one. Luna: And by wrong you mean too low, right? Because we're scared to charge what it's worth. Lucas: Exactly. Or too high and you get zero traction. Either way, you've left money on the table or killed your launch. But there's a specific tactic I've seen work really well for solo founders: structured customer interviews before you write a line of code. Luna: Like, asking people what they'd pay before you even have a prototype? Lucas: Precisely. I was digging into a case study from a founder who built a small B2B SaaS tool for independent insurance agents. He didn't build anything for the first two months. He just talked to agents. Fifty of them, one-on-one. Luna: Fifty is a lot for a solo founder. That's probably a full-time job for a few weeks. Lucas: It is. But he said it saved him a year of pricing guesswork. He used what's called the 'willingness to pay' framework. Instead of asking 'How much would you pay for this?' — which people answer dishonestly — he asked a series of comparative questions. Luna: Like what? Give me an example. Lucas: Sure. He would describe his planned tool — say, a policy comparison dashboard — and then say: 'If this tool cut your quote time in half, would you pay more for it than you currently pay for your CRM?' That anchors the conversation to something real. Luna: So you're comparing it to an existing expense they already have. That's clever. Lucas: Right. Because if they say yes, you know the price can be at least as high as their current CRM subscription. Then he'd drill down: 'Would you pay 20 percent more? 50 percent more?' And he'd watch for hesitation. Luna: What did he find? Did they actually pay what they said? Lucas: He landed on forty-nine dollars a month after those interviews. That was the sweet spot where most prospects said 'yes' without flinching. When he launched, he tested a higher tier at seventy-nine and a lower at twenty-nine. The forty-nine dollar plan had the highest conversion rate by far. Luna: So the interviews predicted the actual price point pretty well. Lucas: Within about ten percent, yeah. But here's the key: he also asked about their biggest pain point and how much that pain cost them annually. One agent told him that slow quoting cost him about twelve thousand dollars a year in lost business. That's way more than forty-nine a month. Luna: So he realized he could charge more. Why didn't he? Lucas: Because he wanted to maximize the number of customers, not revenue per customer. He was bootstrapped and needed cash flow fast to cover his own living expenses. Forty-nine dollars got him a yes from almost everyone. At seventy-nine, maybe half said no. Luna: That's a trade-off a lot of founders don't think about. They see a high price and think 'more revenue' but miss the conversion hit. Lucas: Exactly. And here's another angle: he asked a second question during those interviews. He said: 'If you bought this and it didn't work, how much would you feel you wasted?' That question gets at the perceived risk. Luna: What did they say? Lucas: Most said between twenty and fifty dollars. So he knew that pricing below fifty reduced the mental barrier to purchase. That's a common psychological threshold. Luna: So forty-nine was right under that ceiling. Lucas: Exactly. He didn't just guess. He had data from fifty conversations that told him: at forty-nine, the risk feels low, the value feels high compared to their CRM, and the conversion should be solid. Luna: I love that. But I wonder — what if you're building something completely new, something people don't have a comparison for? Lucas: Then you use a different technique. You ask about the cost of the problem, not the value of the solution. For example, 'How much time do you spend on this task per week? What's your hourly rate?' Multiply it out. Luna: So you're building the price from the pain itself. Lucas: Right. I saw another solo founder who built a tool for freelance writers to track pitch submissions. There was no comparable product. So he asked each writer: 'How many hours a month do you spend manually tracking pitches? What do you bill per hour?' The average was about six hours at fifty bucks an hour — that's three hundred dollars of lost time per month. Luna: So he could price at, say, twenty-nine bucks and still be a no-brainer. Lucas: He priced at nineteen, actually. He wanted to be an impulse buy. But he knew the ceiling was much higher. The interviews gave him the confidence to not underprice by too much. Luna: That's smart. And it's so much better than the typical approach of 'I'll just charge what my competitors charge.' Lucas: Which is often wrong because your target customer might be different. Or your feature set is different. Or your brand perception is different. Luna: So what's the actual interview process? How do you run these conversations? Lucas: First, recruit people who match your ideal customer profile. Not friends or family. Real potential buyers. You can find them on LinkedIn, industry forums, or even cold email. Luna: And you offer something in return? A gift card or early access? Lucas: Some founders do. But many find that people are willing to talk if you frame it as market research. Say 'I'm building a tool to help and I'd love your input.' Keep it to twenty minutes. Have a structured script. Luna: What's in the script? Lucas: Start with their current workflow. Then the pain points. Then the cost of the pain. Then the willingness to pay questions I mentioned. And finally, ask them to rank features by importance — that helps you decide what to build first. Luna: So you're getting pricing and product validation in one conversation. Lucas: Exactly. And the best part: after the interview, you can follow up with a prototype or a landing page and see if their stated willingness translates to actual clicks. The founder I mentioned had a pre-launch page with a 'sign up at forty-nine dollars' button. Twenty percent of his interviewees signed up. Luna: That's a strong signal. Lucas: It is. And it's way better than building something and then realizing no one will pay what you need. Luna: I want to try this with my next side project. I've been guilty of the 'guess and adjust' method. Lucas: We all have. But the data shows that founders who do even ten structured interviews before launch price more accurately than those who don't. It's one of those high-leverage activities that bootstrapped founders have time for — because we don't have a VC breathing down our necks to ship fast. Luna: Right. And speaking of time, we're able to produce episodes like this every day because of a small group of listeners who support the show. If these conversations are useful for what you're building, you can chip in at buy me a coffee dot com slash fexingo. It's what keeps this whole thing ad-free and going. Lucas: Yeah, it's a small but mighty group — and it literally funds the research and hosting. So thank you to those who do. Luna: Alright, back to pricing. Lucas, any final tip for a founder who wants to start these interviews tomorrow? Lucas: Yes. Don't ask 'Would you pay X?' — ask 'At what price would this be a no-brainer for you?' That open-ended question gives you a range, and you can analyze the distribution. The median answer is often very close to the optimal price. Luna: I like that. It's not about what they'd pay, it's about what feels trivial. Lucas: Exactly. Because if it's a no-brainer, they'll buy. And that's the goal — not maximizing price, but maximizing paying customers. Luna: Good stuff. Next episode, let's talk about how bootstrapped founders use customer churn interviews to fix retention. Lucas: Perfect. That's a natural follow-up.