I built a SaaS that got 0 paying customers at launch. Distribution was the real problem all along.
I spent 4 months building a SaaS product. Coded every feature myself. Polished the landing page for weeks. Set up the onboarding flow. Made sure everything was perfect.
Launch day came. Zero paying customers. Not one single signup.
I sat there staring at my analytics dashboard — zero conversions, zero traffic, zero everything. I'd built something that, in theory, solved a real problem. But nobody knew it existed. And that's when the realization hit me: the problem was never the product. It was distribution.
Here's what I did wrong:
I was building in a complete vacuum. I spent 90% of my time building features nobody asked for and 10% of my time thinking about how to actually reach people. I optimized button colors, rewrote error messages, refactored code that nobody would ever see. I was busy, but I wasn't being effective.
I never once talked to a potential customer before building. I never validated demand. I just assumed "if I build it well enough, they'll find me." Classic indie hacker trap.
Here's what I changed:
I stopped building and started listening. I flipped my ratio: 90% distribution, 10% building. I started looking for businesses that were already searching for solutions in my space — companies actively expressing intent rather than me guessing who might need the product.
The shift was immediate. Instead of cold-pitching random founders and getting ignored, I found people who were literally looking for what I'd built. My first 10 customers came from this approach, not from feature #47 on my roadmap.
The hard truth:
Distribution is the real moat, not your product. You can have a mediocre product with great distribution and survive. You can have a world-class product with zero distribution and die. I learned this the hard way after 4 months of wasted building.
This experience is actually what led me to build clienthunter.ai — a tool that finds businesses actively looking for solutions in your niche so you don't have to guess who to pitch. It solves the exact problem I kept hitting: how do you find people who actually want what you're selling, without spending every waking hour on manual outreach?
I'm not saying building doesn't matter — it does. But if you're spending 90% of your time in your code editor and 10% finding customers, flip that ratio. You'll thank yourself later.
What about you?
Have you ever built something that flopped because of distribution? What did you change to turn it around? I'd love to hear your stories — we're all figuring this out together.
The 90/10 flip is right, but I’d separate “distribution” into two jobs: finding intent signals and earning trust after the first click.
The first 10 customers usually don’t come from a bigger launch. They come from places where the pain is already visible: forum questions, competitor complaints, review sites, search queries, job posts, or people describing a broken workflow in public.
I’m curious: when you found those first 10 customers, what signal made you confident they were actively looking rather than just generally matching your ICP?
Seeking US-Based Cofounder | Digital Lottery Display SaaS (Production-Ready)
I've built a SaaS platform that helps US lottery retailers—gas stations, convenience stores, smoke shops—boost lottery sales while cutting down on theft and mismanagement.
The problem: Lottery retailers manage tickets manually, leading to inventory shrinkage, theft, and missed sales opportunities. There's no modern, connected system for real-time display control or sales tracking.
What we built: A full-stack platform with a back-office dashboard (sales management, inventory tracking, theft prevention, advertisement management) connected to customizable animated displays retailers can control remotely. Push a button, update ticket numbers and pricing across locations instantly. Includes seasonal themes (holidays, events) to keep displays fresh and engaging.
Tech stack: Next.js, Python, PostgreSQL, AI-powered features throughout.
Status: Live and production-ready. Built solo, fully functional, waiting on the right go-to-market partner.
What I need: A US-based cofounder who understands retail/lottery distribution, has industry connections, or has sold into gas stations/convenience stores before. You'd lead sales, partnerships, and market entry while I continue owning product and engineering from Pakistan.
What I bring: Full technical ownership, a working product, and the ability to ship fast and iterate based on what the market tells us.
Open to equity split or revenue-share discussions depending on fit. If you know the US lottery/convenience retail space and want to build something real, let's talk.
This lines up with my experience so much. The piece people gloss over is HOW you find the ones already looking, because it's not magic, it's just paying attention to intent. For us that meant searching threads and subreddits for people literally asking "anyone know a tool that does X," reading the 1 star reviews on competitors (that's a warm buyer telling you exactly what they hate), and setting alerts on the phrases our buyers use when they're annoyed. Showing up the same day someone vents about the problem converts way better than any cold sequence, because you're answering something they already feel instead of trying to create the need. Distribution ended up being a daily habit of hanging out where the problem gets said out loud, not a launch day thing.
Exactly I had the same problem. Building is kind of easy but the distribution is still freaking hard!!
The reality is that we need to go find the first customer and convince them, one after the other. It takes time and it is hard but this is how it is.
It is sad but building the product and all the cool features coming to life was the easy part, especially with AI today we feel we can build anything.
But to find and convince customers, we still need to fight!
My latest project aims to help you in this fight, it helps you to find customers and look for people who could be interested and buy your product.
If you want to try, here it is birdreply.com
Let me know if you have any feedback about birdreply.com , I would be really happy to improve it!
Thanks!
yeah it is
This is the trap a lot of technical founders fall into. Building feels productive because you can measure progress, but customer conversations usually move things faster.
My distribution problem was structural rather than self-inflicted, but the lesson landed in the same place. I lease domain names (technically: subdomains with full NS delegation), and it turns out no classic marketplace can list that — they all verify ownership via WHOIS and close the deal with a transfer, and a subdomain has neither. Flippa even bans subdomain sales explicitly. My entire "default" sales channel didn't exist before I wrote a single line of code, I just didn't know it yet.
Being locked out was oddly clarifying though. If listings are impossible, the only path is treating it like a product: launch channels for awareness, public answers for trust, and SEO for the intent moment — in my case a static page per catalog item, because people only search for a name in the week they're starting something. Launched last week: the awareness channels produced kind words and zero sales so far, which matches your experience and half this thread. The intent channel is slow but it's the only one where the visitor arrives already wanting the thing.
One question on your flip: did the first 10 customers from intent-search convert at a visibly higher rate than your cold outreach, or did they mostly just take less effort per conversation?
The product angle here is interesting. What's been the biggest challenge in getting this to work in production? I've seen similar approaches struggle with edge cases.The distribution challenge is real. Most first-time founders focus too much on product and overlook the marketing runway needed before launch. What channels worked best for you after realizing this?
The 90/10 flip is the right instinct, but I'd push one layer deeper: not all "distribution" effort is equal, and the founders who recover fastest from a zero-signup launch tend to pick two or three repeatable signal sources — competitor complaints on G2/Capterra, a specific subreddit or Slack community, job postings that mention the exact pain — rather than treating distribution as one generic activity. Otherwise it's easy to burn 90% of your time on outreach that isn't reaching anyone with real intent, which is the same mistake wearing a different label. What actually moved things for me on a support-tooling product was treating each channel as a hypothesis to kill quickly: track reply rate and time-to-first-call by source for two weeks, then cut anything under a threshold instead of spreading effort evenly across all of them. Since you're now building clienthunter around this exact problem, how do you validate that the intent signals it surfaces are actually correlated with someone being ready to buy, versus someone who just mentioned a related keyword once?
This is a lesson many technical founders learn late.
We’re seeing a similar thing with our WordPress Webequipe PDF Search plugin. Building the plugin was only one part. The harder part is finding the right people who already feel the problem — websites with manuals, reports, policies, forms, or documentation where normal WordPress search cannot find PDF content.
What helped us is shifting from “let’s add more features” to “where are people already struggling with PDF discovery?” That changes the whole marketing approach. Distribution is not just promotion; it is understanding where the pain already exists.
I'm building an AI platform for retail traders, and I almost made the same mistake—spending weeks improving features instead of validating whether people actually trusted the workflow.
One thing I've started realizing is that distribution isn't just about getting traffic. It's about collecting evidence. Every conversation, comment, or piece of feedback tells you whether your assumptions are actually true.
I'm now treating community discussions as part of product development rather than something to do after shipping. A single honest conversation has changed my roadmap more than hours of coding.
Curious—once you found your first 10 customers, what feedback surprised you the most?
This resonates completely. I launched a free AI tools
directory 6 weeks ago and had the exact same experience.
Product Hunt spike then silence. Turns out I had 700+
pages but only 11 URLs in my sitemap — Google couldn't
find 98% of my site. Distribution and discoverability
are completely different problems and nobody talks about
the technical SEO side enough for new founders.
The 90/10 flip is real but I'd push back slightly on the framing.
It's not just about spending more time on distribution, it's about
doing distribution before you build. Talking to people first changes
what you build, not just how you sell it.
The "found people already looking" approach is the right instinct
though. Intent signals beat cold outreach every time. Someone
complaining about a problem in a forum is worth 100 cold emails
to people who might have the problem someday.
Four months in a vacuum is painful but it's probably the most
common founder mistake there is. At least you caught it.
This is me right now, i even scraped the wishlist page because i was shy of people waiting to actually try my product. Im now regretting it. Working on SEO right now, hopefully things turn out good. Best wishes for your product too.
good writeup. one thing from my own experience though: "find people already searching" works when the intent is actually visible, like someone posting that they need X or a job ad that gives it away. in a lot of b2b and local niches nobody's searching because they don't know the category exists yet. i spent too long only chasing visible intent and just ended up competing with every other vendor watching the same signals.
what worked better for me was picking one narrow type of customer and waiting for a timing trigger, like they just hired for a role or opened a new location. fewer leads but they actually replied.
agree distribution is the part everyone underrates. figuring it out at 4 months beats 4 years.
The “distribution was the real problem” line hits hard — same thing I kept seeing after launch spikes.
What changed your outcome most: better channel choice, better problem wording, or just more conversations per week?
I’m trying to separate “message fix” vs “channel fix” for early founders and your post is one of the clearest breakdowns.
This hit me harder than I expected to admit publicly.
I spent 10 months building Wealtii (a digital asset index fund platform) completely solo. 315,000 lines of code. Nine Docker containers on AWS. A genuinely beautiful product I was incredibly proud of.
Launch day? Absolute silence. Zero users. Zero deposits. Zero anything.
The exact same wall you hit. And the exact same humbling realization: I had confused building with making progress.
The flip you describe is real. The moment I stopped hiding behind my IDE and started having one-on-one human conversations, everything changed. My first 30 users did not come from any clever growth hack. They came from personal messages where I was radically transparent about what I was building and why.
The thing I would add to your list: when you are building something where trust is the product (like a financial platform), distribution is not just about finding customers. It is about finding the right customers who are willing to take a chance on you early, give you brutal feedback, and help you shape something worth distributing at scale later.
Those first 30 users gave me more product insight than 10 months of solo building did.
Great post. This needs to be required reading for every solo founder before they write their first line of code.
The ratio framing clicks for me. I launched my first product this week and made distribution the product decision, not an afterthought: instead of building the SaaS first, I built the free tool version of it — a checker that answers the exact question my audience googles ("when is my LLC's filing deadline?"). The free tool is the distribution. Every state deadline gets its own SEO page, the checker is the landing page, and the paid product (automatic deadline tracking) only gets built if enough checker users leave an email.
One thing I'd add to your take: for solo founders with no audience, "90% distribution" doesn't have to mean outreach. It can mean building something searchable. People with a $400 late-fee problem are already typing it into Google — I just need to be the answer. Slower than cold pitching, but it compounds and costs $0.
Curious whether you found intent-based outreach kept converting past the first 10, or if the channel got noisier as you scaled it?
Distribution over product is the right lesson, but I'd push back a little. Four months with zero customer conversations before launch isn't a distribution problem, it's a validation problem that showed up disguised as one. If you'd talked to five people in month one, you'd have known by month two whether to keep building. Not disagreeing with where you landed, just think the diagnosis undersells what actually went wrong early on.
Same lesson, different flavor. I build ad creatives for mobile apps, and I almost made your mistake in reverse: spent weeks refining video edits before sending a single sample to anyone. What changed things was checking who already had money moving, apps actively running video ads in the Meta Ad Library, instead of guessing who might want one made. Confirmed spend beats a good pitch every time.
I have a huge distro problem... thats my biggest enemy right now. what are you guys doing to combat that? i am not very active on socials so im guessing thats my biggest hurdle.
This is just the general trap a lot of founders, including me, fall into, but it is always about distribution. I have seen people sell really weird products; they knew where their clients were... It's important to know DISTRIBUTION first; other things follow.
This is me right now. Built for months, and only now realizing distribution is the hard
part — and the part I'm worst at. I think we hide in the code because building is the
comfortable thing and you can explain yourself "why"; distribution is scary because it's not our skill. How did you push past that discomfort at the start?
The distribution realization is the right one, but there's a follow-up trap worth naming: most founders solve it by posting in founder communities. IH, Product Hunt, Twitter/X, r/startups. It feels like distribution because other founders engage and traffic goes up.
But if your customer isn't a founder, you've just moved from building in a vacuum to distributing in a vacuum. The signal is warmer but it's still the wrong audience.
The question that changed my approach: "where does this frustration already exist in writing?" Not "where should I post?" but where are people already describing the exact problem your product solves, in their own words. A Reddit thread where someone is venting about their specific pain right now is a completely different audience than a general growth post on IH.
The motion that actually converts seems to be: be the second or third person to respond to a live complaint in a niche community, with something genuinely useful. Not broadcasting into a general feed.
Hard agree that distribution is usually the actual bottleneck, not the product. I hit a version of this building a niche sports content site — the product (real-time recaps, tactical breakdowns) works fine, but getting in front of the right audience without competing head-on against much bigger established sites in the same space has been the harder problem.
This is exactly where I am right now.
I spent 60 days building Reportify —
an AI client reporting tool for Indian
agencies — and the product works
beautifully. But getting first users
has been the real challenge. I made
the same mistake: too much building,
not enough distribution. The "90%
distribution, 10% building" flip is
something I needed to hear today.
Launching on Product Hunt tomorrow
which feels like my first real
distribution move. Curious — when
you found people "actively expressing
intent" what channels were most
effective for you?
This resonates with me. As someone building AI products, it's tempting to keep improving the model or adding features. But I've started realizing that understanding where users already hang out and how they discover solutions is probably a bigger competitive advantage than another feature.
I am going through same at the moment pretty much, my advise is for you to keep pushing, of course it would have been much easier to have distribution in advance but sometimes you cant influence timing of GTM and maybe have to publish fast.
"The problem was never the product, it was distribution" is the line most of us learn too late. The fix you landed on is the real insight: stop broadcasting, go find the people who are already describing the problem out loud.
The motion that's worked best for me:
Full disclosure: I'm building Prowlify for this exact motion on Reddit — it surfaces threads where people are already asking for a solution, explains why each one matters, and drafts a human reply you approve before anything gets posted (no auto-spam). We launched on Product Hunt today.
If it's useful to you: I'll do a free Reddit intent audit — tell me your product and who your ideal customer is, and I'll send back 8-10 live Reddit threads where people are asking for what you build, each with a draft reply. No strings, whether or not you ever touch the tool.
90/10 building to selling is the default setting of every technical founder ever. Not a mistake it's a comfort zone. Building gives you a dopamine hit every commit. Selling gives you rejection until it suddenly does not pull the ratio flip is not a tactic. It's a personality upgrade.
I'm currently building my own AI startup, and this is exactly the mindset I'm trying to follow. It's tempting to keep adding features, but getting real user feedback early is far more valuable than another week of development.
The part I would underline is intent, not just distribution.
A lot of founders hear "do distribution" and translate it into more posting. But the useful shift in your story is that you stopped trying to create demand from cold traffic and started finding people already showing demand.
The checklist I’m using now is:
That gives better signal than launch traffic alone. I’m building Prowlify around this pattern for Reddit conversations, so this post is painfully relevant.
Completely agree. Product gets all the attention, but distribution is what determines whether anyone ever experiences that product in the first place.
It really resonated with me, thank you so much for sharing this!
I came from the B2C side and made a similar mistake in a different way))) I started vibe-coding a very simple free product: a fill-in brief homeowners can give to their cleaner. It came from my own pain, and I also saw many emotional Reddit posts from people tired of explaining the same things again and again.
Because it was so easy to build, I barely thought about distribution. I built it fast, launched it, added analytics, and then stared at 0 visitors.
I really felt that part of your story!
Then I realized the demand was latent. The pain is real, but it does not show up clearly in search. It is spread across a long tail of different queries, and many people do not know a product like this exists.
So I ended up with the same lesson: distribution has to start before the product. AI has made building much easier. Finding demand and reaching people is still the hard part.
This really resonates with me. It's easy to think the hard part is building the product, but getting people to discover it is a completely different challenge. I'm currently spending much more time on SEO, community engagement, and learning distribution than I expected. Thanks for sharing your experience.
This hits close to home I just launched something myself and I'm realizing distribution is the actual hard part, not the building. What ended up working for you, if anything?
The “launch day is not distribution” lesson is painfully real. I’m in a launch window right now and the biggest shift for me has been treating distribution as a research loop, not a promo checklist.
The useful signal is not “did anyone like the announcement?” but:
That last part is what separates polite attention from buying intent. I’m trying to spend less time polishing the thing and more time finding places where the pain already shows up in public.
This hits close to home. I built an iPhone app that generates music entirely on-device (no servers, no subscription) and had almost the exact same blind spot — I spent basically all my energy on the engineering side and quietly assumed decent App Store search terms would do the rest. They don't, even when they're dialed in.
What's actually worked lately isn't more building, it's just talking to real people directly — small creators who'd genuinely use it, not a blast to an audience. Slower than I'd like, but it's the first thing that's produced actual conversations instead of silence.
Curious whether the "actively searching for solutions" approach kept working for you long-term, or whether you had to keep finding new channels once that first wave dried up?
The 0-customers-at-launch thing is almost always distribution, agreed. But there's a quieter version of the same lesson on the build side: a lot of us pour the effort into the product working and skip the boring "is this safe to actually take money through" pass, then scramble when the first real user shows up. Distribution gets you the user; that pass makes sure the user doesn't become an incident. Both are the unglamorous work that doesn't feel like "building."
I think distribution and validation get mixed together a lot. You can have great distribution and still fail if you're attracting the wrong audience. Talking to potential customers before building solved both problems for me—it helped shape the product and gave me the first people to tell when it launched.
Living this right now with TRIPTI-ai, group travel planner. The painful part is that distribution failure and product failure can look identical if you only look at revenue.
I’m trying to separate the questions now: are strangers finding it, do they understand it, do they try the core loop, and does anyone pay after seeing value? If the answer dies at step 1, more features are probably avoidance, not progress.
I’m treating Reddit, Quora, and niche forums as both distribution and research: log the exact pain, workaround, language, and whether they ask for a tool.
Curious how you qualified “actively looking” before pitching. What made someone worth contacting?
This is a good reminder that launch day is not distribution. It’s just one moment. The real work is showing up repeatedly where the right people already talk about the problem, preferably before you have something to sell
The part that took me too long to accept is that distribution is not a phase after building, it is a constraint you design around from day one. Same trap here, I built first and thought about reaching people last.
What changed things for me was picking a pond instead of an ocean. One narrow group that already gathers somewhere and already complains about the exact problem, ideally a boring niche most people ignore. Then I showed up in that place for weeks before I had anything to sell, just being useful. By the time I launched, the first users were people who already knew me from answering their questions.
Two questions that would have saved me months. Where do these buyers already gather, and can I be useful there before I ask for anything. If you cannot name the specific place, the product is not the risk yet. The silence is.
The distribution-first point is real, but I’d add one layer: not every reply is a buying signal. In a WhatsApp outreach test I’m running, “send it” looked promising at first, but it cost the prospect nothing. The stronger signals were process answers, price questions, demo requests, and trust objections. So now I’m separating distribution from validation: distribution gets the conversation, but the quality of the reply tells you whether there is buying intent. How are you qualifying intent once clienthunter surfaces a potential buyer?
The 90/10 flip is the lesson that took me embarrassingly long to internalize too. I'm the founder of Automateed (an AI book creator and publishing marketplace), and my version of your "zero signups" moment was realizing authors weren't going to stumble onto us. They were already asking their exact questions in specific rooms: writing subreddits, Quora, author Facebook groups. The demand wasn't missing, it was just somewhere I wasn't showing up.
What changed things wasn't a growth hack, it was treating those rooms as places to genuinely help rather than pitch. Answer the KDP pricing question, explain why AI books lose coherence over a long manuscript, and only mention the product where it's actually relevant and with full disclosure. Intent-based, like you said, but the "outreach" is being useful in public instead of cold DMs. It compounds slowly and it doesn't feel gross, which matters when you have to do it every single day.
One thing I'd add to your framing: distribution isn't a phase you finish, it's a habit. The founders I see stall are the ones who treat it as a launch-week sprint instead of a daily 30 minutes forever. Good, honest post. That vacuum trap gets almost everybody once.
This hits home, I did basically the same thing on my last project. months heads down building, and maybe a week actually thinking about who'd see it. the thing that finally worked for me wasn't a big relaunch, it was boring: finding 10-15 people a day who'd literally described this problem somewhere and just replying with something useful, no pitch. A few of them found the product on their own.
Distribution is often the symptom. The root cause we see more often: the product was validated with users who would use it, not users who would pay for it. Those are two different discovery processes.
Definitely checking this app out ill leave feed back after review
This story is somewhat similar to mine. I guess many first-time founders have the same story.
One thing I learned the hard way: validate before building. I ran a MiroFish simulation before writing code, and it gives me different side of my thought process.
This hits hard because a lot of builders confuse “real problem” with “problem I can describe clearly.”
The better signal is usually outside your own head: repeated complaints, manual workarounds, people asking for recommendations, bad reviews of existing tools, or someone already spending money to solve it badly.
That’s the gap I’m working on now: finding those signals before building, then turning them into short opportunity briefs.
I think marketing is harder than building. I learned a lot from this post, and I’m sure I’ll use clienthunter.ai because I find it hard to find clients. And thank you for Start Free period.
Living this on a vertical B2B niche right now. The 90/10 flip sounds right — but warming channels before you have anything to sell is its own job. Reddit/LinkedIn/trade forums want weeks of useful answers before a link is even tolerable.
What helped me reframe: distribution isn't "marketing after launch" — it's joining conversations where buyers already ask questions (even if your product isn't ready). An intent log from those threads beat feature #47 on our roadmap.
Curious which channel finally moved the needle once you stopped building?
This. The Brief Network shipped 8 newsletters in 30 days with zero paid distribution — just Reddit comments and organic IH engagement. The product (Beehiiv + static sites) is boring infrastructure, but the distribution (content-first, niche focus) is where the signal lives. 33 organic subscribers prove distribution unlocks everything else. What distribution channel surprised you most in your learning?
I felt this in my bones. I'm living it right now.
Same story: full-stack dev from Chengdu, China. Got laid off, spent months building an AI bookkeeping SaaS for
freelancers. Polished every edge case. Universal CSV parsing that handles 200+ bank formats. Receipt OCR across 50+
languages. Invoice generation from plain English. All the things I thought freelancers desperately needed.
Launched. Radio silence.
I realized I'd built a solution to MY problem (I hated bookkeeping as a freelancer), but I
never asked if enough other freelancers hated it enough to switch tools.
What I'm doing differently now:
I stopped adding features and started answering questions. Reddit r/freelance, HN comments, Indie Hackers —
anywhere freelancers are talking about bookkeeping pain, I show up and actually help. No link dropping. Just answers.
Some of those people DM me afterward asking what I use. That's when I mention it.
I'm documenting the build in public now. Not "look at my product" posts. More like "here's what I learned about
parsing European decimal commas with LLMs" — stuff that's genuinely interesting to other devs. Those posts get shared.
Product links in the bio, not the post.
I'm targeting the messiest edge cases as my wedge. Chinese bank CSVs. WeChat Pay screenshots. Multi-currency
invoices where the client pays in EUR but I track in USD. The stuff QuickBooks and Xero fail at. Instead of trying to
be "bookkeeping for everyone," I'm becoming "bookkeeping for freelancers working across borders and platforms." That
narrow positioning actually makes distribution easier — I know exactly which communities to show up in.
Your point about flipping the ratio is spot on. I'm aiming for 50/50 now — still building because the product needs to
be good, but treating distribution as part of the job, not an afterthought.
One question for you: when you say you "found people literally looking for what you'd built" — where were you finding
them? Reddit? X search? LinkedIn? I'm curious what channels actually worked for finding intent, not just awareness.
(And yeah, clienthunter looks like it solves a real pain. The meta-layer of "I built a tool to solve the
distribution problem I had" is a great story in itself.)
I've been aware of this problem for a long time, but I've never found a good way to deal with it. Anyone got ideas? Not the usual generic advice — I mean actual steps I can put into practice.
“90% distribution, 10% building” – that’s absolutely correct. This is what developers need to keep in mind.
This resonated a lot. I made the same mistake with my first project — spent months perfecting the code before talking to a single user. The shift from "build-first" to "distribution-first" is the hardest lesson for technical founders.
One thing that helped me was doing "sales calls before the product exists" — reaching out to potential users and asking if they'd pay for a solution before writing a line of code. It's uncomfortable but it validates demand immediately.
Would love to hear what eventually worked for you in terms of distribution!
This matches what I’m seeing with AI-built apps too: building is getting cheaper, but launch trust is not. For anything with API or model cost, distribution only works if early users can understand what they can do, who pays for each action, and what happens on retries or failures.
I’ve been calling that a launch ledger while working on SettleMesh: auth before paid work, usage records separate from analytics, clear checkout, and a user-visible history. It is less glamorous than features, but it makes distribution safer because the product can survive real users.
I think the interesting part is that distribution and the product experience aren't separate problems they amplify each other. Getting the right people to your website is only half the battle. If your landing page doesn't immediately communicate the value, even qualified traffic leaves.
I've seen founders spend months chasing more visitors when the real opportunity was helping the visitors they already had understand the product faster.
I feel this a lot. I have been building and building for the past year and a half, and never really stopped to think if it was enough or i should keep going. Until one of my users reached out, and started dumping feedback like have never seen before.
I think it really toggled a switch, because all of the sudden i had one of my most active users tell me.. "stop building, you have a great product".
You can get so caught up in bettering something, that you start going off track and lose the original vision.
Obviously my app is not huge, but just from switching focus for the past few months i can already see the results, and the traction that is building, when you start to focus more on distribution rather than building.
This really resonates with me. I'm in exactly this position. I've spent years building a product with a focus on quality and long term value. It's easy to believe that if you build something truly useful, people will eventually find it. The reality is that even the best product can remain invisible if nobody knows it exists.
I'm learning that building and distribution are two completely different skills. Thank you for sharing this perspective. It was a timely reminder that helping people starts with reaching them.
This is a lesson I’m learning the hard way too.
Building feels productive because you can control it. Distribution is harder because it forces you to find out whether anyone actually cares enough to change what they’re doing.
I’m building an early SaaS product, and I’ve realized “the product works” is not the same as “the right people know it exists, trust it, and feel enough pain to try it.”
The part about flipping the ratio really stands out. Spending more time talking to people who already show intent probably gives better signal than polishing another feature nobody asked for.
Launch is not the finish line. It’s where the real learning starts.
This hits hard. Most SaaS don’t fail because of the product, they fail because distribution gets treated as an afterthought.
When you shifted to distribution-first, what channel actually started working best for you?
The 'I never validated demand' post-mortem is the standard one, and it's often true, but it's also the one that lets you off the hook a little — it turns 'the distribution didn't exist' into 'I skipped a step everyone told me to do.' I built the opposite way: straight from my own paywall pain, so I was literally the customer, which is the strongest form of demand validation available. My launch a week ago still hit ~2 upvotes on PH and got flagged on HN. What that told me is that 'the need exists' and 'a working distribution channel exists for reaching people who share that need' are actually separate hypotheses, and the second one is much harder to check without actually running the launch. Curious how you're framing the fix now — are you going back to build a channel first (audience, content, community) before the next launch, or trying to hand-carry the current product into distribution channels other people have already built (partnerships, listings, adjacent creators)?
This matches what a lot of builders realize too late, spending way more time on the product than on who actually needs it. The intent log idea from the comments is smart, it turns customer language into something reusable instead of just a gut feeling. Do you think that first channel keeps working as you scale, or will you need a second one once you run out of people to cold-message directly?
The 90/10 split you describe matches what I've seen with early-stage products: technical founders treat distribution as a post-launch afterthought instead of a parallel workstream from day one. One thing that's worked for me is treating public complaints in forums and niche communities as a proxy for real search intent, since it's far cheaper to find someone already frustrated with a gap than to convince someone who's never considered the problem. I'd push back gently on one point though: distribution-first only works if you're filtering for people who actually have the problem and budget, otherwise you just get faster vanity signups that churn immediately instead of slower ones. How are you qualifying buying intent versus casual interest when clienthunter surfaces a company, and have your first 10 customers stuck around past their first renewal?
This reminds me of something I notice as a video editor.
Founders often think they're selling features, but viewers are actually asking, "How does this make my life easier?"
The best SaaS videos I've studied don't start with dashboards or UI they start with the pain, then reveal the product as the solution.
Distribution gets attention. Storytelling earns trust.
Total reality check. I’ve fallen for the "build it and they will come" myth hard. Spent weeks obsessing over tiny frontend details while ignoring the most important piece: getting in front of people who actually need the tool.
Distribution truly is the moat, not your polished code or landing page. Shifting focus to seek out users already hunting for your niche solution is such smart advice. Thanks for laying out your hard lesson so clearly!
Living this exact thing right now, so — solidarity. The trap I fell into: thinking "build it and post it on my own channels" was distribution. It's not. Posting to an account with no audience is shouting in an empty room. What actually moves it is going where your buyers already gather and being genuinely useful there for weeks before you ever mention your thing. Distribution isn't a launch-week task, it's the job. Curious what's starting to work for you?
very real problem. definetley have to work on that
I ran a Microsoft reseller for almost 20 years and the pattern never changed: the companies that won were rarely the ones with the best tech, they were the ones with the best pipeline. One thing I'd add to your 90/10 flip: talk to the customers who did not buy, the objections tell you more about positioning than the wins do. What channel actually surfaced those first 10 high-intent buyers?
I'm learning the same lesson with my own saas .
Building feels productive , but talking to users is what actually moves the product forward.
Really relatable. I went through the same thing with my Chrome extension — spent months building, then realized distribution is a completely separate skill. What ended up working for me was finding niche communities where people were already asking for the problem my product solves, instead of trying to reach a broad audience.
Distribution being the real problem after launch — that's the pattern I keep seeing too.
What actually moved the needle for me (still early): stop broadcasting, start showing up in threads where someone already describes the pain — Reddit especially. Two subs, search problem language not product name, reply helpfully before linking anything.
Curious what you built and which channel felt closest vs totally dead — sometimes it's the channel, sometimes it's the wrong conversation type.
This hits on something crucial - intent-based distribution beats cold outreach every time. When people are already searching for a solution, you're just showing up at the right moment. The key insight is that distribution channels that start with intent are repeatable and scale once you crack them. Most indie hackers skip this part because it feels less exciting than building the feature, but you can't get to product-market fit without solving it first.
good
What really stands out here is how easily “0 customers” gets mistaken for a product issue, when more often it’s actually an attention problem.
Even a solid product can stay completely invisible if it isn’t sitting in the right places. Distribution isn’t just something you do at launch—it’s an ongoing effort to show up where people are already looking for solutions.
The shift that seems important is moving away from “how do I get people to find my product?” and toward “where are people already trying to solve this problem?”
That one change reframes everything. Instead of pushing something out into the world, you’re plugging into conversations and demand that already exist.
"This hit hard. I'm in the exact same position right now — built GhostLeaks, a breach monitoring tool (Flask + HaveIBeenPwned API), launched on Product Hunt, got 4 upvotes and zero paying customers. I spent months perfecting features nobody asked for. Just started shifting to distribution — Telegram groups, Instagram DMs to cybersecurity creators, cold outreach. First potential customer came from Telegram today but wanted the code before paying. The distribution struggle is real. Thanks for writing this — needed the reminder that the product isn't the problem."
Living this right now. 6 weeks in, 37 features, £4/month infrastructure, 0 paying customers. Your 90/10 ratio hit hard — I've been doing the opposite. 5,700 LinkedIn impressions, animated demos, landing page polish, Product Hunt, Indie Hackers posts. All broadcasting. Zero listening. Someone on my last IH post said it perfectly: 'Your list is six broadcast channels and one conversation.' This week I'm flipping it. 10 calls with IT consultancy owners. Not pitching — just asking 'how do you do SOWs today?' No demo. No link. Just listening. Distribution matters, but the step before distribution is understanding whether the problem you're solving is the problem they're feeling.
Worth splitting the first-10 story from the "distribution is the moat" line, they're different claims. What got you the first 10 was demand capture: people already searching, already spending time or money on the problem. That's the fastest channel because the intent is pre-built, but its ceiling is however many people are already looking. A distribution moat is a repeatable channel that also reaches people who don't know they have the problem yet. Intent capture gets you unstuck at zero, it doesn't stay the moat by itself.
Same with the 90/10 flip. That ratio is just wherever your binding constraint sits this month. At zero customers it's distribution. Once you have ten and their feedback, some of it swings back to build.
Living this right now. I launched a WhatsApp AI bot template expecting the launch itself to do the distribution — it didn't. My first actual paying client (for a voice agent) came from a referral, not from any channel I built. The lesson that stuck: distribution isn't a launch-day event, it's a daily habit. Curious about the intent detection — how do you spot businesses "actively looking" without drowning in false positives?
This resonates. It's surprisingly easy to spend weeks polishing features that nobody has asked for. I'm starting to realize that getting even 10 conversations with potential users before adding the next feature can save months of unnecessary work.
This is an incredibly painful but vital lesson. "Four months coding, zero days validating" is almost the default state of indie hacking.
The most valuable shift here is what you said: "I stopped building and started listening." For builders, the hardest part of distribution is that it doesn't give you the clean, predictable compile-success feedback loop that code does. It feels non-linear.
To make it manageable, try treating your distribution like code modules. Instead of "doing marketing," set up tiny, repeatable loops. For example, a "problem-signal loop" where you check relevant keywords weekly, drop value, and collect feedback. It turns a vague, overwhelming task into a systematic checklist. Thanks for being so transparent about this; more founders need to read this before they start their next project.
People often fall into this trap of building what they think people want without spending the time to talk to people first.
I would be a little careful with the label "distribution problem" here.
The useful change was not just that you did more distribution. It was that the distribution finally gave you better evidence.
Once you started finding companies already looking for something like this, the signal got cleaner. What were those first 10 customers already doing before they found you?
Were they replacing a spreadsheet, a VA, a broken manual search process, another tool, or just a vague frustration?
That difference matters because "people who need better outreach" is broad. "People already spending time or money to find buyer intent" is a much more usable market.
What made distribution bearable for me was making every outreach message a specific observation about that company's product. Even the people who never reply teach you something, so the time never feels wasted. It stops being a tax once it starts feeding your roadmap.
The 90/10 flip is right, and I'll add the split that took me longest to see: rented distribution vs owned distribution. Going where intent already lives (search, forums, communities) is rented. It works, but you pay the toll every single time, and the day you stop showing up the traffic stops.
Building Automateed (an AI book creator with a publishing marketplace), the thing that finally compounded was owned distribution baked into the product. The marketplace means every author who publishes has a reason to bring their own readers, so each listing quietly makes the next author's decision a little easier. That took far longer to pay off than posting in communities, but it keeps working while I sleep, which rented distribution never does.
So if I were doing it again I'd still run your intent-first playbook on day one to survive, but I'd design one owned loop from the start instead of bolting it on at month six. The founders I watch stall are usually the ones who got great at manual outreach and never built anything that distributes itself.
Curious where clienthunter's signals come from, mostly job posts and forum intent, or somewhere less obvious?
The intent frame is right, and the comments already covered validation, so I'll add the wrinkle I'm living instead: intent-based distribution assumes the searcher can get the value alone. I build a peer-review product, and the person searching the pain query wants an answer in 90 seconds; my product needs them to sign up AND pull a colleague in. Showing up where they already search (which I do, pain-query content since mid June) solves discovery, but for anything network-shaped the conversion gap moves one step later, from "find them" to "will they spend social capital." Worth flagging because "flip to 90% distribution" reads differently depending on whether your product delivers value to one person or needs two. For the second kind, intent gets you the reader; the invite is a separate, harder problem, and no distribution ratio fixes it. That's the part I'm testing now, with a decision date pre-written so I judge it on evidence instead of launch-day mood.
The insight about intent is what actually changes the game. You're not cold-pitching anymore - you're showing up where people are already searching for a solution. That's so much higher conversion than trying to convince someone a problem exists.
The 90/10 flip only works if it's specifically intent-focused distribution though. Otherwise it becomes just doing more of the same visibility stuff. But targeting the exact places where your customer already knows they have the problem? That compounds.
"The intent insight is sharp. Worth pushing one layer: the founders actively searching for solutions vary wildly by stage (pre-seed chasing free tools, Series A hunting integrations). ClientHunter shows you who's searching. SoftRankings shows you which stage is searching.
Combining both: stage-segmented intent data. Pre-seed looking for easy setup? Series A wanting integrations? That's the signal that actually moves pricing & positioning, not just 'people want this.'
You've already cracked intent. Stage-segmented intent unlocks positioning."
yeah i can definitely about distrubution being really tough my site ornymo is struggling
I am living the same lesson right now with a dev tool. Retention is fine and the landing converts, but none of that matters at single digit daily visits. The mental shift that helped me was realizing a launch is a spike, not distribution. What actually compounds is the boring part: showing up every week in the places my users already are and being useful there without pitching. Slower than a launch day, but it does not reset to zero the next morning.
One thing I’d add here: keep a tiny “intent log” from those first 10 customers.
Not just where you found them, but the exact phrase they used, what they were replacing, and what made them reply. That becomes your content/outreach map.
If the same wording shows up in Reddit threads, search results, and sales calls, you have a channel and positioning, not just a lucky source.
The "intent log" idea is gold — I did almost exactly this manually for months. Scraped Reddit threads, read app store reviews, tracked the exact phrases people used when describing their pain. What surprised me was how often the same 3-4 phrases showed up across completely different channels: a 1-star review on Google Play, a rant on r/SaaS, and a "what do you use for X" thread on r/Entrepreneur would all use nearly identical wording.
That pattern is what tells you the positioning is real, not just one person's opinion. And the "what they were replacing" part is especially underrated — when someone says "I switched from X because..." in an app review, that's your competitive angle written for you.
I ended up turning this whole process into RightIdea.app because the manual version was eating 10+ hours a week. It cross-references Reddit discussions, App Store/Google Play reviews, and search volume to surface these patterns automatically. Still early, but the core insight is exactly what you described: the words people already use to describe the problem ARE your positioning and your channel map.
I think one of the biggest mindset shifts is realizing that distribution isn't what happens after the product is finished.
It determines what product gets built in the first place. The founders who treat customer discovery as part of product development usually end up wasting far fewer months building things nobody was already looking for.
Four months building, zero days validating demand with a real customer before launch is a pattern so common it almost has its own genre on IndieHackers. The product working correctly and the product being wanted are two completely different questions and only one of them shows up while you're building.
The 90/10 flip going forward is the right instinct. Finding businesses already actively searching for a solution changes everything because you're not convincing anyone the problem exists, you're just showing up where they already are.
the part worth underlining from your own story: it wasn't "distribution" in the abstract that fixed it, it was intent. you stopped interrupting people who weren't looking and started showing up where they were already searching for the thing. that's a completely different game from "do more marketing", which is usually just louder interruption.
small pushback on the moat line though: distribution got you the first 10, but if the product doesn't retain them you've just built a faster way to fill a leaky bucket. they gate each other rather than rank, distribution earns the shot and the product decides if it counts. the genuinely useful bit is that intent is repeatable, not luck: the threads and "alternative to X" searches where people describe your problem are a channel you can work for the next 100 the same way you found the first 10.
This comment was deleted a month ago.