# When to Hire Your First Salesperson > A practical readiness test for founders deciding whether their first sales hire should happen now, later, or not yet. By BuildPurdue Team · July 24, 2026 · 6 min read Source: https://www.buildpurdue.org/blog/hire-first-salesperson --- **Hire your first salesperson when you can explain who buys, why they buy, and how you currently reach them. Then hire someone to repeat that motion with you, not someone expected to invent the whole sales system alone.** ## Key takeaways - Treat repeatability as the hiring gate, not a particular revenue milestone. - Keep selling until you can name one customer type, one painful problem, and one sales path that works more than once. - Write down the trigger, objection, proof, channel, and time to close for every deal. - Make the first hire a bridge: they take over a documented motion while the founder keeps owning the hardest conversations. ## Do the founder-led work first Early customers are more than revenue. They show you which problem is urgent, which buyer has authority, what language makes sense, and what objections stop a deal. [Mercury's founder-led sales blueprint](https://mercury.com/blog/the-founder-led-sales-blueprint) frames the readiness test this way: you should be able to say, "I know I can sell my thing when I speak with [X type of person] who has [Y problem]." If you cannot fill in that sentence, another salesperson will be guessing on your behalf. That does not mean the founder has to become a polished closer. It means the founder must stay close enough to the buyer to learn the pattern. [Y Combinator's guidance on doing things that do not scale](https://www.ycombinator.com/library/96-do-things-that-don-t-scale) makes the same practical point: founders should manually win and delight early customers because the work teaches them what a later process needs to preserve. A useful pre-hire test is simple. Pick one narrow customer group, run the sales conversations yourself, and record what happens. Do not combine three customer types and call the result a sales process. If every win came from a different audience, a different promise, and a different channel, you have a collection of anecdotes, not a motion someone else can run. ## Define a readiness gate There is no universal deal count that guarantees a good hire, but a rough range can create discipline. [Empra Labs' founder-led GTM playbook](https://empralabs.com/blog/founder-led-gtm-playbook) uses about 10 to 20 founder-closed deals as a practical checkpoint, provided those deals show a repeatable pattern. The number is a prompt to inspect the evidence, not a passcode. Before opening the role, answer these questions: - Can you describe the buyer in one sentence without using a market as broad as "small businesses"? - Does the buyer have a recurring problem with a clear cost, risk, or delay? - Can you explain where qualified conversations come from? - Can you predict, within a reasonable range, how many conversations produce one deal? - Can you show a new person what to say, what to ask, what to demonstrate, and what happens after the call? Empra Labs recommends looking for a single channel that produces deals you can explain and reproduce across at least 10 wins. That is a stronger test than saying sales are "going well." A lucky referral, a founder's personal reputation, and one unusually urgent customer may produce revenue without producing a repeatable process. ## Document the motion while you still own it Your first sales playbook does not need to be a 40-page manual. It needs enough detail for another person to understand why the last deals happened. [Empra Labs' playbook](https://empralabs.com/blog/founder-led-gtm-playbook) recommends recording five fields for each opportunity: 1. The trigger: what changed or happened that made the buyer look for a solution? 2. The objection: what nearly stopped the deal? 3. The proof: what evidence made the buyer comfortable? 4. The channel: how did the conversation begin? 5. The time to close: how long did the decision take? [Dock's founder-led sales guide](https://www.dock.us/library/founder-led-sales) recommends building repeatable templates for calls, follow-ups, and onboarding. Use those templates as a starting point, then leave room for the buyer's actual context. The point is consistency with judgment, not robotic scripts. Also write down the boundaries. Which customers should you refuse? Which requests are custom work rather than product demand? Which promises can the company make today? Mercury's practitioner guidance emphasizes being direct about what the product can and cannot do. That honesty gives a new hire a safer place to operate than vague instructions to "sell the vision." ## Make the first hire a bridge The first salesperson should extend a working motion. They should not be expected to discover the customer, invent the positioning, build the CRM, set pricing, and close a full pipeline at the same time. For many early teams, the first useful hire is a salesperson who can sell and document, not a senior executive hired to manage a department that does not exist yet. Dock's guide describes the first sales hire as someone who needs to build the system as well as close deals. Empra Labs similarly recommends that the founder keep owning pipeline while the new hire ramps. Plan the handoff in stages: 1. The founder runs the call and the new hire observes. 2. The new hire runs part of the call using the founder's questions and examples. 3. The new hire owns straightforward opportunities while the founder joins harder or strategic calls. 4. The founder reviews the deal record and objections every week. 5. The process changes only when new evidence justifies the change. Budget for the overlap. A hire who needs to learn the buyer and the product is not a failed hire because they do not produce a predictable pipeline immediately. The founder's job is to keep learning from the market while the new person learns the motion. ## What to avoid - Hiring because the founder is tired of selling, while the buyer and sales path are still unclear. - Choosing a big title before defining the work the person will own. - Handing over a CRM full of contacts with no record of why deals closed. - Measuring activity alone, such as emails sent or demos booked, without checking qualified conversations and closed deals. - Leaving the founder out of sales calls immediately after the hire starts. - Changing the target customer, pricing, and sales process all at once, then blaming the hire for weak results. ## FAQ ### Should I hire a salesperson before product-market fit? Usually, no. If you are still changing the target customer and the core problem every few weeks, founder-led selling is still research. Hire help when you can describe the customer and the motion clearly enough to teach it. ### Is 10 to 20 deals a hard rule? No. Empra Labs uses it as a practical checkpoint, not a law. Ten deals from one repeatable customer group can be more useful than twenty deals that came from unrelated situations. ### Should the first hire be a VP of Sales? Usually, the first hire should be close enough to the work to sell, learn, and document. A senior executive may be right for a larger team with an established motion, but an early company should avoid paying for management before it has a system worth managing. ## Wrap up Before you post the role, write the one-sentence buyer definition, pull the last 10 deals into a simple table, and look for the pattern. If you cannot explain why the wins happened, keep selling and keep documenting. If you want a second set of eyes on the handoff plan, bring it to [buildpurdue](/cohort) for a practical founder review.