Most published sales playbook examples are generic frameworks dressed up with a cover page. This page walks six concrete playbook examples from real-looking motions, with the stage criteria, objection responses, pricing guidance, and segment variations each one ships. Steal what fits.
The problem with most published sales playbook examples: they are generic. "An ideal customer profile," "a discovery framework," "pricing guidance." No specifics. The reader finishes the article knowing they need a playbook, with no model to copy. This page runs six playbook examples that are specific: the exact ICP for a mid-market SaaS team, the exact ten discovery questions a FinServ enterprise team uses, the exact five objection patterns an industrial team ships, the exact stage criteria a dev-tools team enforces. The point is not that these specifics will transplant verbatim; it is that specific examples let you see the shape and adapt rather than imagining.
Search for "sales playbook example" and the results are blog posts with a cover page, three sections of "define your ICP, build your discovery framework, write your objection responses," and no specifics. The reader cannot adapt an abstraction. The playbook examples that teach are the ones that are specific enough to feel almost over-detailed, which is where this page is going.
A playbook example optimized for 30-day SMB SaaS cycles has nothing useful to say to an industrial team selling 180-day deals. Published examples rarely name the motion they are optimized for, so readers try to apply SMB structure to enterprise and vice versa. The examples below name their motion explicitly: SMB SaaS, mid-market SaaS, enterprise SaaS, FinServ, industrial, dev-tools. The structure is motion-specific.
Many playbook examples assume a mature CRM, a sales ops function, named sales enablement, and a trained manager layer. For teams without these, the example is a target state, not an immediate copy. The examples below note which maturity assumptions are embedded so readers can see where their situation diverges and adapt.
Common published examples give one or two sample stage criteria that read like checkbox items. Real stage criteria are specific and vary by stage: discovery exit is different from demo exit, demo exit is different from proposal exit, proposal exit is different from contract-sent exit. The examples below give full stage-exit criteria across all pipeline stages for each motion, which is where the content actually earns its keep.
Playbook examples that have not been refreshed in two or three years reference deprecated competitors, outdated pricing conventions, and buyer personas that have evolved. The examples below are set in a current 2026 context with current product tiers, current competitor landscape, and current typical pricing. They will need refreshing in two years regardless.
A playbook example that does not mention the comp plan is only half the picture. The playbook and the comp plan need to echo each other; a playbook that pushes multi-threading while comp pays only on single-threaded new logo will not drive multi-threading. The examples below include the compensation structure that goes with each playbook so the relationship is visible.
Each example below gives the ICP, the discovery framework, the stage definitions with exit criteria, the top objections and response patterns, the pricing guidance, and the comp structure for one real-looking motion. Together they cover most B2B sales shapes.
ICP: companies 20 to 200 employees, product-marketing fit confirmed, buyer is Head of Sales or Head of Marketing with budget authority under 25K. Discovery: five questions, 15 minutes. Stages: Discovery, Trial, Proposal, Closed. Trial exit: product used by three users in 14 days. Proposal exit: verbal buy-in from decision maker. Objections: too expensive (pattern: ROI math); not enough time to evaluate (pattern: pilot proposal); already using free tier of competitor (pattern: specific feature differentiation). Pricing: self-serve to 25K with no approval; discount to 15 percent off list at rep discretion. Comp: flat 10 percent on new MRR with quarterly SPIF on upsell. The whole playbook document is 18 pages.
ICP: companies 200 to 2000 employees, named champion identified pre-opportunity, deal size 50K to 250K ACV. Discovery: ten questions over two 45-minute calls, MEDDPICC structure. Stages: Discovery, Demo, Technical Review, Proposal, Negotiation, Closed. Demo exit: economic buyer joined for second half. Technical exit: IT or security team cleared for pilot. Proposal exit: written success criteria confirmed. Objections: already evaluating competitor X (pattern: specific feature differentiation plus side-by-side proof); concerns about implementation (pattern: named reference plus services scope); procurement timing (pattern: pre-approved MSA). Pricing: list to 100K; approval chain above. Comp: 8 percent on new logo, 10 percent on upsell, kicker on multi-year.
ICP: companies 2000 plus employees, Fortune 2000 preferred, buying committee of five to seven, deal size 250K to 2M ACV. Discovery: 15 questions across three 60-minute meetings with different stakeholders, Challenger structure. Stages: Qualification, Discovery, Technical Deep-Dive, Business Case, Procurement, Legal, Closed. Discovery exit: economic buyer, technical buyer, user champion all engaged. Business Case exit: written ROI co-authored with champion. Procurement exit: MSA redlines closed. Objections: existing enterprise agreement (pattern: adjacent-system positioning); multi-year commitment (pattern: flexible ramp); security review (pattern: pre-staged SOC 2 package). Pricing: no self-serve; multi-year preferred. Comp: 6 percent base plus 2 percent accelerator above quota.
ICP: banks, credit unions, wealth managers, insurance carriers over 500M AUM or 100K accounts, deal size 300K to 3M. Discovery: 20 questions including explicit regulatory posture, SOC 2 / FedRAMP / PCI requirements. Stages: Discovery, Compliance Review, Technical Review, Business Case, Procurement, Legal, Deployed. Compliance Review exit: internal risk team approval documented. Technical Review exit: data residency and encryption posture confirmed. Business Case exit: written ROI with regulatory team sign-off. Objections: data residency (pattern: regional deployment proof); regulatory audit (pattern: pre-staged attestation package); vendor concentration risk (pattern: multi-year transition plan). Pricing: enterprise only; multi-year standard. Comp: 5 percent base plus 3 percent accelerator plus 2 percent compliance-pass bonus.
ICP: manufacturers 100 to 2000 employees, buyer is operations or engineering lead, deal size 15K to 150K annual spend. Discovery: 8 questions over 30-minute discovery and 60-minute technical demo, SPICED structure. Stages: Discovery, Technical Demo, Sample Shipment, Proposal, Closed. Technical Demo exit: specific use case verified. Sample Shipment exit: in-plant validation data. Proposal exit: procurement contact identified. Objections: price per unit (pattern: TCO calc); switching cost from current vendor (pattern: transition services); approval chain (pattern: pre-staged purchasing packet). Pricing: list to 50K; volume tiers above. Comp: 7 percent on new accounts; 4 percent on repeat orders.
ICP: engineering teams of 10 to 500 developers, self-service usage already present, deal size 20K to 300K ACV. Discovery: six questions over 30-minute call, triggered by usage signal (team workspace reaching threshold). Stages: Signal, Qualification, Expansion Call, Proposal, Closed. Qualification exit: economic buyer named. Expansion Call exit: cross-team expansion commitment. Objections: already using free tier successfully (pattern: enterprise-feature pivot); open-source alternative (pattern: operational cost comparison); procurement complexity (pattern: streamlined MSA). Pricing: self-serve to 20K; sales-assisted above. Comp: 10 percent on new logo, 8 percent on expansion, no cap.
Each example above is calibrated for a motion. Before copying stage criteria or objection patterns, run the fit checks below. Mismatches between the example motion and your motion will show up as adoption failure in the first quarter.
A playbook built for a 90-day mid-market SaaS cycle has to be substantially adapted to run on a 240-day enterprise FinServ cycle. The number of stages, the stage exit criteria, the proposal timing all change. If your cycle is within 20 percent of the example you are borrowing from, direct copy is usually workable. Beyond 20 percent, expect to rebuild stages and criteria.
An SMB example with single-threaded buyer will not survive contact with an enterprise buying committee of seven. The playbook stages and the discovery framework depend heavily on committee shape. Match the example to your actual buying motion, not to your aspirational motion.
FinServ, healthcare, and government motions have regulatory gates that other examples omit. Industrial motions have in-plant validation gates. Dev-tools motions have usage-trigger gates. If your motion has a gate the example does not model, add the stage or you will have reps advancing deals that are not actually ready.
The comp structure in each example above is calibrated to its motion. Copying stage structure without comp alignment produces incentive misalignment. If your organization pays flat commission on new logo and the example assumes an upsell kicker, the behavior the example drives will not emerge. Align the comp or expect the playbook to underperform the example.
Several examples assume structured discovery data, named economic buyer fields, and MAP density on opportunities. Teams without these will need a data-maturity pass before the example runs. The playbook rebuild usually goes alongside the data-cleanup pass, not after it; attempting one without the other produces a playbook on top of unreliable records.
Five mistakes we see when teams copy a published example without adaptation. If the plan is to copy one of the six examples above, read these first.
Teams that copy stage exit criteria verbatim from a published example usually run into friction in the first quarter because the criteria do not match the actual motion. Stage criteria need to be your criteria for your deals, with the example as inspiration not as gospel. Adapt in the first draft; verify with top AEs; iterate for two or three quarters.
An enterprise example has multi-threaded buying committees, named champion requirements, business case documents. Teams that aspire to enterprise will often copy the enterprise example before they have the motion to support it. The result is a playbook that reads correctly for a motion the team is not yet running, which produces adoption failure in month two.
Discovery frameworks need to match cycle length. Twenty discovery questions work in a 180-day enterprise cycle; they overshoot a 30-day SMB cycle and burn out buyer attention. Match the discovery depth to the cycle length; the examples above calibrate this per motion for a reason.
Each example above assumes a comp structure. Copying the playbook structure without aligning comp produces incentive misalignment and underperformance against the example. Either align comp or adapt the playbook to the comp you actually have; running one without the other produces a worst-of-both.
The examples above are snapshots of working playbooks. Working playbooks iterate quarterly. Teams that copy and do not iterate end up with the example frozen on day one, while the market and the product keep moving. The copy is the start; the quarterly refresh is the discipline that keeps the playbook relevant.
HubSpot ships a Playbooks module. Here is how each example above would be delivered in each tool.
| Feature | Strkr | HubSpot (Sales Hub Professional + Playbooks) |
|---|---|---|
| Motion-specific playbook routing | Automatic by segment field | Manual playbook selection |
| Stage exit criteria as record fields | Native with stage-transition gating | Property-based; no gating |
| MEDDPICC / Challenger / SPICED templates | Shipped templates per methodology | Custom build |
| Multi-segment playbook library | Unlimited playbooks with routing | Up to 50 on Professional |
| Objection response library on record | Native snippet panel | Playbook card side panel |
| Compensation plan integration | Native comp preview on opportunity | Separate tool required |
| Playbook example import from Notion / GDoc | Mapping-based import | Manual rebuild |
| Pricing for 40 reps running six playbooks | Flat per-seat; six playbooks included | Pro at 100 per seat with playbook limit |
Four teams who used a published playbook example as the starting point for their own build. The adaptation decisions mattered more than the source.
A mid-market SaaS team used an enterprise playbook example as inspiration but adapted the stage structure (five stages instead of seven), compressed the discovery (eight questions instead of fifteen), and dropped the Business Case stage. The remaining structure fit the motion. Within two quarters, average cycle time dropped by 18 percent while win rate held, which was the goal.
An industrial team was running a four-stage playbook without a sample-validation gate. Deals were closing on verbal commitments and churning in month three because the use case had not been validated in-plant. The team added a Sample Shipment stage with explicit exit criteria from the industrial example above. Close rate on sample-validated deals rose from the previous average, and the three-month churn dropped materially.
A dev-tools startup building a PLG motion for the first time copied the Example 6 structure almost verbatim because the motion was new to the company and the team had no better baseline. The usage-signal triggered discovery, the compressed stage structure, and the expansion-focused comp all transplanted well because the company's motion was close to the example. New AE ramp dropped from 7 months to 4 inside two quarters.
A FinServ enterprise team was running a generic enterprise playbook without a Compliance Review stage. Deals were advancing to Proposal without the risk team engaged, then slipping two or three quarters when regulatory issues surfaced. The team rebuilt the playbook using Example 4, adding the explicit Compliance Review stage. Forecast accuracy rose from 69 percent to 91 percent across four quarters, which materially improved the CFO conversation.
Start a 14-day Strkr trial with six motion-specific template playbooks, stage-exit criteria, and objection libraries ready to adapt. See how a playbook example actually runs on production pipeline.
You can start with one of them as a baseline, but direct copy almost never produces a working playbook on first attempt. The examples above are calibrated for specific motions (cycle length, deal size, buyer committee, regulatory posture). Run the five fit checks before copying anything, and expect to adapt stage criteria, discovery depth, and objection patterns to your actual motion in the first draft.
Example 2, the mid-market SaaS playbook, is the closest match for most mid-market B2B SaaS motions in the 50K to 250K ACV range with a 60 to 120 day cycle. Teams below that range will find Example 1 (SMB) more applicable; teams above will find Example 3 (enterprise). The dev-tools example applies narrowly to PLG motions with established self-serve usage.
Four to eight weeks for the first draft, two to three quarters for the first stable version. The first draft is a document review and a top-AE workshop. The stable version requires rolling out to the floor, measuring stage-criteria completion and win rate, iterating on the criteria that are not getting filled or not predicting outcomes, and settling into a version the floor actually uses. Teams that expect to be done in a week usually produce something unused.
The examples above cover AE motions from first discovery through close. SDR motions (prospect targeting, outbound cadence, meeting-set qualification) sit upstream and need a separate playbook. The right-shape SDR playbook is often one-fifth the length of an AE playbook because the surface area is narrower; it belongs on the same shared library but should not be collapsed into the AE playbook.
The stage exit criteria section. Teams usually read the discovery section and the objection section carefully and skim the stage criteria. The stage criteria are what determine whether reps advance deals correctly, whether forecasts are accurate, and whether coaching conversations are grounded in evidence. Teams that borrow stage criteria thoughtfully and skip the rest of the example often get more lift than teams that borrow everything else.
Yes. The Strkr playbook library ships six base playbooks matching the motions in Examples 1 through 6 above, with configuration guides for adapting each to a team. Teams can start from the template and adapt rather than build from scratch. The templates are not a shortcut around the thinking work; they are a starting point that saves the first two weeks of blank-page work.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
