Founder-Led Sales: Your First 100 Conversations

If you build things, you already know the trap. The product is nearly done, the landing page looks decent, and the plan for getting users is some version of "post it and see." Then it goes live, a few people click, nobody pays, and you have no idea why. You cannot tell whether the idea is wrong, the pricing is wrong, the copy is wrong, or you just have not shown it to enough of the right people. You are flying blind, and blind is an expensive place to build from.

There is an older, slower, deeply unglamorous fix that works better than almost anything you can automate at this stage: go talk to people. Not a thousand people through an ad. Not a mailing list you do not have yet. The first hundred, one real conversation at a time, with the founder (that is you) on one end. This guide is about what those conversations actually are, why they are the best money and the best research you can get early, and how they turn into paying users without you ever giving a "pitch."

Where does the money actually come from?#

The money does not come from the conversation directly. Nobody pays you for chatting. The conversation is the front of a very short pipeline, and the revenue falls out the far end.

You find someone who plausibly has the problem
  ↓
You start a genuine one-to-one conversation (mostly listening)
  ↓
You understand their problem better than they can explain it
  ↓
It becomes clear whether your product actually solves it
  ↓
If it fits, you offer to help (not a pitch, an offer)
  ↓
Some say yes and pay
  ↓
They use it, tell you what is broken, and sometimes refer the next person
  ↓
Revenue, plus the exact information you need to get the next yes faster

Notice that every arrow is doing double duty. The middle steps are research: you are learning the shape of the problem, the words people use, the alternatives they have tried, what they would pay to make it go away. The bottom steps are sales: an offer, a yes, a payment. Because the pipeline is short and human, you get both signals from every single person you talk to, even the ones who say no. A no that comes with a reason ("I would pay for this, but only if it also did X") is worth more than a silent signup. If you want the wider framing of why revenue always traces back to solving a real problem for a real person, where online money actually comes from covers the general mechanism this sits inside.

How it actually works#

A founder-led sales conversation is not a demo and it is not a pitch. Roughly, you should be listening for two thirds of it. The structure that works, loosely, looks like this.

You open by being a real person with a real reason to talk to them. Not "Hi, I built an app, want to try it?" but something tied to them specifically: a comment they posted, a problem they mentioned, a tool they complained about. The point of the opener is only to earn the next two minutes.

Then you ask about the problem, not the product. "How are you handling X right now?" "What is the annoying part?" "What have you tried?" "What happens if you just do nothing about it?" You are trying to understand their world well enough that you could describe their problem back to them better than they described it to you. When you can do that, something shifts. They stop feeling sold to and start feeling understood, which is rare enough that it does most of the persuading for you. This is the same instinct behind selling when you hate selling: if the whole thing is about them and their problem, it stops feeling like the pushy thing you were dreading.

Only after you actually understand the problem do you connect it to what you built, and only if it genuinely fits. "The thing you just described, the part where you have to re-do it every Monday? That is the exact thing I built this to remove. Want me to set it up for you and you tell me if it helps?" That is the offer. It is specific, it is tied to a problem they just told you about in their own words, and it lowers the risk by putting you on the hook to make it work.

The reason this converts so well early is that you are not persuading a stranger to trust a brand. You are one human offering to solve a problem for another human who just admitted they have it. That is the most natural sale there is. It happens to also be the most honest, which is the whole point of doing business this way.

A simple example with numbers#

These numbers are made up to show the shape of the thing, not a promise. Do not treat them as typical. Your real numbers will be different, and finding out what they are is exactly why you do this.

Say your goal is your first ten paying users, and your rough plan is a hundred conversations. Hypothetically:

• You reach out to or reply to 250 people to start conversations.
• Of those, 100 turn into an actual back-and-forth. (Most outreach goes nowhere. That is normal and not a sign you are bad at this.)
• Of those 100, maybe 40 clearly have the problem you solve.
• Of those 40, you make a real offer to 25, because the other 15 either are not ready, are not a fit, or you ran out of time.
• Of those 25 offers, 10 say yes and pay.

Now put a hypothetical price on it. If your product is 30 dollars a month and 10 people say yes, that is 300 dollars a month in recurring revenue. That is not life-changing money. But look at what else you now hold: 100 conversations worth of notes about who has this problem, how they describe it, what they tried before, what almost stopped them from paying, and which single feature came up over and over. That second thing is worth far more than the 300 dollars, because it is what lets you turn the next hundred conversations into thirty yeses instead of ten. The revenue keeps you honest. The learning is the real payoff. For the closely related walkthrough of getting from zero to that first handful of customers, see how to get your first 10 customers.

What you need#

You need less than you think. Most of what people buy to "get ready" for this is procrastination with a receipt.

Required:

• A product, or a good enough version of one, that solves one clear problem. It does not have to be finished. It has to be real enough that you can help someone with it, even if you are manually holding parts of it together behind the scenes.
• A way to talk to people: a personal account on wherever your users hang out, a working email, a calendar link if calls make sense.
• A place to write down what you hear. A plain document or a spreadsheet is fine. One row per conversation.
• Enough time to actually have the conversations and follow up. This is the real cost.

Optional, and genuinely helpful:

• A simple way to take payment (a payment link is plenty at this stage).
• A short list of the questions you want to ask, so you do not blank in the moment.
• A private way to onboard the first users by hand, so their first experience is you personally making sure it works.

Nice to have, and easy to overbuild:

• A CRM. You do not need one for a hundred rows. A spreadsheet is a CRM.
• A polished onboarding flow. Do it by hand until the hand hurts, then automate the part that hurt.

What it costs#

In dollars, close to nothing. A domain, maybe a payment processor's per-transaction fee, maybe a cheap tool or two you already have. You can run this whole phase for the cost of your existing stack.

The real cost is time and ego. Time, because a hundred genuine conversations is a lot of hours, and there is no shortcut that keeps the quality. Ego, because you will hear that your favorite feature is the one nobody cares about, that your pricing is off, and that the thing you thought was your product is actually a nice-to-have next to the thing you built in an afternoon. That is not failure. That is the information you came for. It only feels bad because you were hoping to skip it.

How long it takes#

Longer than a launch, shorter than guessing. If you talk to a few people a day, a hundred conversations is a matter of weeks, not months. What controls the speed is mostly two things: how easy your users are to find, and how good you get at starting conversations that do not feel like spam.

Finding them is a research problem before it is a sales problem. If you do not yet know exactly where your people gather and what they complain about, spend a little time up front on that. Mining subreddits for the topics people actually want and using Reddit and similar communities for market research are both fast ways to find both the watering holes and the exact language people use, which makes your openers land. The better your research, the fewer conversations you waste on people who were never going to be a fit.

What beginners usually get wrong#

The most common mistake is talking too much. You built the thing, you are excited, and you want to explain every feature. Every minute you spend explaining is a minute you are not learning, and it flips the conversation from "I understand your problem" to "please buy my product." Aim to listen more than you speak, especially early.

The second mistake is pitching before understanding. If you lead with the product, you will get polite nods and no honesty. Lead with their problem, and people tell you the truth, including the truth that stops the sale, which is the truth you most need.

The third is treating a no as a dead end instead of data. Ask why. "Totally fair, can I ask what would have made this a yes?" You will hear the same three objections over and over, and now you know what to fix or what to say next time.

The fourth is being spammy in the outreach itself and burning the community you were counting on. Blasting identical DMs to a hundred strangers does not count as founder-led sales. It is just spam with your name on it, and it poisons the well. What a cold DM that is not spam actually looks like and cold outreach that actually works both cover how to reach out in a way that earns a reply instead of a block.

The fifth is trying to automate too soon. The instinct to systematize is a good instinct pointed at the wrong moment. There is nothing to systematize yet, because you do not know what works. Automate after the manual version is working, not instead of it.

How I would start#

If I were starting from scratch on a new product, here is the order I would go in.

First, I would get crisp on who has the problem and where they are. One sentence: "This is for people who X and are frustrated by Y." If I could not write that sentence, I would go do research until I could, because everything downstream depends on it.

Second, I would find ten of those people this week, in the communities where they already are, and I would start real conversations without mentioning my product at all. Just questions about the problem. The goal for week one is to understand, not to sell.

Third, once I had heard the same problem described three or four times in the same words, I would start making offers, tied directly to what each person told me, and I would onboard the first yeses by hand. I would treat those first users like the most important people in the world, because they are.

Fourth, I would keep a running document of every conversation and re-read it weekly, looking for the pattern: the objection that keeps coming up, the feature everyone actually cares about, the phrase that makes people lean in. That pattern is the blueprint for everything you eventually automate. If you want a structured version of this exact sequence with a conversation tracker to fill in, I put together a short free companion, the First 10 Customers Playbook, and you can grab it here.

What I would not do#

I would not build more product before talking to anyone. The temptation is enormous and it is almost always wrong. More features do not fix a market you do not understand.

I would not hide behind a form. A survey or a waitlist feels productive and safe, and it gives you shallow, sanitized answers. A conversation gives you the messy truth. Choose the truth.

I would not outsource these conversations. This is the one job the founder cannot delegate, because the whole value is that the person who can change the product is the person hearing the feedback. Hand this to a salesperson too early and you get the sales without the learning, which is the worst of both.

And I would not measure this phase by revenue alone. Three hundred dollars a month is not the win. The win is that you now know, from a hundred real people, exactly what to build, who to sell it to, and what to say. That knowledge is what makes the scalable version of this business possible at all. This is the same idea that runs underneath how making money online actually works: the money follows understanding, not the other way around.

The close#

Founder-led sales feels like the opposite of building a scalable online business, and in a narrow sense it is. You are doing the least scalable thing possible: one human, one conversation, one problem at a time. But that is precisely why it works this early. You are not trying to grow yet. You are trying to learn what is true, and get paid a little while you do it, so that the thing you eventually scale is built on something real instead of a guess.

Your first hundred conversations are not a chore you have to get through before the real work starts. They are the real work. Everything you automate later is just a way to have those same conversations, at scale, without you in the room. You cannot skip straight to that. You have to earn it, a hundred conversations at a time.