132 users, 3 current customers, and a renewal failure I should have prevented
On April 21, 2026, StatusPage.me got its first paying customer (since the "reboot" in September last year).
Today, 81 days later after the first paying customer, the product has:
- 132 registered users
- 29 active users in the last 30 days
- 149 monitors created
- more than 42 million uptime checks performed
- 2 active annual subscriptions
- 1 lifetime customer
- 1 former monthly customer who did not renew
- $24.65 in normalized monthly recurring revenue (ARR/12)
So far, four customers have paid us at least once. Three are still active customers, but only two contribute recurring subscription revenue.
That distinction is less exciting than combining every payment into one large number, but it is considerably more useful.
The biggest lesson from the first 81 days is that usage, buying intent, and willingness to pay are three different things.
1. Product activity is not the same as buying intent
Some users do much more than casually create an account.
They create several status pages, configure monitors, connect custom domains, and invite teammates.
From the founder dashboard, that looks like a customer preparing to buy.
Sometimes it is.
Other times, they are evaluating alternatives, testing a specific workflow, or simply discovering how much they can achieve without paying.
I used to interpret deep setup activity as a strong conversion signal.
Now I treat it as a reason to investigate, not as a reliable prediction.
A user can clearly understand the product, invest time configuring it, and still not feel enough urgency to pay.
2. The work changed after the first payment
Before revenue, most of my attention went toward building features.
Once customers started paying, the priorities became much less glamorous:
- fixing billing webhook edge cases
- handling duplicate and delayed events
- cleaning up broken custom-domain states
- improving slow dashboard pages
- preventing invalid monitor configurations
- making downgrades and expired subscriptions behave predictably
- reducing situations that required manual repair
None of these improvements makes for an impressive launch announcement.
But once people depend on the product, operational correctness becomes part of the product.
A feature that works only in its ideal state is not finished. It is a future support conversation waiting patiently for its turn.
3. Revenue quality matters more than the largest available number
We collected roughly $430 during the last 30 days.
That includes annual and lifetime payments.
It is real cash, and for a bootstrapped product that matters. But it is not the same as having $430 in MRR.
The current recurring monthly revenue is $24.65.
Annual subscriptions improve cash flow. Lifetime deals help fund development. Neither should be presented as predictable monthly revenue just because the resulting headline looks more impressive.
The less flattering number is usually the one that tells you what the business actually needs to improve.
4. One customer churned, and I do not know exactly why
Our first monthly subscriber did not renew.
Initially, I treated that as ordinary churn. Later, I discovered that a bug had prevented the renewal reminder email from being sent.
The subscription expired, but I kept their status page active while I contacted them and provided a direct checkout link.
They still have not renewed, so I cannot claim the email bug was the only reason.
Maybe they no longer need the product.
Maybe the value was not strong enough.
Maybe the missed reminder broke the momentum at exactly the wrong time.
The uncomfortable part is that I allowed an avoidable operational failure to become mixed with a customer retention question.
Now I cannot cleanly separate product churn from billing-flow failure.
That is a much worse position than simply hearing, “We no longer need this.”
The lesson is not only that churn feedback matters.
It is that renewal infrastructure must be reliable enough that, when a customer leaves, you can trust that they actually made that decision.
What I am focusing on next
The immediate goal is not to inflate the feature list.
It is to understand why active users do not become customers, and why some customers do not remain customers.
That means:
- improving the trial-to-paid path
- identifying which actions genuinely correlate with conversion
- making plan limits and upgrade options easier to understand
- contacting users who completed meaningful setup but did not buy
- improving churn and failed-renewal feedback
- continuing to remove operational friction
StatusPage.me is no longer just an idea.
It has users, customers, real infrastructure load, and real operational obligations.
But usage is not yet a repeatable business model.
That is the part I am working on now.
I publish the underlying numbers on our Open Startup dashboard:
The distinction that stood out to me is between operational failure and product failure.
If a customer leaves because they chose to, that's valuable feedback. If they leave because your renewal process broke, you've lost the ability to interpret the signal. Protecting the quality of your feedback loops is just as important as protecting revenue.
That is exactly what bothered me most.
Losing the renewal is one problem. Losing the ability to understand why it happened is worse.
It made me realize that retention data is only meaningful when the billing, notification, and renewal flow is reliable enough not to contaminate the signal.
I think there's an interesting strategic discussion here that probably goes beyond what fits in a thread.
If you're open to it, what's the best email to reach you?
Happy to hear the strategic angle here first. What specifically did you notice about the product or positioning?