40 Days After Launch: 200+ Daily Active Users, But $0 Revenue
Hey Indie Hackers,
I launched my product SoonLab about 40 days ago.
It’s an AI game maker platform where people can create and play simple games with prompts. The product is still early, but we’ve already reached 200+ daily active users.
At first, I thought this was a strong signal.
People are coming back.
People are creating games.
Some users even share feedback, suggestions, and bugs with us.
But here’s the uncomfortable part:
Revenue is still $0.
No paid users yet. No real monetization signal.
So now I’m trying to understand what this really means.
Is it a pricing problem?
Is it a product value problem?
Is it because the current users are curious, but not willing to pay?
Or is it normal for an early-stage AI product to get usage before revenue?
One thing I’ve learned is that “users” and “customers” are not always the same thing.
Getting people to try something is not the same as getting them to pay for it.
Right now, I’m thinking about a few possible next steps:
Add a clearer paid plan with stronger limits for free users
Talk to active users and understand what they would actually pay for
Focus more on creators who want to publish, share, or monetize their games
Improve the product before pushing monetization harder
Test small paid features instead of launching a full pricing system too early
I’m curious how other founders think about this.
If you had 200+ DAU but $0 revenue after 40 days, what would you do first?
Would you focus on monetization now, or keep improving activation and retention?
Would love to hear honest thoughts.
The distinction between "users" and "customers" you're hitting on is real, and it's often the hardest thing to internalize when you have engagement but no revenue. I'd prioritize talking to your most active users before touching the product or pricing — specifically ask them what would make them pay, not whether they'd pay. You'll often discover the monetizable use case is slightly different from what you built. The "200 DAU" number also hides a lot — if 10 power users account for 80% of activity, your monetization path is very different than if it's 200 casual browsers rotating in and out. Do you have any sense of that breakdown?
This feels less like a pricing issue and more like unclear monetizable value. In AI game tools especially, users will create and play for free unless there’s a strong “publish, distribute, or monetize” incentive tied to payment.
200 DAU in 40 days is a fantastic engagement signal, Nolan, but you hit the nail on the head: users are not customers. Right now, you are subsidizing their AI computing costs for free, so of course they are happy!
Before changing the product or building new features, you need to test price elasticity immediately. I’d recommend putting up a hard paywall or strict daily limits on free prompts. If your retention drops to zero, you know it was just a novelty tool. If a percentage of those 200 users upgrade or complain bitterly about the limits, you’ve found your core value proposition. Give them a reason to pay before you spend more time building!
The question worth sitting with: are the people coming back doing the thing that would make them pay, or are they doing something adjacent to it? Sometimes high engagement masks the fact that the core paid use case hasn't been reached yet.
The gap between active users and revenue is real — congrats on 200+ DAU though, that's solid traction. Have you tried using n8n to automate user follow-up sequences? I built a workflow that triggers personalized onboarding emails based on in-app behavior at near-zero cost. Happy to share the workflow if useful.
i'd do one thing before any pricing changes: find your five most active users and ask them directly what they would pay for. not in a survey, on a call. and ask specifically what outcome they're trying to get from the platform not what features they want. that conversation usually reveals whether you have a pricing problem or a value problem and those require completely different fixes. have you done any of those calls yet and if so what did you hear
Maybe try: 1. Segment users by behavior (builders vs tinkerers). 2. Talk to the top 10–20 builders and ask what outcome they’re trying to achieve and what would feel “payworthy.” 3. Test a tiny paywall exactly where that outcome happens (e.g. publishing, exporting, or building a collection), instead of a broad pricing page.
Thank you!
Honestly, congrats on the 200 DAU, that's the hard part and you've already cleared it. I'm over here building an AI travel app still scratching for traffic, so from where I'm standing that's a great place to be.
For what it's worth, I wouldn't touch monetization hard yet. People coming back daily is the rare asset, don't risk killing it to chase early revenue. I'd keep pouring into the users first, make the thing genuinely sticky, and let the paywall come later.
The model I keep thinking about is how Anthropic and OpenAI do it. They let people use the thing pretty freely, and the limits tighten gradually as the value becomes obvious. You earn the right to charge once people can't imagine going back. Same logic for you: grow the usage, then slowly lower the free limits as people get hooked, instead of slamming a pricing wall up on day 40.
Talk to your most active users before anything though. They'll tell you what they'd pay for way better than any guess.
Keep posting your evolution, rooting for you.
Thank you, really appreciate this.
I agree with the idea of not forcing monetization too hard too early. Right now, my priority is still to make SoonLab more useful and sticky, especially for users who are actively creating and sharing games.
The Anthropic/OpenAI comparison is helpful. Let users feel the value first, then introduce limits more naturally when the value is clear. That feels much better than adding a hard paywall before we fully understand the user behavior.
And yes, talking to the most active users is probably the most important next step. I want to understand what they keep coming back for, what feels missing, and what would actually be worth paying for.
Thanks for the encouragement. I’ll keep sharing the journey.
200 da u is good, but it is not revenue. ask the 10 most active users what they would pay for.
200 DAU means you have an audience problem solved but a willingness to pay problem unsolved, and the fastest way to find out is just asking your most active 10 users what they would pay for, not what features they want.
Thanks!
200+ DAU with $0 revenue is still useful, but I would not read it as validation yet. I’d read it as attention plus habit, not payment intent.
The first thing I’d test is not a full pricing system. I’d test where the value becomes serious enough that a user would accept a limit.
For SoonLab, the paid buyer is probably not the person casually making one prompt game. It is more likely the creator who wants to publish, share, remix, or build a small game collection around an audience.
So I’d separate the users into two groups:
people playing with AI game creation for fun
people trying to make something they can share publicly
The second group is where monetization probably starts.
I’d test one simple paid wall first: free users can create and play, but publishing/exporting/sharing more serious game projects sits behind a small paid plan.
That tells you whether people value the output enough to move beyond curiosity.
Happy to put a tighter version in writing if useful. I’d map the monetization test, free vs paid limits, first paying segment, and a 7-day plan to find whether SoonLab has real revenue intent.
This is very helpful, thank you.
I agree that 200+ DAU is more like attention + habit, not real validation yet. The split between casual users and creators who want to publish/share is especially useful.
We’re also starting to think that monetization should probably begin around serious output, not basic creation. A simple paid wall around publishing, exporting, or sharing more complete projects sounds like a much better first test than launching a full pricing system.
Would love to see your tighter version if you’re open to sharing it.
Yes, this is exactly the part I’d make more structured.
The risk now is testing monetization too broadly and learning the wrong thing. If casual prompt-game users reject payment, that does not mean SoonLab has no revenue potential. It may only mean the paid wall is being shown to the wrong usage type.
The useful version is separating curiosity usage from serious output intent.
Drop your email and I’ll send over the tighter version. I’d keep it focused on the first paid boundary, the creator segment most likely to pay, and a simple 7-day test to see if SoonLab has real revenue intent.
The "200 DAU, $0 revenue" pattern isn't a pricing mystery. It's a category structural issue worth naming before any monetization tweak.
Three things to pressure-test:
Category is brutal. Roblox owns AI-enabled game creation with real creator economy ($1B+ paid to creators). Rosebud AI, Buildbox, GDevelop, Unity Muse compete in adjacent lanes. Roblox can ship AI generation tomorrow with 70M DAU and creator monetization already built. Solo platform play against this is structurally hard.
Plays-per-game on your featured grid run 100-1000. This is your best content. Long tail likely much worse. AI-generated games tend toward "play once, never return" — novelty without depth, no progression, no social loops. What's your D7/D30 retention? If users churn after first game, no monetization model survives.
The "users come back" claim needs scrutiny. 200 DAU could be 50 power creators + 150 curious browsers. Without retention curve, DAU is vanity. Real question: what % of week 1 users still active week 4?
The deeper question isn't monetize vs improve. It's: who comes back, and why? If users return because they enjoy throwaway games, monetization fails because no game generates engagement worth paying for. If users return building real games with progression/saves/sharing — that's monetizable. Different products entirely.
Your 5 listed steps are all reactive tweaks, none addresses this. Real strategic paths:
Lean into creator economy — players pay creators, you take cut. Needs 10-100x current player base. Hard but Roblox-validated.
Pivot to B2B — sell to game studios/marketing teams who want rapid prototyping. Higher revenue per customer, smaller market.
Niche down to specific game type for specific audience. Defensible if narrow.
Accept platform doesn't work consumer — pivot to creator tool/API for other apps.
Really appreciate this. This is probably the most useful way to frame the problem.
One thing that stood out to me is that active users and paying users can sometimes be separated by a perception gap.
Usage tells you what people are doing. Feedback, suggestions, and bug reports tell you they are engaged. But neither necessarily tells you what role the product occupies in their mind.
For example, users may return frequently because they see it as:
while the founder sees it as a creator platform or business tool.
Those can produce very similar usage metrics but very different monetization outcomes.
The trap is that healthy activity can make both sides believe they are talking about the same product when they may not be.
Before making major monetization decisions, I would want to understand how active users actually describe the product in their own words. That perception gap might explain more than the pricing model does.
Thank you for your suggestion!
200 daily users at $0 is a genuinely interesting spot — people clearly want the thing, so the money question feels separate from the "do they care" question. I've got a free tier on my own project and go back and forth on this constantly. Are you treating the $0 as a pricing/packaging problem to crack, or are you okay sitting in the free-growth phase longer to build the base first?
The price points don't look like show stopper at all. The homepage is overly populated and is direct showing promot box. I suggest you to create some compelling games by youself and shocase those on home page. Write something about product and the unique value propostition of your tool. Then provide a CTA button to get to the prompt page.
Basically what i think is you must study the pattern of users using your platform was it just a one time curiosity action or they are trying to use the platform regularly, this data needs to be now converted to a useful information of analytics then you will understand much about your product and how people are using it that way either you get more ideas for improving or (dont take me wrong) sunsetting the product is worth. I personally feel the idea is good... i dont know if your user develop the game for selling in yes then there is again your monetisation option just like play store and app store concept, in simple terms you can be Steam
I'd also look at repeat usage as a leading indicator. DAU can show interest, but consistent creation activity is what typically signals real user value and future monetization potential. Understanding how often users come back to create may be more insightful than the headline DAU number itself.
You're already very impressive. My platform, Briefcast, currently only has a handful of users. Having users is a great thing because as a platform, monetization won't happen immediately. It's more about users creating value for themselves on the platform. If they can generate value, the profit model is just a matter of product strategy. Furthermore, you should focus more on what these users are doing on the platform, what they find good and bad, and address their core needs. That's how you achieve your breakthrough from 0 to 1.
Great framing on the separation. One thing worth adding: the 200 DAU number only matters for monetization if the same users are creating repeatedly, not just generating once out of curiosity. If you track creator retention separately from raw DAU, you'll probably find the real paying segment is much smaller but much more qualified. The upgrade prompt test should be targeted at repeat creators specifically — that's where you'll get honest signal on willingness to pay.
I'd separate the test into two numbers before changing pricing: creator retention and creator intent. 200 DAU only matters for revenue if the same users repeatedly finish or share games, not just generate one thing for novelty.
A low-friction test: add one paid-only export or publish constraint for the top creators and measure attempted upgrades, not completed upgrades. If nobody even hits the constraint, monetization is premature; if they hit it and complain, you finally have a pricing conversation with the right segment.
The feedback, bug reports, and feature suggestions you're already receiving are more valuable monetization signal than you're treating them. You don't need a new user research initiative — you need to read what you already have differently.
Bug reports tell you who cares enough about the product working correctly to spend time reporting it. Those users have already made an emotional investment. Feature suggestions tell you what someone wishes the product could do — that's almost always what they'd pay for if it existed. If you categorize your existing messages by theme, you'll probably find 2-3 clusters that show up repeatedly. The most common feature request cluster is likely your first paid tier.
The more important question underneath all of this: have you actually asked anyone to pay for anything yet? "200 DAU and $0 revenue" could mean nobody wants to pay, or it could mean you haven't presented a payment option with any friction. Those are completely different diagnoses. If there's been no paywall, no upgrade prompt, no checkout flow — then you have zero information about willingness to pay, and you need to create that test before drawing any conclusions.
On aryan_sinh's structural critique: the Roblox concern is real for the consumer platform path. But there's a B2B angle that sidesteps it entirely — game studios, marketing teams, and educators who need rapid game prototyping don't care about Roblox's creator economy. If any of your 200 DAU are using this for something professional rather than recreational, that segment probably has 10x the willingness to pay of the consumer segment and doesn't require competing on consumer scale.
I made this mistake on an older launch, DAU looked healthy but two very different users were hiding in the same number. The people building and sharing were worth talking to, the casual tinkerers were not. I'd interview the 10 users who published the most and test the first paywall exactly there. For packaging I still bounce between a plain doc, ChatGPT, and PostPilot for rough hooks, ngl.
200 daus means people are showing up, so i would look at where the first impression is leaking. when i kept hitting that gap with app launches, i ended up building appkit to iterate screenshot sets faster. happy to share what i learned if useful.
2
2
200 daily actives is a good sign, but i would still ask where the activation gap is. usage without revenue usually means the value is not sharp enough yet.
The line that "users and customers aren't always the same thing" is really the whole game here. I'd reframe the question though: it's less pricing-vs-product-value, and more which return behavior actually maps to willingness to pay. On my tiny iOS memo app early DAU looked healthy too — but the people coming back daily had wired it into a routine, and nearly every paying user came from that group, not the novelty crowd. For an AI game maker, "plays a game once" and "comes back to keep building one game" are completely different signals, and only one of them is monetizable. Can you split your 200 DAU by which of those they're doing before touching price?
This is a great reframing. Thanks for pointing this out.
Every indie hacker hits the wall. The ones who make it work are the ones who adjust, not quit. What's your next move?
I still believe users will pay for real product quality.
So my next move is to keep improving SoonLab — especially the game creation experience, output quality, sharing flow, and creator-side value.
I don’t want to force monetization too early before the product is truly worth paying for. But I also agree that we need to adjust, test, and learn faster instead of just hoping users will convert later.
200 DAU without a single conversion usually means one of two things: the people coming back are the wrong segment (curious rather than willing to pay), or there's a missing step between "I use this" and "I'll pay for this."
The question I'd be asking now isn't "why isn't anyone paying?" It's: have I actually asked anyone to pay? Not a paywall, just a conversation. "What would it take for you to pay for this?"
I had a similar gap with Genie 007. Some users came back every week, paid conversion was almost zero. Turned out I'd made it too easy to stay on the free tier and the people who'd pay were waiting for me to ask. Added a clear upgrade moment and asked directly — paid conversion went from under 2% to 14% in about 3 weeks.
What does your current monetisation flow actually look like? Is there a specific moment where a free user is prompted to upgrade?
To be honest, our current monetization flow is still very weak. We don’t have a clear upgrade moment yet, and we haven’t directly asked enough active users what would make them pay.
Right now, users can create and play quite easily, so we may have made the free experience too open without creating a natural paid step.
Your example is very useful. I think our next step should be talking to active users directly and testing a clear upgrade moment around serious use cases like publishing, exporting, sharing, or creating more advanced games.
Thanks for sharing the conversion example too. That makes the problem feel much more actionable.