Solo SaaS niche check: verify the ledger, not screenshots

You are about to spend months on a small SaaS, so start with the ledger a stranger can verify. A screenshot can show a good month, a clean dashboard, or a flattering lifetime total. A stranger-verifiable ledger gives you a dated record you can test against your own hours, costs, and support load. Without a date, a number is just a memory, not evidence.

Screenshots are claims, not evidence

Founder screenshots are useful for spotting a pattern, but they are not a financial statement. They can hide churn, refunds, one-off spikes, or the cost of the ads that drove the traffic. When you are deciding whether to copy a niche, you need the same kind of evidence you would accept from a stranger: a dated record that shows whether the product is still earning.

For a solo operator, the question is whether the niche can support a price, a margin, and a support load that fit one person's week. Treat the public numbers as a benchmark, not a promise. Avoid building a product that needs a team you will never hire.

A ledger is the benchmark

StoryShort's Stripe ledger showed $21,175 MRR, 382 active subscriptions, $21,882.79 in prior-30-day revenue, and $553,387.33 in lifetime revenue as of 2026-08-30.

The ledger did not establish profit or a 27,000-user paying base, even though it recorded that lifetime total.

StoryShort's TrustMRR-verified revenue was $19,279 MRR with 347 active subscriptions.

StoryShort's public pricing lists Starter at $39, Growth at $69, Influencer at $129, and Ultra at $199.

Samuel Rondot created a standalone MVP in about two weeks after noticing a rival's public revenue and likely Facebook-ad traffic.

StoryShort operates without a growth team or external support staff.

That combination is worth studying because it shows a small product can be built quickly and run lean. Do not treat the numbers as a template for every niche. Treat them as proof that a stranger-verifiable record can separate a real revenue record from a story. If you cannot get that kind of record in your own niche, the benchmark is weaker.

When you study a profile like this, count the hours the founder saved, not just the revenue earned. A small build and a lean operating load matter more than a big headline number.

Test the niche before you write code

Use this list when a niche looks attractive. Each item is a yes/no test, not a research project. Answer each item from a stranger-verifiable source, or treat the niche as unproven. The list is short on purpose. A solo operator should be able to finish it before the idea gets romantic. A niche that needs a long due-diligence process may need a company, not a product.

• Ledger access. Open a dated payment record or a third-party verification page without a long wait.
• Per-subscription MRR. Divide monthly recurring revenue by active subscriptions, then ask whether the price is defensible.
• Volatility. Compare the recent month to the prior month and note any big gap.
• Margin and cost. Name the main costs and decide whether the margin survives them.
• Reuse of existing stack. Point to existing code, hosting, billing, or automation that would carry the product.

Ledger access keeps you from chasing a claim. Per-subscription MRR tells you whether the niche supports a price that pays for your time. Volatility shows whether the revenue is a trend or a spike. Margin and cost keep you from mistaking revenue for profit. Stack reuse protects your hours, which are the real budget.

Run the checklist before you write code. Move on if any item fails. Set a build time limit if all items pass, then revisit the ledger after the next billing cycle. Continue only when the numbers still hold; otherwise, stop before the hours compound.