What's in the kit
The workbook
The Buyer Negotiation Blueprint, with its rate reduction tabs: a Rate Bridge that takes the offer one lever at a time, a live Rate Bridge Summary and a filled fictional example. It lives in your company's files, not on our website.
Thirteen prompts
For building the baseline, making the ask, reading what comes back, and locking it in and checking. Copy, fill in the brackets, paste.
The routine
What to run and when, from the week before you ask to the quarter after you sign. Most of the time is you checking the AI's homework.
The one rule: a saving is only real if it leaves your company's cost base, net of whatever you pick up. Almost every saving creates cost somewhere on your side, and work that simply moves to another of your teams is not a saving at all, however good it looks on your line. The prompts hold your assistant to that rule too, and the AI suggests while named people decide.
Step 0: pick your assistant
About half of U.S. employees now use AI at work (Gallup, 2026), mostly to write and summarize. The same assistant can do a lot more for a negotiation, but what it can see depends on your license and what your company has switched on. Start with the one you already have.
Microsoft 365 Copilot
- Keep the workbook and the invoices in OneDrive or SharePoint, where your finance files already live.
- With a paid Microsoft 365 Copilot license, Copilot can search your email and files, and Edit with Copilot can update the workbook in Excel. The free Copilot Chat only works from what you have open or upload.
- Paste prompt 1 at the start of the chat, or save it in a Copilot notebook if you have one.
- Invoices usually arrive as PDFs. Copilot reads them, but check the numbers it pulls out against one invoice yourself before you trust the other eleven.
ChatGPT Business or Enterprise
- Create a project for the negotiation, add the workbook, the contract schedules and the invoice export, and paste prompt 1 into the project instructions.
- Connect the apps your company allows, like Outlook, SharePoint, Gmail or Google Drive. On Enterprise, an admin has to turn them on first.
- A file you upload is a snapshot, so re-upload the workbook after you change it. The ChatGPT add-in for Excel and Google Sheets can apply changes to the workbook you have open.
- Export invoices to CSV rather than uploading twelve PDFs. Prompt 2 gets much more accurate, and much cheaper.
Gemini in Google Workspace
- Open the workbook in Google Sheets, save it as a Google Sheet, and check that the formulas and dropdowns came across.
- Save prompt 1 as the instructions of a Gem. Gems can use files from your Drive.
- Gemini can use your Gmail, Drive and Calendar only if your Workspace admin allows it. Gemini in Sheets shows you a preview before it changes anything.
- If your finance system can export to Sheets directly, point Gemini at that rather than at a download.
No approved AI for this at work?
- Do not paste contract pricing, invoices or your negotiating position into a personal AI account. Approval to use AI for writing is not approval to upload commercial terms.
- Practice on the fictional Harborlight Mutual example on the workbook's Rate Bridge Example (fictional) tab, so you are ready when you do get access.
- Or run the routine by hand. Prompt 8 in particular is just a list of questions, and it works fine on paper.
Using Claude or another approved assistant? The prompts are plain English and work there too. Product features and plan names change often (these were checked against each company's help pages in September 2026), so if a step doesn't match what you see, your AI or IT team can tell you what's switched on.
The routine
| When | Prompt | Time |
|---|---|---|
| Before you pick up the phone | 1, 2, 3 and 4 | About an hour |
| Before you offer a service level | 6. Who is actually using it | 30 minutes, plus the replies |
| The day before the conversation | 5. Decide what you will trade | 30 minutes |
| When you are ready to ask | 7. Draft the ask | 15 minutes |
| The day the proposal lands | 8. Take the proposal apart, then 9. Find the savings theater | About an hour |
| If a second provider quotes | 10. Normalize the competing quotes | 30 minutes |
| Once you have agreed the deal | 11. Turn the bridge into contract language | 30 minutes |
| When the number goes into the savings report | 12. Write the savings claim you can defend | 20 minutes |
| Every quarter after that | 13. Did the saving actually show up? | 15 minutes |
Prompt 13 is the one everybody skips, and it is the one that tells you whether any of this was real. Put it in your calendar for a quarter after the new terms start.
Before you start: use the AI your company has approved for work data, not a personal account. These prompts involve your contracts, your invoices and your negotiating position. If you are not sure whether your tool keeps that data inside your company, ask before you paste anything, or strip the numbers and use the prompts for structure only.
If your assistant cannot reach your email or your finance system, export what it needs and attach it. Every prompt here works on attached files, and for the invoice work a CSV export beats a pile of PDFs.
Build the baseline, before you ask
Two or three evenings of work, done in about an hour. Do this before you pick up the phone.
Project instructions
This teaches your assistant the workbook, the columns and the rules, so you don't repeat them in every chat. Rule 1 is the whole article in one sentence.
You're helping me prepare for and run a rate reduction conversation with an outsourcing provider. The deal: [SERVICE] is delivered by [PROVIDER]. Current annual spend is about [AMOUNT]. Our contract runs to [DATE]. I'm [MY NAME], [MY ROLE]. My target is [TARGET], and my real walk-away is [WALK-AWAY]. My record is the Rate Bridge tabs in the Buyer Negotiation Blueprint [FILE NAME OR LINK]. On the Rate Bridge tab the columns are: Lever, What changes, Annual saving offered, Where the saving lands, What we give up for it, Cost we pick up, Who has to agree, How solid is it, Starts, Our share of the benefit, Risk if it goes wrong, Net saving to the company (auto), Flag (auto), Notes and next question. Lever is one of: Volume or scope removed, Service level lowered, Automation, Commercial model change, Straight margin concession, Term or payment trade, Other. Where the saving lands is one of: Leaves our cost base, Moves to another internal team, Moves to another budget line, Unknown. How solid is it is one of: Modeled only, Provider asserted, We verified the math, Contracted with a date. Follow these rules every time: 1. A saving is only real if it leaves the company's cost base, net of any cost we pick up. Most savings create cost somewhere: card fees, our own people covering work that comes back, a system change on our side. Put that figure in "Cost we pick up" so the workbook can subtract it. If the work simply moves to another one of our teams, or the cost moves to someone else's budget line, it is not a company saving, however good it looks on my line. Say so every time you see it, and tell me when a lever costs more than it saves. 2. Every number you give me names its source: the invoice and period, the contract section, the email's sender and date, or the file name. If you can't find a source, say so. Don't fill gaps with guesses or industry averages unless I ask for a benchmark and you label it as one. 3. You suggest. People decide. What we accept, what we trade away and what we sign belong to me and the named decision makers. 4. My target, my walk-away, my leverage notes, our budget and anything about individual employees are internal only. Never put them in anything written for the provider. 5. Use plain English and short sentences. When I'll paste results into the workbook, give me a table in the Rate Bridge column order with only the rows that change. 6. When something is unclear, list it as a question for me rather than assuming.
What does one unit actually cost us?
If you can't say what a ticket or an invoice costs you today, you can't tell whether anything you're offered is good. This is the number the whole conversation runs on.
Work out what we actually pay per unit of work for [SERVICE] with [PROVIDER]. Use [THE LAST 12 MONTHS OF INVOICES], [THE CONTRACT AND ANY RATE CARD OR SOW], and [ANY VOLUME OR SLA REPORTING]. Give me: A. Total paid to this provider over the last 12 months, by month, from the invoices rather than from the budget. Note any month that looks incomplete. B. The volume delivered over the same period, in the unit this service is really measured in (invoices processed, tickets closed, claims handled). If more than one unit is plausible, show me each and say which one the contract uses. C. Cost per unit, by month and for the year. Flag any month more than 15% off the average and tell me what drove it. D. Everything in the total that is not the base rate: change orders, pass-through costs, travel, licenses, platform or technology fees, one-time charges, overtime, out-of-scope work, inflation or indexation uplifts. Show each as an amount and as a share of the total. E. The base rate as quoted in the contract, next to what we actually pay per unit including everything in D. Tell me the gap. F. What you could not determine from these documents, and which document would answer it. Show the arithmetic in a table I can check against the invoices, month by month. Do not round anything until the final line. If the invoice totals do not reconcile to the annual figure, stop and tell me rather than adjusting.
Find the money that isn't on the rate card
Most of the savings in a provider relationship are not in the rate. They're in the work you're buying that nobody decided to buy.
Look through [THE LAST 12 MONTHS OF INVOICES], [CHANGE ORDERS], [THE CONTRACT AND SOW] and my email with [PROVIDER] since [DATE] for spend we might not have decided to make. Find: 1. Work billed that isn't clearly in the SOW, with the invoice line and the contract section it should have come from. 2. Change orders, especially any that became permanent run-rate cost rather than one-time. 3. Volume we send that has low value: categories, requestors or transaction types where the cost per unit is high or the work looks avoidable. Quantify each. 4. Service levels we pay a premium for. For each, what the premium is worth in money, and which part of our business asked for it. If you can't find who asked, say that, because it's usually the best line in this list. 5. Anything we pay for twice: work the provider does that a team of ours also does, or tooling we license on both sides. 6. Automatic increases: indexation, annual uplifts, tiered rates that stepped up, minimum volume commitments we're paying into and not using. Rank everything by annual amount. For each one, tell me who in our business would have to agree to stop it, and list it as a candidate line for the Rate Bridge with a suggested Lever.
What leverage do we actually have?
Most buyers walk in with one lever, the threat of an RFP, and it's usually the weakest one they have. Several of the others cost you almost nothing.
Help me work out our real leverage with [PROVIDER] before I ask for a reduction. Use [THE CONTRACT], [THE LAST 12 MONTHS OF INVOICES], my email and meeting notes with them, and anything you can find about their published results or recent announcements. Tell me: 1. What this account is worth to them, in money and in anything else visible: reference value, logo value, a new capability, a foothold in our industry or region. For this and for item 3, if you cannot point to a source I could open, write UNKNOWN. Do not estimate from industry patterns. An honest UNKNOWN is more useful to me than a guess I might repeat in a meeting. 2. Our contract position: notice periods, renewal or extension dates, termination rights, benchmarking or most-favored-customer clauses, volume commitments, and any price review mechanism we already have a right to use. Quote the section for each. 3. Timing. When does their financial year end? When does our renewal decision have to be made? Which of us is on the clock? 4. What we could offer that costs us little and is worth real money to them: a longer term, more volume or a new scope, faster payment terms, a case study or reference, a named executive relationship, fewer contract exceptions, a simpler governance model. Rank these by what they are plausibly worth to them and explain the ranking. Do not put a dollar figure on any of them unless our own contract gives you the basis for one. 5. What weakens us: switching cost, how long a transition would take, knowledge only they hold now, tooling we don't own, internal appetite for another transition. 6. An honest read on whether we would really run a competitive process, and what it would cost us to do it properly. Mark this whole output internal only.
Make the ask
Thirty minutes. Decide what you will trade while nobody is sitting across from you.
Decide what you'll trade, before the room
The trades you make under pressure are worse than the ones you decide in advance. This turns the article's list into your list.
Using the leverage work and the baseline, help me decide what I'm willing to trade for a reduction on [SERVICE]. Build me a table with one row per possible trade. For each: what we give, what we'd expect back in money, who inside our business has to agree, who it affects and how badly, how reversible it is, and whether it's something I can offer in the first conversation or should hold back. Cover at least: volume or scope we could remove, service levels we could lower, a longer term or earlier renewal, payment terms, consolidating work with them, a shared-savings automation deal, moving to unit pricing, reference or case study value, and simplifying governance. Then tell me: 1. My opening position and why. 2. The three trades I should be happiest to make, and why they cost us least. 3. The two that look cheap and are not, with what actually breaks. 4. Anything on this list that needs someone else's agreement before I can offer it, and who. 5. What I should not put on the table at all in this round. Internal only. None of this goes to the provider.
Find out who is actually using what you are about to trade away
Somebody in your business is relying on that response time, and it probably isn't the person in the room. This is the artifact that protects you eighteen months later when they escalate.
I am about to offer changes to [SERVICE] that affect these service levels or scope items: [LIST THEM]. Using [THE SLA AND VOLUME REPORTING], [THE TICKET OR INVOICE DATA], my email and meeting notes, and [THE CONTRACT]: 1. Work out who actually consumes each one. Which teams, sites, business units or individuals raise the queries, need the fast turnaround, or depend on the work we are thinking of removing? Use the data, not assumptions. Show me the evidence for each name: the volume they raise, the threads they appear in, the dates. 2. Tell me which of these service levels look unused. If nobody has used the four-hour response in a year, that is the best news in this whole exercise, and I want the numbers behind it. 3. Tell me where the contract says a service level exists because a specific team asked for it, and whether that team still exists in the same form. 4. Draft a short note to each affected owner, four or five sentences, plain and friendly. Say what we are considering changing, what it would mean for them in practice, when we need to hear back, and that we will not agree it without them. Do not mention the money, our target or our negotiating position. 5. Give me a list I can keep: each owner, what they are being asked to confirm, the date asked, and a blank for their answer. Then tell me which of these changes I should not offer at all until someone has replied.
Draft the ask
Asking for a rate cut gets you a rate cut. Asking for a lower total cost with the bridge shown gets you a conversation about the actual business.
Draft my note to [NAME] at [PROVIDER] asking for a reduction on [SERVICE]. Make it do these things: 1. Ask for a reduction in what this service costs us in total, not a discount on the rate card. Give the number or percentage and the date we need it from. 2. Say explicitly that any proposal needs to come with a bridge: one line for each thing that changes, showing how much of the reduction comes from removing volume, from changing service levels, from automation, from a commercial model change and from their margin. 3. Say what we're open to trading, using only the items I marked as first-conversation offers: [LIST THEM]. 4. Ask for it broken out by what starts when, because a saving that begins in month seven is worth about half of one that begins in month one. 5. Be direct and warm. These are people we work with every week. No threats, no consultant language, no mention of an RFP unless I say to include one. Keep it under 250 words. Give me the email and a three-line version I could say on a call.
Read what comes back
An hour, the day the proposal lands, before anyone starts celebrating.
Take the proposal apart into levers
A proposal is designed to be read as one number. The workbook needs it as separate lines, which is also the only way to see what you're agreeing to.
Here's the provider's proposal: [ATTACH OR PASTE IT]. Turn it into Rate Bridge rows, in the workbook's column order. One row per distinct thing that changes. Never one row called "discount". For each row, fill in what the document actually supports: - Lever: one of the allowed values. - What changes: in plain words, as a buyer would describe it. - Annual saving offered: annualized. If the proposal gives a monthly number or a percentage, convert it and show your working. - Where the saving lands: Leaves our cost base, Moves to another internal team, Moves to another budget line, or Unknown. Read this carefully. If the proposal moves work back to us, or assumes our people do something they don't do today, that is not a saving that leaves our cost base. - What we give up for it: only what the document actually says we give up. If the document claims a saving with no corresponding change, leave this blank, because the workbook will flag it and that flag is the point. - Cost we pick up: what this change costs us somewhere else, annualized. Card fees, our own people covering work that comes back, a system or process change on our side, extra overtime. Use the document's own figure where it gives one, and where it does not, say what we would need to find out and from whom. Leave it blank rather than guessing, but tell me every row where you think there is a cost nobody has quantified. - Who has to agree: the team or role in our business, based on what the change touches. - How solid is it: Modeled only, Provider asserted, We verified the math, or Contracted with a date. Almost everything in a fresh proposal is one of the first two. Don't be generous. - Starts: the date the saving begins, not the date we sign. - Our share of the benefit: for automation or a model change, only if the proposal states it. - Risk if it goes wrong: Low, Medium or High, with one line of reasoning in Notes. Then list separately: anything in the proposal that increases cost, anything with no number attached, and any assumption about our side that the proposal needs to be true.
Find the savings theater
This is the pass that stops you quoting a number to your executive committee that you have to walk back later.
Work through the Rate Bridge rows you just built and be hard on them. Tell me: 1. Every saving that doesn't actually leave our company's cost base, with where the cost goes and roughly what it will cost that team. Total these separately from the headline. 2. Every saving with no corresponding change on the sheet. For each, the one question to ask the provider about it. 3. Every saving that depends on us doing something: sending less volume, approving faster, providing data, changing a process. For each, whether anyone on our side has agreed to it and what happens to the saving if they don't. 4. Savings that start late in the year, with what the first twelve months are really worth compared with the annualized number. 5. Anything that reduces cost by moving risk to us: lower service levels on work that matters, thinner cover at month end or peak, removing a control, less senior staff on the account. 6. Where the same saving might be counted twice across two lines. 7. If the proposal changes the commercial model, what happens to future efficiency gains, and whether anything in it commits them to keep passing savings on. Then give me two numbers: the headline they're offering, and what I should actually tell my executive committee. And give me the five questions for the next call, most important first.
Normalize the competing quotes
An unnormalized rate comparison is the one you'll quote upward and then have to retract. This is the article's rate normalization section as a routine.
I have quotes or rates from more than one provider for [SERVICE]: [ATTACH OR PASTE THEM, INCLUDING OUR INCUMBENT'S CURRENT TERMS]. Normalize them so they can actually be compared. For each quote, build a full picture of annual cost including everything, not just the quoted rate: - What the rate does and does not include: supervision and team leads, quality checking, training and ramp, attrition backfill, technology and platform fees, licenses, travel, transition costs, governance and reporting, inflation or annual uplift. - Who does the work that the other quote includes. If one quote assumes our people do quality checks, price that at our cost and add it. - Any assumed volumes, and whether they match ours. - Any minimum commitment, tiering or volume band, and what happens if we fall below it. - Transition cost and the months of double-running to get there, for anyone who isn't the incumbent. Give me a side-by-side table: quoted rate, total annual cost normalized, cost per unit, and year-one cost including transition. Then tell me how much of the apparent gap is real once normalized, what's still unknown, and exactly which question to each provider would close the biggest remaining unknown.
Lock it in and check
Once at signature, then fifteen minutes a quarter. This is the part everyone skips.
Turn the bridge into contract language
A bridge you agreed in a meeting and never wrote down becomes a discount you can't explain in eighteen months. This is also where the productivity commitment lives or dies.
Here's the agreed bridge: [PASTE THE AGREED ROWS FROM THE WORKBOOK]. Here's the current contract: [ATTACH THE RELEVANT SCHEDULES]. Draft the points our legal and procurement team needs to get into the amendment. For each agreed lever: 1. What has to be written down for this saving to be real: the new rate or unit price, the new service level, the volume assumption, the effective date. 2. What we agreed to give up, written as the actual change to the contract, so nobody argues about it later. 3. What happens if the assumption behind the saving doesn't hold: volumes come in higher, the automation doesn't land, the self-service portal isn't adopted. Then flag anything that needs a clause we probably don't have yet: - If we moved to unit pricing: a productivity commitment. Propose options, such as a stepped rate over the term, a volume band, or a benchmarking right, and say what each is worth to us. - If there's a shared-savings automation deal: how the benefit is measured, who measures it, how our share changes over time, and what happens to the tooling if we leave. - If service levels dropped: what the reporting shows, so we can see the effect on the business rather than just on the report. - If anything is phased: the dates, and what happens if a phase slips. Also list every part of the agreed bridge that this amendment would not actually bind, because that's the part that quietly disappears. Keep our target, walk-away and leverage notes out of this entirely.
Write the savings claim you can defend
This is the moment the whole article comes down to: the headline number or the real one, written in front of your own boss. Get it right here and nothing else can come back at you.
Write the entry for our savings report for [SERVICE] with [PROVIDER], from the agreed bridge: [PASTE THE AGREED ROWS FROM THE WORKBOOK]. Give me: 1. The headline number the provider will quote, and what it is: the reduction in their bill. 2. The net number for our company, after everything we pick up on our side, and how it is calculated. 3. A line for each lever: what changes, what we gave up, what it saves net, when it starts, and whether it is contracted, verified or still only modeled. 4. The first twelve months separately from the annualized figure, because anything starting later in the year is worth less than it looks. 5. What has to happen for the unverified part to become real, with an owner and a date for each. 6. The risks, in one short paragraph: what could make this number wrong, and who is carrying that risk. Write it so that if someone reads it in eighteen months, after the service has changed and half of us have moved on, they can tell exactly what we agreed and why. No adjectives. If the honest number is a lot smaller than the headline, say the honest number and show why; that is easier to defend now than to explain later. Then give me three sentences for the slide, and one sentence I can say out loud if someone asks why our number is lower than the provider's.
Did the saving actually show up?
Nobody checks. The number goes in the savings report, the report goes to finance, and the invoices do whatever they were going to do.
Check whether the reduction we agreed on [SERVICE] is actually happening. Compare [THE INVOICES SINCE THE NEW TERMS STARTED] with [THE AGREED BRIDGE] and [THE SIGNED AMENDMENT]. Tell me: 1. Line by line, what each agreed lever was supposed to save by now and what the invoices show. Name the invoice and period for each. 2. The total we expected to have saved to date, next to the total we have actually saved. 3. Anything that reappeared under a different name: a new fee, a change order, work that came back as out-of-scope, a pass-through that wasn't there before. 4. Volumes against what the deal assumed, and what the difference does to the saving. 5. Whether anything we agreed to give up has actually been given up, or whether we're still getting the service and just paying less for now, which is a bill arriving later. 6. Whether the cost per unit moved the way we expected, using the same unit as the baseline. 7. Anything in the amendment that should have happened by now and hasn't. Finish with three sentences I can put in the quarterly business review, and the single question to put to the provider's account lead.
We tested it on a fictional negotiation first
We ran prompts 2 to 13 against the Harborlight Mutual example from the workbook: a year of invented invoices, a contract pricing schedule, the provider's proposal, a competing quote and the email thread around it. We used two AI models from different companies and gave them the documents directly, not through live connections. Between them, they caught:
- A platform charge of 3,600 a month, 43,200 a year, that sat outside the rate card and outside the number the buyer quoted internally as their cost per invoice.
- A change order that was supposed to be a six-month fix and had quietly become a permanent monthly charge.
- Two items in the proposal, worth 90,000 of the 490,000 headline, that moved work back to the buyer's own shared services and month-end teams. Neither is a saving for the company.
- A two-point margin giveback with nothing given up for it, flagged as the line to ask about first.
- The automation saving that does not start until month seven, so the first year is worth about half the annualised number.
- A move to unit pricing with no productivity step-down, which hands every future efficiency to the provider.
- A benchmarking right in the contract that the buyer had never used.
- A competing quote that looked cheaper per unit until quality checking, a platform licence and a volume assumption well above the buyer's actual volume were added back.
Your results will depend on what your assistant can see and how you fill in the brackets. Check every number before it goes anywhere near your executive committee.