TL;DR
Founder-led sales is a superpower that most founders underuse. Buyers value founder access, authenticity, and the ability to make commitments that a sales rep can't. The key is structured discovery (don't let conversations drift), clear next steps (always end with a committed next action), and using your founder status to access senior buyers that SDRs can't reach.
Founder-led sales is one of the most underrated advantages in early-stage B2B. Buyers know they're talking to the decision-maker — which creates a level of trust and accountability that an SDR or AE can't manufacture. Here's how to use it effectively.
Use your founder status as an opener Cold email as founder consistently generates 2-3x better reply rates than the same email from an SDR. "Hi [Name], I'm [Name], co-founder of [Company] — I'm personally reaching out to a small number of [job title] leaders because I'm convinced [specific insight about their problem]." The founder reaching out personally signals seriousness and makes the prospect feel valued.
Structure discovery calls like a consultant The mistake founders make: they immediately demo the product and start selling. The right approach: spend the first 20 minutes understanding the prospect's situation, goals, challenges, and current approach. Only then demonstrate how your product addresses what you've just learned about them. This turns the demo into a prescription rather than a pitch.
The structured close framework At the end of every meeting, don't say "sounds good, I'll follow up." Instead: "Based on what we've discussed, I think [specific product feature] directly addresses [specific problem they mentioned]. What would need to be true for this to be a priority for your team in the next 60 days?" This question surfaces objections, budget reality, and stakeholder dynamics immediately — rather than letting deals stall in the "we're thinking about it" stage.
Committing the next step in the meeting Every meeting should end with a specific committed next step: a follow-up meeting with the economic buyer, a pilot proposal, a reference customer call, or a signed proposal. If the prospect won't commit to a specific next step in the meeting, the deal is likely not real. "What's your timeline for making a decision, and what would the evaluation process look like?" surfaces this clearly.
From Cactus: Cactus works with founder-sellers regularly — the most impactful coaching shift we make is moving founders from 'feature tour' demos to consultative discovery-first conversations, which typically improves close rate by 30-50%.
Cactus Marketing embeds with B2B tech startups to turn strategy into pipeline. We've worked with 60+ companies, supported 12 exits, and contributed to $7B+ in client valuations.
Book a free 30-minute call — we'll give you a concrete plan for your situation.
Book a free strategy call →How do I hire my first SDR?
Hire your first SDR only after you've personally closed 5–10 customers and can articulate exactly what messaging, ICP, and objection handling worked. An SDR hired before the founder has figured out the sales motion will fail — they need a playbook to follow, not to build one from scratch.
What should an SDR quota be?
A typical SDR quota in B2B SaaS is 8–15 qualified meetings booked per month, or $150–300K in pipeline generated per quarter. The right number depends on your ACV, lead source, and market. Set quota based on what's achievable from proven activity metrics, not what would be convenient for the business.
How do I onboard an SDR?
Build a structured 30-60-90 day plan with clear milestones: product mastery in week 1, ICP and messaging training in week 2, supervised calling in week 3, and independent ramping with quota from day 31. Document everything — the SDR should have a playbook on day one, not six weeks later.
What is a good SDR conversion rate?
A good SDR conversion rate is 2–5% of outbound contacts to qualified meeting, and 25–40% of qualified meetings to SQL (sales accepted opportunity). Below these benchmarks suggests targeting, messaging, or qualification issues — not necessarily SDR execution.