Sales motion — discovery, qualification, and the first AE transition.
The outbound infrastructure produces meetings. The sales motion is what happens between the meeting being booked and the deal being closed. For pre-PMF teams, this is the founder; for post-PMF teams, this is the first AE; for both, the discipline is the same — discovery, qualification, multi-thread engagement, proposal, close.
Seven chapters. Discovery call architecture, qualification frameworks (BANT, MEDDIC, SPICED done right rather than as theater), demo engineering, multi-thread engagement strategy, proposal and contract design, the founder-led sales motion through the first $1M ARR, and the first AE transition — when to hire, who to hire, how to hand off.
The empirical pattern observed across pre-PMF and early-PMF B2B teams: founders who run their own sales motion through the first $1-2M ARR convert at 20-35% from qualified meeting to closed-won. Founders who hire an AE in the first $200K ARR convert at 5-15%. The differential is not the founder's superior sales skill — it is the embedded ICP-and-product knowledge that an AE cannot replicate in their first 90 days. This reference is the operational discipline that makes founder-led sales work, and the structured handoff that makes the AE transition produce a step-up rather than a step-down.
Layer one — the call architecture.
Discovery call architecture
The 30-minute discovery call structure: opening (2 min), context (5 min), discovery (15 min), proof (5 min), next-step (3 min). The per-section objective, the per-section failure modes, and the operational discipline that produces the 60-80% advancement rate from first call to second.
Qualification frameworks
The canonical B2B qualification frameworks (BANT, MEDDIC, SPICED, GPCT), the empirical per-framework effectiveness by stage and ACV tier, the failure mode of treating frameworks as checklists rather than conversational architectures, and the operational selection criteria.
Demo engineering
The demo-during-discovery anti-pattern, the structured-demo architecture for the second call, the per-feature showing decision, the customer-in-the-driver-seat demo pattern, the empirical conversion-rate differential by demo discipline, and the failure modes (overwhelming the buyer, demo-as-pitch, no problem anchor).
Layer two — close mechanics.
Multi-thread engagement
The single-champion failure mode (a champion who loses internal politics loses the deal regardless of product quality), the multi-thread engagement pattern, the per-role engagement architecture (champion, economic buyer, technical buyer, end user, blocker), the empirical conversion-rate lift on three-plus-thread deals.
Proposal and contract design
The proposal-as-summary vs proposal-as-pitch distinction, the per-clause architecture of a B2B SaaS proposal, the legal-vs-business-terms separation, the procurement-navigation pattern, the e-signature handoff, and the operational discipline that turns a verbal yes into a countersigned contract.
Layer three — the team transition.
Founder-led sales
The founder-led sales discipline: how to run a sales motion as the founder without losing time on engineering, the per-week time allocation, the operational structure (single calendar, single CRM, single pipeline review), and the empirical conversion-rate ceiling at the founder-only stage.
The first AE transition
The empirical timing of the first AE hire ($500K-1.5M ARR typical, with stage and segment variance), the AE profile (industry experience vs founder-mentee, the per-segment fit), the hand-off playbook, the 90-day ramp expectations, and the failure mode of the premature AE hire that produces 12 months of below-founder performance.
The sales motion is the founder's job through the first $1M ARR.
Allston Labs runs the upstream layer — outbound infrastructure, reply handling, meeting booking — and hands off qualified meetings to the founder for the sales motion itself. When the AE transition arrives, we operate the upstream pipeline that the new AE inherits.