design-sales-processlisted

# Design Sales Process Build an operating system around buyer decisions and observable evidence. A sales process should improve judgment and handoffs, not reward moving records forward. ## Inputs Read `.agents/gtm-context.md`, existing lifecycle and opportunity definitions, buyer journey evidence, closed-deal histories, CRM field definitions, timestamped stage events, handoff requirements, segment and motion differences, and current governance. Establish the scope, as-of date, design owner, users, and decision the process must improve. When history is sparse, produce a provisional design and measurement plan. Do not present copied stage names, benchmark conversion rates, or guessed service levels as validated defaults. Read [the process-design methods](references/methods.md) when defining stages, exits, exceptions, metrics, or rollout. Use [the sales-process template](assets/sales-process.md). ## Workflow 1. Define the motion, segment, object, start and end points, users, and business decisions in scope. 2. Map the buyer's decisions, validation work, and legitimate stop paths separately from seller activities. 3. Audit the current process using timestamped records, interviews, counterexamples, and downstream handoff failures. Separate observed behavior from policy and aspiration. 4. Design the smallest stage set in which each stage represents a materially different buyer or decision state. 5. Give every stage observable entry evidence, exit evidence, disqualifiers, and