-
1
Research the buyer before you draft a single line
Every effective pitch is 70 percent research and 30 percent writing. Before you draft, spend 20 minutes building a buyer sheet: company revenue, headcount, recent funding or earnings notes, product launches in the last 90 days, the primary buyer's LinkedIn and role tenure, and any public signal that tells you what they are worried about this quarter. Pull this into Strkr CRM as a Research tab on the account record so the pitch travels with the deal, not in a document the next rep cannot find. Strkr AI drafts the first version of the research sheet from public signals when you create the account, which cuts the manual time to under five minutes per prospect. The pitch you write for a growth-stage SaaS CMO reporting to a new CRO sounds nothing like the pitch for a public-company CFO six quarters into a cost-cutting cycle. If your pitch sounds the same across both, it is tuned to your product, not to the buyer, and it will convert at the baseline rate for cold copy, not the premium rate for targeted copy. The research sheet should also note three names other than the primary buyer: the sponsor who will champion the deal internally, the economic buyer who signs the contract, and the detractor who will raise the hardest objection. Pitching only to the primary contact without naming the other three is how pitches land well in the first call and die quietly in the following week when the detractor you did not plan for shuts it down inside the buyer's organization.
- Build a one-page buyer research sheet before drafting any pitch
- Capture company context, buyer role, tenure, and current public pressure signals
- Store the sheet in Strkr CRM on the account record so it travels with the deal
- Let Strkr AI draft the first version from public signals; validate before pitching
Tip: If you cannot answer "what is this buyer worried about this quarter" from your research sheet, you are not ready to write the pitch yet.
-
2
Write the opening hook: a 20-second problem statement
The opening is the only line that gets 100 percent attention, so spend 60 percent of your drafting time there. The hook is a single sentence that names the problem the buyer already has in their own language, and a 10-second credibility anchor that lets them know you are not a generalist. Avoid product-first openings like "we help companies grow revenue" because they are indistinguishable from the previous five pitches the buyer has heard this week. Instead, open with the specific friction: "Series B revenue teams are losing six to eight weeks per hire because their pipeline review and forecast cadence are built on three disconnected tools." Then anchor: "We helped a 40-rep team at a similarly staged company cut that cycle in half." The hook does two things: it tells the buyer you understand their job, and it tells them you have done it for someone like them. If the hook is right, the next 90 seconds of pitch becomes a conversation. If the hook is wrong, the rest of the pitch is talking to someone who has already mentally hung up. Store three to five hooks per segment in Strkr CRM as a Pitch Library, versioned, so reps pick the hook that matches the buyer profile rather than reinventing it on every call. The hook should also pass the "would a buyer say this out loud to their boss" test. If the problem statement is one you can imagine the buyer forwarding verbatim to their CFO as a reason to take the next meeting, the hook is working. If the hook needs translation before the buyer could share it internally, the hook is still in sales language and will not travel inside the buyer's organization, which is where most of the real selling happens between meetings.
Tip: Read your hook out loud. If it sounds like a brochure, cut it and try again. If it sounds like something a human would say in a coffee shop, keep it.
-
3
Structure the pain segment around three specific frictions
The pain segment is where you earn the right to show the product. Keep it short: three specific frictions, 20 seconds each, drawn from the buyer research you did in step one. Avoid listing every problem your product solves, because every added problem dilutes the specificity of the ones that matter. Each friction should include a cost: time wasted, revenue leaked, or a strategic bet the buyer cannot make because of the friction. Costs make pain concrete. "Pipeline reviews take 90 minutes a week per manager" is a measurable cost. "Pipeline reviews are inefficient" is a complaint. Measurable costs convert, complaints do not. Use the Discovery Call insights that live inside Strkr CRM to pattern-match the right three frictions for each buyer segment, and let Strkr AI suggest the top three frictions from the activity history on similar closed-won accounts. The pain segment should end with the buyer nodding, not with you reciting. If you are talking more than 60 seconds without a confirmation question, you have slipped into monologue mode and the pitch is losing them. Rank the three frictions by what the buyer most recently said matters, not by what you most want to sell. A buyer who just raised capital cares about scaling the sales motion. A buyer six quarters into cost-cutting cares about consolidation and efficiency. The same product can solve both, but the pitch for each buyer leads with the friction that matches their current pressure, which is the signal that you heard what they said in discovery.
- Pick three specific frictions from the buyer research sheet; drop every other problem
- Attach a measurable cost to each friction: time, revenue, or strategic opportunity
- Ask a confirmation question after each friction to keep the pitch conversational
- Store the frictions by segment in Strkr CRM Pitch Library; let Strkr AI suggest matches
-
4
Insert proof: one case study, named customer, quantified outcome
Proof is the single highest-converting segment of any pitch, and most sellers underuse it. One named case study, with a quantified outcome, from a company that looks like the buyer, outperforms a list of logos every time. The structure is three sentences: who the customer is (segment, size, buyer role), what their friction was (same friction you just named), what the outcome was with a specific number ("cut forecast error from 22 percent to 8 percent in two quarters"). Avoid vague proof like "many of our customers see significant improvements." Vague proof is treated as noise. Named proof with numbers is treated as evidence. Store case studies as structured records in Strkr CRM Case Study Library with segment, buyer role, friction, outcome, and quote fields, so reps can filter the right proof story in under 10 seconds during a live call. Strkr AI matches the best case study to the current opportunity based on segment and buyer role, which means reps stop defaulting to the one case study they remember and start pitching with the one that fits. The right proof story is the one the buyer could introduce to their boss on Monday. Capture new case studies the week they happen, not the week before the next pipeline review. The quantified outcome is freshest when the customer sponsor still remembers the before-state, and the quote reads as more credible when it is signed within 30 days of the measurable milestone. Strkr Flows can automate a weekly nudge to the customer success team to capture outcomes against the success criteria that were defined in the proposal, which keeps the Case Study Library growing on evidence rather than on anecdote.
Tip: Ask for permission to use the customer name in your pitch at the point you sign the renewal, not six months later. The window closes fast.
-
5
Position the product in two sentences, not twenty
Product positioning is where most pitches collapse. The temptation is to list every feature. The reality is the buyer wants to know two things: what the product is in one sentence, and why it is different in one more sentence. Resist the demo urge; the pitch is not the place to show the product, it is the place to earn the right to show the product next week. A tight positioning line looks like: "Strkr is a unified revenue platform that combines CRM, forecasting, and automation in one system, which means your pipeline reviews, forecast submits, and hygiene rules all run on the same data instead of three disconnected tools." That is 42 words. If you cannot say what the product is and why it is different in under 50 words, you have not thought about positioning hard enough yet. Store the positioning line in Strkr CRM Pitch Library at the top level, not per rep, so every pitch starts from the same definition and the sales team is not accidentally selling five different versions of the product. Positioning also decays as the market shifts. The line that worked when the category was new will sound generic once three competitors publish similar language. Audit positioning quarterly against the top three competitors the buyer will evaluate. If the positioning line could be swapped onto a competitor's website with only a logo change, the differentiator is weak and the positioning needs to be sharpened. Strkr AI can summarize competitor positioning from public signals and surface the overlap, which gives marketing a short list of places where the Strkr positioning needs to pull further ahead.
- Write one sentence that names what the product is
- Write one sentence that names what makes it different from the next three competitors the buyer will see
- Keep the combined positioning under 50 words
- Store the line centrally in Strkr CRM Pitch Library; audit it quarterly
-
6
Handle the three objections you will hear every time
Every pitch triggers roughly three objections, and they are the same three objections every time within a given segment: price, implementation effort, and risk. Write a scripted response to each, 20 seconds long, with a specific proof point attached. Price objections handled with "we offer transparent per-seat pricing with a 30-day pilot that lets you validate ROI before you commit a full contract" land better than "we are competitive on price." Implementation objections handled with a named customer who went live in a specific number of weeks land better than "we are easy to implement." Risk objections handled with a specific contractual guarantee or a named reference customer land better than "we are a safe choice." Store the responses in Strkr CRM Objection Library tied to segment, so reps have the right response at hand instead of improvising on the call. Strkr AI listens to call recordings and tags the objections it hears, which gives you a weekly report on which objections are rising and which are fading, so the library stays current rather than frozen on day one. The order you handle objections matters. Address price last, not first, because a buyer who agrees the implementation is manageable and the risk is contained is a buyer who will accept a higher price than one who has not yet been convinced on either. Reps who lead with price concessions train the buyer that the price is negotiable, which widens the discount and shrinks the deal size without any corresponding lift in conversion.
- List the top three objections you hear in each segment from the last 90 days of calls
- Write a 20-second scripted response to each, with a specific proof point attached
- Store the responses in Strkr CRM Objection Library tied to segment
- Let Strkr AI tag objections from call recordings; refresh the library quarterly
Tip: The strongest objection response always includes a specific name or number. Generic reassurance converts at the same rate as no response.
-
7
Close for a specific next step, not a generic yes
The pitch closes with a next step, not with the sale. The next step is a confirmed calendar event with a named stakeholder on a specific date, not a vague "I will send over some information" or "let me know if you are interested." Reps who close for a specific next step on 80 percent of pitches see 2 to 3 times higher opportunity creation rates than reps who close with open-ended questions, which is consistent with Pavilion research on discovery conversion. The right close looks like: "Based on what you shared about the forecast cycle, the next useful conversation would be a 45-minute working session with your head of RevOps where we walk through your current pipeline and show what Strkr Forecasting would surface. I have a slot Thursday at 10 or Friday at 2, which works?" That close is specific, framed around their stated friction, and gives two options which converts higher than a single ask. Store the close script by segment in Strkr CRM Pitch Library and let Strkr AI auto-draft the follow-up email with the confirmed calendar event prefilled, which cuts rep admin time by 60 to 70 percent per pitch. The close is also where you qualify the stakeholder map. The right next-step invitation names a specific person on the buyer's side ("your head of RevOps"), which gives the buyer a reason to introduce you to that person rather than carrying the follow-up alone. Pitches that end with a named stakeholder invitation move to multi-threaded deals 2 to 3 times faster than pitches that end with a vague "let's talk again next week," and multi-threaded deals convert at materially higher rates.
-
8
Capture the pitch outcome in Strkr CRM every time
Pitches you do not log do not improve. Every pitch outcome, win or lose, needs to land in Strkr CRM against the opportunity with four data points: which hook was used, which case study was referenced, which objections came up, and what the next step was. This is 30 seconds of rep work and it is the single highest-leverage investment you can make in pitch iteration. Strkr AI pulls the data from call recordings and prefills the fields, so the 30 seconds becomes 10 seconds of validation. Over 60 to 90 days you build a dataset of which hook converts best per segment, which case study moves which buyer role, and which objections correlate with lost deals. That dataset is how the pitch stops being a document and starts being a tested asset. Treat the pitch like a product your team ships; measured, iterated, and never frozen. Pitches that live on a slide deck without instrumentation drift because reps improvise, and improvisation at scale produces average pitches, not winning ones. The pitch log is also the input to coaching. A manager running a weekly one-on-one can filter the rep's last five pitches in Strkr CRM, see which hook was used and what the outcome was, and have a coaching conversation grounded in the actual deal rather than recall. Grounded coaching converts into measurable rep improvement 2 to 3 times faster than general feedback, which is one of the clearest findings in the published sales coaching research from Pavilion and Harvard Business Review.
- Log every pitch outcome in Strkr CRM with hook, case study, objections, and next step fields
- Let Strkr AI pull call data to prefill the fields
- Review the 90-day data every quarter: which hook per segment, which case study per role
- Retire low-converting hooks and promote high-converting ones to the Pitch Library
Tip: If your team cannot tell you which pitch hook converts best per segment this week, you are shipping a pitch, not running one.
-
9
Iterate the pitch on a 90-day cadence
Pitches drift. Buyer problems shift, competitor messaging evolves, your product changes, and the pitch that worked last quarter starts converting below baseline. Review the pitch every 90 days using the Strkr CRM data you captured in step eight. Pull hook performance by segment, case study performance by buyer role, objection volume shifts, and next-step conversion rate. Promote the top-performing variants into the Pitch Library and retire the bottom 20 percent. Share the retrospective with the whole sales team on the first Monday of the quarter, because pitch quality is a team sport, not a rep-level secret. When you ship pitch changes, note the version in Strkr CRM so you can see which deals were pitched on which version. If the quarter after a pitch change sees a 10 percent drop in opportunity-to-closed-won conversion, roll back the change and investigate before rolling forward. Treat the pitch the way a product team treats a shipping product: measured, iterated, versioned, and never finished. The quarterly retro is also when you compare top-performing and bottom-performing reps on the same pitch version. If one rep converts at twice the rate of another using the same hook, the delta is a coaching opportunity, not a pitch problem. Record the retro findings inside Strkr CRM so pitch changes have a traceable reason, and so the next head of enablement does not reinvent the pitch from scratch every time there is a leadership change.