Software Sales On Fire

Tuesday episode on getting buyers to respond: the warmest buyer in your territory may be reachable only through your best partner rep — and "send me more leads" is an ask they can't act on. This episode covers why "more leads" produces nothing (no filter, no cost-benefit, no stated benefit), the three-account homework — a relevant problem, an active initiative, and a person the partner can introduce — the thirty-minute joint discovery session with your systems engineer, and how to name the partner's benefit honestly: customer success, services work, or a complementary sale. Includes the full role play where a partner rep expects a contacts grab and leaves agreeing to walk through three accounts.

In This Episode

• Today's Pipeline Problem — why "send me leads" fails: no filter, no cost-benefit, and a benefit the partner has to guess at
• The Play — What to Say and Do — pick the three accounts, request the short session, name the partner's win — with the Elena-and-Derek role play
• Put AI to Work — the account shortlist, the session ask, and the partner-benefit check
• The Rep Mailbag — the partner who said "sounds good" and went silent, the channel-manager rule, and one partner versus two
• The Inside Edge — the territory multiplier, leading with the partner's win, and why access is the scarcest resource in sales
• Your Move Today — pick your best partner, finish the three-account homework, send the ask

Key Takeaways

• "More leads" gives the partner nothing to act on — three named accounts gives them everything.
• Each account needs three things: a relevant problem, an active initiative, and a person your partner can introduce.
• Bring your SE: the session becomes technical depth for their account planning, not a pitch.
• Name the partner's benefit out loud — customer success, services work, or a complementary sale — before they have to ask.
• Spend the first ten minutes on their book of business. Introductions are earned inside the session.

Do This Today

• Pick your best partner rep and complete the three-account homework — problem, initiative, person.
• Send the ask: thirty minutes, one page per account, your SE joining, no contacts request.
• In the session, open with their book of business and close with one commitment from each side.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-03-ask-your-best-partner-for-three-accounts#downloads

• The Three-Account Partner Ask — The one-pager to bring to your partner session — three accounts, the evidence for each, and the partner-benefit statement that answers the money question. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-03-ask-your-best-partner-for-three-accounts#downloads
• The Joint Discovery Session Planner — The agenda and ground rules for the thirty-minute partner session — including the first ten minutes that are about their book of business. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-03-ask-your-best-partner-for-three-accounts#downloads
• AI Prompts: Partner Account Requests — The three prompts from this episode — the account shortlist, the session ask, and the partner-benefit check. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-03-ask-your-best-partner-for-three-accounts#downloads

Monday pipeline episode: the warmest leads in your territory are already talking to your company — in the support queue. This episode covers the four expansion signals (scale, reporting, integration, additional teams), the one-line test that separates a fix the customer already deserves from a legitimate new use case, the three-term routing agreement to build with customer success, and the handoff that earns the next signal. Includes the full role play where a third reporting ticket reveals a new COO and two new offices — an expansion motion already underway.

In This Episode

• Today's Pipeline Problem — why every signal dies in a closed ticket: incentives, training, and the pounce that closed the channel
• The Play — What to Say and Do — define the four signals, build the routing process, handle the handoff — with the Elena-and-Priya role play
• Put AI to Work — the signal translator, the partner pitch, the opener builder
• The Rep Mailbag — the overloaded support team, the channel burned by a pouncing AE, and telling signal from noise
• The Inside Edge — support as your early-warning system, and why protecting deserved fixes keeps the channel open
• Your Move Today — audit a month of tickets, book the partnership meeting, open with one question

Key Takeaways

• Scale, reporting, integration, additional teams — growth questions are buying signals in costume.
• The test: is the customer describing today being broken, or tomorrow being bigger?
• A fix the customer already deserves never becomes a pitch — protecting that line is what keeps signals flowing.
• Capture must cost under a minute; feedback must come within a day.
• One pounce closes the channel for a year; one thank-you keeps it open forever.

Do This Today

• Pull a month of support tickets on your top five accounts and run the one-line test.
• Book thirty minutes with the support or CS lead — bring the three-term agreement.
• Next signal: open with one genuine question about how the growth is going. Nothing else.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-02-enlist-support-engineers-to-recognize-expansion-signals#downloads

• The Signal Spotter's Guide — The four expansion signals — scale, reporting, integration, additional teams — with the one-line test that separates a support fix from a new use case. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-02-enlist-support-engineers-to-recognize-expansion-signals#downloads
• The Support Partnership One-Pager — The three-term agreement to bring to your support and CS leads — capture mechanism, response commitment, and the line between deserved fixes and new use cases. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-02-enlist-support-engineers-to-recognize-expansion-signals#downloads
• AI Prompts: Expansion Signals — The three prompts from this episode — the signal translator, the partner pitch, and the opener builder. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-02-enlist-support-engineers-to-recognize-expansion-signals#downloads

Sunday number-control episode: the one feature you don't have is swallowing the deal. This episode covers why feature requests are use cases in costume, the four excavation questions (who, how often, what now, what good looks like), the honest alternative audit — including conceding where the competitor is genuinely better — and the decisive call: proportion it, reposition the deal, or walk. Includes the full role play where "no native field-level encryption" shrinks from hard requirement to two fields and a quarterly audit.

In This Episode

• Today's Pipeline Problem — how a bullet point becomes the headline, and why answering the checkbox instead of the use case feeds it
• The Play — What to Say and Do — excavate the use case, audit alternatives honestly, make the decisive call — with the Elena-and-Raj role play
• Put AI to Work — the use-case excavator, the honest alternative auditor, the proportion framer
• The Rep Mailbag — the decisive gap your manager wants kept alive, the fake gap your competitor invented, and the downplayed gap that exploded after go-live
• The Inside Edge — the gap inventory, authoring the scorecard, and the gap conversation as the audition for the relationship
• Your Move Today — excavate your haunted deal, audit it honestly, build the gap inventory

Key Takeaways

• Feature requests are use cases in costume — answer the use case, never the checkbox.
• Who, how often, what happens now, what good looks like: four questions that shrink most elephants.
• Conceding a real gap accurately is what makes the rest of your claims believable.
• Loud gaps get proportioned; decisive gaps get a reposition or a professional walk.
• A disclosed gap is a shared problem; a hidden gap is a delayed betrayal.

Do This Today

• Write the use case underneath the feature gap haunting your live deal.
• Run the honest alternative audit — let the answer, not hope, set your forecast.
• Build your gap inventory with a composed sixty-second response per gap.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-01-the-feature-youre-missing-is-becoming-the-whole-deal#downloads

• The Use Case Excavator — Four questions that convert any feature request into the underlying business problem — plus the golden follow-up that restores proportion. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-01-the-feature-youre-missing-is-becoming-the-whole-deal#downloads
• The Gap Decision Framework — Audit the alternatives honestly — native-adjacent, integration, roadmap, workaround — then decide: proportion it, reposition the deal, or walk. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-01-the-feature-youre-missing-is-becoming-the-whole-deal#downloads
• AI Prompts: The Feature-Gap Deal — The three prompts from this episode — the use-case excavator, the honest alternative auditor, and the proportion framer. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-11-01-the-feature-youre-missing-is-becoming-the-whole-deal#downloads

DealFire catches your deal in flight. Start with today's sticking point — not the entire account history. This special bonus episode walks through five clear steps using an illustrative $85K software opportunity, including Brainstorm and returning to your saved work. DealFire works with the context you supply; it does not automatically read your CRM. Plus a quick look at The Hot Seat and Forecast Defense.

Everything in the Studio is completely free to use today — take full advantage now, as that may change.

Direct Links

• DealFire: https://www.softwaresalesmastery.com/studio/dealfire
• Brainstorm: https://www.softwaresalesmastery.com/studio/brainstorm
• Software Sales Mastery Studio (all four tools): https://www.softwaresalesmastery.com/studio

In This Episode

• Why DealFire Exists — the "what should I do next?" problem and the four moments to use it
• A Real-World Deal You Can Plug In — Maria's $85K deal goes quiet after finance tightens spend; what she types into DealFire and the move she makes
• Brainstorm: What Are You Not Thinking About? — branches, going deeper, and the explore-then-decide workflow
• Your Work Is Saved — Go Back Anytime — deals and conversations saved in your browser on that device
• The Rest of the Studio — The Hot Seat and Forecast Defense
• Your Move Today — five minutes on the deal bothering you most

The Five Steps — What to Do and Why

• Open DealFire and name the deal. Find the conversation again and keep opportunities separate.
• Give today's snapshot and ask, "What should I do next?" Start with the current sticking point and only the facts that matter; add more context if asked.
• Ask one focused follow-up. Turn a direction into an email, question or buyer-verifiable next action without repeating the deal description.
• Explore the same deal in Brainstorm. Keep the deal selected, use its current situation, and choose "Brainstorm this" on a useful branch to investigate overlooked possibilities.
• Choose one action, then return with what changed. Review before sending, take the action, and reopen the saved deal with a short update — no full-history retelling.

Try It Yourself — Paste This Into DealFire

> Eighty-five thousand dollar deal, forecast to close this quarter. My champion is the Director of Sales Ops. The demo went well and he took the proposal to his VP. Now finance is making every team justify new spend, and the CRO floated using an add-on from their existing CRM vendor instead. My champion said he'd get back to me in two weeks. It's been two weeks and he's gone quiet. What should I do next?

Then ask a follow-up, such as "Write the email to my champion that gets a response without sounding desperate." Then open Brainstorm and ask, "What am I not thinking about on this deal?"

Good to Know

• Your DealFire deals and conversations are saved in your browser on that device. Use the same browser to reopen, review and update them; clearing browser data or switching devices won't carry them over.
• Keep sensitive customer details general when you need to, and use your own judgment before anything goes to a buyer.

Get the Free Book

Download 10 Secrets of Software Sales Mastery instantly at https://www.softwaresalesmastery.com

Saturday deal clinic: the buyer already leans to your competitor. The question isn't whether you can win — it's whether the preference can legitimately be changed. This episode covers the four mechanisms that create preferences (experience, relationship, recency, authority), the legitimate-opening test (new, material evidence — not "we're better" or "we're cheaper"), the update-not-attack language that protects the buyer's judgment, and the graceful exit that keeps the account for next time. Includes the full role play where a rep turns "we're pretty far down the road with your competitor" into a fair side-by-side on the one requirement that postdates the preference.

In This Episode

• Today's Deal Clinic — preferences are starting conditions, not verdicts
• The Play — What to Say and Do — diagnose the mechanism, test for the opening, introduce evidence as an update, define the proof point — with the Jordan-and-Priya role play
• Put AI to Work — the mechanism analyst, the legitimate-opening finder, the side-by-side designer
• The Rep Mailbag — the "never walk away" manager, the CIO who publicly champions the competitor, and the flip the buyer regretted
• The Inside Edge — losing competitive deals fast as a weapon, the change file, and competing as a preview of how you'll serve
• Your Move Today — diagnose your live competitive deal, run the opening test honestly, start your change file

Key Takeaways

• Diagnose what created the preference before you spend an hour fighting it — the mechanism decides everything.
• New, material evidence is the only legitimate lever; "cheaper" is a price move and "better" is a claim.
• Frame evidence as an update that protects their earlier judgment — reversal feels like diligence, not defeat.
• Ask what the proof would change before you run the test; their answer is the real qualification.
• When you walk, walk with the relationship intact — the renewal window is your re-entry.
• Flip only what you'd stand behind at go-live.

Do This Today

• Write down the mechanism behind your live competitive deal — or make the diagnostic call.
• Run the legitimate-opening test honestly; design the exit if the answer is "nothing new."
• Start your change file on every competitive loss: mechanism, date, what would change it.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-31-the-buyer-already-prefers-your-competitor-can-you-still-change-their-mind#downloads

• The Preference Diagnostic — Classify what created the buyer's preference — experience, relationship, recency, or authority — and learn the hardness, response, and walk-away trigger for each. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-31-the-buyer-already-prefers-your-competitor-can-you-still-change-their-mind#downloads
• The Legitimate Opening Test — The brutal-honesty checklist for whether new evidence could legitimately change the preference — plus the update-not-attack language. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-31-the-buyer-already-prefers-your-competitor-can-you-still-change-their-mind#downloads
• AI Prompts: The Second-Choice Deal — The three prompts from this episode — the mechanism analyst, the legitimate-opening finder, and the side-by-side designer. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-31-the-buyer-already-prefers-your-competitor-can-you-still-change-their-mind#downloads

Partner reps cover thirty vendors — the ones who get brought into deals are the ones who made it effortless. This episode builds the three assets: a trigger card of 3–5 customer sentences a partner rep can recognize in a live meeting, a forwardable ten-second introduction, and an explicit answer to "what's in it for me" in the partner's real frames. Includes the full coffee-meeting role play, the monthly rhythm that keeps the system alive, and how to repair a dropped referral.

In This Episode

• Today's Pipeline Problem — why partner-sourced deals close faster, and the three things that must happen in real time for a referral to be born
• The Play — What to Say and Do — the trigger list, the ten-second introduction, the partner's win, and the rhythm — with the Alicia-and-Roger role play
• Put AI to Work — the trigger miner, the introduction writer, the partner-value articulator
• The Rep Mailbag — certification vs. the trigger card, how long the rhythm takes, and repairing a dropped referral
• The Inside Edge — partner reps as your sales force, borrowed trust as crown jewels, and giving the first referral
• Your Move Today — write your triggers, send the intro email to three partner reps, say the partner's win out loud to your best one

Key Takeaways

• Referrals die from friction, not relationships — recognition, safety, and partner value must all fire in a live meeting.
• 3–5 triggers in customer words; a list of twelve is a list of zero.
• The partner rep should never compose the intro — write it for them, forwardable in ten seconds.
• The partner's win is usually not commission: unstuck deals, services growth, looking smart, renewal protection.
• Assets without rhythm evaporate: monthly stories, quarterly trigger refreshes, same-day loop closing.
• A referral is borrowed trust — handle it like the partner's credibility, because it is.

Do This Today

• Write your 3–5 triggers; test them against your last five closed deals.
• Send the trigger card and intro email to three partner reps with "Would you actually forward this?"
• Tell your best partner rep their win in one sentence, unprompted.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-30-make-it-easy-for-a-partner-rep-to-bring-you-into-a-deal#downloads

• The Partner Trigger Card — The one-page recognition system: 3–5 customer sentences that mean 'call these people,' each with what it means and what it costs if ignored. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-30-make-it-easy-for-a-partner-rep-to-bring-you-into-a-deal#downloads
• The Forwardable Introduction Templates — Two ready-to-forward intros — the warm handoff and the one-pager pass — plus the partner's-win sentence that makes partner reps want to send them. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-30-make-it-easy-for-a-partner-rep-to-bring-you-into-a-deal#downloads
• AI Prompts: The Partner Kit — The three prompts from this episode — the trigger miner, the introduction writer, and the partner-value articulator. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-30-make-it-easy-for-a-partner-rep-to-bring-you-into-a-deal#downloads

Most QBRs end with applause and no change. This episode turns yours into a working session: build the ask list before the slides (decisions, resources, air cover — each with what, by when, and what it unlocks), run a "What I Need From This Room" closing segment, get a yes, no, or decision date on every item, and lock it all with a sixty-second readback and a same-day written summary. Includes the full role play where a rep closes his QBR with three commitments in ten minutes, and the fortnightly triage that keeps them from drifting.

In This Episode

• Today's Pipeline Problem — half your stalls are internal, and the QBR is the one room that can clear them
• The Play — What to Say and Do — build the asks first, run the closing segment, lock the commitments — with the Devon role play
• Put AI to Work — the ask generator, the ask-pressure test, the commitment memo
• The Rep Mailbag — the twenty-minute QBR with no time for asks, the commitments that went nowhere, and the manager who says executive asks look weak
• The Inside Edge — sell internally with external rigor; bank credibility between QBRs; the commitment habit is leadership training
• Your Move Today — write your three asks now, end your next review with one explicit ask, chase whatever's drifting from the last one

Key Takeaways

• Measure the QBR by what's different Monday, not by how the slides landed.
• Every ask is complete: what, by when, and what it unlocks.
• "A yes, a no, or a decision date" — the unowned maybe is the only bad outcome.
• Convert volunteered help into a dated meeting before the room dissolves.
• Read back the commitments in sixty seconds; send the written summary the same day.
• Treat commitments like pipeline: tracked, dated, followed up.

Do This Today

• Write your three asks — decision, resource, air cover — with what each unlocks.
• End your next review of any kind with one explicit ask and a readback.
• Follow up on one drifting commitment from your last QBR.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-29-finish-your-qbr-with-decisions-owners-and-resources#downloads

• The QBR Ask Planner — Turn your pipeline review into three complete asks — a decision, a resource, and air cover — each with what, by when, and what it unlocks. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-29-finish-your-qbr-with-decisions-owners-and-resources#downloads
• The QBR Commitment Tracker — The same-day summary format plus the fortnightly triage that keeps decisions, owners, and resources from drifting. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-29-finish-your-qbr-with-decisions-owners-and-resources#downloads
• AI Prompts: QBR Commitments — The three prompts from this episode — the ask generator, the ask-pressure test, and the commitment memo. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-29-finish-your-qbr-with-decisions-owners-and-resources#downloads

Your VP wants to leapfrog your champion and call the CFO — and you know it will backfire. This episode covers the three-move challenge: anchor to the shared goal, explain the buyer impact with account facts only you have, and bring a workable alternative with a built-in test. Includes the full role play where a rep talks his VP off the direct-call play without a moment of defiance, the rules for executing faithfully when you're overruled, and the bright line where tactics end and integrity begins.

In This Episode

• Today's Pipeline Problem — the two failure poles: silent compliance and the frontal objection
• The Play — What to Say and Do — the three moves plus the two-branch aftermath, with the full Marcus-and-Laura role play
• Put AI to Work — the challenge rehearsal, the alternative builder, the honest-risk memo
• The Rep Mailbag — the VP whose overruled call backfired, the integrity line, and the new rep afraid of the "not a team player" label
• The Inside Edge — how reps become the people VPs consult, and why the best challengers are the best at being overruled
• Your Move Today — write the three-line challenge for the live deal that worries you

Key Takeaways

• You have information your VP doesn't — the deal needs you to speak up; the framing is buyer intelligence, not objection.
• Anchor to the shared goal first, one-on-one; never challenge in the group review.
• Describe what the buyer will do with account facts — never "that's a bad strategy."
• A warning without an alternative is friction; convert the VP's underlying goal into a safer play with a built-in test.
• Overruled on tactics: execute faithfully, document once, neutrally. Asked to misrepresent: that's the line — never carry fiction.

Do This Today

• Pick the live deal where a senior instinct worries you; write the three-line challenge (goal, buyer impact, alternative).
• If it's live, have the one-on-one conversation this week.
• Set the standard now for how you'll execute the next time you're overruled.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-28-how-to-tell-your-vp-their-deal-strategy-could-backfire#downloads

• The Upward Challenge Planner — The three-move structure — anchor to the shared goal, explain the buyer impact with your account facts, bring the alternative — plus the overruled-aftermath rules. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-28-how-to-tell-your-vp-their-deal-strategy-could-backfire#downloads
• The Executive Alternative Builder — A one-page worksheet for converting your VP's aggressive move into a safer play that achieves the same underlying goal. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-28-how-to-tell-your-vp-their-deal-strategy-could-backfire#downloads
• AI Prompts: Challenging Upward — The three prompts from this episode — the challenge rehearsal, the alternative builder, and the honest-risk memo. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-28-how-to-tell-your-vp-their-deal-strategy-could-backfire#downloads

"Three times pipeline coverage" is an average of averages — and it fails reps whose real win rate, deal size, and cycle don't match the slogan. This episode runs the backward math with your own numbers: quota ÷ real average deal ÷ real win rate = the qualified opportunities that must enter your pipeline, dated against your actual sales cycle. Includes the full role play where a manager turns a rep's "I'm not closing" anxiety into a one-line diagnosis — an entry-volume problem since March — plus the weekly checkpoint that catches a shortfall in week three instead of week eleven.

In This Episode

• Today's Pipeline Problem — why the three-times rule is dangerous, and the imagined numbers that make plans lie
• The Play — What to Say and Do — the five steps: real numbers, backward division, dating against your cycle, the gap plan, the weekly checkpoint — and the role play with Elena and her manager Dana
• Put AI to Work — three prompts: the honest-numbers audit, the coverage calculator, the weekly checkpoint assistant
• The Rep Mailbag — the "embarrassing" real win rate, the manager who mandates 3x coverage, and running the math in November when it's already short
• The Inside Edge — manage entries, not pipeline totals; know your numbers like an athlete; the worksheet as a career instrument
• Your Move Today — find your three real numbers, run the backward division, calendar the weekly checkpoint

Key Takeaways

• You are not an average: your win rate, deal size, and cycle determine your coverage — for many reps it's 5x, not 3x.
• Honest denominators only: no-decisions and ghosted deals count in your win rate.
• Coverage is dated: an opportunity that enters too late for its cycle is next quarter's hope, not this quarter's coverage.
• Every shortfall is one of three problems — entries, win rate, or deal size — and each has a different fix.
• Entries are the leading indicator; pipeline totals are the lagging one that flatters.
• If the math says the territory can't supply the entries, have that conversation in January with the worksheet.

Do This Today

• Pull four quarters; find your real win rate, real average deal, real cycle (round win rate down, cycle up).
• Run quota ÷ average deal ÷ win rate → the entries your year requires, dated against your cycle.
• Put the 15-minute weekly checkpoint on your calendar, repeating.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-27-work-backward-from-quota-to-the-deals-you-actually-need#downloads

• The Backward Coverage Worksheet — The five-step math from quota to the opportunities you actually need — your real win rate, real average deal, real cycle, and the dated coverage plan. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-27-work-backward-from-quota-to-the-deals-you-actually-need#downloads
• The Weekly Checkpoint Card — The 15-minute Friday ritual that turns the quota math from a poster into steering — entries, running win rate, slips. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-27-work-backward-from-quota-to-the-deals-you-actually-need#downloads
• AI Prompts: The Quota Math — The three prompts from this episode — the honest-numbers audit, the coverage calculator, and the weekly checkpoint assistant. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-27-work-backward-from-quota-to-the-deals-you-actually-need#downloads

Most business reviews are usage reports nobody acts on — and they train the customer to see you as a tool with a bill attached. This episode rebuilds the review around three parts: achieved outcomes in the customer's own numbers (with their spoken confirmation), remaining gaps named honestly before the customer names them, and the customer's next priorities — the discovery engine that hands you next year's pipeline. Includes the full role play where an honestly-named gap surfaces a January acquisition and turns into a dated follow-up meeting.

In This Episode

• Today's Pipeline Problem — why the report-card review and the defensive review both kill the account's future
• The Play — What to Say and Do — the three-part architecture, the preparation that makes it possible, and the role play with Karen, the VP of Operations facing site thirteen
• Put AI to Work — three prompts: the outcomes-and-gaps builder, the priorities preparation, the same-day follow-up
• The Rep Mailbag — the executive who delegated the review, the champion who got defensive about a gap, and running this inside a mandatory vendor template
• The Inside Edge — the review as the first meeting of the next deal, the outcome ledger, and honesty as the moat
• Your Move Today — rebuild the original intent, send the one-page agenda, script the gap you already know about

Key Takeaways

• Nobody renews usage — customers renew outcomes. A review that never mentions outcomes is a report.
• Their numbers, not your dashboard — and get the customer to confirm the outcome out loud.
• Name the gap first, diagnose without defending, and separate the outcome from the person who ran the rollout.
• An honestly-diagnosed gap is the opening of the next opportunity's business case.
• The priorities question is the best discovery you'll get all year — listen without pitching.
• Close with a dated follow-up tied to their stated priority: that's pipeline, not a review.

Do This Today

• Pick your most important account — schedule the review if none exists.
• Rebuild the original intent: what they bought to achieve, in their words and numbers.
• Write the gap you've been hoping nobody raises, and script naming it with its cause and plan.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-26-the-customer-review-that-opens-the-next-opportunity#downloads

• The Outcome Review Agenda Template — The one-page agenda that gets executives in the room — achieved outcomes, remaining gaps, and the customer's next priorities, in that order. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-26-the-customer-review-that-opens-the-next-opportunity#downloads
• The Outcome Ledger — The running record that makes every review write itself — what the customer bought to achieve, updated at every touch. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-26-the-customer-review-that-opens-the-next-opportunity#downloads
• AI Prompts: The Customer Review — The three prompts from this episode — the outcomes-and-gaps builder, the priorities preparation, and the same-day follow-up. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-26-the-customer-review-that-opens-the-next-opportunity#downloads

Your best prospect is the company that already bought from you — yet most installed bases are one-department islands, because expansion is the part of the job nobody's process covers. This episode turns a successful deployment into a deliberate expansion strategy: make the first success undeniable, map the other departments before you ask for one, make the ask small and safe for your champion, and build a separate business case for each department — their problem, their numbers, their words, with your first win as evidence, not the headline. Includes the full role play where the ask actually lands, and the honest line between real expansion and wishful multiplication.

In This Episode

• Today's Pipeline Problem — why expansion stalls: the vague ask, the copied case, and the land-and-forget
• The Play — What to Say and Do — the four moves, and the role play with Victor, the operations director whose champion-introduction opens the door Dana already knocked on
• Put AI to Work — three prompts: the expansion map, the department-specific business case, the three-line forwardable intro
• The Rep Mailbag — the champion who offers five introductions, the slow customer-success gatekeeper, and expanding at eight weeks
• The Inside Edge — treat the second department as a new customer who shares a building, build the bridge before you need it, protect the champion's capital
• Your Move Today — the proof paragraph, the expansion map, and the small ask, this week

Key Takeaways

• Success in one department is evidence, not momentum — expansion is a series of new first-class campaigns.
• Expansion built on "it's going pretty well" collapses; expand on verified results in the customer's numbers.
• Never ask "who else should I talk to?" — name one person, one reason, and make the champion's risk one email.
• Each department gets its own business case: their problem, their metrics, their owner. Your first win is evidence inside it, never the headline.
• "I don't think this is a fit for your team right now" is the sentence that makes your next case believable.
• The best introductions answer questions the second department is already asking — your champion knows where they live.

Do This Today

• Write the proof paragraph for your strongest deployment — their numbers, quotable.
• Sketch the expansion map: six departments, their version of the problem, their leader, honest fit rating.
• Prepare the small ask for the single best-fit department and have that conversation with your champion this week.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-25-one-department-down-how-do-you-get-into-the-other-six#downloads

• The Expansion Map Template — Map the departments beyond your first win — each one's version of the problem, the leader who owns it, the entry point, and the honest fit rating. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-25-one-department-down-how-do-you-get-into-the-other-six#downloads
• The Department Business Case Builder — Rebuild the case for each new department from their point of view — and the checklist that keeps you from sending the copied case. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-25-one-department-down-how-do-you-get-into-the-other-six#downloads
• AI Prompts: The Expansion Strategy — The three prompts from this episode — the expansion map, the department-specific business case, and the three-line forwardable introduction. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-25-one-department-down-how-do-you-get-into-the-other-six#downloads

When your prospect announces an acquisition, expansion, or new leadership, every rep in your territory sends the same congratulatory email. This episode is the alternative: read announcements as commitments, not news. Learn the five-step process — read past the press release, translate the announcement into operational strain, name who owns it, test the fit honestly with a single sentence, and enter with a point of view instead of a pitch. Includes the full role play with a VP of Revenue Operations six weeks into a painful acquisition, and the honest verdict on when to pursue and when to file it under watch.

In This Episode

• Today's Pipeline Problem — why two hundred identical "congratulations!" emails get deleted, and what an announcement actually contains if you know how to read it
• The Play — What to Say and Do — the five steps from headline to entry strategy, and the role play with Karen, the VP of RevOps inheriting two pipelines that don't agree
• Put AI to Work — three prompts: the announcement deep-read, the fit test that argues against you, and the outreach draft
• The Rep Mailbag — beating competitors who "got there first," the new CRO who knows your product, and leadership demanding same-day outreach on everything
• The Inside Edge — every public commitment creates private pressure, the watch file, and why the best entries don't feel like sales
• Your Move Today — ninety minutes on one announcement: source reading, three strains, one named owner, the fit sentence

Key Takeaways

• The announcement is never the story — the strain it creates is the story.
• Read the source material, not the press release; leadership's exact phrases become your outreach vocabulary.
• The person who owns the strain is rarely the person named in the announcement — and rarely talking to your competitors.
• Write the fit sentence before any outreach: if it stretches, watch instead of pursuing.
• Enter with a point of view about their problem — no flattery, no features, no demo offer.
• Every public commitment creates private pressure; find the person carrying it and be useful early.

Do This Today

• Pick one announcement from the last 60 days in your territory.
• Read the source, list three strains, name the owner of the most urgent one.
• Write the fit sentence — pursue if it holds, watch-file it if it doesn't.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-24-your-prospect-just-announced-big-plans#downloads

• The Announcement-to-Entry Playbook — The five-step process that turns earnings commentary, acquisitions, expansion, and leadership changes into a specific account-entry strategy — from source reading to the point-of-view outreach. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-24-your-prospect-just-announced-big-plans#downloads
• The Fit Test Worksheet — The one-sentence fit case, the skeptic's counter-argument, and the watch-file format for announcements that aren't your opening yet. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-24-your-prospect-just-announced-big-plans#downloads
• AI Prompts: The Account-Entry Strategy — The three prompts from this episode — the announcement deep-read, the fit test that argues against you, and the point-of-view outreach draft. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-24-your-prospect-just-announced-big-plans#downloads

Bonus interview. Dave Murphy has spent 43 years in software — most of it leading sales engineering teams, plus professional services, marketing, product management, and customer success. He is currently at Harness, and early in my career I had the privilege of working for him as a sales engineer. In this bonus episode, Dave breaks down the rep-and-SE partnership from the SE side of the table: what great reps do differently, how much preparation a customer-specific demo really needs, the ways reps lose a technical buyer's trust, how to build a rhythm that holds across every deal, and the superpower he says most SEs never fully use.

In this episode

• Why credibility, not feature count, decides deals where the products are close
• The four ways reps lose a technical buyer: wrong competitor claims, guessed answers, unrealistic timelines, and technical talk with no business benefit attached
• What "prepare together" actually means — and why your SE should critique your part of the meeting too
• The worst thing a rep can do during a demo, and how to plan your interruptions instead
• Consistency, avoiding surprises between teammates, and letting your SE work with technical contacts independently as a force multiplier
• The most memorable deal: beating the Gartner leader as the underdog by tying fewer features to what actually mattered
• Attitude as the SE superpower — enthusiasm and conviction — and the hobby videotape exercise that exposes the gap
• Lightning round: prepping your SE, the one technical answer every rep should have (how pricing works), and sales acumen as the hidden skill of every great SE
• Dave's favorite career moment: being told to fire two people on day one, and what he did instead

Free Downloads

All three are free, no signup, on the episode page: https://www.softwaresalesmastery.com/episodes/2026-10-24-bonus-dave-murphy-what-great-reps-do-differently-with-their-se

• The Rep and SE Preparation Guide — https://www.softwaresalesmastery.com/episodes/2026-10-24-bonus-dave-murphy-what-great-reps-do-differently-with-their-se
• The Technical Buyer Credibility Checklist — https://www.softwaresalesmastery.com/episodes/2026-10-24-bonus-dave-murphy-what-great-reps-do-differently-with-their-se
• AI Prompts for Demo Prep and Technical Credibility — https://www.softwaresalesmastery.com/episodes/2026-10-24-bonus-dave-murphy-what-great-reps-do-differently-with-their-se

Scroll to the "Free downloads" section on that page and they open right there.

Connect with Dave

Dave Murphy is on LinkedIn — that's the network he uses. He's currently at Harness.

Get the book

*10 Secrets of Software Sales Mastery*, loaded with proven ways to generate more pipeline and win deals over the competition, at softwaresalesmastery.com.

"There's no budget" ends more deals than any competitor — but it's a status report, not a wall. Budget is allocated to problems in proportion to the case made for them, which means "no budget" is shorthand for one of four situations: genuinely unavailable funding, low priority, unclear ownership, or a business case that hasn't earned investment. This episode gives you the diagnostic question that reveals which one you're facing, the path forward for each, and the full role play where a champion's "my VP said no budget this year" turns out to mean something entirely different.

In This Episode

• Today's Pipeline Problem — why budget is allocated, not found, and the four situations hiding behind the same two words
• The Play — What to Say and Do — the diagnostic question, all four paths with exact language, why discounts never answer a budget objection, and the role play with Lauren
• Put AI to Work — three prompts: the diagnosis, the priority mapping, and the CFO stress test
• The Rep Mailbag — the seven-month fiscal-year wait, the discount that didn't move the deal, and the problem nobody's budget owns
• The Inside Edge — budget is a snapshot of last year's priorities, the deal lives one floor above where it died, and the power of saying "this isn't the right time"
• Your Move Today — re-diagnose every deal you've filed under "no budget"

Key Takeaways

• "No budget" is a diagnosis, not a verdict — find out which of the four situations you're actually in.
• The opening question: "Is the money not there this year, or has nothing made the case for it yet?"
• Low priority means reconnecting the problem to a funded priority — never arguing your product up the list.
• Unclear ownership means your job shifts from selling to organizing — the purchase needs a home before it needs a price.
• A discount never answers a budget objection — if a lower price doesn't move it, belief was the blocker.
• The honest "this isn't the right time" is the fastest credibility builder in sales.

Do This Today

• List every deal you've filed under "no budget."
• Write which of the four situations each one is — and what evidence you actually have.
• Book the diagnostic call for any deal you never truly diagnosed.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-23-theres-no-budget-is-there-a-path-forward#downloads

• The No-Budget Diagnostic — Tell the four kinds of 'no budget' apart — unavailable funding, low priority, unclear ownership, unearned business case — with the confirming evidence and the path forward for each. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-23-theres-no-budget-is-there-a-path-forward#downloads
• The Priority Connection Worksheet — Reconnect a low-priority problem to something already funded — the mapping exercise that revives 'no budget' deals. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-23-theres-no-budget-is-there-a-path-forward#downloads
• AI Prompts: The No-Budget Diagnosis — The three prompts from this episode — the four-situation diagnosis, the priority mapping, and the CFO stress test for your business case. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-23-theres-no-budget-is-there-a-path-forward#downloads

Most stalled deals were never attached to anything with a date on it. A compelling event is not a pain point — it's a consequence with a deadline: what happens to the customer's business if they do nothing, and when that consequence arrives. This episode resets discovery around the four questions that surface it: the current process, the consequences in three layers, the priority against everything else, and the personal motivation to act. Includes the full role play re-running discovery on a sixty-day stalled deal, and the one-sentence pulse test for every deal in your pipeline.

In This Episode

• Today's Pipeline Problem — why "they really liked it" isn't a reason to act, and how requirements-gathering masquerades as discovery
• The Play — What to Say and Do — the four-question reset with exact wording, and the role play with Michelle, whose renewal spreadsheet just became a compelling event
• Put AI to Work — three prompts: the pipeline audit, the consequence-interview rehearsal, and the sanity check before you commit
• The Rep Mailbag — urgency around an old, tolerated pain; the compelling event only the champion knows about; and the manager demanding CRM compelling events
• The Inside Edge — the best forecasters are the best disqualifiers, the one-sentence habit, and why compelling events decay
• Your Move Today — write the sentence for your three biggest deals, and fix the close dates on any deal that doesn't have one

Key Takeaways

• A compelling event is a consequence with a date — pain points don't close deals, deadlines do.
• "What happens if nothing changes?" is the most important sentence in discovery. Ask it and be quiet.
• A consequence without priority is a nice-to-have with good numbers — test it against the budget conversation.
• A compelling event only the champion knows about is a hypothesis — help them socialize it upward.
• You can't create urgency; you can only uncover it. Pain plus change is what converts an ache into an event.
• The one-sentence test: what happens if they do nothing, and when? No sentence, no commit.

Do This Today

• Write the one-sentence compelling event — in the customer's words — for your three biggest deals.
• For any deal without one, write the exact consequence question for the next call.
• Move out the close date (or move down the category) on every deal that fails the test.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-22-whats-the-compelling-event#downloads

• The Compelling Event Discovery Guide — The four-question reset — current process, consequences, priority, and motivation — with exact wording for each and the one-sentence pulse test for every deal. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-22-whats-the-compelling-event#downloads
• The Consequence Question Bank — Twenty-five field-tested questions for surfacing the cost of the status quo — organized by process, cost, future consequence, priority, and personal motivation. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-22-whats-the-compelling-event#downloads
• AI Prompts: The Compelling Event — The three prompts from this episode — the pipeline audit, the consequence-interview rehearsal, and the sanity check to run before you commit a deal. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-22-whats-the-compelling-event#downloads

"Couldn't we just build this with AI?" is no longer a brush-off — a good engineer really can prototype your core workflow in weeks, and the rep who dismisses the question loses the room. This episode runs the balanced build-versus-buy discussion: welcome the question out loud, then guide the comparison across six dimensions — delivery, ownership, integration, maintenance, security, and ongoing cost — with questions that make the buyer supply the numbers. Includes the full role play with a CTO whose team already built sixty percent, and the judgment call for when building is genuinely the right answer.

In This Episode

• Today's Pipeline Problem — why the question is legitimate now, what the weekend prototype leaves out, and why it's a buying signal, not a brush-off
• The Play — What to Say and Do — welcome the question, the six dimensions with language for each, when to recommend building, and the role play with Daniel the CTO
• Put AI to Work — three prompts: the total-cost framework, the skeptical-CTO rehearsal, and the honest-fit check that argues both sides
• The Rep Mailbag — re-engaging the buyer whose internal build stalled, the CFO floating "build with AI" as a tactic, and being honest when your product can be approximated
• The Inside Edge — curiosity over fear, the two-season game with companies that build, and owning the comparison instead of defending the product
• Your Move Today — write six dimension questions for your two most active evaluations

Key Takeaways

• The build question is legitimate now — treat it as a smokescreen and the room reads your defensiveness as weakness.
• Welcome the question out loud; confidence earns you the right to shape the comparison.
• The prototype is the visible five percent. Delivery, ownership, integrations, maintenance, security review, and ongoing cost are the rest.
• Ask questions so the buyer supplies the estimates — a cost they name is a fact; a cost you name is a sales tactic.
• When building is genuinely right, say so. The credibility pays for years.
• Never call a bluff and never say "told you so" to a returning builder — grace is a two-season strategy.

Do This Today

• Identify whether the build option is live in your two most active evaluations.
• Write one question per dimension — delivery, ownership, integration, maintenance, security, cost — phrased so the buyer supplies the estimate.
• Practice the opener out loud: curious, not prosecutorial.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-21-couldnt-we-just-build-this-with-ai#downloads

• The Build-Versus-Buy Discussion Guide — The six-dimension framework for guiding an honest build-versus-buy comparison — with the opening move that earns you the right to lead it and the question for each dimension. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-21-couldnt-we-just-build-this-with-ai#downloads
• The Total Cost of Ownership Worksheet — Price the build option honestly — the weekend prototype versus the three-year commitment — with every cost category buyers typically omit. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-21-couldnt-we-just-build-this-with-ai#downloads
• AI Prompts: The Build-Versus-Buy Discussion — The three prompts from this episode — the total-cost framework, the skeptical-CTO rehearsal, and the honest-fit check that argues both sides. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-21-couldnt-we-just-build-this-with-ai#downloads

Your team came home with two hundred badge scans, the scanner vendor called it a great show, and three weeks later the event produced zero opportunities — because a badge scan is a contact record, not a conversation. This episode rebuilds the event around three numbers: substantive conversations, qualified conversations, and confirmed next steps with dates. You'll get the booth conversation that sorts the floor in one question, the booking ask that closes while they're standing there, the same-night follow-up motion, and the full role play where a raffle-chasing director turns into a Friday meeting.

In This Episode

• Today's Pipeline Problem — what a scan actually is, why the big count prevents the behaviors that produce results, and the three numbers that replace it
• The Play — What to Say and Do — set goals the scanner can't measure, the sorting question, booking the next step on the spot, and following up from the hotel; plus the role play with Frank at the raffle
• Put AI to Work — three prompts: pre-show target prep, the same-night follow-up drafter, and the skeptical post-event read
• The Rep Mailbag — the VP who measures cost per scan, running a different game inside marketing's booth script, and five of eight booked follow-ups going dark
• The Inside Edge — the two-week sprint mindset, pre-booking before the plane leaves, and why a real next step must cost the other person something
• Your Move Today — sort your last event's list into three honest piles and reach out to one real conversation today

Key Takeaways

• A badge scan tells you a name, title, and email — all buyable for thirty cents — and nothing about problem, authority, or reason to act. The list looks like pipeline; it's a mailing list.
• Measure events in three numbers: substantive conversations, qualified conversations, and confirmed next steps with dates.
• A real next step costs the other person something — a booked meeting, a scheduled demo, a promised introduction. "I'll send you information" is a scan with extra steps.
• Book it on the spot while they have their calendar in their pocket; "just send me information" is an answer — accept it and don't count it.
• Follow up the same night, individually, referencing the conversation. By Monday you're a vendor again.
• Two hundred scans and four next steps is a bad event; sixty scans and fifteen next steps is a great one.

Do This Today

• Sort your last event's list into three piles: real conversations, scans you never spoke to, and confirmed next steps.
• Look at the third pile — that's the gap between what the event looked like and what it produced.
• Reach out to one real conversation from pile one today, with specifics and one small specific ask.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-20-you-scanned-200-badges-how-many-opportunities-did-you-create#downloads

• The Event Goals Planner — Set the three numbers that matter before the show — substantive conversations, qualified conversations, and confirmed next steps — with per-rep daily targets and the pre-booking checklist. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-20-you-scanned-200-badges-how-many-opportunities-did-you-create#downloads
• The Same-Night Follow-Up Playbook — The follow-up motion that starts while the booth is still standing — the three-sentence email, the LinkedIn multiplier, and the timing window that keeps conversations alive. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-20-you-scanned-200-badges-how-many-opportunities-did-you-create#downloads
• AI Prompts: Event to Pipeline — The three prompts from this episode — pre-show target prep that won't invent priorities, the same-night follow-up drafter, and the skeptical post-event read. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-20-you-scanned-200-badges-how-many-opportunities-did-you-create#downloads

Twenty-six acceptances, zero conversations. An accepted connection request is the lowest-cost yes in professional life — one tap, no commitment, often no memory of it — and both common next moves fail: the immediate pitch confirms exactly what the buyer suspected, and silence turns a person into inventory. This episode builds the four-step progression from connection to real conversation, with the language for each step, the honest read on response rates, and the full room where an IT director calls out the approach to his face.

In This Episode

• Today's Pipeline Problem — what an acceptance actually means, the two failure modes, and why a connection is permission to be visible rather than a lead
• The Play — What to Say and Do — the honest connection note, visible relevance and its strict usefulness test, the question worth answering with no ask attached, and an invitation small enough to accept; plus the role play where Roger challenges the whole method
• Put AI to Work — three prompts: the relevance read that refuses to speculate, the question test, and post ideas you write yourself
• The Rep Mailbag — the manager who measures acceptances, what to do with three thousand old connections, and whether this works if you don't post
• The Inside Edge — fewer requests, a target list small enough to be real, and a two-year time horizon that compounds
• Your Move Today — count your two-way exchanges from the last ninety days, then pick five connections and write one real question each

Key Takeaways

• Accepting a request costs one second and means only that you weren't a risk to someone's feed. Treating it as interest is the most expensive misread in social selling.
• The immediate pitch spends your one first impression on someone who has told you nothing; silence turns connections into inventory you'll never use.
• Relevance must be visible before any ask. The test: would someone who will never buy from you still find this worth reading?
• A question worth answering is about their world, answerable in two sentences, useful to you either way, and sent with no meeting request attached.
• One follow-up at most, weeks later, with a genuine reason — then stay visible and stop messaging. A cadence turns a neutral connection into a permanent no.
• A two-way exchange is a real win and is not a meeting. Nothing in your forecast moves because someone replied.

Do This Today

• Sort your connections by recent and count how many of the last ninety days' acceptances produced an actual two-way exchange.
• Pick five connections at accounts you genuinely want — only five.
• For each, write one thing you know from their own words and one question you'd actually like answered, with no ask attached. Send one today.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-19-your-buyers-accept-your-linkedin-requests-then-nothing-happens#downloads

• The Connection-to-Conversation Progression — The four steps from accepted request to real exchange — the honest connection note, visible relevance, the question with no ask attached, and an invitation small enough to accept. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-19-your-buyers-accept-your-linkedin-requests-then-nothing-happens#downloads
• The Question Worth Answering Worksheet — Turn the question you were about to send into one a busy buyer will actually answer — with the qualification-attempt test and worked examples. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-19-your-buyers-accept-your-linkedin-requests-then-nothing-happens#downloads
• AI Prompts: From Connection to Conversation — The three prompts from this episode — the relevance read that refuses to speculate, the question test, and useful-post ideas you write yourself. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-19-your-buyers-accept-your-linkedin-requests-then-nothing-happens#downloads

Your business case says three-point-two million. The champion loved it, finance went quiet, and the feedback came back as "the numbers seem aggressive." That is not an argument about math — it's a statement that the number isn't auditable. This episode takes a blended ROI total apart into cash savings, capacity gains, risk estimates, and revenue assumptions, labels each one honestly, and puts a named owner inside the customer's business behind every figure — including the full room where a CFO pushes back and the one-point-nine-million-dollar claim gets withdrawn on purpose.

In This Episode

• Today's Pipeline Problem — why "the numbers seem aggressive" means unauditable, and why a blended total asks the CFO to do your work
• The Play — What to Say and Do — the four categories and their honesty tests, the three labels, assigning internal validation owners, building the narrow version that survives finance, and holding the line when someone wants the number bigger; plus the full role play with Sarah, a CFO
• Put AI to Work — three prompts: the four-category separator, the label pass that surfaces untraceable figures, and the validation plan
• The Rep Mailbag — correcting your own champion's optimistic ROI, using marketing's case-study percentages, and the manager who wants risk and revenue added to justify the deal size
• The Inside Edge — collect the customer's figures from the first conversations, validate before finance sees it, and build a case your champion can't lose with
• Your Move Today — four columns plus a names column, and the percentage of your total that a CFO will discount

Key Takeaways

• Cash savings, capacity gains, risk reduction, and revenue assumptions are four different kinds of claim. Blended into one total, a CFO can't tell which parts to trust — so she discounts all of it.
• Capacity is hours, not dollars, unless an operational decision is attached: absorbing growth without hiring, eliminating overtime or contractors, or redeploying to stated work.
• Describe risk exposure in the customer's words and let them price it. Never multiply an invented cost by an invented probability.
• Keep revenue upside outside the total — it depends on the customer's execution, not yours. A case that stands without it is far stronger.
• Labeling weak figures as weak is what makes the rest believable. Every figure in the total needs a named owner inside the customer's organization who confirmed it.
• A defensible eleven-month payback gets funded. An indefensible two-month payback gets questioned and shelved.

Do This Today

• Sort every benefit line in your biggest live business case into cash, capacity, risk, or revenue.
• Add a column for the name and title of the customer-side person who confirmed each figure — leave it empty if the source is you, a benchmark, or a calculator.
• Every empty cell either gets an owner this week or comes out of the number.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-18-your-roi-looks-amazing-the-cfo-doesnt-believe-it#downloads

• The Four-Category Business Case Worksheet — Take your blended benefit total apart into cash savings, capacity gains, risk reduction, and revenue assumptions — with the honesty tests for each one. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-18-your-roi-looks-amazing-the-cfo-doesnt-believe-it#downloads
• The Validation Owner Planner — Who inside the customer's business validates each figure, the two-minute question to ask them, and the names column that turns a vendor document into a business case. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-18-your-roi-looks-amazing-the-cfo-doesnt-believe-it#downloads
• AI Prompts: Making an ROI Case Defensible — The three prompts from this episode — the four-category separator, the label pass that finds untraceable figures, and the validation plan. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-18-your-roi-looks-amazing-the-cfo-doesnt-believe-it#downloads

It's Saturday's deal clinic. The committee loves your solution, your champion advocates in every meeting, the demo went great — and the deal is dying anyway, because one person you may never have met can end it. This episode works the stalled deal end to end: finding the veto player before they use their power, getting the real objection instead of the twice-relayed rumor, naming the personal and operational stakes behind it, and running a direct resolution plan — including the full room where the security director finally says what "concerns" actually meant.

In This Episode

• Today's Pipeline Problem — why deals with universal support die, the two translations that destroy the objection before it reaches you, and the three things to identify: objection, influence, stakes
• The Play — What to Say and Do — find the veto player before you need them, get the objection from the source, understand the stakes, run the direct plan with a deadline; plus the full deal-clinic role play where Grant the security director states the real objection and correctly reserves his no
• Put AI to Work — three prompts: the power map from your deal notes, the objection decoder, and the resolution plan that names its own limits
• The Rep Mailbag — the veto player who won't meet, the blocker rooted in old history, and whether going over the blocker's head is ever right
• The Inside Edge — the strongest sellers meet the veto player early, and treat the veto as the most honest signal in the deal
• Your Move Today — name the veto player on your most confident deal, and set your own two-to-three-week clock

Key Takeaways

• "Everyone likes your solution" and "everyone can say yes" are different sentences — there is nearly always someone with formal authority or informal kill power, and in many stalled deals they've never been in a meeting with the rep.
• The relayed objection has been translated at least twice; nobody relaying bad news wants to be the one who got it wrong. Get it from the source or send written, specific questions the veto player can answer in two minutes.
• The veto is almost never about the product. Identify the stakes — personal, operational, political — and what they emphasize is what they're protecting.
• Go to the veto player with permission, never around them. Match evidence to the objection in the smallest credible form: a two-hour architecture review, not a whitepaper.
• A commitment to examine is not support. The forecast says stalled until the objection is resolved — and if every direct channel is closed, that closure is the answer: a deal you're not allowed to work is a deal to walk from.

Do This Today

• Take your most confident stalled deal and write down the veto player's name — ask your champion: "After everyone else says yes, who could still stop this?"
• Write down the real objection from the source, and the personal or operational stakes behind it.
• Set your own clock: two to three weeks for the real objection or real engagement — or the deal comes off the forecast honestly.

Free Downloads

Everything below is free — no signup. Get it on this episode page: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-17-everyone-likes-your-solution-except-the-person-who-can-kill-the-deal#downloads

• The Veto Player Map — Find the person who can kill your deal before they use it — formal authority, informal influence, real vs. relayed objection, and the two-to-three-week clock. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-17-everyone-likes-your-solution-except-the-person-who-can-kill-the-deal#downloads
• The Objection Decoder Worksheet — Take the vague, twice-relayed objection that reached you and work out the direct questions that will find the real one at the source. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-17-everyone-likes-your-solution-except-the-person-who-can-kill-the-deal#downloads
• AI Prompts: Finding and Resolving the Veto Player — The three prompts from this episode — the power map, the objection decoder, and the resolution plan that names its own limits. · Download: https://www.softwaresalesmastery.com/podcast/episodes/2026-10-17-everyone-likes-your-solution-except-the-person-who-can-kill-the-deal#downloads