Hire the first salesperson when you can describe a job they have a reasonable chance of succeeding at. A revenue target alone is not a job description.
The role might involve creating pipeline, qualifying demand, closing customers, or managing a more complex buying process. Decide which of those responsibilities are truly ready to transfer and which remain unresolved company-building work.
Test what can be taught
Can you explain the target customer, buying trigger, pitch, qualification criteria, common objections, and next steps? Can another person observe examples? Are there enough relevant opportunities to practice the process?
You do not need perfection. You do need a foundation that makes the hire more than a bet that someone else will discover the entire business model.
Identify the founder dependency
Some deals close because the founder can change the product, promise unusual support, or draw on personal relationships. Those are real advantages, but they may not transfer directly to an employee.
Write down where the founder still changes the outcome. Decide whether to teach the judgment, provide support, or change the offer so it can be sold more consistently.
Decide whether the gap is commercial or technical
Do not assume every sales bottleneck requires the same hire. A salesperson should own business discovery, qualification, account progression, and the commercial decision. A sales engineer should own repeatable technical discovery, solution fit, demonstrations, architecture review, and proof.
Review the qualified opportunities that are waiting on the founder. If the founder is still discovering the buyer, urgency, offer, or sales motion, keep learning before transferring the job. If qualified deals repeatedly need the same technical evaluation and founder availability is the constraint, use the technical-founder versus sales-engineer hiring framework to define the role and capacity case.
Define the first ninety days
Specify what the person should learn, demonstrate, and own. Include call quality, accurate qualification, useful CRM records, and progress through the actual sales cycle. Use revenue expectations that reflect the time required for customers to decide.
A hypothetical enterprise role with a long buying cycle may need early evaluation through demonstrated competence and qualified progress. Pretending a long cycle disappears for a new hire creates incentives to overstate opportunities.
Provide the conditions for success
Name the manager, product support, marketing inputs, tools, and decision rights. Decide how pricing exceptions and product commitments are handled. A salesperson should not have to improvise those policies in front of a buyer.
Require a handoff acceptance test
Do not treat a folder of recordings and a CRM reassignment as proof that the motion transferred. Have the new owner lead discovery, document buyer evidence, recommend the next action, and route one real exception through the agreed approval path. Then audit whether another person can understand the decision without asking the founder to reconstruct it.
The founder-sales handoff checklist defines the ten operating artifacts, decision-rights matrix, 30-day transition, and weekly review. Use it to distinguish what is transferred, what still needs founder support, and what remains unresolved company-building work.
Choose the profile for the job
Experience at a successful company is relevant only when the responsibilities transfer. A person who inherited a mature process may face a different job in a startup still building one. Evaluate how candidates reason about uncertainty and show their work.
Use the hiring scorecard and founder-led sales guide to make the transition concrete. The hire should increase the company’s ability to sell, not simply reduce the founder’s calendar pressure.
Co-founder and CEO of Stackmatix, startup advisor, and former Head of Sales at MightyHive. Connect with Matt on LinkedIn ↗ · More about Matt →