A revenue screenshot can make a small software business look easier to copy than it is. It may show money coming in, but not whether the number is current, what drove the sales, or how much work went into getting them. That gap is the problem Income Claim Check is built to examine: public income claims from indie hackers, checked against evidence where possible and labelled when the evidence falls short.
A claim is not the same as proof
The site is a content archive, not a finance tool. It gathers claims circulating on X, Indie Hackers, and newsletters, then publishes write-ups that link back to the original claim and to payment or other primary-source evidence when available. Its stated aim is to distinguish what can be supported from what remains a founder's account.
That distinction matters because a revenue figure can be technically real and still leave important context out. A payment-platform reading may support that transactions occurred, while saying little about whether the business is growing, whether the product is still live, or whether its sales came from a repeatable channel. A founder interview can supply useful context, but it is not the same kind of evidence as a payment record. Income Claim Check presents these differences through verdicts such as verified and partially verified, rather than treating every number as equally established.
How the checks are presented
The archive is the main way in. Readers can search and filter evaluated claims, then open an individual check to inspect its findings and linked sources. The visible examples pair a short business description and claimed revenue with an explanation of what evidence was found and why the verdict was assigned.
The site's stated review framework looks beyond revenue evidence. It also considers whether the product is live, signs of demand, the author's credibility, solo feasibility, how replicable the business might be, and timing or competition. A verdict bench displays scores across those dimensions and shows how they contribute to the overall result. In practice, that gives readers more to work with than a single green checkmark: a claim may have payment support while its growth story, author, or business model remains less certain.
This is useful for people researching small software businesses before choosing a market or spending time building. The archive can help surface the difference between a reported success and a model with evidence behind it. It is also a form of finance-content for readers who want sources attached to the story, not just a revenue number passed around as fact.
What the verdict cannot settle
The framework is a way to assess public claims, not an independent audit of a company's books. The site itself says its revenue figures are claims it checked, not audits. A payment-platform reading can support a revenue figure without proving profit, customer retention, acquisition costs, or the founder's take-home income. Those are different questions, and the described checks do not promise to answer all of them.
Some claims may be only partly verified or remain unverified because the evidence is missing, indirect, or old. The write-ups can explain that uncertainty, but they cannot make unavailable records appear. The scores also involve judgments about matters such as replicability and solo feasibility. They offer a consistent set of lenses, not a guarantee that another founder can reproduce the outcome.
That makes the archive better for informed skepticism than for investment decisions or build instructions. It is not a payment processor, financial advice, or a get-rich guide. Readers should follow the sources and treat the verdict as a reasoned assessment of the material available, not a certification of the underlying business.
A reference, not a blueprint
The site is free and runs on the web. Its narrow focus is its practical boundary: it checks public income claims, rather than helping a founder measure their own finances or plan a startup. The value depends on whether a particular claim has enough public evidence to examine, and on readers being willing to look past the headline number to the sources and caveats.
Income Claim Check is for indie hackers and startup researchers who want a more grounded starting point for evaluating online revenue stories. It is not for anyone looking for audited financial statements, a complete account of how a business runs, or a recipe they can copy with predictable results.
Real indie income claims, with proof