Ten AI prompt templates that run a working sales cycle — who you reliably win, what is actually happening at the account, the sequence that earns a reply, the questions that find the cost of doing nothing, and the plan that closes it. Below, watch one deal travel all ten.
The scenario
Meridian Freight Systems sells warehouse and supply-chain software to mid-market distributors. $18M in recurring revenue, $110K average deal, five months from first call to signature. Replies to outbound have fallen from 9% to 3%, and 58% of qualified deals now end in no decision rather than a loss to a competitor — which means the pipeline is full and the quarter is short. Here is how the ten prompts take that from a volume problem to one closed deal at Brightwater Distribution.
The buyer does not choose a rival. They choose to keep doing what they do now, which costs them nothing this quarter.
The deal rests on one contact. When that person changes role, the deal does not slow down — it disappears.
Open pipeline divided by the target. Comfortable, and the easiest number in sales to inflate.
The journey
Ten prompts, in order. Each one’s output becomes the next one’s input, building a single running Deal Brief.
Defines who is worth a rep’s time, and says out loud who is not.
“Everyone in distribution with more than fifty trucks.”
“Three of your last six wins share a condition your targeting ignores.”
An ideal customer profile is the set of conditions under which you reliably win — not a description of the companies you would like to sell to. Size and industry are what Meridian screens on today, and both are equally true of the deals it loses.
The prompt refuses to build a profile from open deals — only closed outcomes count — and it states the sample size it had to work with.
Turns public material into one reason to call, or a decision not to.
“Brightwater Distribution, six sites. Here is their annual report and their job ads.”
“Their support contract ended in March. The new VP started the same month.”
Every line is graded Sourced, Inference or Unverified, and Sourced means named and dated. A brief that is mostly Inference has not been researched, and the grading makes that impossible to hide behind formatting.
Had no trigger been present, the brief would have said so and recommended leaving the account alone until one appeared. No invented quotes, no “I saw your post” unless the post was pasted in.
Builds five touches on one verifiable fact, then runs the delete test on every line.
“Write me a sequence for Brightwater. Our reply rate is 3%.”
“Under ninety words, one ask, subject line of four.”
The delete test is the method: name the exact sentence that would make a busy person delete the email, then rewrite that sentence and show both versions.
If the only honest hook is weak, the prompt says the account is not ready and names the trigger to wait for — which is a cheaper outcome than five touches nobody answers.
Builds the questions that make the buyer do the arithmetic out loud.
“Thirty minutes with the VP and the Director of Ops on Thursday.”
“Eleven late shipments a month, $4,200 each. They said the number.”
Cost of inaction is what the current situation costs per year if nothing changes, and it only works when the buyer produces the number. A figure the seller supplies is a figure procurement argues with.
The prompt also lists what not to ask: the leading questions and the pain-prodding that reads as manipulation to a senior buyer.
Classifies the objection before answering it, and concedes what is true.
“It is more than we budgeted, and we just spent on the upgrade.”
“That is not a price objection. It is a budget-owner objection.”
An objection is a real constraint, a missing piece of information, or a proxy for something the buyer has not said — and the response depends entirely on which. Most sales training skips that step and goes straight to a rebuttal, which is why most rebuttals make the deal worse.
No rebuttal scripts and no manufactured scarcity. Where the objection is a genuine disqualifier, the prompt recommends withdrawing and names what would have to change.
One card a rep can read in thirty seconds, honest about where the rival wins.
“We are against Tallgrass, and against doing nothing.”
“Tallgrass wins on integration. Say so, then move the ground.”
A battlecard is used live, thirty seconds before a call, by someone who is nervous — so the moment reality contradicts it, the rep stops trusting the whole card.
Nothing goes on the card that Meridian could not show the buyer the source for. Claims without proof are listed separately as [NEEDS PROOF] rather than quietly used.
Writes the page that survives being forwarded to people who were not in the room.
“Proposal by Friday. Procurement reads it, not the VP.”
“$128K against $554K they are already paying in penalties.”
A conservative case models the result when things go worse than planned, and it is the only case a finance reader trusts. Meridian’s old proposals led with the best case and were read as marketing.
If the business case does not hold at conservative assumptions, the prompt says so before the proposal is sent rather than after it is rejected.
Diagnoses the silence, then writes touches that each carry something new.
“Twenty-three days since the proposal. Dana has gone quiet.”
“Four causes, ranked. The top one is not the one the rep assumed.”
Follow-up either carries information the buyer did not have, or it trains them to stop opening your email. Losing to a competitor, losing to no decision and losing to a reorganisation need three different responses, so the diagnosis comes before the writing.
No invented deadlines and no discount expiring on a date Meridian would ignore. Where the read is that the deal is dead, the recommendation is to close it and record why.
Forces every open deal to prove it is real, then re-cuts the forecast on what survives.
“$6.2M of pipeline against a $1.4M quarter. We are covered.”
“$4.1M of it has no second contact and no scheduled next step.”
Pipeline coverage is open pipeline divided by target, and it is the most comfortable number in sales because it is the easiest to inflate. The inspection asks one question of every deal — what evidence exists outside the rep’s optimism — and re-cuts the total on the answers.
The prompt does not invent probabilities to make the arithmetic work, and it names the fields missing from the export that limited the analysis.
Works backwards from the buyer’s date and puts both sides on one schedule.
“They need it live before peak season. November 1.”
“Security review is the critical path. It starts this week or the date moves.”
A mutual action plan is one schedule both sides agree to, worked backwards from the buyer’s own date, with an owner against every step including theirs.
No manufactured deadlines. If Brightwater needs more time for a legitimate reason, the plan reworks the dates around it and states what the delay costs them.
All 10 prompt templates with full copy-paste text and worked examples — a downloadable PDF plus a plain-text copy file. Lifetime updates.
Instant download · lifetime updates
The nine prompts above produce the thinking — who to work, what is happening there, what it costs them to do nothing, and which deals are real. The tenth turns it into three documents that go to the buyer. All three below came out of the Brightwater Deal Brief.
| Step | Owner | Date | Depends on |
|---|---|---|---|
| Security questionnaire returned | Meridian | 22 Sep | Brightwater IT sends the form |
| Reference call with a peer distributor | Meridian | 26 Sep | Customer consent confirmed |
| Security review complete | Brightwater IT | 10 Oct | Questionnaire |
| Business case into the budget meeting | Dana, Dir. Operations | 3 Oct | Final pricing |
| Budget approval | VP Supply Chain | 6 Oct | Business case |
| Legal review and redlines | Both | 17 Oct | Approval |
| Signature | VP Supply Chain | 24 Oct | Legal |
| Implementation kickoff | Both | 28 Oct | Signature |
| Live ahead of peak season | Brightwater | 1 Nov | Kickoff |
Six distribution centres report separately. Month-end consolidation takes four days. Eleven shipments a month miss the contractual window with your largest retail customer.
$554,400 a year in service-level penalties, from your own contract terms and your own shipment count.
Multi-site inventory and exception reporting across all six sites, live before peak season, with the existing ERP left in place.
Peak season adds volume to the same process. The penalty exposure rises; the four-day close does not shorten.
We are paying roughly $554K a year in service-level penalties on the retail contract. Eleven shipments a month miss the window, and the cause is that the six sites do not see each other’s stock until the month-end close, four days later.
I am asking for $128K to fix it before peak season. On a conservative estimate — 60% of those penalties avoided, not all of them — that returns $332K in the first year. The ERP stays as it is.
Two things worth knowing. Security review is the long pole and IT has the questionnaire now. And if we do not decide by 24 October, it will not be live before peak, which means we run this peak the way we ran the last one.
Happy to walk through the numbers before the meeting.
Meridian and Brightwater are fictional, so every number here is ours to show you. The prompts produce the structure; the figures come from whatever you paste in.
Feed the Deal Brief in and it builds a real .pptx with native, editable charts. Or take both generators together in the bundle, $25.