How to Read Our Gumroad Product Estimates
Historical inputs, reproducible calculations and the limits of the public archive.
What these public examples measure
Use an estimate to select products for closer investigation. Your own sales export is the reference for actual revenue; public competitor signals cannot reveal private transactions, costs or profit.
This page documents historical examples published on this site. It is not a validation study of the paid product or a statement that every current report uses the same calculation.
Where the inputs come from
| Input | Available evidence | Limit |
|---|---|---|
| Listed price | Stored USD value and product URL | Historical prices and discounts may differ; check the live listing. |
| Sales proxy | A preserved numeric input from the historical dataset | The original derivation of each sales proxy is not recorded in this archive. |
| Revenue estimate | Stored price multiplied by the sales proxy | A model output, not a transaction total or profit. |
| Time | Archive date: March 17, 2026 | Original collection date and revenue period are unknown. |
A sales proxy must not be relabeled as a verified sale count. We can reproduce the multiplication and identify the listing, but cannot reproduce the upstream inference without its original derivation.
A revenue estimate you can reproduce
10 selected public product examples are preserved in this archive. Original collection date and revenue period are not recorded. This is a historical example set, not a representative market sample.
Stored calculation for Ultimate Brain for Notion: $129 × 15,093 = $1,946,997. It combines a listed price and a sales proxy: a reproducible model, not verified earnings or monthly revenue.
Historical prices, discounts, refunds, bundles and transaction costs can change actual earnings. Reproducing arithmetic does not measure the model’s error.
Download the source archive (JSON). The file includes product URLs, archived values and the source revision. Unknown dates remain null instead of being replaced by today’s date.
Suggested citation: InsightRaider, Selected Gumroad product examples, archive dated 2026-03-17. Cite this snapshot and its limitations together; do not describe it as audited seller revenue.
What would establish accuracy?
Validation needs dated seller records, matching products and periods, treatment of refunds and discounts, a defined sample and a published error calculation. This archive supplies no such study, so we publish no validated accuracy percentage for these examples.
From a snapshot to a weekly comparison
- Choose offers serving the same buyer and problem. Record billing period, license and included support.
- Keep dated observations of each listing. An editorial update does not refresh the underlying data.
- Compare matching fields and periods. A changed price or model can change an estimate without new sales.
- Test one pricing or positioning decision against your own customer feedback and sales.
The public archive has no dated observation series, so it cannot demonstrate weekly growth. Check observation dates and coverage separately for any current report.
Use the evidence for your next decision
Start with product examples, then choose a workflow for your research.
Public examples are free to read. Dashboard access requires a paid subscription; review the offer and access conditions first.
Create an account · Offer and access conditions
What a revenue estimate tells you
InsightRaider helps digital product sellers compare the market around an existing offer. Its revenue figures are estimates derived from public signals, rather than access to a creator's private payment account. Use them to identify products worth investigating and to follow changes over time. They are not a substitute for a seller's own sales records, and they do not tell you how profitable a business is.
Revenue and profit answer different questions. A product with substantial sales may also have advertising, affiliate, support, production, or refund costs. Public marketplace information rarely provides that complete picture. Before comparing two figures, check the product format, price, currency, period, and observation date. A lifetime estimate for a download cannot be compared directly with a monthly subscription figure.
How public signals inform the estimate
The starting point is information visible around an offer: its listed price, category, reviews, ratings, and other available marketplace signals. Revenue estimation combines these observations with assumptions about the relationship between public activity and sales. Availability differs between products and platforms. A mature download with years of reviews provides a different kind of evidence from a recently launched community.
A review is evidence of a review, not a transaction count. Buyers do not all leave feedback, and the share who do can vary with the product, audience, and seller's requests. Likewise, a listed price may differ from the amount buyers paid after discounts or earlier price changes. Treat a single signal as one part of the comparison, rather than proof of a precise revenue total.
Illustrative example: why assumptions matter
Consider a hypothetical $40 download with 20 buyer reviews. If, purely for illustration, one in twenty buyers left a review, the implied volume would be 400 sales. Multiplying by the listed price produces $16,000. If one in ten buyers left a review, the same public observations imply 200 sales and $8,000. Neither assumption establishes what the seller actually earned.
This simplified example is not InsightRaider's production formula and not an accuracy guarantee. It shows why apparently small assumptions can change an estimate substantially. It also omits discounts, refunds, taxes, and price history. The useful question is whether the product belongs in your comparison set and which additional evidence would make your decision more reliable.
Read an estimate in four steps
First, establish what is being sold. Open the creator's current listing and check the deliverable, intended customer, license, and payment schedule. A template bundle and a membership may share a category while solving different problems. Remove products that would not be credible alternatives for the customer you serve.
Second, compare several relevant offers rather than treating the highest figure as typical. Third, inspect the surrounding evidence: review activity, price changes, and the history available for that product. Fourth, write down the action the evidence supports. That might be testing a clearer package description, investigating a support gap, or monitoring a competitor for another week before changing your own offer.
Understand uncertainty and update timing
InsightRaider's market data is refreshed weekly. A weekly observation is a dated snapshot, not a live payment feed. Short promotions, a changed bundle, a relaunch, or a switch between one-time and recurring pricing can complicate comparisons. Missing history means there is less evidence to interpret; it should not automatically be read as zero sales or a failed product.
For an important decision, compare the observation date with the current storefront and repeat your review after another update. Record what changed and what remained uncertain. A movement in an estimate does not, by itself, establish the cause. Your own conversion, retention, and support data remain the strongest evidence for deciding whether a change worked for your business.
Questions about the data
Can an estimate prove that my idea will sell? No. It can help you identify existing offers and formulate a test, but customer conversations and actual purchases are needed to assess your own offer. Does a higher estimate mean a better product? No. Fit, quality, audience size, age, and promotion can all affect the comparison.
If a listing looks wrong, send the product URL, the field in question, the observation date, and the public source you checked through our contact page. Those details make a discrepancy easier to investigate. Avoid sending customer records or private payment credentials. For a practical research routine, continue with the dashboard guide below.