3 products live, 0 paying customers — here's what I've learned about distribution in 30 days

The dev.to conversation and the two Valix API calls are worth more than 200 passive views for one specific reason: those people had already decided they had the problem before they found you. Cold traffic is just curiosity. Someone who already built a similar tool, or a developer who hit your trial endpoint twice, is a potential customer actively looking for a solution.

The thing that tends to break the silence for most founders I have seen is narrowing the conversation to the smallest possible slice of your target user and going to where they already are. Not posting broadly, but finding the one forum, Slack group, or subreddit where people complain about the exact problem. For Autoreport, that might be a Stripe community or a Slack for bootstrap founders who run revenue. For Valix, developer communities in Spain where people integrate fiscal data.

The asymmetry is brutal but real: 10 targeted conversations beat 1000 broadcast impressions at this stage. Sounds like you already feel that intuitively.

Building 3 products in 30 days while documenting the distribution lessons is actually solid output. The "building was easy, distribution is hard" thing is real and most people don't feel the weight of it until they're exactly where you are right now. One thing that helped me: pick one product and go all in on one distribution channel for 30 days before touching anything else. The temptation to ship the next thing is partly how the distribution problem stays invisible. When I forced myself to focus on just one product and one community for 6 weeks straight, the learning compounded in a way that spreading across 3 never could. Are any of the 3 getting organic traffic or trial signups at all, even without paid customers?

This hits hard. Building multiple products and still seeing zero customers is honestly more common than people admit. Respect for sharing it openly

Resonates a lot. I'm also a non-developer (animator by trade) who shipped a niche tool — a bitmap font generator for game devs. Same experience: building took weeks, distribution is taking months.

What's shifted the needle most for me: going where the specific frustration already exists, rather than general founder spaces. For Valix, that might be Spanish dev communities or forums where devs complain about fiscal ID validation being a pain. The people who feel that exact pain will respond differently than a general IH audience.

The Autoreport idea is interesting because Stripe founders are a finite, findable group. Have you tried posting in Stripe's official community or subreddits where Stripe users hang out? The people who'd pay for a weekly PDF digest are probably the ones who've already opened Stripe's dashboard 20 times this week wishing the data was surfaced differently.

Distribution being "uncertain" vs. code feeling like "progress" — I think that's the trap. With code, you get a green checkmark. With distribution, the feedback loop is weeks long and mostly silence. Keep going.

This resonates a lot — especially the part about “building being the easy part.”

I’ve been going through something similar. I built a tool around freelancer outreach, and technically it works well. But the real challenge has been exactly what you said — finding people who actually feel the pain enough to change their current behavior.

One thing I’ve started noticing:
People don’t respond to “better tools,” they respond to “different outcomes.”

So instead of trying to pitch features, I’ve been experimenting with showing a completely different way of doing the same thing (more visual, more contextual). Still early, but it feels like a more promising direction than just improving the existing workflow.

Curious - in your case, have you found any moment where a user immediately got it without much explanation? That’s what I’m still chasing.

The thing you said about that one dev.to conversation teaching more than 200 views is the crux of it. What broke the silence for me wasn't a marketing tactic — it was responding in a specific thread where someone was describing exactly the problem I'd built for, and saying something useful enough that they DM'd me. That single interaction turned into the first real user.

The instinct to "go deep in one or two communities" is exactly right. The pattern I've noticed is: the breakout doesn't come from your own posts (those get 10-20 views and polite upvotes), it comes from being genuinely helpful in someone else's thread where the pain is already live. You become the person people associate with that problem space.

One thing worth tracking — those two Valix API calls are more valuable signal than anything else you described. A developer who made two calls either hit a validation edge case and moved on, or they're evaluating for real. Either way, that's worth investigating. Can you see what IDs they validated? The structure of the input tells you a lot about the use case (e.g., NIFs for payroll vs. CIFs for invoice validation are very different buyer personas).

Really appreciate the honesty here — the "posting on IH feels uncertain but it's where the feedback is real" line nails something most solo devs don't admit out loud. I'm a similar profile (backend-leaning, built a lightweight memo tool as an indie project) and I had to retrain myself that distribution isn't a phase after building — it's the actual job, every day.

One thing that helped me: instead of cross-posting the same launch message to 5 communities, I picked two places (IH + one niche subreddit) and just read and replied to other people's posts for a week before mentioning my own. The reply-to-post ratio I aim for is roughly 10:1. It's slow, but the DMs and qualified signups that come from it are on a completely different quality level than cold traffic.

For your three products, which one has the clearest "who hangs out where" answer? Valix sounds like it has a sharply defined audience — Spanish dev forums, backend communities. Have you tried seeding it there by helping with unrelated questions first?

The two Valix API calls are worth paying close attention to. Most founders dismiss signals that small, but someone in Spain specifically found your trial endpoint, evaluated it, and used it twice — that's a developer who has the problem right now. If you can find and talk to that person, you'll learn more about pricing and positioning in one conversation than in months of broader distribution experiments.

The "go deep in 1-2 communities instead of broadcasting everywhere" shift is the right instinct. There's a pattern where solo founders spread across 5-6 platforms and end up with shallow presence everywhere instead of credibility anywhere. The communities that work best for developer tools tend to be the ones where people are already asking questions about the specific problem you solve — Stack Overflow threads, Reddit posts asking "how do I validate Spanish NIFs in production," niche Slack groups. Being the person who consistently answers those questions builds more qualified pipeline than any amount of cold posting.

One thing worth considering with Autoreport: Stripe founders already get emails from Stripe's own dashboard. Your positioning needs to make clear what your weekly PDF shows that Stripe's built-in analytics don't — otherwise you're fighting an incumbent that's free and already installed.

Your point about one dev.to conversation teaching more than 200 views is the most underrated insight in this whole post. I've been in a similar phase building developer tools — shipping fast with AI, then hitting the distribution wall hard. The pattern I keep seeing is that answering someone else's question in a thread where the problem already exists converts dramatically better than any launch post or cold pitch.

For Valix specifically, have you looked at Spanish fintech dev communities or Stack Overflow threads about NIF/CIF validation? API products tend to break through when developers encounter them at the exact moment they're wrestling with the problem. Two real API calls from a real developer is actually a strong signal — it means the demand exists, you just need to be present where those developers are actively looking for solutions.

This is a good reality check. Building got compressed hard by AI, but distribution still seems brutally manual. The biggest signal here was not views, it was intent, people who already had the problem. Feels like the early game is less “launch louder” and more “find the smallest group already complaining about this exact pain point.”

I understand you and you right building it's the easiest part the users or customers or even testers that's it's really the difficult part to deal with.

This is honest, and that is why it lands.

A lot of builders think zero paying customers means zero progress, but what you described is actually the phase where real learning starts. The interesting part is that your strongest signals did not come from broad reach, they came from small moments of genuine use and recognition.

That usually means the problem may be real, but the audience path is still being discovered.

Your point about distribution being a separate skill is also important. Many technical founders underestimate that. Building proves capability. Distribution proves relevance.

The part I would keep leaning into is exactly what you said: finding conversations where the pain already exists instead of trying to manufacture attention. Two real API calls from the right person can be more valuable than thousands of passive impressions.

You are not early because nothing is working. You are early because the feedback is still sharp, specific, and close to the source.

Keep going. This reads like someone who is learning the right lessons, not just the easy ones.

Yeah, this is such a familiar phase — shipping is deceptive because it feels like progress, but distribution is where the real difficulty starts. The shift from ‘building in isolation’ to ‘building in context of a community’ is usually what unlocks everything.

What stood out most is that your signals didn’t come from scale, but from very specific interactions — a dev.to comment, a couple of real API calls. That’s often more valuable than hundreds of passive views.

We’re also exploring something in that direction — instead of broad reach, focusing on intent-driven engagement where the problem already exists.

Also sharing something I’m building in parallel — You have an idea. $19 puts it in a real competition. Winner gets a Tokyo trip (flights + hotel booked, minimum $500 guaranteed). Round just opened, so best odds right now: tokyolore.com

The honest framing here is right: building and distribution are genuinely different skills, and AI only accelerated the building side.

For Autoreport specifically — the product itself has a built-in distribution advantage you might not be fully using yet. Stripe founders are a fairly concentrated audience: they're active in Stripe's own community, #buildinpublic on Twitter/X, and this forum. More importantly, the 'Monday morning PDF in your inbox' is a very concrete value prop that's easy to try once with a personal intro.

The thing that usually unlocks the first paying customers for utility tools like this isn't a launch post — it's finding 5-10 people who literally use Stripe, giving them access, and then asking for honest feedback. Not to convert them, just to learn. The conversions come from that loop.

You mentioned the distribution feedback here has been good quality. What's the most actionable thing you've heard so far?

That’s rough, I’m kind of in the same phase.

Out of curiosity — how are you handling user messages / support right now?

I’m starting to get a few and it already feels messy between emails and random stuff. Still trying to keep it simple without using heavy tools.