Founder sales next-step close
End every early founder sales call by booking the next concrete step instead of waiting for the prospect to return.
Why this can grow a startup
Early founders are often strong in the middle of a sales conversation because they understand the product, market, and workflow better than any first sales hire. Jason Lemkin says the missing skill is simpler: never leave the meeting without a next step. That could be another demo, another stakeholder, a pilot, or a contract timeline. The tactic keeps founder-led demand from dying in the inbox.
Source-backed example
Jason Lemkin advises founders and product leaders to ask for the next meeting, stakeholder, or step at the end of every sales conversation, then log it in the CRM.
Source-reported evidence
Source: Lenny's Podcast transcript dataset · Browse Lenny's Podcast transcript dataset tactics
sales meetings with scheduled next step
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 21, 2026
When to use it
Use this when Email, LinkedIn is relevant to conversion, sales and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Email and LinkedIn, using evidence from Lenny's Podcast transcript dataset as context—not as a promised result.
- Record a baseline for: Target users from this channel who complete the intended first action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.