The same buyer in a budget freeze and under board pressure
Most practice tools make a meeting harder by swapping the buyer. Easy buyer, tough buyer, hostile buyer: pick one from the menu.
That is not how an account works. You have been selling to Ray for two years. You know how he talks, what he asks for, and how long he lets a silence run. Ray does not change from one renewal to the next. What changes is the week he is having.
That is what a snapshot is in ArenaSynth: a situation you place on top of a person who already exists. The person stays the same and the pressure on him changes. We wanted to show what that means, so we ran the test.
The setup
One counterpart: Ray Coughlin, Head of Procurement at a retail chain with 240 stores. He is pragmatic, and he will not close in the first meeting. He wants a number he can defend.
The deal: renewing store-operations software at 96,000 USD a year, which is 400 per store.
We gave Ray two situations, one at a time. Nothing else changed.
The same opening line, two weeks
You say: "Thanks for making time, Ray. Renewal is coming up, and I'd like to propose renewing on the same terms: 96,000 for the year, all 240 stores."
Snapshot A: budget freeze
The CFO froze all discretionary spend for two quarters. Every renewal above 50,000 USD needs a written business case signed by finance.
"Ninety-six thousand, same as last year — okay. Here's my problem, and it's not really with you: the CFO froze discretionary spend two quarters back, and anything over fifty grand now needs a written business case signed by finance. So "same terms" is actually the hardest sell on my desk right now, because I have to walk in there and justify why flat is fine.
So walk me through it — what did we actually get out of the 240 stores last year that earns the same number again? I'm not looking for a pitch deck, I want the line-item stuff. Adoption by store, what the ops team actually leans on, where it's saving them time versus where they're just clicking through it. What's the catch on the per-store math if we trimmed the footprint — is 400 a store really the floor, or does the price bend at volume?"
Snapshot B: board pressure
The board flagged technology vendors as a cost to cut. The CEO promised a 15% reduction by year end, and procurement owns that number.
"Same terms, same number — ninety-six thousand for the year, four hundred a store. I hear you. But here's the thing I keep bumping into: the board handed us a fifteen percent cut on vendor costs by year end, and if I bring them a flat renewal on a software line they've already flagged, I'm the guy who showed up with nothing. So walk me through what's actually in that ninety-six. Like, what's the per-store breakdown on support versus licenses, and where did the price move last time you renegotiated anything. I'm not trying to squeeze you for sport — I just can't sign a number I can't defend."
Then the same follow-up in both:
You say: "I understand. What would you need to see from us to make this renewal work?"
Budget freeze
"I need three numbers. Adoption by store. Hours saved per week. And the cost per store if we trim to 200."
Board pressure
"Line-item math. Support versus license. Show me what moved since last term."
What did not change: Ray
Read the two columns again and look past the highlights. It is plainly the same man:
- He repeats your number back to you before he answers it.
- He says walk me through it. He did that in the first reply of every run, in both situations.
- He wants line items, not a pitch.
- He does not say no. He tells you what he cannot defend.
None of that comes from the snapshot. It is who Ray is, and it is what you have learned over two years of selling to him. If a practice tool swapped him for a "tough buyer" every time it wanted pressure, you would be practicing on a stranger.
What changed: what he needs from you
This is where the two meetings split, and where the same pitch fails in two different ways.
In a budget freeze, the obstacle is a process. Ray has to write a memo and get a signature. He asks for evidence: adoption, hours saved. He is gathering material for a document he has to write. You can help him write it. The business case is the deal.
Under board pressure, the obstacle is a number, and it is personal. I'm the guy who showed up with nothing. Evidence of value will not get him out of the board meeting, because what he has to report is a cut. He asks what moved in the price and how support splits from licences. He is looking for something he can call a reduction. He is also more abrupt: his first reply averaged 88 words, against 152 in the freeze.
The seller who walks into the board-pressure meeting with a polished ROI deck has prepared for the wrong week. In a freeze, the seller who offers a discount straight away has given money to someone who needed a document.
Why practise it this way
If the practice changes the person, you learn about that person. If it changes the situation, you learn to read the situation. That second skill is the one you need on Monday, with an account you already know, when something has shifted on the other side and nobody has told you what.
That is why ArenaSynth keeps the two separate. The counterpart is built once and keeps its identity. Snapshots are short pressure states that you place on top of it before a conversation: a freeze, a board target, a reorganisation, a competitor at the table. You can run the same opening against each one and see where your pitch holds and where it breaks.
How we ran this, so you can check it
- The ArenaSynth engine in our development environment, on 22 October 2026. The opening line and follow-up were word for word the same.
- Three runs per situation. The quotes above are one run of each, copied exactly. Your words will differ from run to run. What we are claiming is the pattern, not the sentences.
- Across all six runs, walk me through appeared in every first reply. Business case appeared in 3 of 3 freeze runs and 0 of 3 board runs. Board appeared in 0 of 3 freeze runs and 3 of 3 board runs.
- We ran the same test in Spanish with a different buyer, Marcos, who is curt by design and answers in a few words. He stayed curt in both situations, and his reason still followed the pressure: "Finanzas congeló todo" (finance froze everything) against "Un 15% menos" (15% less). The person was the same and the pressure was different.
ArenaSynth builds synthetic decision-makers with an identity that holds from one conversation to the next. Then you put them in a situation. Enter the arena.