DEV Community: DL

3,000 cold emails and zero customers. The list was never the test.

DL — Tue, 11 Aug 2026 08:20:20 +0000

The number shows up in postmortems more than any other. Three thousand cold emails sent. Five thousand. Ten thousand. Zero customers.

The reflex is tactical. Rewrite the subject line. Improve the personalization. Switch tools. A/B test the call to action. Buy a better list.

Those moves can matter. But they assume the problem is how the emails were sent. There is a question the send count was not built to answer.

Cold email volume measures reach. It does not measure whether the person on the other end had a current reason to buy.

This is the split that most outreach postmortems skip. A list of 3,000 founders is a reach number. It says nothing about whether any of those founders were already spending time, money, or workaround effort on the exact problem the product solves.

A founder who is already paying for a tool that does this badly is a precision target. A founder who might benefit from this someday, if they think about it, is a reach target. Cold email at scale is excellent at hitting the second group. It is nearly useless for finding the first.

Picture the inbox of a founder who gets 30 cold pitches a week. Most are for tools that sound useful in theory. She deletes them without reading, not because the copy is bad, but because none of them connect to something she is currently failing at. The one email she would open is the one that names the exact workflow she was cursing about that morning. But a scraped list of 3,000 "founders who might be interested" will never contain that signal.

When cold emails produce zero responses across thousands of sends, the usual read is bad copy or failed deliverability. Sometimes that is true. But a flat-zero response rate across a large list is more often a precision failure. The list contained people with no current reason to engage, and no subject line fixes that.

So the question worth asking is not "how do I get more replies?" It is whether any of those 3,000 people were already failing at the task the product does. Were they searching for a solution? Were they paying for a competitor they disliked? Were they losing hours every week to a manual process the product automates?

If yes, for even a small share, the fix is copy, deliverability, or timing. Those are solvable.

If no — if the list was built from a broad scrape of "founders who might be interested" — the volume was testing reach, not demand. No personalization creates a buying moment for someone who does not have the problem yet.

Cold email is not dead. It is a reach tool being asked to do a precision job. When the list has no precision, the volume amplifies silence instead of signal.

Sometimes the right move is not to send more emails. It is to find the fifty people who are already paying to fail at this, and talk to them directly.

A few related cases I keep notes on:

Why 3,000 cold emails got zero customers: https://review.trustescrow.co/answers/why-3000-cold-emails-got-zero-customers
Why a SaaS gets stuck at $3K MRR after funnel fixes: https://review.trustescrow.co/answers/why-saas-stuck-at-mrr-plateau
Why a free lead magnet got attention but no paid customers: https://review.trustescrow.co/answers/why-free-lead-magnet-got-no-paid-customers
Why a waitlist did not convert into paying customers: https://review.trustescrow.co/answers/why-waitlist-did-not-convert

The volume was high in all of those. The precision was not.

If you sent thousands of cold emails and the silence was total, check whether the list was ever reaching people who had a current reason to buy — before you rewrite another subject line.

Your waitlist is not a demand signal. It is a curiosity receipt.

DL — Mon, 10 Aug 2026 10:57:32 +0000

A founder builds a landing page, adds a waitlist form, shares it in a few places, and watches the signups climb. 50 people. 200 people. 500 people.

The number feels like proof. If that many people signed up, the demand must be real.

Then the product launches. The waitlist gets an email. A small fraction logs in. A smaller fraction activates. Almost nobody pays.

The common read is a launch execution failure. Better email sequence. More personal outreach. A sharper onboarding flow. Those are worth trying. But they skip past a prior question that the waitlist number was never designed to answer.

A waitlist signup costs the person nothing — no money, no time, no workflow change, no social risk. It is one click followed by an email field. The same person can join ten waitlists in an afternoon and intend to use none of them.

That is not a moral failure of the signup. It is a measurement problem. The waitlist was measuring interest, and interest is not the same as demand.

Demand leaves traces that interest does not. A person with demand is already spending time, money, or workaround effort on the problem. They have a deadline, a boss asking for it, a client waiting, a tool they are paying for that does it badly. They are not curious whether a solution exists. They are already failing without one.

A waitlist signup rarely captures any of that. It captures someone who thought the idea sounded interesting enough to enter an email — which is a real signal, but a different and weaker one than most founders treat it as.

This is why waitlist-to-paid conversion rates are often in the low single digits, and why the founders behind them feel betrayed by a number that looked like validation. The number was never testing the question they thought it was.

The harder signal to collect, and the one that actually predicts whether someone will pay, is whether any of the people on the waitlist were already trying to solve this problem before the waitlist existed. Were they searching for it? Were they paying for a bad alternative? Were they spending hours on a manual workaround they hated?

If the answer is yes for a meaningful share of the list, the waitlist may contain real demand. The product needs to find those people and serve them first.

If the answer is no — if the list is mostly people who liked the idea but had no current pain — the waitlist was a curiosity collection, not a demand test. The product may still be good. But the number does not prove it, and optimizing the launch sequence will not fix a list full of interested bystanders.

That is a different verdict than "the launch emails need work." Sometimes the honest call is to stop treating the waitlist count as evidence, go find the people who were already failing at this, and rebuild the demand signal from something that costs the person more than an email address.

A few related cases I keep notes on:

Why a waitlist did not convert into paying customers: https://review.trustescrow.co/answers/why-waitlist-did-not-convert
Why a free lead magnet got attention but no paid customers: https://review.trustescrow.co/answers/why-free-lead-magnet-got-no-paid-customers
Why a SaaS gets stuck at $3K MRR after funnel fixes: https://review.trustescrow.co/answers/why-saas-stuck-at-mrr-plateau
Why a vibe-coded app works but gets no users: https://review.trustescrow.co/answers/why-vibe-coded-product-gets-no-users
The signups came in all of those. The demand did not.

If your waitlist converted at 2% and you are wondering whether the problem is the email sequence or the product, the prior question is whether the list was ever testing demand in the first place.

Hundreds of free users and zero paid. The free signups were never the test.

DL — Sun, 09 Aug 2026 07:46:15 +0000

A recent SaaS postmortem tells a familiar story. A founder launches an AI sales tool, gets hundreds of free signups in the first weeks, and then none of them convert to paid.

The reflex is to fix the conversion path. More onboarding emails. A sharper pricing page. A timed trial. A founder might run all of those, and the number still does not move.

Sometimes the conversion path really is the problem. But there is a prior read that free-to-paid posts usually skip past.

A free signup is not a buying signal. It is a curiosity signal.

Free removes the question that paying forces. When someone signs up for free, they are answering "is this interesting enough to try?" They are not answering "would I pay to solve this?" Those are different questions, and confusing them is what makes 220 free users look like 220 almost-customers.

The harder signal is whether any of those free users did something that costs them something — time, workflow change, data migration, asking a teammate to look at it, replacing a tool they already paid for.

A free signup costs nothing. The same person can sign up for ten tools in a week and use none of them. A workflow change, even a small one, is closer to commitment because it costs the user something they cannot easily get back.

This is why free-to-paid conversion benchmarks are misleading at the individual product level. A 5% conversion rate means one thing if the free users came from a broad social post, and something very different if they came from people already paying for a competing tool they hated. The rate is the same. The signal underneath it is not.

The useful test is not "how do I get more of the 220 to pay?" It is whether any of them reached a moment where the free version stopped being enough — a deadline, a team handoff, a client deliverable, a paid workaround they were already using — and the upgrade became the smaller cost.

If that moment did not appear for any of the 220, the free signups may have proven the topic is interesting. They did not prove the offer has a buying moment.

That is a different verdict than "the funnel needs more steps." Sometimes the honest call is to reposition the paid offer toward a different moment, narrow the free tier so it cannot substitute for the paid one, or stop treating curiosity as near-demand.

None of those are a quick fix. But they are the ones that prevent a founder from spending six months optimizing a conversion path that was never going to convert, because the free users were never testing the same question the paid product answers.

A few related cases I keep notes on:

Why a free lead magnet got attention but no paid customers: https://review.trustescrow.co/answers/why-free-lead-magnet-got-no-paid-customers
Why a SaaS gets stuck at $3K MRR after funnel fixes: https://review.trustescrow.co/answers/why-saas-stuck-at-mrr-plateau
Why a vibe-coded app works but gets no users: https://review.trustescrow.co/answers/why-vibe-coded-product-gets-no-users
Why a Product Hunt launch got attention but no signups: https://review.trustescrow.co/answers/why-product-hunt-launch-got-no-signups
The free signups came in all of those. The paid moment did not.

If your free-to-paid number is stuck near zero after weeks of onboarding tweaks, the next audit may need to look at whether the free action was ever testing the paid question.

Your vibe-coded app works. That is not the same as someone needing it.

DL — Sat, 08 Aug 2026 10:40:05 +0000

The tooling story is now familiar. A founder prompts, iterates, ships. The app runs. The demo works. Maybe the README is clean. In a weekend, or two weeks, something real exists that used to take months.

Then nobody comes.

The common read is distribution failure. Post to Product Hunt. Submit to directories. Write a launch thread. Try TikTok. The build was fast, so the thinking goes, the distribution should catch up.

Sometimes that is true. But there is a prior layer that fast builds make harder to see, not easier.

Build speed is a supply signal. It says the founder can now produce working software quickly. It does not say anything about whether anyone was already failing at the task that software does.

Before vibe coding, the slowness of building forced a kind of accidental demand test. If it took six months to build something, the founder usually talked to people, searched for evidence the problem was real, and hesitated before committing. The friction filtered out weak demand by making commitment expensive.

Vibe coding removes that friction. It makes commitment nearly free. A founder can build a complete, working app in the time it used to take to do the first customer interview.

That is a genuine win for building. It is also why so many vibe-coded apps hit a wall that feels like a surprise. The wall was always there. The slow build was hiding it.

The useful test is not "can this app be built?" The build already answered that. The test is whether anyone, before the app existed, was already spending time, money, or workaround effort on the problem it solves.

A few signals separate the two:

A product built into an existing workflow meets people who were already doing the task badly. They recognize the tool because it removes a step they hate. The first conversation is not "what does this do?" It is "where has this been?"

A product built ahead of any workflow meets people who have to be convinced the task is worth doing at all. The first conversation is education. Adoption is slow even when the product is good, because the buyer has no current reason to change.

Vibe coding makes the second case look like the first. The app works, so it feels like the workflow must exist. But working software and an existing painful workflow are two different things.

The harder question, after the build is done and the silence starts, is not "how do I distribute this faster?" It is whether the direction is still alive — or whether the right call is to narrow the offer, reposition it toward a workflow that already hurts, or stop and rebuild the demand evidence before building further.

None of those are fun. But they are the ones that save months, because the build was never the bottleneck. The demand evidence was.

A few related cases I keep notes on:

Why a vibe-coded app works but gets no users: https://review.trustescrow.co/answers/why-vibe-coded-product-gets-no-users
Why a SaaS gets stuck at $3K MRR after funnel fixes: https://review.trustescrow.co/answers/why-saas-stuck-at-mrr-plateau
Why a Product Hunt launch got attention but no signups: https://review.trustescrow.co/answers/why-product-hunt-launch-got-no-signups
Why a free lead magnet got attention but no paid customers: https://review.trustescrow.co/answers/why-free-lead-magnet-got-no-paid-customers
The product worked in all of those. The attention came. The buyer moment did not.

If your vibe-coded app has been live for weeks and the silence is still the loudest signal, the next move may not be another launch. It may be checking whether the direction was tested before the build started.

Why your SaaS is stuck at $3K MRR (and the funnel fix may not be the right fix)

DL — Sat, 08 Aug 2026 07:18:29 +0000

I keep seeing the same number in SaaS postmortems.

A founder gets to around $3K MRR. Sometimes $1K. Sometimes $10K. Then the line goes flat for months.

The reflex is to audit the funnel. Tighten the trial. Rewrite the pricing page. Add a sales step. Run a retargeting campaign.

Those moves are reasonable. They may even be necessary. But there is a prior question that most plateau posts skip past.

Is this plateau a funnel problem, or a direction problem?

Those are different failures, and they call for different verdicts.

A funnel problem means the right buyers are arriving, understanding, trusting, and then dropping at a specific step. The fix is local. You find the leak and patch it. The direction is still alive.

A direction problem is harder to face. It means the offer is aimed at a buyer who never had a strong current reason to move, or the product proved it works but never proved someone would pay for that specific outcome, or the audience that loved the free version was never the audience that would pay.

When the plateau is a direction problem, funnel optimization does not break the plateau. It stabilizes it. You convert slightly more of the wrong buyers, and the number still does not move.

The uncomfortable part is that a direction problem can look exactly like a funnel problem from the inside. The trial-to-paid rate is low. The churn is a little high. The ads bring clicks but not signups. Every one of those symptoms has a funnel fix. And every funnel fix feels like progress because it produces activity.

The test that separates them is narrower.

Ask whether any buyer has reached the paid moment and then come back with a specific, repeatable reason. Not "they liked it." Not "they found it useful." A reason tied to a workflow, a deadline, a cost they were already paying, or a failure they were already failing at.

If that reason exists and the plateau is still there, the funnel is the likely layer. Fix the steps between arrival and that moment.

If that reason cannot be found, or if it only exists among people who already build similar products, the plateau may be one level up. The honest call is not "optimize the funnel again." It is narrow the offer, reposition the buyer, or in some cases stop.

That is a harder verdict than "run more experiments." But it is the one that saves months.

A few related cases I keep notes on:

Why a SaaS gets stuck at $3K MRR after funnel fixes: https://review.trustescrow.co/answers/why-saas-stuck-at-mrr-plateau
Why a free lead magnet got attention but no paid customers: https://review.trustescrow.co/answers/why-free-lead-magnet-got-no-paid-customers
Why a Product Hunt launch got attention but no signups: https://review.trustescrow.co/answers/why-product-hunt-launch-got-no-signups
Why a vibe-coded app works but gets no users: https://review.trustescrow.co/answers/why-vibe-coded-product-gets-no-users
None of those are funnel postmortems. They are direction postmortems. The product worked. The attention came. The buyer moment did not.

If your plateau has survived two or three funnel fixes and the line is still flat, the next audit may need to be one level up, not one step deeper.

Free Downloads Can Prove Interest. They Do Not Prove Paid Intent.

DL — Tue, 28 Jul 2026 08:26:23 +0000

Free is a useful test.

It is just easy to forget what it is testing.

A recent course postmortem made that distinction pretty clean. The founder had built a polished course on agentic engineering. Before launching it, he created a free blueprint with the stack, starter prompts, and enough material to help someone begin. The blueprint got about 20 downloads right away, and the lead-magnet list was around 40 by launch.

Then the course went live.

Zero purchases.

The obvious read is that the list was too small. That is probably true. But it is not the whole read.

The free blueprint tested whether people were curious enough to take a useful technical asset at no cost. The paid course asked for a different behavior: commit money and time to a premium learning path from that creator, at that moment.

Those are not the same signal.

You see the same shape in other public postmortems.

One creator got 1,320 people into a free course from ads. Only 70 started it. Nobody bought the paid program.

Another AI-operated business had blog traffic, free tools, a free playbook, and a free newsletter. The machine worked. Revenue was still zero.

A developer published 21 paid guides, got views across DEV, and sold none. Readers were willing to consume useful material. They were not showing paid commitment to that offer in that place.

Different cases, same trap:

free action gets counted as buyer evidence.

It may not be.

A download can mean the topic is interesting. A signup can mean the promise is understandable. A free trial can mean the friction is low enough to poke around. A free course enrollment can mean the headline was good enough for a cheap yes.

None of those automatically means someone has reached a buying moment.

That matters because the next fix changes depending on which signal you actually have.

If people download the free asset and then ask buying questions, request a deeper result, compare options, or try to solve the paid problem immediately, that is stronger.

If they download, skim, collect, save for later, or never start, the free asset may have attracted information seekers.

The hard part is not getting more free interest.

The hard part is separating curiosity from commitment before building the next paid layer around it.

This is where "make the paid thing free" can be both reasonable and misleading.

Sometimes turning a stalled course, guide, or template into a free asset is the right move. It can build credibility, search surface, audience, or trust. The work may still be useful.

But that changes the job of the asset.

It no longer proves that the original paid offer was close to working. It may prove that the material is better as a trust-building front door than as the thing people buy first.

The risky sentence is:

"People wanted the free version, so the paid version just needs a better funnel."

Maybe.

But maybe the free version solved the low-commitment part of the problem, and the paid version never reached people with a reason to pay now.

That is a different diagnosis.

I keep a longer answer page on this pattern here:

https://review.trustescrow.co/answers/why-free-lead-magnet-got-no-paid-customers

Source examples:

GammaVibe course postmortem: https://gammavibe.com/updates/i-built-a-premium-course-and-sold-zero-copies/
Questie free-course postmortem: https://medium.com/@questie_analytics/how-i-earned-0-with-1-320-leads-and-what-went-wrong-2622f4ea4b13
Moneylab AI business postmortem: https://money-lab.app/blog/66-days-zero-revenue-ai-business-post-mortem
DEV guide-sales postmortem: https://dev.to/ariauser13/i-built-21-practical-guides-for-indie-devs-60-days-later-540-views-eu0-revenue-heres-the-honest-4k3m

Product Hunt, MCP hubs, and directories can prove availability. They do not prove distribution.

DL — Fri, 24 Jul 2026 10:26:43 +0000

I keep seeing the same launch result show up in slightly different clothes.

A founder launches on Product Hunt. Some people look. Almost nobody signs up.

Another builder submits an MCP server to hubs and package indexes. The listing is live. Installs stay close to zero.

Someone else gets a WordPress plugin approved, or submits to a dozen startup directories, then checks analytics a week later and sees almost no movement.

The tempting read is:

"That channel does not work."

Sometimes that is true. But the sharper signal to separate first is narrower.

Those surfaces may have proven availability, not distribution.

Availability means the thing exists somewhere a person could find it.

Distribution means the right person has a reason to find it, trust it, understand what to do next, and move it into a real workflow.

Those are not the same test.

Product Hunt can prove that early adopters were willing to look at the product page. It does not prove that visitors had a current reason to create an account, move data, invite a teammate, or change how they already work.

An MCP hub can prove that a server is packaged and listed. It does not prove that a user reached a useful tool call, remembered when to invoke it, or came back after the first install.

A plugin directory can prove the plugin was approved. It does not prove that anyone is searching that directory with the exact pain the plugin solves.

The problem is that all of these results look clean in a launch report.

Published.
Listed.
Approved.
Indexed.

Those words feel like progress. They are progress, but they are not buyer movement.

The next question is not "where else can this be listed?"

It is:

Where did the movement stop?

Did people never arrive?
Did they arrive but not understand the promise?
Did they understand it but not trust it?
Did they try it once but fail to reach the first useful result?
Did they reach the result but have no reason to repeat the behavior?

Those are different failures.

More listings can only fix the first one.

This is especially easy to miss with AI tools and agent products because the build can be impressive before the adoption path is real. A demo can work. A README can be clean. A Product Hunt page can look polished. An MCP server can be technically valid. None of that proves the product has entered a buyer's working day.

So if a launch, listing, or directory submission produces silence, I would be careful calling it a distribution failure too quickly.

It may be a pre-distribution result.

The thing is on a shelf.

The harder question is whether there is a route from that shelf into someone's work.

Longer notes I keep on the two narrower versions of this:

Product Hunt attention without signups: https://review.trustescrow.co/answers/why-product-hunt-launch-got-no-signups
MCP listings without adoption: https://review.trustescrow.co/answers/does-mcp-server-listing-prove-distribution