# SaaS selling strategies that move deals > Twelve selling strategies that hold up against buying committees: value framing, pilot design, mutual action plans, champion coaching and competitive displacement. Source: https://saas-marketing.net/guides/saas-selling-strategies/ Topic: SaaS Sales Type: guide Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/guides/saas-selling-strategies/ ## Short answer Selling SaaS into a buying committee is a sequencing problem, not a persuasion problem. The strategies that reliably move deals are value framing against the status quo, a written mutual action plan, pilots with pre-agreed success criteria, champion coaching, multithreading by function, procurement preparation, and displacement timed to the incumbent's renewal. A mediocre rep running the sequence beats a great rep improvising, because committees stall on process gaps rather than on doubt. ## Key takeaways - A written mutual action plan with named owners and dates is the single most influential artefact in a stalled deal. - The competitor in most B2B SaaS deals is the status quo, so frame value against doing nothing before comparing features. - Pilots without written success criteria agreed in advance convert far worse, because nobody can declare them a success. - Multithread by function, not by seniority: security, finance and the end-user team each block for different reasons. - Displacement campaigns should start 120 days before the incumbent's renewal, because auto-renewal notice windows close early. - Champion coaching means arming someone to sell internally when you are not in the room, which is most of the time. --- The uncomfortable finding in modern B2B sales is that technique matters much less than sequence. Gartner's buying research puts six to ten people in a typical software decision and roughly 83 percent of the buying journey happening without any supplier in the room. Deals don't die because a rep phrased a value proposition badly. They die because the security review started in week nine instead of week two, and the quarter ran out. So this page is about process. Twelve strategies, each with the situation it fits, the exact move, and how you know it worked. ## 1. Frame value against the status quo, not against a competitor Most SaaS deals are lost to "we'll revisit next year", not to a rival. So the first value conversation should quantify the cost of doing nothing, in the buyer's own numbers. The move: get the buyer to state their current process in units. Hours per week, tickets per month, errors per quarter, headcount required. Then price that at their loaded cost. A support team spending 14 hours a week on manual triage at a 65 dollar loaded hourly rate is spending roughly 47,000 dollars a year on the thing you replace. Now your 30,000 dollar product is a saving rather than a cost. Signal it worked: the buyer repeats your number back to you in a later meeting, or uses it with someone else. If you never hear the number again, it didn't land and they're still comparing you to zero. Failure mode: inventing the number yourself. A value calculator you filled in has no credibility inside their finance review. It has to be their data, gathered in their words. ## 2. Write a mutual action plan, and treat refusal as the signal A mutual action plan is a shared document listing every step from here to go-live, with a named owner on each side and a date. Security review, legal, procurement, technical validation, implementation kickoff. The move: introduce it right after a successful demo, framed as "here's what the next six weeks look like, help me get the dates right". Then keep it live in a shared doc, not a PDF. Signal it worked: the buyer edits it. A buyer who adds their own step, or corrects a date, has taken co-ownership of the process. That's the strongest qualification signal available in enterprise SaaS. Failure mode, and the useful one: they won't engage with it. That isn't a document problem. A buyer who will not put dates against their own process is telling you the deal is not funded, not prioritised, or not real, and you've learned it in week three rather than at the end of the quarter. This is the single most influential artefact in the whole list, and it works because it converts a vague intention into a set of specific commitments somebody has to break out loud. On a stalled deal, a mutual action plan gives you a legitimate, non-needy reason to contact the buyer: a date passed and you are checking whether it should move. That's a far better re-engagement than 'just circling back', and it works because they agreed to the date. ## 3. Run paid pilots with written success criteria Pilots fail because nobody defined what success looked like, so at the end there's no basis to declare anything and the deal drifts into a second pilot. The move: before the pilot starts, write down three measurable criteria, the evaluation date, and who decides. "Reduce average triage time from 40 minutes to under 20 across at least 200 tickets, measured on 14 November, decided by the support director." Get it in writing, in the mutual action plan. Charge for it. Above 25,000 dollars ACV a paid pilot is almost always right, because it forces the budget conversation early and makes the buyer allocate real internal resource. Free pilots get deprioritised the week something urgent appears. Keep the fee modest and creditable against year one. Signal it worked: the buyer assigns internal staff time to the pilot. If nobody on their side is doing work, the pilot is a demo with extra steps. ## 4. Coach the champion for the meetings you won't attend Your champion is going to defend this purchase in an internal meeting you'll never see, probably against a CFO who has three other requests on the same agenda. Whatever they take into that room is your actual sales pitch. The move: build them a one-page business case in their company's format, not yours. Cost, payback period, what happens if we don't, who else uses it. Add the three objections their finance lead will raise, with answers. Rehearse it with them on a call. Signal it worked: they send you a question that could only have come from a colleague. That means the material circulated. Silence means it sat in their inbox. Failure mode: sending marketing collateral. A glossy PDF with your logo on it reads as vendor material in an internal meeting and gets discounted accordingly. A [champion business case template](/templates/champion-business-case/) in the buyer's own format survives that room much better. ## 5. Multithread by function, not by seniority Reps are taught to go higher. The more useful axis is sideways, because the functions that block a SaaS deal each block for different reasons and the VP cannot answer for any of them. The pattern in the security row is worth naming. Vanta built a business on the fact that security review is where enterprise SaaS deals go to sit for six weeks, and the correct response is to have the SOC 2 report, penetration test summary and completed questionnaire ready to hand before anybody asks. A trust page that answers 80 percent of the questionnaire removes weeks from the cycle. That's a marketing asset that closes deals, and it's covered further in [how to market to a B2B SaaS buying committee](/guides/b2b-saas-buying-committee/). ## 6. Time displacement to the incumbent's renewal, 120 days out Displacing an incumbent is a calendar exercise before it's a persuasion exercise. Most enterprise contracts auto-renew unless notice is given 30 to 90 days before the term ends, so a buyer who loves your product in month eleven still cannot act. Here's the worked sequence against a contract renewing on 31 March. **Displacement sequence, 120 days out** Incumbents routinely respond to displacement with a steep discount and a promise of the missing feature next quarter. Your champion needs an answer ready before it lands: ask what changed, ask for the roadmap commitment in writing with a date, and point out that the price was available all along. Improvising this conversation loses deals that were otherwise won. ## 7. Prepare procurement before procurement arrives Procurement's job is to slow you down and extract concessions. That's not adversarial, it's their function, and you can prepare for it. The move: three weeks before you expect procurement involvement, send the champion your standard contract, your security documentation, your insurance certificates and your supplier onboarding details. Ask what else their process requires. Most procurement delays are document-gathering delays, and you can do that work in advance. Signal it worked: procurement's first email asks a substantive question rather than requesting seven documents. That's two weeks saved. ## 8. Anchor price before they anchor for you If you present a single number, the buyer's counter-anchor is zero and every conversation afterwards is a negotiation downward from your list price. The move: present three options, with the largest first, and be prepared to explain who each one suits. The point of the top option is not that they'll buy it. The point is that the middle option now has a reference point that isn't your competitor's price. Failure mode: discounting before being asked. A rep who offers 15 percent to speed things up has taught the buyer that the list price was fiction, and every subsequent negotiation starts there. ## 9 to 12. The four that fill the gaps **Sell the implementation, not just the product.** The end-user team's real objection is that their next month gets worse. A named implementation owner, a week-by-week rollout plan and a defined support commitment answer it. Deals with a written implementation plan stall noticeably less at the final approval stage. **Use consumption or seat ramps for large deals.** A buyer nervous about a 200,000 dollar commitment will often sign a ramped deal starting at 80,000 and stepping up over 18 months. You get the contract, they get the risk reduction, and the ramp schedule is much easier to negotiate than the headline number. **Book the next meeting in the current meeting.** Trivial, and the difference between a 30-day cycle and a 60-day one. Chili Piper exists because the gap between "I'll send some times" and an actual calendar entry is where deals lose weeks. Never end a call without a diarised next step. **Run a documented loss review on every lost deal.** Not the rep's version. Ask the buyer, three weeks later, with no pitch attached. The pattern across 20 losses tells you whether you have a pricing problem, a product gap, or a process problem, and those need completely different responses. Most teams record "lost to competitor" and learn nothing. Every strategy here is a process artefact: a document, a date, a pre-prepared asset. None of them is a phrase to say on a call. That is deliberate. A mediocre rep running a mutual action plan, multithreading by function and preparing procurement will beat a charismatic rep improvising, consistently, because committee deals are lost to gaps in process rather than to insufficient persuasion. ## Making this stick across a team Individual reps adopting individual techniques produces nothing measurable. What produces a measurable change is making the artefact mandatory at a stage gate: no deal enters stage three without a mutual action plan, no pilot starts without written success criteria, no opportunity passes forecast review without a named economic buyer. That's why [MEDDPICC](/glossary/meddpicc/) works in enterprise SaaS: it's a checklist of the things that stall deals, applied as a gate rather than a coaching topic. Codify the gates in a [SaaS sales playbook template](/templates/saas-sales-playbook-template/) so new hires inherit the process rather than reconstructing it. Tooling supports this but doesn't create it. Call recording and analysis platforms like Gong surface which conversations contain the discovery questions you require; sequencing platforms like Salesloft and Outreach enforce the cadence around displacement timing. The stack options are compared in [the SaaS sales stack](/tools/saas-sales-tools/) and [sales engagement platforms compared](/tools/sales-engagement-platforms/). If you're standing up a motion from nothing, the ordering is different and covered in [sales strategy for a SaaS startup](/playbooks/saas-startup-sales-strategy/). **Deal health check, run at stage three** ## What to do next Pick one artefact and make it mandatory this quarter. If you only do one, make it the mutual action plan, because it both improves deals and tells you which deals aren't real, which is worth more to your forecast than anything else on this list. Then run loss reviews on the next ten losses with the buyer rather than the rep, and see whether the pattern is price, product or process. My strong expectation is process, and that's the cheapest of the three to fix. The wider strategic frame sits in [SaaS sales strategies](/saas-sales/), and the demand side that feeds all of it is in [SaaS lead generation](/saas-lead-generation/). ## Frequently asked questions ### What is a mutual action plan? A shared document listing every step from evaluation to go-live, each with a named owner on both sides and a target date. It covers security review, legal, procurement, technical validation and implementation. Its real function is diagnostic: a buyer who will not co-own dates is telling you the deal is not real, which is information you want in week three rather than month four. ### How do you sell SaaS to a buying committee? Map the committee by function rather than seniority, because each function blocks for a different reason. Security wants a SOC 2 report and a penetration test summary, finance wants a business case with a payback period, the end-user team wants to know who administers it. Build a specific asset for each and give your champion all of them in a form they can forward. ### What is champion coaching? Preparing your internal advocate to sell on your behalf in meetings you will never attend. That means a one-page business case in their company's format, the three objections their CFO will raise with answers, and a clear ask. Most deals are decided in internal meetings, so the quality of your champion's material matters more than the quality of your demo. ### How do you displace an incumbent vendor? Start 120 days before their renewal date, because auto-renewal notice windows commonly close 30 to 90 days out. Find the specific unmet need rather than attacking the incumbent generally, offer to run a parallel pilot on one workflow, and quantify the switching cost honestly. Buyers trust a vendor who names the migration pain more than one who pretends there is none. ### Should SaaS pilots be paid or free? Paid, in almost every case above 25,000 dollars ACV. A paid pilot forces a budget conversation early, which surfaces whether money exists, and it makes the buyer allocate real internal resource. Free pilots get deprioritised the moment something urgent appears. Keep the fee modest and creditable against the first year contract. ### What sales methodology works best for SaaS? MEDDPICC is the most useful for enterprise SaaS because it forces you to name the economic buyer, the decision criteria and the paper process, which are exactly the gaps that stall committee deals. Challenger works well for category-creation products. The methodology matters less than whether the team runs it consistently, since inconsistent application of a good framework produces nothing.