I shipped v2 with zero paying customers. Here's the honest version.
Two weeks after launch, I had 9 signups and ₹0 in revenue. Two of those signups were me and my co-founder. Two more were friends being nice.
That's the real number I was sitting with before I built v2.
I could've kept doing outreach — my reply rate on manual LinkedIn DMs was actually decent, ~37%. But replies weren't converting. People were curious, not paying. And when I looked honestly at why, it wasn't a distribution problem. It was that the product still had rough edges I was hoping people wouldn't notice.
They noticed.
So here's what I actually fixed in v2, and why:
→ Real Story mode. My whole pitch is "content that doesn't sound like AI." Turns out my pipeline was good at structured posts and mediocre at personal/narrative ones — exactly the format that builds trust on LinkedIn. Built a separate mode for it instead of forcing one prompt to do both jobs badly.
→ AI gatekeeper. I was manually catching bad/generic output before showing early users. That doesn't scale and it's not a real product. Built an actual check layer so the system catches it, not me.
→ Credit system starting at ₹39. My old pricing had no cheap way to just try it. I was asking people to trust a stranger's tool at full price. ₹39 removes that excuse.
→ Payment bugs, fixed. This one's embarrassing to admit — some paying-intent users were hitting checkout failures. I don't know how many I lost to this before I found it.
I'm not going to pretend v2 fixes the real problem, which is that I still don't have proof people will pay.
What it fixes is: nobody can say no because the product got in their way instead of the product not being good enough yet.
Going 100% LinkedIn organic from here — no more outreach sprints, no more distraction chasing. Built a 60-day content calendar and I'm just going to post and watch what happens to the ₹39 tier.
I'm also doing this alongside a nursing degree, so if updates go quiet for a bit, that's why — not because I gave up.
I have also shipped three v2 build products with 0 paying customers right now, but I am not losing hope. I know they will come. Kudos that you are still shipping while being busy studying to be a nurse.
The payment-bug part is worth isolating from the broader "will people pay?" question, because a broken checkout can look exactly like weak demand.
I would split the path into a few observable events: pricing CTA clicked, checkout session created, checkout page rendered, payment completed webhook verified, and access/credits granted. If created is healthy but completed is flat, the issue is likely payment UX or authorization. If completed exists but credits are not granted, it is webhook/access-control. If CTA-to-created is flat, it is positioning or friction before payment.
That way your 60-day organic test is measuring demand, not silently testing whether the payment plumbing survived v2. The ₹39 tier is a good move; I would make one "stranger checkout" test part of every release before each content push.
The honest version is the useful version, so thank you for this. I'm at a similar stage with my own product (launched, real early access, no users yet), and the line that hit me was "rough edges I was hoping people wouldn't notice. They noticed." That's the trap: hoping instead of verifying.
The payment bug lesson generalizes further than it looks: every funnel step you haven't personally walked as a stranger is a step that might be silently broken.
Question on the AI gatekeeper: how do you test that the check layer itself stays consistent? Model-based checks can quietly change behavior over time (model updates, prompt drift), so I'm curious whether you have a fixed set of known-bad examples you re-run against it, or whether you're judging it live.
Good luck with the 60-day calendar, and respect for doing this alongside a nursing degree.
the reason that one hides for months is that a broken checkout is silent by construction. a failed payment leaves an object you can go and look at, but a button nobody reaches leaves no error and no row anywhere, so it looks exactly like disinterest.
worth wiring up a counter now rather than a bug hunt later: watch
checkout.session.createdagainstcheckout.session.completed. near-zero created means nobody is reaching stripe at all. healthy created with flat completed means they arrive and the payment step itself fails. funnel numbers on their own will never separate those two.Man I feel this.
The part about people being curious but not paying really hit. That's the part I'm scared of too.
But fixing the product before trying harder outreach is something I needed to hear. I keep thinking I should push marketing but maybe I should just make the product better first.
Respect for shipping v2. That takes guts.
Also nursing degree alongside this? Insane. You're built different.
Watching this journey.
The honesty in that title alone takes guts — most people would've buried the zero paying customers part. Shipping when things aren't working yet is underrated as a growth strategy.
The payment bug confession is the most telling part - you had real intent signals (37% reply rate) but the friction wasn't messaging, it was actually in the product and checkout. That's hard to debug when you're doing manual outreach.
The ₹39 tier is smart positioning too. Most people won't pay for a stranger's tool at full price when they don't know if it works for them. Lowering the barrier to "try this" instead of "commit to this" changes the conversation entirely.
Really interested to see how the 60-day LinkedIn organic experiment plays out. You have the message (the LinkedIn use case is clear), the product is cleaner, checkout works now - everything aligns. That's the setup where content-driven growth actually works.
The payment bug confession hit hard — so easy to assume conversion problems are messaging when the checkout is literally broken. Respect for being honest about the real numbers. Good luck with the 60-day calendar.
37% reply rate with almost no conversion is interesting, especially now that you've removed several of the product and checkout issues.
I'd be curious what you hear from the people who were engaged enough to reply but still decided not to try or pay.
Good question — honestly still figuring that out. My guess is it's not one thing: some were curious but not in "switch tools now" mode, some hit friction I didn't know about (turns out our payment button was actually broken until today, so that's a real chunk of it right there — just shipped the fix in v2).
Rather than guess further, I'm going to reach back out to everyone who replied but didn't convert and just ask directly. Will report back what I find — figured being honest about the messy middle is more useful here than a polished answer I don't actually have yet.
Interesting update after our earlier conversation around trust and authenticity.
The product fixes seem important, but I’m curious what you discover from the people who engaged but didn’t convert.
The interesting signal will be whether the remaining gap is product friction, or something deeper about how users perceive the value.