01
Add your game.
Paste your Steam store URL or appid. We pull the public metadata, assign your title to a cohort, and show you exactly why — every classification comes with its reasoning attached.
Titlesignal reads your own Steamworks history and computes a revenue trajectory as a P10/P50/P90 band — then tells you what the band means for launch timing and discount depth.
read-only API key · encrypted at rest · revoke anytime
$42k — $98k
P10 $42k · P50 $70k · P90 $98k
Launch week · developer-net · your inputs only
Illustrative range — your real band is computed from your own Steamworks history, not from a rule of thumb.
How it works
01
Paste your Steam store URL or appid. We pull the public metadata, assign your title to a cohort, and show you exactly why — every classification comes with its reasoning attached.
02
Upload your Steamworks exports (wishlists, sales, traffic — any interface language), or connect a read-only API key later for daily sync. Key activations are separated from paid units automatically, so a press-key wave never looks like a launch.
03
Your trajectory arrives as a P10/P50/P90 band with the model version stamped on it. Your first band appears as soon as your history covers 56 days; with a full export, that's minutes after upload. Wide band? That's the honest answer. It narrows as your history grows — never because we squinted.
What you get
Wishlist forecasts as P10/P50/P90 ranges, computed from your own history and stamped with the model version — so you can hold us to what we said last month. Revenue bands arrive when your own sales history — or your cohort — can carry them. Until then the panel says so instead of guessing.
Wishlists, paid units, revenue and traffic on separate, timezone-correct axes — with key activations shown apart from sales, because they are not sales.
See what the calendar costs you: our timing view flags crowded weeks so your launch doesn't drown in someone else's marketing budget.
What a −20% actually does to your net revenue, computed from your own price history — not folklore from a forum thread.
Anomaly alerts with context: when your wishlists spike, we tell you it happened AND where the traffic came from.
Invite your artist, your publisher contact, your accountant — roles from viewer to owner, org-level isolation, audited.
The method
Every forecast Titlesignal produces follows four rules, and they are product law, not marketing:
“$312,000.” — false precision
P10 — P50 — P90 · the honest shape
R1
If the data supports a wide range, you see a wide range. A precise-looking number would be a lie with good typography.
R2
We never scrape store pages, never estimate another developer's revenue, never train on your private numbers. Comparative figures, where they appear, are aggregates over a cohort of at least eight consenting titles — never attributable to anyone.
R3
Every model component must outperform a naive forecast on a preregistered backtest before it reaches your screen. If the simple answer wins, you get the simple answer.
R4
Estimated net multipliers, untagged traffic share, publisher-era gaps in your history — every known limitation is printed on the output, not buried in a footnote.
Your data
Free calculator
Your wishlists, your conversion, your price — a range in ten seconds. Illustrative math until you connect your data; then it's your real band.
$42k — $98k
P10 $42k · P50 $70k · P90 $98k
Launch week · developer-net · your inputs only
Illustrative range — your real band is computed from your own Steamworks history, not from a rule of thumb.
FAQ
No — and we won't build it. We only work with data our customers own and chose to bring. Aggregate cohort medians (minimum eight titles) are as close as anyone gets to anyone else's numbers. This is a product rule, not a limitation waiting to be lifted.
“around $300k…?”
one guess · no shape · no plan B
$198k — $312k — $487k
P10 floor to plan on · P50 · P90 upside
illustrative — your band comes from your own history