B2B SaaS Sales Cycle Anatomy

A typical mid-market B2B SaaS cycle (ACV $15k–$100k) runs 30–90 days and follows seven stages. (1) Lead qualification: BDR or AE confirms the prospect matches the ICP (right company size, industry, tech stack, and active pain). Unqualified leads exit to marketing nurture. (2) Discovery: the AE conducts a 30–60 minute structured conversation to understand the prospect's specific pain, current solution, decision process, budget, and timeline. Discovery quality determines the deal direction — weak discovery produces generic proposals that lose to better-prepared competitors. (3) Technical demo: a customized product demonstration showing specifically how the product solves the problems identified in discovery. Generic demos close at dramatically lower rates than discovery-informed demos. (4) Business case development: the AE and champion collaboratively build the ROI model and internal justification that the champion will use to win internal approval. (5) Technical evaluation: IT/security review of the product's security posture and integration compatibility. Enterprise deals always include this stage. (6) Commercial negotiation: pricing, contract terms, SLA commitments. (7) Close: contract signature and handoff initiation to CS and implementation.

Discovery is the stage where the most information is available to the AE and where the deal direction is most malleable. A skilled discovery conversation surfaces: the "compelling event" — the specific business reason the prospect needs to solve this problem now rather than in 6 months (a compliance deadline, a new VP who made a commitment, a competitor shipping a feature they must respond to). Without a compelling event, deals stall indefinitely in evaluation. The "pain chain" — the business impact of the problem (not "our agents are slow" but "slow agent response is costing us $300k/year in customer churn based on our worst CSAT cohort analysis"). The pain chain gives the AE the business language for the proposal and the champion the ammunition to win internal budget approval. The decision process — who must approve? Who has veto power? What does a "yes" look like in their organization? This determines the stakeholder plan for the rest of the deal. Product Ops contributes to discovery quality by developing the discovery question framework that Maps to the product's core value propositions, and by training new AEs on the questions that surface the most commercially relevant insights for each customer segment.

The sales-to-CS handoff is where the most customer context is lost in the typical SaaS company. Everything the AE learned during discovery — the compelling event, the specific use case, the internal champion's goals, the key stakeholders, the promises made — must be systematically captured and transferred to the CS team before the first customer call. CS Ops designs the handoff architecture: (1) A structured deal briefing template that the AE completes as a condition of receiving their commission on the deal — not optional, not a nice-to-have. (2) The template maps to the discovery framework: what problem specifically brought them to sign? What does the champion have staked on this working? What are the 3 most important outcomes they must achieve in the first 90 days? What concerns or objections came up that were not fully resolved? (3) A mandatory AE+CSM handoff call (30 minutes) reviewing the briefing together before the customer kickoff — allowing the CSM to ask clarifying questions and the AE to provide context that is hard to capture in writing. (4) The handoff briefing is stored in a searchable format in Gainsight and Salesforce so that any future team member who touches the account can understand the original context.