A streamer attribution tool for indie devs has real demand and a structural data problem baked in.
There's a post on r/gamedev from a few months back. Developer talks about clawing their game back from Steam obscurity, mentions a spike after some streamer coverage, then says something that stuck with me: they had no idea which streamer actually moved the needle. 70 upvotes, 55 comments, half of them being other devs saying "same."
That post is the seed for Streamer Attribution & Campaign Tracker for Games. And honestly, the demand signal is about as clean as you'll find in this space.
If you've shipped an indie game on Steam, you know the feeling. You wake up to a wishlist spike. Something happened. You check Twitter, you scan Twitch VODs, you Google your game title. Maybe you figure it out. Maybe you don't. And even when you do find the streamer, you're left doing mental math with incomplete data: estimated viewers, rough conversion guesses, no actual revenue numbers.
Keymailer and Lurkit have been around for five-plus years handling key distribution to creators. G2 reviews for both tools have the same complaint showing up repeatedly: no way to tie streams to sales. Devs are already paying for an incomplete workflow. That's the wedge.
The proposed solution is a dashboard that issues unique keys or links to streamers, pulls from Twitch and YouTube APIs to detect stream events by game title, and cross-references those timestamps with Steamworks data to generate per-creator attribution cards. The "aha moment" in the pitch is specific: you see that a streamer's two-hour session on a Tuesday correlated with 47 wishlists and roughly $340 in estimated revenue in the 24-hour window after. Vague correlation becomes a named, quantified number.
I genuinely like that framing. It's the right product instinct.
Here's where I have to slow down, because the fatal flaw here is not minor.
Steamworks does not expose per-referrer sales counts. Valve buckets traffic into categories like "External Website" without named source URLs or individual creator identifiers. That means you cannot actually close the attribution loop on revenue. What you can do is correlate timestamps, look at sales/wishlist deltas in a time window, and present that as an estimate.
The tool's own risk section acknowledges this and suggests marketing it as "statistically correlated revenue lift estimates." That's honest. But it's also a fragile foundation for a product whose entire value proposition is "know exactly who moved the needle."
Wishlists are granular in Steamworks and are a real data point. But devs care about revenue, and the revenue number will always be a proxy. If beta users feel like the numbers are educated guesses dressed up in a dashboard, trust collapses fast. This isn't a marketing problem you can write your way around. It's a data access problem that Valve controls.
And Valve has a history of changing or restricting API access without warning.
The other thing that keeps nagging at me: indie devs don't have ongoing campaigns. They have launches. Most use Keymailer or Lurkit in a 6-8 week window around a release and then go quiet.
A $29-79/month SaaS built on that pattern faces real structural churn. The proposed fix is a "pre-launch campaign planner" that keeps devs engaged 3-6 months before launch. That's a reasonable idea, but it's also a second product with its own scope. Solving the launch-window usage problem by building planning features is the kind of thing that sounds clean in a pitch and gets complicated fast in practice.
The math isn't hopeless. Blended LTV of ~$936, 88% gross margins, break-even at 17 customers. Those numbers are fine for a bootstrapped solo project. But the churn assumption baked into that LTV (18-24 months average) feels optimistic given the launch-cycle dynamics.
The counterargument section of this idea includes something I think deserves more attention: Lurkit and Keymailer have consciously chosen not to build deep attribution after five-plus years. That's not an oversight. Either they've tried and hit the same Steamworks wall, or their users don't actually pay for it when it's on the table.
The "why now" argument also has a timing problem. Mature Twitch and YouTube APIs, rising creator costs, devs caring more about ROI. All true. Also all true since roughly 2019. If the market timing was compelling, someone would have shipped this already. Maybe the answer is that no one has executed well on it yet. Maybe the answer is that the Steamworks data ceiling kills the product before it gets traction. I genuinely don't know.
What I do know is that the Lurkit partnership angle mentioned in the differentiation section is probably the smartest move available. Becoming their attribution layer instead of their competitor sidesteps the CAC problem and gets distribution on day one. Whether Lurkit would actually do that deal is a different question.
The validation test here is unusually concrete and I respect it. Build a Notion template. Pull Steamworks CSVs, cross-reference with SullyGnome stream data, produce a per-creator ROI card by hand. Offer it free to 10 devs on r/gamedev. Charge $50 flat for the next 10. If 5 pay, the problem is real.
That's a good test. It also tells you something important: if the manual proxy numbers feel useful to devs even knowing they're estimates, you have something. If devs look at the estimated revenue lift and say "I can't trust this," you have a problem that no amount of technical polish will fix.
The AI angle is actually the most interesting long-term play here. Natural-language campaign debrief summaries that say "your best performer was a mid-tier Twitch streamer whose session drove an estimated 12x ROI, recommend offering $300-500 for your next launch" transforms a dashboard into something that feels like advice. That's harder to replicate than the underlying data. But it only matters if people trust the underlying data in the first place.
Do the manual version first. Ten devs, two weeks, real feedback. The product question and the trust question both get answered at the same time.