Founder-led sales: listen before you sell

Somebody has said yes to a conversation about your product. This is exactly what you want: you finally have their attention, the working demoA live or recorded showing of how a product works. In an early sales conversation, a focused demonstration covers the smallest part that addresses the problem the buyer has described; it doesn't prove that the buyer or another customer achieved a result. is open in another tab, and it would be very easy to spend the next 30 minutes explaining every feature you stayed up too late building. The conversation begins with what happens in the customer's world now, what changed, and whether the problem matters enough to act.

The exchange may happen on a call, over email, in chat, or during setup. Its commercial purpose should be clear: you're discussing a product they may buy while learning how they describe the problem and make the decision.

Founder-led salesEarly commercial conversations run directly by the founder so that customer language, decisions, concerns, and product reactions can change the product, offer, proof, and sales approach without passing through another person first. are a thing that lots of solo builders find really daunting. You're used to building and solving hard technical problems, and the skills you've honed over years feel completely at odds with those you need to sell. But with some guidance, boundaries, and an understanding of the fact that founder-led sales are as much market research and understanding over the thing that happens in a slightly icky way in used car lots the world over - it's less scary than you might think.

By the end of this chapter, you'll have a one-page brief for that exchange and somewhere to record what happened. And hopefully, you'll feel that founder-less sales are a lot less daunting than you did before you opened this screen.

Your advantage is the feedback

Founder-led sales means you stay directly involved in early commercial conversations. Paul Graham makes the case for recruiting users manually and paying close attention because the feedback changes what gets built; it's essentially super-targeted, productive market research. (Paul Graham, July 2013)

This immediate feedback from your direct customer is the strongest reason to do the selling yourself. A buyer uses words you wouldn't have chosen, or cares about a risk you barely considered; you can take that straight back into the product, offer, proof, or next conversation.

Early sales are commercial conversations and a source of immediate feedback. The customer should know you're selling; your curiosity still needs to be real.

The work should stay close while these conversations are still changing what you sell and how you sell it.

Prepare enough to listen

A good conversation brief fits on one page. It gives you enough context to ask better questions without becoming a script.

It needs the buyer, the reason they're speaking to you, what you know, one objective, three to five questions, the price, your strongest proof, and the product area that may be relevant.

If the only reason on the page is that somebody agreed to a call, the conversation still needs to establish whether there is a current problem behind their politeness.

Start with what happens now

Founders commonly spend too much of a sales conversationAn exchange in which a buyer and founder discuss a product and a possible purchase. It can happen on a call, by email, in chat, during a demonstration, or through guided setup; it doesn't require a formal meeting. talking. The rule is that every single sales conversation should begin from a point of listening hard; the detail is free market research, and you can't explain how the product solves this customer's problem until you've heard it.

Across five psychology studies, Tamir and Mitchell found that people placed value on disclosing information about themselves, which speaks more to the benefits of listening. A 2019 meta-analysis of 24 sales studies found that listening helped salespeople adapt to customer needs, while a survey of 162 organizational buyers linked perceived listening with trust and satisfaction. None supplies a magic talk-to-listen percentage. (Tamir and Mitchell, May 2012; Itani, Goad and Jaramillo, September 2019; Agarwal et al., Summer 2005)

Questions such as these give the buyer room to explain what is happening:

• What changed that made this worth looking at now?
• What do you do to solve this problem at the moment?
• Where does that process become slow, costly, risky, or frustrating?
• What have you already tried?
• How important is this compared with the other work competing for attention?
• Who else is affected or involved in deciding what happens next?

You won't need every question, and firing all six in order is less a conversation than a customs interview. A hypothetical “yes, I'd use that” gives you much less to work with than a description of what they tried last week.

Decide whether to continue

The first conversation isn't an exam with an acronym attached. It's worth continuing while four conditions remain credible:

Budget belongs in the discussion when money is a real constraint. A missing budget field isn't a reason to disqualify somebody considering a $39 tool. Missing proof can sometimes become the work of a bounded test; missing need can't.

Show the part they care about

When the buyer asks to see the product or gives a strong buying signalSomething the buyer says or does that indicates they may be considering a purchase or another commercial step. Asking to see how the product handles their problem, involving an approver, requesting implementation details, or discussing payment can be buying signals; general praise isn't enough on its own., the smallest part that addresses the problem they've described is enough. A general tour forces them to translate your product into their life while you narrate the settings menu.

Gong reports analyzing 67,149 recorded screen-share sales demos and found that demos associated with closed deals tended to follow the priorities discussed earlier. It's vendor research on B2B-style demonstrations, so it doesn't establish a rule for email, chat, consumer purchases, or your particular customer. The narrow lesson still fits: let what you heard determine what you show. (Gong, last modified March 4, 2026)

The next question is what the buyer thinks it would change and what still feels uncertain.

Give them the price

If your product has a known fixed price, that figure belongs in your answer when the buyer asks. You don't need three further questions and a small ceremony around “value” before admitting that the account costs $39 a month.

For scoped or enterprise work, a range is enough until the missing details are known; the founder can explain what changes the amount and ask only what is needed to reach a real figure. The buyer can compare it with the consequence they've described, using their numbers instead of an imaginary return-on-investment calculation designed to make your invoice look tiny.

Use the proof you have

An early product may have no customer results, so distinguish what your proof shows from what you hope will happen:

Concerns need a proper answer

An objectionA concern, missing fact, or unresolved decision that may prevent the buyer from continuing. The founder's job is to understand what the buyer means, answer with available evidence, and accept when the concern leads to a no. tells you where the buyer sees risk or missing information. The response is to clarify it, acknowledge it, answer with the evidence you have, and say what remains unknown. Some concerns end in a no, which is a decision you can record and improve on next time.

Financial concerns deserve more attention than an immediate discount. “Too expensive” can mean the buyer can't afford the product, can't see enough value, has the wrong timing or budget, or needs another approver. Those are different problems.

Implementation concernsA concern about the work required to adopt the product, such as setup, data migration, integration, training, changing a habit, disruption, or assigning somebody to own the change. can include setup time, moving data, integrations, training, changing a habit, or nobody having time to own the change. The answer may be product evidence, a clearer plan, a smaller implementation, or an admission that the work is larger than the buyer can take on.

“Send me some information” needs clarification: which information, who is it for, and what decision will it support?

A pilot needs an ending

A pilotA limited real-use test intended to resolve a named uncertainty before a larger purchase or rollout. A bounded pilot has a scope, owners, end date, success evidence, price or explicit free status, and a decision that follows. should have its own dated boundaries. Before any work begins, the agreement needs its scope, owner on each side, end date, success evidenceThe observable result that will determine whether a pilot or test achieved its agreed purpose. It should be defined before the work begins, along with where the evidence will come from and who will assess it., price or explicit free status, and the decision that will follow.

U.S. National Archives guidance for public-sector technology pilots recommends defining the purpose, scope, stakeholders, and success criteria before a proof of concept begins. Its procedures and timelines belong to enterprise records systems, although the planning principle applies well to all. (U.S. National Archives, accessed September 2026)

Without those boundaries, a pilot can become indefinite custom work for somebody who still hasn't decided whether they want the product. You may discover you've started a consultancy, which is at least one way to get a very involved free trial.

Finish with one decision

A sales conversation should end with one action, one owner, and one date. That action can be payment, signup, a named piece of information, a pause, or a clean noA clear decision that the buyer won't continue. It replaces silence or an indefinite “maybe later” with evidence that the problem, product, timing, price, proof, or route to a decision doesn't support a purchase now..

“I'll send more information” counts if the information and the following decision or next step are clear. Follow-up refers to that action; wider sequences belong in the Cold outreach chapter.

Back to the dog groomer

The booking platform from the last chapter takes a customer's deposit when they book an independent dog groomer. It costs $39 a month, has a working demo and no customer results. A groomer the founder knows has described problems with no-shows and deposits, then agreed to look at it.

The founder can ask what happens from booking to appointment, how deposits and reminders work now, and what changing the process would require. If the groomer asks to see the platform or signals that the deposit flow may help, the founder shows that flow. The price is $39 a month, and the working demo shows how the product behaves; no groomer has produced a result with it yet.

The groomer may review the deposit flow by an agreed date, ask for one named piece of information, start the $39 account, or say no. We don't know which, so the example stops there.

Keep a record while you can still remember it

The founder-led sales record (download) contains the brief and a running record for each exchange. Repeated words, concerns, and decisions can then change the product or offer without one person's request becoming a roadmap by lunchtime.

You're ready to move on when the brief is prepared, you know which questions are worth asking, and you can recognize a real next action or a clean no. Building in public can later use recurring questions and customer language, with private details removed and permission sought where somebody could be identified.

Prompt: prepare my founder-led sales conversation

This prompt works once a suitable buyer has replied or agreed to speak. It needs only facts you know; I don't know yet is better input than a customer answer the model has helpfully made up.

I need to prepare for an early sales exchange with a suitable buyer.

Purpose
Turn the facts I provide into a one-page conversation brief that helps me
listen, decide whether the opportunity is worth continuing, discuss my product
and price honestly, and agree one next action. Don't write a persuasive script.

When to use it
A suitable buyer has replied or agreed to speak. The exchange may happen on a
call, over email, in chat, during a product demonstration, or in guided setup.

My context
- Product or service: [what I sell and what it does]
- Selected customer: [who I believe gets the best result]
- Buyer and other people involved: [who uses, pays, approves, or influences]
- Format: [call, email, chat, guided setup, or other]
- Trigger: [why this exchange is happening now]
- What I already know about their current process and problem: [facts, sources,
  and dates]
- What I still need to understand: [missing information]
- Offer and fixed price, or honest range for variable work: [details]
- Relevant product area: [what I could show if asked or if there is a strong
  buying signal]
- Proof I have: [demo, tests, documents, past experience, analogous result,
  expert review, pilot, or none]
- Limits of that proof: [what it can't establish]
- Likely financial or implementation concern: [if known]
- Possible next actions: [payment, signup, named information, another decision,
  bounded pilot, pause, or no]

Your task
1. Separate the facts I supplied, assumptions, and missing information. Don't
   invent buyer needs, answers, quotations, objections, authority, urgency,
   budgets, product results, or outcomes.
2. Recommend one objective for this exchange based on the current stage.
3. Draft three to five plain-English questions. Start with what happens now,
   what changed, the consequence, priority, previous attempts, and who is
   involved only where each question is relevant.
4. Assess whether four conditions appear credible: customer fit, a current
   problem that matters, a gap my product can plausibly handle, and a route to
   a decision. Mark each as known, uncertain, or unsupported and explain why.
5. Suggest a demonstration only if the facts contain a buyer request or strong
   buying signal. Name the smallest relevant product area and don't create a
   general feature tour.
6. State a known fixed price directly. For work whose scope changes the price, identify
   the minimum questions needed for a final price and use my supplied range.
7. Select the strongest honest proof available and state what it shows and what
   it doesn't show. Don't turn a demo, opinion, signup, or pilot into a customer
   result.
8. Turn each supplied financial or implementation concern into a question I
   can clarify. Suggest an evidence-based response only when my context contains
   the evidence, and identify anything I would still need to verify.
9. If a pilot is appropriate, require a scope, owners, end date, success
   evidence, price or explicit free status, and the decision that follows.
10. Suggest no more than two possible next actions. Each must name one action,
    one owner, and a date placeholder. Include a pause or clean no when the
    facts don't support continuing.

Output
# My founder-led sales brief
## Facts I know
## Assumptions
## Missing information
## Objective
## Questions worth asking
## Is this worth continuing?
## Product area to show, if asked or signaled
## Price
## Best available proof and its limit
## Concerns to clarify
## Possible next actions
## What I need to record afterwards

Use standard Markdown and write the brief in my first person. Use ordinary
language and avoid sales acronyms, pressure tactics, fake quotations,
guaranteed outcomes, invented testimonials, and invented customer evidence.
Keep the completed brief to one page where the supplied context allows it.

Sources

• Agarwal, Praveen, Stephen B. Castleberry, Rick Ridnour, and C. David Shepherd. “Salesperson Empathy and Listening: Impact on Relationship Outcomes.” Journal of Marketing Theory and Practice, Summer 2005. Survey: 162 organizational buyers. Accessed September 16, 2026.
• Gong. “Effective strategies for conducting successful sales demos.” Published September 14, 2017; last modified March 4, 2026. Reported analysis: 67,149 recorded screen-share sales demos. Accessed September 16, 2026.
• Graham, Paul. “Do Things that Don't Scale.” July 2013. Accessed September 16, 2026.
• Itani, Omar S., Emily A. Goad, and Fernando Jaramillo. “Building customer relationships while achieving sales performance results: Is listening the holy grail of sales?” Journal of Business Research 102, September 2019, 120–130. Meta-analysis: 24 empirical studies.
• Tamir, Diana I., and Jason P. Mitchell. “Disclosing information about the self is intrinsically rewarding.” Proceedings of the National Academy of Sciences 109(21), May 22, 2012, 8038–8043.
• U.S. National Archives and Records Administration. “Guidance for Proof of Concept Pilot.” Public-sector electronic-records management guidance. Accessed September 16, 2026.