Founder-led sales should produce customers and a clearer understanding of how the company wins them. The founder’s involvement is valuable because product, positioning, and commercial decisions are still changing quickly.
My background includes more than 300 customers closed at MightyHive and $20M in personal sales there. That experience is part of why I want marketing and sales evaluated together. A lead only becomes valuable when the business understands what to do with it.
What is the founder trying to learn?
Learn who has the problem, how they describe it, what creates urgency, and what has to happen before they buy. Record the alternatives they consider, the people involved, and the work required to reach value.
Do not reduce every call to whether the prospect liked the demonstration. A positive conversation can coexist with no budget, no owner, or no reason to act. The sales process should make those differences visible early enough to use them.
How should the first conversations begin?
Start with the customer’s current situation. Ask about a recent example of the problem and follow the sequence of events. What happened? Who noticed? What did the team do? What was the consequence?
Then establish whether your offer addresses something important. Explain the relevant part of the product and ask where the explanation fits or fails. The conversation should test your understanding, not simply give the prospect a tour.
What should a founder qualify?
Qualify the problem, fit, ability to act, and path to a decision. Each is separate. A severe problem does not automatically make your product the right solution, and an interested user may not control the budget.
A useful qualification note includes the evidence, the remaining unknown, and the next question. Avoid filling the CRM with confident labels that nobody can trace to a conversation. “Strong opportunity” is not an explanation.
When should the product demonstration happen?
Demonstrate once you understand enough to choose a relevant story. Show the workflow that matters to the buyer, explain the outcome, and leave space for questions. A complete feature tour can obscure the small part of the product that creates the buying reason.
For a hypothetical operations product, show how a manager handles an exception in the current workflow and how the product changes that work. Ask what would prevent adoption in the buyer’s environment. That question often reveals more than asking whether the interface looks good.
How should pricing enter the conversation?
Discuss price in the context of scope, value, and the buying process. Waiting until the end to reveal a material mismatch can waste time for both sides. Equally, presenting a number without context can encourage a comparison that misses what is included.
Treat price objections as questions to investigate. Is the buyer unconvinced about value, unable to fund the purchase, comparing a narrower alternative, or negotiating? Those situations call for different responses.
When is a pilot useful?
A pilot is useful when it resolves a specific uncertainty that prevents a larger purchase. Define the question, the work, the success criteria, and the decision that follows. Assign an owner on both sides.
An open-ended pilot can become unpaid product work with no route to revenue. The paid-pilot guide explains how to make the commercial step explicit. Do not promise a larger contract merely because someone agrees to test.
Who else needs to participate?
Understand the user, champion, budget owner, technical reviewer, and any procurement or security participants relevant to the deal. One person may fill several roles. The important point is knowing which decisions remain outside the current contact’s control.
Ask the contact how similar purchases happen internally. Help them prepare useful information for colleagues. Do not treat the champion as an obstacle to bypass; they may be the person making the project possible.
What should follow-up accomplish?
A follow-up should move the decision forward. Summarize the problem, what was agreed, what remains unresolved, and the next action with an owner and date. Send material that answers a real question from the conversation.
Repeatedly asking whether someone has “any updates” adds little value. If the project has lost priority, establish that clearly enough to stop forecasting it as imminent revenue.
How should founders handle lost deals?
Separate loss reasons that imply a change in the business from those that reflect a poor-fit opportunity. If several relevant buyers cannot understand the value, investigate the offer. If the product lacks a requirement essential to the intended market, investigate the product or target segment.
Record the buyer’s explanation without automatically treating it as the entire cause. Price can be the easiest reason to give when the deeper issue is low urgency or weak differentiation. Look for patterns across evidence.
What belongs in the CRM?
Keep the fields required to manage the next decision: customer situation, source, stage, relevant people, value or scope, next action, expected timing, and unresolved risks. Define stages by buyer progress rather than seller activity.
A demonstration delivered is something the seller did. A buyer agreeing to evaluate the product against a specific requirement is stronger evidence of progress. The CRM comparison can help select software after the process is clear.
When is the process ready for a salesperson?
Look for enough consistency to explain the audience, pitch, qualification, demonstration, objections, and next steps. You do not need a perfect machine. You do need a job that another person can reasonably learn and improve.
Write down where the founder still makes judgment calls. Decide which can be taught, which require support, and which remain genuinely unresolved. That creates a more realistic first sales hire than hoping experience alone will fill every gap.
How should a founder remain involved after hiring?
Stay close to selected calls, customer outcomes, and changes in the buying process. Give the salesperson room to execute while maintaining a feedback route into product and marketing. Founder involvement should help resolve uncertainty, not create a parallel process nobody can predict.
Review the reasons deals move, stall, and close. The objective is to make successful selling less dependent on one person’s memory and relationships.
A practical weekly sales review
Inspect new qualified demand, opportunities that materially advanced, deals with unclear next steps, and losses that teach something. Choose the actions that can change the week’s outcomes. Keep product feedback separate from promises about what will be built.
Start by improving the next five conversations and the records they produce. The discovery call structure and qualification template provide concrete starting points. Consistency should make learning easier, not turn every customer conversation into a rigid script.
Selling an AI product?
AI software adds questions about output quality, review effort, and the cost of exceptions. The AI sales and GTM playbook connects those questions to a buyer scorecard, a worked economic example, and the decision to move from evaluation to paid rollout.
Co-founder and CEO of Stackmatix, startup advisor, and former Head of Sales at MightyHive. Connect with Matt on LinkedIn ↗ · More about Matt →