What is founder-led sales?
Founder-led sales is the early work of finding suitable buyers, understanding their decision, demonstrating the product, and agreeing a commercial next step. The founder learns which audience fits, which explanation makes sense, and what is required for someone to adopt the software. A useful outcome can also be discovering that an opportunity is unsuitable before you commit weeks to it.
Pete Kazanjy’s Founding Sales describes early founder selling as a process that is developed before being handed to a sales team. Use that as a reason to stay close to the conversations. You can delegate scheduling and preparation while keeping responsibility for factual claims, product boundaries, and what you learn from a buyer. The exercise here focuses on a small SaaS offer rather than a scaled outbound operation.
Who should you speak to before trying to sell?
Choose someone who performs or owns the relevant task and has a plausible path to trying the product. Learn who else needs to participate in the decision. A user may understand the workflow while a colleague controls spending or approves integrations. A conversation with the wrong role can produce enthusiastic feedback without a feasible next step.
Use the audience worksheet and a short explanation from the positioning guide. Approach through a relevant introduction, an inbound request, or another appropriate setting. Avoid turning a person’s participation in a community into assumed permission for repeated sales messages. Fit begins with the task, not the size of a contact list.
How do you begin a sales conversation without showing every feature?
Agree the purpose and the time available, then ask about the current workflow. What triggered the search? How is the task handled today? What needs to be different? What would prevent a trial? These questions help you choose a relevant demonstration and identify whether the current product has a useful role.
For a fictional reporting tool, imagine a small agency preparing weekly client summaries from existing notes. You might ask how the summary is reviewed, which facts must be checked, and who receives the final version. If the agency needs a data integration you do not support, address that condition before presenting an unrelated dashboard. The customer-interview guide helps investigate the workflow; make clear when the discussion moves into evaluating an offer.
What should an early product demonstration include?
Show a short path from relevant input to an inspectable result. Prepare a demo account, explain any manual steps, and let the buyer ask about the parts that matter to their work. A pre-recorded example can support the conversation, but be clear about the version and what has actually been tested. Avoid presenting a mockup as an available feature.
In the fictional agency example, the useful path could be importing sample notes, generating a draft summary, correcting a factual detail, and exporting the reviewed result. Ask whether that output would fit the agency’s handoff. The demo preparation guide covers recording and safe sample material; the activation guide helps define the result a trial should reach.
| Stage | What to show or ask | Observation to record |
|---|---|---|
| Current process | How the agency prepares and reviews a summary now | The actual alternative and the step that needs improvement |
| Demonstration | Sample notes becoming an editable, reviewed draft | Whether the output fits the handoff and what remains missing |
| Offer | The price, allowance, support, and trial or pilot conditions | Questions or objections tied to the stated offer |
| Next step | Who will try what, by when, and how the result is reviewed | An explicit agreement, a pending decision, or a clear decline |
How do you handle objections you cannot solve immediately?
Find out what the objection changes about the decision. A missing export may block the handoff; a preference for a different button color may not. A question about reliability may need a reproducible demonstration, while a requirement you cannot meet may make the current opportunity unsuitable. Record the buyer’s explanation instead of automatically offering a discount or promising a feature.
Founding Sales’ pitching chapter treats demonstration, objections, and follow-up as distinct work. For a small app, a practical response is to state what is available, investigate an uncertain fact, and return with a specific answer. Use the feedback decision guide for requests that might affect the product. Do not put an uncommitted feature date into a sales recap.
When should you discuss price and a paid pilot?
Discuss the real commitment early enough for the buyer to decide whether further evaluation is worthwhile. State the price, currency, billing period, included usage, support, and important limits. A buyer should not invest in a long setup process only to discover that the offer is fundamentally outside their budget or scope.
If a pilot fits, define the task, duration, responsibilities, support, review, and what happens afterward. A paid assisted pilot is different from a self-service subscription; record that distinction when interpreting the result. The first-plan pricing guide helps prepare the offer, while the pricing-page guide helps explain it consistently on the public site.
What belongs in a useful follow-up?
Send a concise recap through the channel the person agreed to use. Include the task you discussed, the relevant product facts, the open question, and the next step you actually agreed. An illustrative recap could read: You want a weekly client summary that a reviewer can edit before export. The demo covered that workflow with sample notes. You will check the export with your reviewer, and we agreed to discuss the result next Tuesday. Use only details that are true for that conversation.
If no next step was agreed, do not write as though a pilot has started. Ask a bounded clarification where appropriate, or close the opportunity with a reason. A polite decline gives you useful information about fit. Repeated follow-up without new information or an agreed purpose usually teaches you less than speaking with another suitable buyer.
Which sales stages should a first-time founder track?
Keep a simple record of relevant conversation, agreed demonstration, active evaluation, offer discussed, purchase, and delivered first result. Define each stage by evidence rather than optimism. An interesting reply is not an agreed meeting, a meeting is not a pilot, and a pilot is not automatically a recurring customer. Record the current blocker and next owner alongside the stage.
The worksheet includes blank fields for offer version, task, decision participants, next action, and outcome. Once someone starts using the app, follow the retention guide to investigate continued value. Before delegating more sales work, review which parts of the process you can explain and repeat accurately. The goal is a useful customer relationship and a clearer buying path.