A founder I was talking to recently said something I’ve heard, in different words, maybe twenty times in the last year: “I finished the product. I posted it on X. Nothing happened. I’m freaked out.”
He’d spent months building. The product was, by his own honest assessment, genuinely good. He’d assumed — and this is the part I want to focus on — that distribution would be the easier half of the job. Or at least the more obvious one. Build the thing, hit deploy, put it in front of people, watch them show up.
Then he hit deploy. And nobody showed up.
I’ve been on both sides of this. I’ve built things and watched the post-launch silence stretch out for weeks. I’ve run early-stage enterprise sales for my own startups. And now I spend a lot of my time working with founders who are stuck at exactly this point — the moment after ship, before traction.
That sentence sounds simple. In practice, it changes almost everything about what a founder does in the first 90 days after launch. Let me explain what I mean by it, why I think it’s the right frame, and what it looks like to actually run it.
The Mistake I Made (And Most Founders Make)
The first time I shipped something, I treated the launch as a marketing problem from the jump.
I wrote a launch post. I wrote a follow-up post. I started thinking about positioning, about content cadence, about which channels we’d be on, about whether we needed an early newsletter. I built a Notion doc called “Distribution Strategy” and filled it with channels and experiments.
What I didn’t do — and this is embarrassing to admit — was pick up the phone and call ten people.
The reason I didn’t is the reason most technical founders don’t. Building has a clean feedback loop. You write code, the tests pass or fail, you move forward. Posting on X has a feedback loop too, even if it’s noisier. But cold-calling someone, getting on a Zoom, and watching them try your product? That’s open-ended. It feels unscalable. It feels like the kind of work you graduate out of, not the kind of work you start with.
So I avoided it. I told myself I was being strategic. I was actually just being scared.
And the cost of that avoidance was real. By the time I finally did get on calls — months later — I’d built features nobody wanted, written copy that didn’t land, and burned a chunk of runway on the assumption that marketing was the lever. The lever was sales. Specifically, the kind of one-at-a-time, hand-held, watch-them-use-it sales that doesn’t scale. The kind of work I’d been avoiding precisely because it didn’t scale.
I’ve since done this the right way, and the difference is not subtle.
Why Distribution Is a Sales Motion at the Start
There are three reasons the sales-first frame matters, and they compound.
First: at zero users, you don’t have a marketing problem. You have a learning problem. Marketing assumes you know what your product is, who it’s for, and why they care. At zero users, you don’t actually know any of those things — you have hypotheses. Sales calls are how you turn hypotheses into knowledge. Every conversation either confirms your understanding or breaks it. Marketing channels can’t do that for you. A post that gets no engagement doesn’t tell you whether it’s the channel, the copy, the offer, the audience, or the product. A call where someone says “honestly, the problem you’re describing isn’t even in my top five” tells you everything.
Second: your first 10 customers are bought, not sold to themselves. When a product is unknown, has no social proof, no reviews, no case studies, and no peer recommendations — which is true of every product on launch day — nobody walks in off the street and buys it. They are pulled in, one at a time, by a founder who got them on a call, listened to their problem, showed them the thing, set it up for them, and walked them through their first use. That’s not a marketing funnel. That’s a sales motion. Trying to skip it is like trying to skip the part of weightlifting where the weights are heavy.
Third: the things you learn from 5 hand-held conversations are the inputs to every marketing asset you’ll ever build. Your landing page copy comes from how those 5 users described the problem. Your onboarding sequence comes from where those 5 users got stuck. Your positioning comes from the moment one of them said “oh, this is like X but for Y” and you realized that’s actually what you’d built. Marketing without those inputs is guesswork. Marketing with those inputs writes itself.
The order matters. Sales first. Marketing as a compounding effect of what sales taught you.
What “5 People Watching the Workflow” Actually Means
The number 5 is not magical. The principle is: small enough that you can be hands-on with each one, large enough that you start seeing patterns. Some founders will work with 3. Some will need 10. The shape of the work is what matters.
You identify 20 people who, based on what you’ve built, should obviously have the problem. Not 200. Not your TAM. Twenty specific humans, by name, in roles you’ve thought about.
You reach out to all 20. Cold message, warm intro, LinkedIn, email, doesn’t matter. You’re not asking them to buy. You’re asking for 30 minutes of their time to learn about their workflow.
Of the 20, maybe 5 to 7 respond. Of those, maybe 3 to 5 take the call. That’s your concierge cohort.
On the call, you do not pitch. You ask about their current workflow. Specifically, you ask about the part of their work that your product touches. Not “what tools do you use” — that’s a feature conversation. You want phrases like “the worst part of my week is…” and “the thing I keep meaning to fix is…” and “I’d genuinely pay to make this go away.”
If they describe the pain in their own words, unprompted, you’re onto something. If they don’t — if they’re polite but vague, if they describe the problem only after you’ve described your product to them, if they say “yeah, that’s interesting” — you’re not in pain territory yet. Polite interest is cheap. The real signal is when someone tells you their current workflow is broken before you’ve said a word about your product.
If the pain is real, then you pivot. The pivot line I use is something like: “Based on what you just described, I think the thing I’ve been working on might actually solve this for you. Would you want to see if it does?”
That’s not a pitch. It’s an offer to test a hypothesis together. The framing matters because it keeps the feedback loop honest. You’re not trying to convince them. You’re trying to find out if you’re right.
You walk them through it. You set it up for them. If it works, you don’t drop them into self-serve and wave goodbye — you stay on the call, you watch them use it for the next week, you message them when they get stuck, you fix things in real time. You are their concierge.
This is the part most founders skip because it feels unscalable. That feeling is correct. It is unscalable. That’s the point. You are not trying to scale yet. You are trying to learn.
What You’re Actually Learning
A founder asked me once: “What am I supposed to be writing down during these calls?” Here’s what I look for, in roughly this order of importance.
Their exact language. Not the polished version they’d put in a LinkedIn post. The slightly-frustrated, off-the-cuff phrasing they use when they’re describing the problem to a friend. That language is what goes on your landing page. Your words will never carry the weight that theirs do.
How they currently solve it. Every problem worth solving already has a workaround. Spreadsheets, a junior employee, a hacky Zapier flow, just doing it manually at 11pm on Sundays. The workaround tells you two things: what the bar is for your product (you have to be meaningfully better than the spreadsheet), and what the switching cost is (you’re not competing with nothing — you’re competing with the muscle memory of doing it the old way).
How they would actually buy. This is the question I think most founders forget to ask, and it’s the one that changes the most about your GTM. Who signs off? Whose budget? What’s the procurement process? Is there a security review? Is there a tool they need to integrate with first? Is this a credit-card purchase or a six-month sales cycle? You can’t design a sales motion without knowing the shape of how the purchase happens.
Where they got stuck. If you’re watching them use the product, write down every place they hesitated, asked a question, or did something unexpected. Each one is a feature decision, a copy decision, or an onboarding decision waiting to happen.
What they did after the call. Did they come back to it? Did they invite a teammate? Did they ask when they could pay? Did they ghost? The follow-up behavior is more honest than anything they said in the call.
Five conversations of that depth give you more than any number of analytics dashboards will at this stage. Ten conversations and patterns start to emerge. Twenty and you basically know what you’re building, who it’s for, and how to talk about it. That is the input to marketing. Without it, you’re guessing.
When You Graduate from Concierge
The concierge phase ends when you can answer three questions without hedging.
The first: can you describe your customer in one specific sentence — not “marketing teams” or “B2B SaaS founders” but “performance marketers at e-commerce brands spending $50k+/month on Meta ads who are reviewing creative weekly”?
The second: do you have a repeatable conversation? Meaning, when you get on a discovery call with a new prospect in that segment, you can predict with 70%+ accuracy what their workflow looks like, what their pain is, and what they’re going to say when they see the demo. If you can’t predict it, you haven’t done enough calls.
The third: have at least three of your concierge users used the product without you holding their hand, and come back, and told someone else?
When those three are true, you can start building marketing assets — landing page, content, channels, the works — that compound. Before they’re true, you can’t. The assets just don’t have the right inputs. I’d guess most founders hit those three answers somewhere between conversation 10 and conversation 25. Not 100. Not 1,000.
The Objection I Hear Most
The most common pushback I get on this frame is some version of: “But I’m building a self-serve product. My whole thesis is that this scales without sales touch. If I do concierge for the first 10 users, I’m not actually testing the thing I built.”
I understand the worry. It’s wrong, but I understand it.
You’re not testing self-serve when you do concierge. You’re testing whether the underlying problem is real and whether your solution solves it. Self-serve is a delivery mechanism. Delivery mechanisms work when the underlying offer works. If the offer doesn’t work, self-serve doesn’t save you — it just lets you fail faster and with less information about why.
The right sequence is: get 5 to 10 people through it with you on the line, find out it actually solves their problem, watch where they get stuck, fix those things, then test whether someone can get through it without you. That’s when you find out if self-serve works. Doing it the other way around — launching self-serve first and waiting for the analytics to tell you why nobody activated — costs months and teaches you very little.
Sales touch at the start is not a contradiction of self-serve. It’s the only honest way to find out if self-serve will work.
The Real Reason Founders Resist This
The reason technical founders default to “build then market” instead of “sell then build then market” isn’t strategic. It’s emotional. Building is comfortable. Marketing-from-a-distance — posts, ads, content — is also comfortable, because there’s no specific human on the other end whose reaction you have to absorb in real time. Sales conversations, especially early ones, are uncomfortable. People say no to your face. People say “I don’t get it.” People say “this is fine but it’s not a priority.” Those are hard things to hear when you’ve spent three months building.
The instinct is to avoid that discomfort by burying yourself in work that doesn’t have a human on the other end. More features. Better copy. A new landing page. Another channel experiment. All of it lets you feel productive without ever putting the thing in front of someone who might say no.
The founders I’ve watched break out of the post-ship paralysis are the ones who accept that the discomfort is the work. Not a sign you’re doing it wrong. Not a phase to optimize past. The discomfort of sitting on a call with a stranger who hasn’t agreed to like your product yet, watching them poke at it, hearing what they actually think — that is the early-stage GTM work. It’s not the prelude to it.
That’s the whole job for the first 90 days. Everything else compounds from there.
Filed under: GTM