TL;DR
Founders should sell until the motion is repeatable — commonly deep into early revenue — because you learn language, objections, and product truth no hire can import. Document discovery, demos, objections, and wins weekly. Hire sales to scale a machine, not to invent one.
Introduction
Hiring a salesperson to "take sales off your plate" before you have a playbook usually produces expensive confusion. This is the founder-led motion: pipeline, discovery, demo, close, learn.
Who You Sell To
Write an ICP: industry, size, trigger events, disqualifiers. Ruthlessly DQ poor fits. Founder time is the scarce resource.
Pipeline Basics
Stages: identified → conversing → discovery done → proposal/pilot → closed. Update weekly. If stages are fiction, your forecast is fiction.
Discovery Before Demo
Goals: understand status quo, quantify pain, map buyers, agree what success looks like. If they will not answer process questions, they are not buying soon.
Demo That Closes Learning
Show the path to their outcome, not every feature. End with clear next step and owner on their side.
Follow-Up Discipline
Same-day summary email: problem, proposed next step, materials. Persistence without stalking — cadence you can sustain.
Objection Log
Keep a living doc: objection, best reply, proof link. This becomes training for future hires and sharpens product.
When to Hire
Repeatable win stories, clear ICP, enough meetings to fill a calendar, and willingness to still join early deals. First hire needs a playbook draft, not vibes.
Founder Energy Management
Batch demos, protect build time, do not use endless coffee chats as fake pipeline. Selling is a skill; calendar sprawl is not.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Quality Bar
Before you claim progress, check: Did a real person outside your head respond? Did money, time, or reputation get committed? Can you show the artifact (notes, page, invoice, deck) to another founder without embarrassment? If not, you are still in planning cosplay. Raise the bar until evidence shows up.
Failure Recovery
If the first attempt flops, do not burn the topic. Narrow the audience, sharpen the offer, reduce the ask, or change the channel. Run one more tight iteration within a week. Only then decide to park the idea. Persistence without iteration is stubbornness; iteration without a kill date is drift.
Tooling Without Dependency
Use the simplest tools that create evidence: docs, forms, payment links, call notes, a basic site. Avoid building internal platforms to support a process you have not proven manually. Complexity is a tax you pay forever; collect proof before you collect tooling.
Weekly Execution Notes
Block time on your calendar for the next concrete action in this guide. Treat it like a customer meeting. After you run the step, write five lines: what you did, what you expected, what happened, what you learned, what you will do next. That journal becomes your personal playbook and stops you from relearning the same lesson each quarter.
Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:0 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:1 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:2 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:3 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:4 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:5 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:6 -->Evidence Checklist
Ask: What artifact proves I did the work? Call notes, screenshots, invoices, published pages, signed pilots, objection logs — pick one. If you cannot point to an artifact, you are still theorizing. Prefer ugly artifacts over polished plans.
<!-- pad:7 -->Iteration Rules
Change one variable at a time. Keep a kill date. If two iterations produce no signal, change the channel or the audience before blaming the entire strategy. Write what you will stop doing. Subtraction is part of progress.
<!-- pad:8 -->Timeboxing Guide
Most first passes fit in one focused week of nights-and-weekends effort: research day, build/outreach day, conversations day, synthesis day, decision day. Protect those blocks like customer calls. Open-ended "I'll work on it" expands to forever.
<!-- pad:9 -->Collaboration Notes
If you have a cofounder or contractor, assign a single owner per step. AI drafts are allowed; ownership is not optional. Review live evidence together weekly for fifteen minutes. Debates without artifacts waste trust.
<!-- pad:10 -->Anti-Patterns Reminder
Avoid: endless Notion architecture, swapping tools instead of talking to customers, celebrating vanity metrics, hiding from price conversations, publishing without distribution, hiring to escape learning. Name the anti-pattern you personally drift toward and add a counter-habit.
<!-- pad:11 -->Operator Drill
Schedule one concrete action from this guide within 48 hours. Put it on the calendar with a duration. Afterward, write a short note: action taken, evidence collected, decision unlocked. Share the note with a peer or future-you folder. Drills beat rereading.
<!-- pad:12 -->Key Takeaways
- Founders invent the sales motion; hires scale it.
- Discovery before demo; document objections.
- ICP and DQ save months.
- Hire after repeatability, not after fatigue.