How to build a vertical-specific sales playbook

Vertical playbooks fail when the vertical is too broad. 'Healthcare' is not a vertical, it is a universe. A rep selling into a 25-provider dental group runs a completely different motion than a rep selling into a 400-bed hospital system or a Series B digital health startup. Before you write a line, pick one vertical and define the sub-segments inside it that actually share a buying committee, a budget shape, and a regulatory posture. Most teams land on three to five sub-segments per vertical. For SaaS: early-stage startup, growth-stage, late-stage, public. For financial services: community bank, regional bank, credit union, wealth management, insurance carrier. For healthcare: ambulatory, acute care, payer, life sciences, digital health. For manufacturing: discrete, process, industrial OEM, aftermarket services. Scope the playbook to the sub-segments where you have at least 10 closed-won logos or a clear strategic reason to invest ahead of the data.

• Name the vertical and list every sub-segment that sells differently
• Attach ACV range, cycle length, and typical buying committee to each sub-segment
• Drop sub-segments where you have no wins and no strategic mandate to invest
• Publish the sub-segment map on page one so reps know which track applies

A vertical playbook has three owners, not one. Enablement owns the structure, the rollout, and the measurement loop. Product Marketing owns the positioning, the proof points, the ROI model, and the competitor cheatsheets. The Vertical SME owns the industry truth: how buyers in this vertical actually make decisions, what jargon is table stakes versus red flag, what regulations compress or expand the deal cycle, and which personas carry real budget authority. The SME is usually a top rep who has lived in the vertical for years, an SE with deep domain scars, or an outside advisor on contract. Without a named SME, the book will sound generic to any buyer who has worked in the industry for more than two years. Lock the squad with a weekly 30-minute working session for the length of the build, and give the SME veto power on anything that misstates how the industry works.

• Name one owner each from Enablement, Product Marketing, and Vertical SME
• Set a weekly 30-minute working session for the full build window
• Give the SME explicit veto on industry claims, jargon, and persona assumptions
• Carve 4-6 hours per week on each owner's calendar for interview and drafting work

The fastest way to write a vertical playbook that lands is to borrow the language of buyers who already bought. Pick three to five current customers across your target sub-segments and run a structured 45-minute interview with the economic buyer and the champion from each account. Ask them to walk you through the problem that made them look, the internal conversation that formed the buying committee, the two or three competitors they considered, the proof they needed to approve the purchase, and the metrics they are now tracking to prove the project worked. Record every call. The discovery questions, the ROI math, the objection responses, and the competitor framing you will write in the next steps come almost directly from these interviews. If reps can hear a line in the playbook that sounds like something a real buyer in their vertical said out loud, they will trust it and use it.

• Interview the economic buyer and the champion for each reference account
• Walk the full buying story from trigger to approval to post-sale metrics
• Capture verbatim phrasing on pain, risk, and ROI language
• Record and transcribe every session for pattern analysis across accounts

Open the playbook with a two-page industry primer that any new rep can internalize in ten minutes. Section one: the three to five industry pains that drive projects in this vertical right now, each in plain language, each with a data point from a credible industry source, each tied to a measurable business cost. For SaaS: NDR compression, CAC payback stretch, platform consolidation pressure. For financial services: deposit flight, core modernization cost, examiner scrutiny on model risk. For healthcare: labor cost inflation, prior authorization overhead, value-based care contracts. For manufacturing: supply chain volatility, aftermarket margin leakage, skilled trades turnover. Section two: the buying committee map specific to this vertical, including the economic buyer title, the technical evaluator title, the end user, the compliance or security gate, and the typical procurement path. Reps need to know in the first call who they are talking to and who is missing from the room.

• List the 3-5 industry pains tied to measurable cost or risk, with sources
• Draw the buying committee with real titles seen in your closed-won deals
• Call out the compliance, security, or regulatory gate specific to the vertical
• Flag the typical procurement path so reps know how long legal and security will take

The discovery section is where the vertical playbook earns its keep. For every persona on the buying committee, write six to ten discovery questions in the exact language a buyer in that vertical uses. A generic question like 'tell me about your current process' lands flat. A vertical-specific question like 'how are you handling the new CECL loss modeling requirement across your consumer loan book' lands with a community bank CFO because it signals the rep has sold to community banks before. Group the questions by deal stage: trigger and pain in early discovery, process and buying committee in mid-stage, proof and risk in late-stage, and procurement and legal in close. Keep each question short enough to say out loud in a single breath. Reps will not read a paragraph in the moment, they will read one line and ask it.

• Write 6-10 discovery questions per persona in verbatim industry language
• Group questions by deal stage: trigger, process, proof, procurement
• Keep every question short enough to say in a single breath on a live call
• Pair each question with the signal to listen for in the buyer's response

A vertical playbook without an ROI model is a brochure. Write a short, defensible value hypothesis for the vertical with two or three measurable levers reps can plug customer data into on a call. For each lever, show the baseline (what the industry average looks like), the target (what good looks like after the project), the delta (the gap you can close), and the dollar impact (how that delta translates to revenue, cost, or risk reduction in this vertical). Keep the model in a one-page table reps can screenshot into a deck. Avoid Strkr-specific pricing or dollar figures in the ROI section itself, because the point is to quantify the buyer's problem, not to pitch your price. If possible, include two anonymized customer case studies with real before and after numbers from reference interviews so the model is grounded in observed outcomes, not projections.

• Pick 2-3 measurable levers that matter in this vertical (cost, revenue, risk, cycle)
• Show baseline, target, delta, and dollar impact for each lever
• Keep the full model on one scannable page a rep can screenshot into a call
• Attach 2 anonymized customer case studies with real before and after numbers

The competitors you lose to in a vertical are usually not the ones that show up in a horizontal competitive deck. In SaaS, you lose to the point tool everyone in the segment already uses. In financial services, you lose to the core vendor's bundled module. In healthcare, you lose to the EHR vendor's native workflow. In manufacturing, you lose to the legacy on-premise suite the operations team has run for 15 years. Write a one-page cheatsheet for each of the two or three competitors you actually see in this vertical. Each cheatsheet covers: how the competitor positions themselves in one line, where they win against you (and why), where you win against them (with proof), the three to four landmines to plant in discovery, and the pricing posture reps should take when the competitor is in the deal. Keep the cheatsheets honest. Overclaiming creates reps who get caught in a pitch and lose the champion.

• Pick the 2-3 competitors you actually see in this vertical, not the horizontal list
• Document positioning, where they win, where you win, with proof for each
• Write 3-4 discovery landmines per competitor to plant in early calls
• Add the pricing posture reps should take when the competitor is in the deal

The last content section is messaging. For each sub-segment and persona combination, write a one-line value proposition, a three-sentence narrative that connects industry pain to your solution to measurable outcome, and a short list of proof points: named customer logos in the vertical, case studies with quantified results, analyst mentions where relevant, and compliance or certification badges that unblock the vertical's security review (SOC 2, HIPAA, PCI, SOX, FedRAMP, as applicable). Pair the messaging with a short library of vertical-specific assets reps can send after the call: a one-page vertical brief, a vertical case study PDF, a short video from a reference customer in the vertical, and a tailored demo script that reorders your standard demo flow to lead with the two or three features that matter most in this vertical. Reps do not have time to assemble a custom follow-up. Assemble it for them.

• Write a one-line value prop and three-sentence narrative per persona and sub-segment
• List named vertical customers, case studies, and compliance badges reps can cite
• Build a short follow-up asset library: brief, case study, video, tailored demo script
• Reorder the standard demo flow to lead with the 2-3 features that matter most here

Vertical playbooks are expensive to build and easy to over-engineer. Before you ship to the whole field, pilot the book with three to five reps who are actively working deals in the vertical. Give them two to three weeks to run the plays, the discovery, the ROI model, and the follow-up assets. Instrument everything from day one: tag opportunities with the vertical and sub-segment, require reps to log which plays they ran and which objections they heard, and tag call recordings so the pilot team can review usage. At the end of the pilot, hold a 60-minute debrief where every pilot rep walks a live deal, calls out which sections of the book worked and which fell flat, and nominates the top edits. Ship the revisions, then roll out to the full field at the next SKO or dedicated launch, with manager certification on the top two plays before reps leave the room.

• Pick 3-5 reps actively working vertical deals and brief them on the pilot
• Instrument CRM fields and call recording tags from day one of the pilot
• Hold a 60-minute debrief at pilot end with every rep walking a live deal
• Ship pilot revisions, then roll out at SKO or launch with manager certification