Software Sales On Fire

By Dean PatinoBusiness Management

Software Sales On Fire episodes

October 25One Department Down. How Do You Get Into the Other Six?
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
20 min
October 24Your Prospect Just Announced Big Plans. Where Does Your Solution Fit?
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
22 min
October 24Bonus: What Great Reps Do Differently With Their SE — 43 Years of Sales Engineering With Dave Murphy
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.
36 min
October 23"There's No Budget." Is There a Path Forward?
"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
22 min
October 22What's the Compelling Event?
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
21 min
October 21Couldn't We Just Build This With AI?
"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
22 min
October 20You Scanned 200 Badges. How Many Opportunities Did You Create?
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
21 min
October 19Your Buyers Accept Your LinkedIn Requests. Then Nothing Happens.
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
23 min
October 18Your ROI Looks Amazing. The CFO Doesn't Believe It.
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
25 min
October 17Everyone Likes Your Solution—Except the Person Who Can Kill the Deal.
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
22 min

About Software Sales On Fire

From the publisher's feed

Ignite your pipeline. Smoke your quota. A daily podcast helping enterprise software sales reps find business, win business, and make their number with greater consistency.

Share Software Sales On Fire

Sign up to save your podcasts

Software Sales On Fire

Software Sales On Fire episodes

About Software Sales On Fire