Latest / The Bootstrapped Tech Founder with Fexingo: Profitable Software Companies Without VC / How Bootstrapped Founders Use Empty-Calendar Pricing Experiments
Transcript
- Lucas: So there's this bootstrapped project management tool — I'm not going to name it because they're still running the experiment — but last December, the founder decided to raise the monthly price by 40 percent. Luna: Forty percent? That's bold. Was it a panic move or did they have a plan? Lucas: Definitely a plan. They'd been flat on revenue for six months, and the founder figured the cheapest time to test a price increase was when nothing else was happening. No product launches. No marketing pushes. A quiet week between Christmas and New Year's when the calendar was basically empty. Luna: That's actually clever. Most people wait for a big feature drop to justify a price hike. But if you want to isolate the price signal, you want zero other variables. Lucas: Exactly. And the results were surprising — zero churn increase from existing customers, but a 12 percent uptick in upgrades to annual contracts. The founder told me the annual upgrade was almost an accident: customers saw the new higher monthly price, did the math on the annual plan, and felt like they were getting a bargain. Luna: So the price increase itself became a sales tool for the annual plan. That's a nice side effect. Lucas: Right. And the whole thing was reversible. They set a six-week experiment window. If churn spiked or new signups dropped, they'd revert and grandfather everyone back. They also grandfathered all existing customers on their old price — the increase only applied to new signups. Luna: Okay, that's the key safety valve. Grandfathering is what makes the experiment low-risk. You're not betting your existing revenue on the test. Lucas: And that's the core idea we want to dig into today: the empty-calendar pricing experiment. When your calendar is empty — a holiday week, a post-conference lull, a time when your customers are also distracted — that's actually the cleanest window to run a price test. You get the purest signal because there's no other noise. Luna: Let's break down the mechanics. First, how do you pick the right empty window? A random Tuesday in February? Or is there a pattern? Lucas: The best windows are when your customers are not making deliberate buying decisions. That sounds counterintuitive — you want to test when they're not paying attention? But that's exactly the point. You're not trying to convert them in that moment. You're trying to measure their reaction without the influence of a sales push or a feature launch. So think: the week between Christmas and New Year's, the week of a major industry conference when your audience is distracted, or even the last week of a quarter when everyone is busy closing deals. Luna: So a quiet period gives you a cleaner before and after comparison. But how do you actually set up the test? Do you just change the price on your pricing page and hope for the best? Lucas: No, you need a structured approach. First, define the metric you're testing. Is it average revenue per user, conversion rate from trial to paid, upgrade rate to annual, or churn? Pick one primary metric. The founder I mentioned used upgrade rate to annual as their primary metric, because they wanted to increase customer commitment, not just short-term revenue. Luna: Secondary metrics would be churn and new signup volume. If new signups drop but churn stays flat and annual upgrades go up, you might still be better off. Lucas: Exactly. Then you decide the test duration. The rule of thumb is: long enough to get a statistically significant sample, but short enough that you don't alienate customers if it goes badly. Two to six weeks is typical. The founder chose six weeks because they had a small customer base — about 2,000 paying accounts — and needed enough time for a meaningful number of signups. Luna: And you should announce it as an experiment, right? Or do you just change the price silently? Lucas: Most bootstrapped founders I talk to prefer to be transparent. They send an email to existing customers saying something like, 'We're testing a new pricing model for new customers. Your price stays the same. We'll let you know what we learn.' That builds trust and reduces the risk of backlash. The founder I mentioned sent a plain-text email with one link to a feedback form. Luna: That makes sense. You're inviting them into the process rather than surprising them. And you're also planting the seed that the old price is a deal — which reinforces their loyalty. Lucas: There's also a psychological layer here called price anchoring. When customers see a higher price — even if they're not affected — it resets their reference point. Later, if you ever do raise prices for existing customers, they'll compare to the higher anchor, not the lower one. It's a long-term move. Luna: So the empty-calendar test isn't just about revenue in the test window. It's about training your market to accept a higher price over time. That's a pretty sophisticated strategy for a solo founder. Lucas: It is. And the beauty is it costs almost nothing to run. No ad spend, no new features, no sales team. Just a pricing change and a revert date. If the experiment fails, you revert and you've learned something. If it succeeds, you've got a new baseline for your pricing model. Luna: One thing I wonder about: what if your product has a free trial? Does the price change affect trial users too? Lucas: Great question. Most founders I've seen apply the new price only to new trials that start during the experiment window. Existing trials that started before the change continue under the old price. That way you're not punishing someone who's already evaluating your product. Luna: And if the experiment succeeds, do you keep the price for new customers permanently? Or do you eventually raise it for everyone? Lucas: That depends on your philosophy. Some bootstrapped founders believe in never raising prices on existing customers — that's a core part of their brand promise. Others do a phased approach: new customers at the new price for six months, then they announce that existing customers will see a smaller increase, say 10 percent, with a six-month notice. The key is to communicate early and often. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. It's a small gesture that keeps us independent. Lucas: Yeah, we don't run ads, and listener contributions are what make that possible. So if you got something out of this episode, that's the link. Now, back to pricing experiments — let's talk about a common mistake. Luna: I'd guess the biggest mistake is not setting a revert date. Too many founders just change the price and see what happens, then feel committed to the new price even if it's hurting them. Lucas: Exactly. Without a revert date, you're psychologically locked in. The moment you see a slight drop in signups, you panic. But with a pre-announced experiment, you're just collecting data. The founder I mentioned had a calendar reminder for February 1 — that was the revert date. If the data wasn't clear, they would revert and try again later. Luna: Another mistake: testing too many variables at once. If you change both the price and the feature set in the same week, you don't know what drove the result. Lucas: Right. That's why the empty calendar is so powerful. Nothing else is changing. No new blog post, no email campaign, no feature release. You're isolating the price signal. And that gives you a clear yes or no answer on whether the new price works. Luna: Let's talk about a specific example outside of project management. I know a bootstrapped email marketing tool that ran a price test over Labor Day weekend. They had about 500 paying customers. They raised the entry-level plan from $19 to $29 per month for new signups, and grandfathered existing customers. Over the four-day weekend, they got 12 new signups — which was actually above their normal rate for that period. And no complaints. Lucas: That's a great data point. The key there is that they picked a holiday weekend when their customers — small business owners — were less likely to be checking email. So the risk of a public backlash was lower. And the new signups they did get were from people who were actively looking, not just browsing. Luna: Exactly. The quality of signups during empty periods tends to be higher because the noise is filtered out. People who sign up over a holiday weekend are more intentional. Lucas: So if you're a bootstrapped founder and you've never run a pricing experiment, here's a concrete playbook: pick a quiet window at least two weeks away, set a primary metric, choose a price increase of 20 to 40 percent, grandfather existing customers, announce the test as an experiment, set a revert date, and then analyze the data. Rinse and repeat. Luna: One more thing: what about price decreases? Could you test a lower price in an empty window? Lucas: You absolutely could. But the signal is a bit noisier because a lower price tends to attract more price-sensitive customers, which can increase churn later. Still, if you're considering a tier change, an empty-calendar test can show you the volume response without the interference of other marketing. Luna: Fair point. So the empty-calendar experiment is really a tool for clarity. It's about removing variables so you can see the true effect of price on customer behavior. Lucas: Yeah, and for bootstrapped founders who can't afford to lose a month of revenue to a bad pricing decision, that clarity is gold. You get a low-cost, high-signal test that you can repeat every quarter or every time you have a pricing question. And over time, you build a pricing muscle that most vc backed startups never develop because they're too focused on growth over profit. Luna: So the next time your calendar looks empty, maybe that's the perfect time to run a pricing experiment. Lucas: Exactly. Use the quiet to learn something loud.