A few weeks after launching PageCalm, I sat down to write a one-page product description. Halfway through, the document said something like "I'm building for small teams who can't justify $29/month for a status page." Then a few lines down it listed my Pro tier at $29/month.
That contradiction is how a four-hour pricing audit started.
What I thought my pricing was
When I launched PageCalm, I shipped three tiers:
- Free — 3 components, 50 subscribers, 5 AI generations per month (the code actually allowed 10, but that's a different story)
- Pro $29/mo — 25 components, unlimited subscribers, 100 AI generations, custom domain
- Team $59/mo — coming soon
The pricing page told a clean story: cheap on Free, get a custom domain on Pro, multi-page when Team ships. I launched and moved on to building features.
Then I went back and actually compared this against what every status page tool offers at every tier. That's when the picture got uglier.
What I found
Here's the part that hurts. The biggest player in the space — the tool I kept telling myself I was an alternative to — has a free tier with 25 components, 100 subscribers, 2 team members, and REST API access. Free.
I was offering 3 components and 50 subscribers. No API. I was materially worse than the incumbent's free tier. Anyone doing a side-by-side picked them and I never even got a shot.
It got worse on Pro. At $29/month, the established player's Hobby plan gave 250 subscribers, 5 team members, 5 metrics, custom CSS, and a REST API. My Pro at $29 gave a custom domain and 100 AI generations and not much else they didn't already have.
So my marketing claim — "cheaper than the alternatives" — was simply false. I was the same price with less feature surface, riding entirely on the AI Incident Writer to carry the difference. That's a bet, but it's not a price story. I was telling the wrong story about my own product.
The deeper problem
The free tier was a conversion leak. Every prospect who actually compared was walking away. The Pro tier was priced for a buyer who didn't exist — someone who wanted AI writing badly enough to overlook everything the established players had that I didn't.
And I'd built the whole thing around a positioning sentence I couldn't actually defend with a feature list.
When you're a solo founder building a SaaS, this kind of self-delusion is easy. You write the pricing page once during launch week, you're proud of it, and then you don't look at it again for months because you're heads-down on features. Meanwhile the assumption that anchored the whole thing — "I'm the cheaper alternative" — is rotting quietly because you never went back to check.
What I changed
I rewrote the pricing structure. Three things mattered most.
Free got dramatically more generous. 25 components instead of 3. 100 subscribers instead of 50. 15 AI generations instead of 10. The math on this is straightforward: components are database rows (free), 50 extra subscribers cost essentially nothing in email, and AI generations on a cheap model are fractions of a cent. The only reason these limits were tight in the first place was lazy gut instinct, not actual cost analysis. Loosening them costs me nothing and stops me from losing every Free tier comparison.
I added a Starter tier at $12/month. Bootstrappers don't want a $29 commitment when all they need is a custom domain and the badge removed. $12 is cheap-SaaS pricing — the cost of a single lunch — and it gives free users a meaningful first upgrade before the full Pro jump. Custom domain, unlimited components, 250 subscribers, 30 AI generations. Same Pro features at lower limits.
Pro gets caps where it should, and stays at $29. I removed the "unlimited subscribers" claim from Pro and replaced it with a 1,000 subscriber cap. This was the hardest change emotionally because "unlimited" sounds great, but the math is unforgiving: a single consumer-scale customer with 20,000 email subscribers and 10 incidents a month would generate 200,000 emails — about $180 in Resend costs against their $29 subscription. One pathological customer wipes out six profitable ones. Caps protect margin. They also force the right conversation when someone outgrows the tier.
I also retired the Team tier from the pricing page entirely. It was "coming soon" with no real ship date and no real feature gap to justify it. That one's permanent — multi-seat shipped as a universal feature across every plan (up to 25 members on Free) and there's no reason to put a paywall in front of your teammates during an incident.
The principles I wrote down
The most useful artifact from the audit wasn't the pricing change. It was a short internal document — a pricing philosophy — I wrote to capture why the new tiers look the way they do, so the next time I'm tempted to change something reactively, I have to argue with my past self first.
The five principles that anchor it:
- Don't compete on price. Compete on focus. Anybody can drop their price tomorrow. Nobody can copy who I built the product for.
- The Free tier is a conversion engine, not a charity. A Free user who eventually converts is worth more than any amount of saved AI spend. If a limit on Free isn't saving me real money, it's just hurting conversion.
- Caps protect margin, not punish customers. Set caps so a normal user never notices and a 10x outlier is forced to upgrade before they cost more than they pay.
- Price for the future product, not the current one. Slack integration, custom CSS — they were on the roadmap. I hold $29 for Pro now and ship those features into it later. Existing customers get them included. I never raise the price to "pay for" features that were always planned. That's how trust dies.
- Plan limits live in one place. I had limits hardcoded in five different files before the audit, and yes, two of them had drifted out of sync. There's now a single source of truth in code. Drift is a tax you keep paying until you eliminate it.
What shipped since
The audit identified specific feature gaps, and since then I've been closing them:
- Webhook API for creating incidents from monitoring tools — the API gap is now closed.
- Draft incidents — webhook-created incidents start as drafts so you can review AI-generated updates before publishing.
- Slack notifications — incident updates pushed to your team's Slack channel, included on every plan including Free.
- Multi-seat accounts — up to 25 team members on every plan. No per-seat pricing.
The pricing restructure gave me room to build. The feature work filled the gaps the audit uncovered.
What this means if you're a PageCalm user
If you're on Free, you have a much more generous Free tier. Same product, better limits, no action needed.
If you've been thinking about a custom domain but $29 felt like a leap, Starter is your option at $12. Same custom domain support, same no-badge experience, just lower headroom on subscribers and AI generations.
If you're already on Pro, nothing changes — you keep everything you had, and I'll ship more features into the same price over time.
What I learned
Pricing audits are uncomfortable. You have to admit your launch-week instincts were wrong, you have to do math you'd rather not do, and you have to compare yourself honestly against tools that have years of head start. It's a lot easier to keep building features and assume the pricing page is fine.
But every day that pricing page stayed at "3 components on Free" was a day I was losing prospects I never even saw. Conversion leaks don't show up in your dashboard — they show up as silence. Nobody emails to tell you they bounced.
If you run a small SaaS and you haven't actually opened your competitor's pricing pages in the last six months, that's your next project. You might find what I found.
I'm building PageCalm — a status page tool for small SaaS teams with an AI incident writer baked in. Free, Starter at $12/month, and Pro at $29/month. Find me on X @elistrattondev or check it out at pagecalm.com.