I keep seeing founders treat distribution as a separate problem that begins after the product is built.
The questions usually sound like this: Which channel should I try? Should I do outbound? Post more? Invest in SEO?
Sometimes the answer really is a better channel. But sometimes the distribution problem began when the product was defined.
The founder knows the solution extremely well, but cannot describe what was happening in the customer's workflow immediately before the customer started looking for help.
That missing context makes every part of marketing vague. You do not know where the person will be, what language they use, when the problem becomes urgent or which outcome matters enough to make them act.
Before looking for more customers, I would reconstruct how the existing ones happened:
This is not only copy research. The answers can change the product.
You may discover that customers value one narrow outcome while the roadmap is focused somewhere else. You may find that urgency exists only in a specific situation, or that the people you are targeting are not the people who experience the problem most often.
No amount of channel optimization fixes a product designed around the wrong situation.
That does not mean every acquisition problem is a product problem. The distinction is whether your current customers describe a repeated trigger, a meaningful outcome and a reason they chose to act.
If you cannot find that pattern, more traffic may only create more confusion.
When you look at your last customer, what happened immediately before they decided to try your product?
This maps onto something I keep circling as a pre-revenue B2B seller: I can describe the failure modes my product addresses in detail, but I can't yet describe the specific moment someone goes from "aware of the problem" to "actively looking for a fix." Those are very different things, and I think I've been treating the first as if it were the second.
Trying to apply your five questions retroactively doesn't work when there's no customer yet — but running them forward as a filter for who to talk to has been useful: instead of "who has this problem," I'm now asking "who's currently mid-crisis with this problem, this week, not in the abstract." The people who fit that description are a much smaller, much more specific group than my original target persona, and they're findable in a way "anyone with this job title" never was.
Curious whether you found the five questions worked better once you had at least one real customer to reverse-engineer, or whether you'd trust them run prospectively too, before any sale exists to study.
This is a good distinction. More traffic can actually make the problem harder to diagnose if you haven't figured out what triggers the customer to act in the first place.
I’d also look at what happens after the click. If the ad gets the right person to the site but the landing page doesn’t match the situation that made them search, you can end up blaming the channel for what is really a message or product-positioning problem.
The “why did they act now?” question is probably one of the most useful ones to ask.
The question I keep coming back to from your list is "why did they act then instead of one month earlier?" That timing question is the one I always skip, and it's the only one that tells you when someone is actually reachable. What's helped me is writing down the trigger in the customer's own words before I write a single line of copy, because my paraphrase is always tidier and more product-shaped than what they said. The other thing I'd add: reconstructing that story usually shows you work you can delete, not just work to add — half my early roadmap was for a situation nobody was actually in. Answering your closing question honestly, the last person who tried something of mine came from a plain "here's the thing I made" note, not a channel I optimized.
The harder version of this question is what to do when you don't have a "last customer" yet to look at. I've been distributing a product for a week and a half with genuine daily effort - real replies, real community participation, not spray-and-pray - and still have zero strangers through the funnel. Your framework asks me to reconstruct the pre-search state of my existing customers, and I don't have any to reconstruct from.
The distinction I've landed on, for anyone in that earlier spot: silence is not the same signal as rejection. Rejection means people arrive, read, and leave - that tells you something specific about the product or the message. Silence means they never arrived in numbers large enough to leave any trace at all, which mostly tells you about reach, not fit. I checked mine directly rather than guessing - referrer logs, not vibes - and it's almost entirely direct traffic and my own testing, nothing organic yet. That's a distribution problem I can act on, not a product verdict I should be reacting to. Worth checking before concluding the product is wrong: do you actually know which of the two you're looking at?
This frames the measurement problem clearly. Most founders measure what customers do with the product, but miss measuring what the customer's workflow looked like before they even started searching. The "what was happening immediately before they decided to try" question is the gap between founders' blindspot and the customer's trigger.
If you don't have visibility into that pre-search state - what tool they were using, what frustrated them, how often the problem recurred - you can't measure the urgency dimension at all. Then distribution becomes a guessing game because you don't know which situation the person will be in when they encounter your ad or post.
This explains why founders see "more traffic = more confusion" - they're driving people to a product designed for a situation they don't actually encounter yet.
This hits close to home. I’ve been learning that more outreach doesn’t fix an offer people don’t clearly value.
One of our first real users liked the product and execution, but pricing was the hesitation. That feedback pushed me to rethink the offer, make services more flexible, and build a startup program instead of just trying to send more traffic into the same funnel.
Sometimes the useful signal isn’t “which channel should I try next?” It’s “what is stopping the people already interested from buying?”
The distinction between an acquisition problem and a product-definition problem is useful. The last-customer question is probably where that distinction becomes visible.