The Sentence They Don’t Want to Hear

Not the columnist, and not the desk. This is for whoever on your paper still has to ring a person up and say the thing that person does not want to hear, out loud, with their own name attached to it.

Ask a room of reporters what the job actually is and you get two answers, and both are right. Knowing what is a story. Checking whether it’s true. The rest of the work is not now handled by something else, whatever anybody claims, and you’d stop reading if I said it was. What I want to do instead is take one task, the one you’d hand to somebody else if you were allowed, and look at why it stays.

Start with where copy comes from, because the trade is honest about this in private and coy about it in public. Most of what fills a publication arrives from somebody who wants it in there. Releases, embargoed reports, listings, council agendas, court lists, company filings, the wires, the trade body with a survey, the exclusive that is really a placement. None of that is new and none of it is shameful. It’s the supply, and no newsroom has ever run without it.

What has changed is that the supply is now bottomless and much better dressed. Every organization you deal with can produce endless clean, quotable, on-message text at no cost. The press office answers you inside the hour, at any hour, in complete sentences, and says nothing at all. Your inbox is fuller than it has ever been and emptier at the same time.

Nothing in that flow will ever hand you the story somebody is keeping out.

That’s not a complaint about public relations. It’s arithmetic. A story worth the name exists because a person has decided it should not exist, and everything that arrives through a channel arrives because somebody wanted it to. The material you need is not in the record. It’s inside a person who has chosen not to say it, and inside another person who will lose something when it’s said. No feed carries that. Nothing can be summarized out of a pile of documents that were never written.

So, the task. You have a document, or two sources, or the strong sense that you know what happened. Now you have to put it to them.

Everything in that call is a decision, and none of it is retrieval. How much do you show. Name the document and you have told them who leaked it, and that person may lose their job by teatime. Hold it back and they say it’s nonsense, and you have burned your one call. When you ring matters, and there is a slightly grubby art to catching somebody before their advisers are awake, which the trade knows about and rarely writes down.

You say who you are in the first sentence, which is the moment you give away every advantage you had.

Then you say the sentence, and the reply is evidence. Not just the words. The pause before the words. The denial that is too specific, and answers a question you had not asked yet. The one that is technically exact and covers a slightly different thing. The offer of a friendly briefing on a different subject entirely. None of that is confirmation and nothing runs on a pause. It is a direction. It tells you which document to ask for next, and which of the four people who could have signed it is worth another call, and you get it live, in somebody’s voice, once.

There is a version of this call that costs you more. The knock on a door where somebody died last night. Most people outside the trade think that’s ghoulish and some of it is, and reporters who do it badly are a decent part of why the public dislikes you. What gets left out is how often the family wants to talk, and how much it matters that the person who turns up is careful, and unhurried, and prepared to leave. That cannot be sent. Somebody has to stand there and be told to go away, or not.

A great deal of verification is tooling and always has been. Checking a register, pulling a filing, working out where a photograph was taken, matching a face against an older image. That work has got faster and better and you should use every bit of it, and anybody who tells you otherwise is romanticizing a trade that never had time for romance.

The bigger problem isn’t the tooling. Making difficult calls is not, on its own, a full week. Most days are the routine flow, and a job made entirely of exceptions has too few hours in it to be a job. Worse, a publisher can decide it doesn’t want the exception at all. Stories that people fight to keep out are slow, legally expensive, and no better for traffic than the cheap stuff. That decision has been taken in real newsrooms, more than once, and nothing about the current machinery makes it less tempting.

There’s one more thing the trade knows and the public doesn’t, which is that the call itself can lose you the story. Give somebody proper notice and you have also given them time. Time to reach a judge, where that works, time to put their own statement out first, time to start deleting things. You still make the call. The rule that you put it to them is not a courtesy, it’s the difference between journalism and something else, and it costs you real stories every year.

None of that makes the exception safe, and on its own it is not a living. It is only the one thing no supply can produce, because supply runs on somebody wanting the thing published, and this is the single exchange where everyone involved would rather it wasn’t.

There’s a release sitting in your inbox now that reads beautifully and tells you nothing. Find the line in it that somebody argued about before it went out, the one that got softened on the way. Then work out who lost that argument, ring them, and ask what the sentence said first.

The Money That Isn’t Theirs

Once a year you hand the whole thing to an accountant who charges more than you do and gets thanked by name for it. That is the trade’s oldest complaint and it isn’t what this post is about. This one is for whoever keeps the books for a business with a yard, a van and an owner who still answers his own phone. Not the finance department of somewhere large. You, and the handful of clients whose whole year you carry around in your head.

Ask anybody what a bookkeeper does and they’ll say it’s entry. They picture typing numbers off paper into a screen, and they have just worked out that a machine can do that, and they are pleased with themselves. You lost the typing years ago. The bank feed arrived, then the rules that code the regulars, then the phone that reads a receipt off a photograph, and the trade quietly reshaped itself around all of it long before anybody found it interesting.

So let’s set out what a month actually is. Reconciling. Chasing the client for the paperwork they have now promised more than once. Coding the odd ones that no rule catches. The tax return, the payroll, the supplier run, the polite letters to people who haven’t paid. Month end journals so the numbers mean something. Then, once a year, that handover to the accountant.

Most of that is being eaten and you can see it happening from where you sit. The regular coding happens without you now. Reconciling is going the same way. The software already flags a duplicate payment and an amount that doesn’t look like the others, and it does it faster than you would.

Here’s the part nobody has ever put a price on.

Once a month, you are the only outsider who looks at that business honestly, up close, one transaction at a time. Think about who else sees it. An accountant sees it once a year, tidied up, when everything in it is already history. A bank sees a balance, the customers see a van, and the owner sees what he needs to see, because he is inside it and running on the story he told himself in January. You see the thing itself, in detail, before anyone has arranged it. That isn’t a skill, it’s a position, and it is made of three plain things. Close enough to see the detail. Often enough to know what has changed since last time. Holding the keys to all of it at once, the bank, the invoices, the payroll, the ledger. Take away any one of the three and the position is gone.

It is also how you know, in the first week of the month, what’s going to go wrong in the summer.

The account looks healthy. It looks healthy because a large slice of what’s sitting in there is tax the business collected on the government’s behalf and hasn’t sent on yet. That money was never his. He has just quoted a job on the strength of the balance, or put a deposit on a van, and nobody in his life has said the sentence out loud. The software will not ring him. It will produce a correct report, on time, and file it in a folder he doesn’t open.

You ring him. That’s the job. It has never appeared on an invoice.

The rest of the list is the same shape. A direct debit that’s been running since he cancelled the service years ago. A supplier whose prices have crept, one small rise at a time, in a way no single invoice shows. Drawings running ahead of what the business actually earned, which nobody notices until the year end and a tax bill. A payment to a company nobody in the office has heard of. An employee’s own bank details sitting quietly on a supplier record.

A lot of that noticing is being automated too, and I think more of it will be. The flag on the odd payment is real. The cash forecast that says the tax bill is coming is real, and it’s better than the one most people do in their heads.

What isn’t in any of it is the rest of what you know. That he isn’t answering emails this month. That his wife does the invoicing and something has gone wrong between them. That the big customer has gone quiet, and last time that happened he borrowed from his brother and didn’t tell anybody. If you go in on a Tuesday, you know the yard is quieter than it was, the good foreman has left, there’s a new van outside that nobody mentioned, and the son is suddenly around a lot. None of that is in the ledger. All of it turns up in the numbers later, and by then it’s the accountant’s problem and it’s too late to be anybody’s opportunity.

Most bookkeepers now work from a screen at home and never set foot in the place, and the yard is not the standard case. It doesn’t have to be. The position was never standing in a yard, it was being inside the same business every month with everything in front of you, and a bookkeeper who is in the bank feed on the fourth of every month has that. What she has less of is the accidental signal, the things nobody would think to send her. So the good ones ring for no reason at all, which is not a soft skill, it’s a sampling method. Anybody who has worked both ways will tell you the remote version needs that call more, not less.

That leaves an uncomfortable piece of arithmetic, and it’s the reason I don’t think this trade is safe just because the noticing is. Your fee is priced on the part that’s disappearing. Transactions, hours, entries, the volume of things touched. The position isn’t any of those. It’s a standing arrangement to be inside somebody’s business every month, whether or not there turns out to be anything in there. A thing like that has to be bought before it pays, or it isn’t in place on the month it matters. Nobody buys it that way. They buy transactions and get the position thrown in, which worked fine while the transactions were expensive. A buyer who has just watched the visible half of the work fall away is not in a generous mood about the invisible half.

Open last month’s file for the client you know best and read down it until you reach the one sentence you’d say to the owner if you had him on the phone with nothing else on the agenda. It’s in there, and it will take you a minute. Send the reports without it, the way you always do, and count how long it takes anybody to ask you for the sentence. I have a view about what that says about your fee, and I’m going to keep it to myself.

What You Left Out of the Report

An apology first, on behalf of everybody who repeated it. It became a fashionable thing to say at conferences, years ago, that we should stop training you, and the people who said it most confidently had never set foot in a reporting room. Meanwhile the lists got longer, the studies got bigger, and there were never more of you. You have been more polite about this than we deserved.

So let me concede the part your trade is tired of arguing about, and then say the thing I actually came to say. Some of the detection is good. On narrow, well-defined tasks a model finds what it was trained to find, reliably, and it doesn’t get worse at the end of a long list. Anyone who has watched a flagged bleed jump the queue and get a patient into a scanner sooner is not going to be talked out of it, and shouldn’t be.

That is a claim about detection. It is not a claim about reading, and the difference is the whole post.

Your day is protocolling, priors, the phone and the dictation. Deciding what the scan should even be, from a request that says abdominal pain, query cause, and nothing else. Pulling the old study and working out whether the thing is bigger. Being interrupted by a surgeon who wants a look now. Telling whoever is at the scanner whether to add the extra sequence. Then the meeting where the oncologists and surgeons sit down with the images and somebody has to say, out loud, what they think that is. Then a list that is never empty, sent overnight to a service in another time zone and coming back for you to live with in the morning.

A great deal of that is being automated and some of it should be. Measurement, comparison with the prior, the segmenting, the reconstruction that lets a scan be quicker and cleaner. The draft on the normal chest film. The chasing of follow-ups that everybody hates and nobody has time for. Good. None of that is the part I came to defend.

The report doesn’t go, because a report is not a description of an image. It’s a signed instruction about what happens next to a person, addressed to a particular reader who will act on it. Change the reader and the same pixels produce different sentences. Change what the referrer can do about it and they change again. That isn’t sloppiness, it’s the job, and it’s why two competent radiologists can write two different true reports on the same study.

Which brings me to the small thing you saw that had nothing to do with why the scan was ordered.

You know the one. It sits at the edge of the field, it is almost certainly nothing, and you have to decide whether to put it in writing. Mention it and you start a chain of appointments and repeat scans and a frightened person who now has a thing, and sometimes a needle goes into something that was never going to harm them. Leave it out, and if it turns out to matter, the name on the report is yours. Nothing in the image tells you which way to go. You settle it with the patient’s age, the referrer, what the follow-up will do to this particular person, and what you can defend later.

Then there’s the phrase. Clinical correlation is advised. Cannot be excluded. Everyone in medicine makes jokes about that language, and most of the jokes miss what it’s doing. Sometimes it is genuine uncertainty written down honestly. Sometimes it is a person moving a decision to somebody with information they don’t have. And sometimes, let’s be adults, it is a person covering themselves. All three are the same act, which is placing the weight of what comes next somewhere specific.

A machine will flag the incidental. It will flag it every time, because flagging costs it nothing. It has no clinic to fill, no patient who can’t sleep, no colleague who has to do the biopsy. The cost of a flag lands entirely on people who are not the flagger, and somebody in the building has to be willing to take a flag and do nothing about it, in writing, with their name on the line.

That is what a tool of this kind actually does, and it is worth saying plainly. A tool that points at things does not settle anything. It moves the question one step along, from whether there is something there to what happens now that somebody has been told there might be. The second question has never been an imaging question. It gets answered in clinics, in waiting lists, and in a conversation with a frightened person who will remember it for years.

The argument that should worry you isn’t about machines at all. If the read comes with the scan, why does the answerable person have to be a radiologist? Let the clinician who ordered it take the report and own the consequence. They know the patient, which you usually don’t. Nothing about the position requires your training, only somebody’s signature.

I think that’s the actual threat to your trade and I don’t think it’s silly. My answer is only that the position doesn’t disappear, it moves, and it lands on somebody with less imaging training and less time, who will then need somewhere to send the hard ones. Where those go is not a technical question. It’s a question about who a health system is willing to have blamed.

And I’m not going to end this kindly, because the honest reading isn’t kind. Every tool your trade has been given has raised what a day is expected to contain. The flags arrive faster than the reporting time you save, and the being-answerable is not a moment at the end of the study. It’s the posture you hold for the whole list, and it’s what makes the ordinary parts tiring. That doesn’t get lighter when the ordinary parts go. It gets more concentrated.

Pick the last incidental you decided not to chase, one of the small ones you settled without slowing down. Work out what you actually used to settle it, and how much of that came from the images. Then answer something I can’t. Who else in that building could have made the same call, and still be willing to explain it a year from now?

Everything in the Job Description Was True

Document management. Diary management. Drafting support. Assisting with disclosure and liaising with counsel. Every line of that was accurate when somebody wrote it, and it is still accurate, and none of it is the job.

Start with the honest part, because the trade already knows it and pretending otherwise wastes your time. First-pass review has been going for years, since long before any of the current noise. Software that ranks documents by how likely they are to matter turned out to work well enough, and it cost a fraction of a room full of people. What’s arrived since then takes the next layer. A serviceable summary of a long transcript. A chronology built off the dates in the file. A first draft of the letter that follows the template, the index, the schedule, the routine instrument. Checking the citations. Working out the deadline from the rule.

Some of that is a relief and some of it isn’t, because a fair amount of it was the billable part, and a job that loses its billable hours has a problem whatever else is true about it.

So what’s left isn’t a task at all. It’s a location.

Take the day it goes wrong. Counsel is on their feet, a witness has just said something that doesn’t match a document, and the room has about the length of one sentence to decide what happens next. A hand comes back without a head turning. Whatever your jurisdiction calls the paginated set everybody in the room works from, you built it. You know the letter is in there. You know it’s the copy with the earlier date, because the argument about which date was right went on and on. The page arrives in the hand. Nobody says anything about it afterward.

That is not retrieval. Retrieval is the part a machine now does better than any of us, and if the question had come in writing with time to answer it, nobody would need you. The speed comes from somewhere else. You have been inside that file since the start, so the document, its wording, the fight about it and the other side’s copy with the wrong date are already in your head. Nothing is being searched. It’s being held. And the knowledge on its own is only a memo that somebody reads later. What makes it worth paying for is that it’s in the room while the room is still moving.

And that is worth saying carefully, because it cuts both ways. The months in the file are exactly what’s being taken away. If the review is done by something else, the person standing in the room on the day has a thinner picture of what’s in there, and nobody in the trade has worked out yet what that does. I can’t either. I suspect the answer is not comfortable and I’d rather say that than pretend the residue is safe.

The trial is the sharp version, but the ordinary version is everywhere in your week. A witness turns up early and has to be met at reception, kept away from the others, given a glass of water. Somebody has to notice that this one is about to come apart, and say so to counsel before they reach the door. A client arrives without an appointment because the letter frightened them. Completion runs late and needs a person holding the signature pages and the room. On the day of the deadline the filing system goes down, so a human being walks it over, and the woman on the counter knows your name.

None of that is written down anywhere as a duty. It happens because you were there.

A great deal of this trade now works from a kitchen table, and the sky did not fall. Bundles get built remotely. Hearings run on a video link, witnesses get met by nobody at all, and mostly it’s fine. If presence were doing the heavy lifting every day, none of that would have worked as well as it has. So the claim isn’t that you have to commute. It’s narrower. It’s that the work concentrates onto particular days and particular rooms, and on those days somebody has to already be there and already know, because a room moves at a speed that has no queue in it. You can’t summon that person. Whoever is present is the only candidate.

I don’t think this post has earned the right to be encouraging, so here is the part I dislike about your position. The title says assistant. You have been at the firm longer than the associate you are assisting, and you both know it, and neither of you says so. Pay follows titles, not work. And the firm can only see you through the parts of your week that leave a record, which are precisely the parts being taken out. The tasks that leave are the ones that were easy to see and easy to count. What’s left is real, and it is nearly invisible from head office, and those two facts have never sat comfortably together in any trade I’ve looked at.

The firms that work this out will pay for presence on purpose, and describe it properly, and stop calling it assistance. What that costs them is somebody who is not billing anything while nothing is happening, which is a harder line to defend on a budget than any of the ones being removed.

For a week, keep a note of every time somebody came and found you in person instead of writing it down. Note what they wanted and whether the answer existed anywhere in the file. That list is your actual job description. Now notice that you have never once put a single item from it on a timesheet.

The Register Nobody Chose

The first piece of your work to go was gisting. Somebody used to send you a pile of documents in a language they couldn’t read and pay you to say roughly what was in them, so they could work out which ones mattered. Nobody buys that now, and honestly nobody should.

You saw this coming before the rest of us did, which is why I want to start the series with your trade rather than a safer one. That roles hollow out while the job title survives is not a new claim on this blog, and the only thing these thirty posts add is the specific trade instead of the general shape. So let’s be specific. The volume work is going. The first drafts are going. Somebody still has to decide what a sentence is for, and that part was never really about words.

The version going around is that you’re a proofreader now. There’s something in it. Post-editing pays less per word than translating and takes a strange kind of attention, and you can only do so much of it in a day before your eye stops catching things. But the squeeze didn’t start here. The memory discounts were already shaving your invoice years before any of this, the grid of percentages that decides a repeat is worth a fraction and a near match is worth a bit more than that. The machine walked into a trade that had already agreed, in writing, that some of your words were worth less than others.

Clients mostly don’t know this part. A bad translation used to announce itself. It arrived stiff and strange, and the client could see something was wrong even if they couldn’t say what. That was useful. The output you get now is smooth, confident, idiomatic, and every so often it has quietly dropped a negative or swapped a term for its near neighbor. Nothing on the surface tells you which sentence to distrust, so you have to read all of them properly, which is the tiring half of the job. You are being paid less to do the harder part.

One decision holds the whole of this trade, and I want to put it in front of you before anything else.

You’re going into a language with two words for you. One you’d use with a stranger, one you’d use with a friend. On an account you have had for years this is not a live question. It was settled once, it sits in the style guide or in the termbase, and you would have to go digging to find out who decided it. The live version is the new client, the file that landed on Friday, no guide, nobody to ask. The source has one word for you and nothing in it says whether this company talks to its own staff as adults or as employees. You won’t find the tone of the head office in there either. You put the question to them and it comes back as “either is fine.” It is never either. The same client will write in six months to ask why the handbook sounds like a letter from a bank.

A machine will pick one. It will pick consistently, at speed, with no idea it made a decision, and once that choice has run through a company’s handbooks and safety notices and internal mail, it is the company’s voice. That is register, the distance you keep from the person reading, and it isn’t a small thing to set by accident. Somewhere in that company a laminated card is screwed to the wall beside a machine, telling the man on the night shift to keep his hands clear, and it speaks to him the way a bank speaks to a stranger. Nobody chose that. It got chosen.

That is the shape of the whole job. The source text is not a brief. It’s one attempt at the thing, made by somebody with a different reader in mind, and your work is to notice what each sentence is doing and then find out whether it can be done that way over here. A safety instruction that assumes a building code the other country doesn’t have. A contract clause naming a remedy that doesn’t exist in the target jurisdiction. A line telling the reader to ring their family doctor, in a country where that isn’t how anybody gets seen. A joke, which has to be replaced by a different joke or dropped, and either way somebody has to decide. None of that information is in the source and none of it is in the target language. It sits with the person who has been in both rooms.

The machine is good, and the trade doesn’t always say so out loud. On clean, well-written, in-domain prose it produces something a tired human at the end of a long list would be pleased to have written. Saying otherwise in front of a client who can read both texts loses you the argument and some of your credibility with it. The trade’s real complaint isn’t that the output is bad. It’s that judging whether it’s bad takes a professional, and professionals are exactly what the buyer thinks they’re no longer paying for.

And I don’t want to leave you with the comfortable version of this, because the comfortable version is wrong. Saying that the interesting work survives is no use to somebody whose interesting work was subsidized by the boring work. The volume paid the rent. If the pile at the bottom goes, the top doesn’t stay where it was, it just gets more crowded. Some people reading this will not have a trade at the end of it, and it won’t be because they weren’t good.

It holds where being wrong costs money or gives offense, and it holds for a reason worth being clear about. It isn’t that the machine can’t produce the sentence. Often it can. It’s that somebody has to know what the sentence is for, who is going to read it, and what they’ll do next, and then be the person who settled it. Interpreting is a different trade with a different answer, and I’m not going to pretend I can cover both in one go. But the written version of this is a job about two worlds that can’t hear each other, and the words were always the smaller half of it.

The next time a client tells you either is fine, don’t let it go past. Write down which one you picked and the one line of reasoning behind it, and leave it in the file where the next translator will find it. Nobody is going to ask you for that line. It is still the only record anywhere of how that company decided to speak to its own people.

In Practice: The Other Side of the Table | Lesson 15: You Are Building a Capability, Not Running a Purchase

The evaluation closes, the contract gets filed, the working group dissolves, and somebody sends a thank you note. Seven months later a different part of the organization starts the same process from nothing.

Nine months, then seven weeks

Composite from a few organizations now several purchases deep: a construction and infrastructure group, on its fourth evaluation of this kind in three years.

Illustratively, the first took about nine months from mandate to signature. The fourth took roughly seven weeks, for a purchase of comparable size and rather more complexity.

The software had not got simpler. What had changed was that the fourth evaluation started with things the first three had produced.

A standing question set, the same one every time. A habit of measuring the baseline before anyone contacted a vendor. A list of the internal groups who could stop a project, with their actual lead times next to their names, updated after each purchase. A rough template for estimating switching cost. And a record of what they had declined to buy, with the reason.

That last one is the rarest. Most organizations keep a careful record of what they bought and no record at all of what they turned down, so the same product gets evaluated twice by different teams and the same objection gets rediscovered from scratch, at full price both times.

What compounds

Four things, and none of them require a center of excellence, a new function, or anybody’s headcount.

Questions rather than templates. A template gets filled in. A question gets answered, and the answers are what you actually needed. The demo requests, the reference questions, the diligence conversation, the pricing question about what moves when usage doubles. Twenty questions on one page, refined a little each time.

The measurement habit. Baseline before vendors. It takes a week and it is the difference between a benefits review that confirms your judgment and one that finds nothing to look at.

The stopper map with lead times. Not a stakeholder list. The groups who can quietly cost you months, and how many months each of them currently costs. This information already exists inside your organization, distributed across the memories of people who have been burned, and writing it down once converts it into something the next team inherits.

The decision log, including the noes. What you bought, what you declined, and why. Two paragraphs each. Kept somewhere findable by someone who does not know it exists.

Four documents, one owner, no budget. That is the whole apparatus.

The asymmetry you can actually close

This series opened with three asymmetries between the buyer and the seller. They know your process because they run it constantly. They know the market because they are in it every day. And they can wait longer than your sponsor’s attention lasts.

Two of those are not available to you. You will never have their pricing data, and you cannot out-wait them on any individual deal.

The third one is entirely yours. Their advantage is repetition, and repetition is a thing you can build. Not by buying more often, which would be a strange goal, but by making each purchase leave something behind that the next one starts from.

An organization on its fourth evaluation with none of that is on its first evaluation, four times. An organization that kept those four documents is genuinely, measurably better at this than it was, and it closed the only gap it was ever able to close.

You will still get some wrong

I have done most of what is in these fifteen lessons, and I have also skipped most of it, usually under time pressure, and some of those purchases were fine. Process is not a guarantee and anyone selling it as one is selling something.

What changes is the character of the mistakes. Without any of this, you make the same three errors repeatedly: no defined no, no measured baseline, no idea who could stop you. With it, you make new and more interesting errors, about things that were genuinely hard to see.

That is a reasonable definition of getting better at something, and it is the realistic version of what this series is offering. Not better outcomes every time. Failures that at least have not happened before.

One thing to do differently

When this evaluation closes, before the group disbands, spend two hours writing down what you would tell the person who runs the next one.

What you would ask earlier. Who you would have gone to see in week one. What the vendor said that turned out to matter. What you declined and why.

Then put it somewhere they will find it without knowing to look. That document is the capability. Everything else in this series is just a description of what tends to be written in it.

In Practice: The Other Side of the Table | Lesson 14: Renewal Is the Real Negotiation

You spent four months negotiating the first contract and you will spend about three weeks on the renewal. The renewal is the one that is worth more.

Six weeks and no alternative

Composite from a few multi-country service operations: a hotel group, guest service and revenue operations across several markets.

The original negotiation had been done properly. Competitive process, three bidders, a discount procurement was rightly pleased with.

The renewal arrived with, illustratively, a forty percent uplift, justified by usage growth that was entirely real. Procurement had six weeks. There was no second quote, because nobody had spoken to the runner-up in two years. Nobody knew what leaving would cost, because nobody had ever worked it out. And the vendor could see the usage data, because the buyer had been sending it to them monthly in the service review.

They negotiated it down somewhat and paid most of it. Which was, given where they were standing in week one of those six weeks, about the best available outcome.

The positions have swapped

At signature you had real alternatives and no dependency, and the vendor had better information about the market than you did.

At renewal that reverses. You now have excellent information about what the product is worth to you, which is a genuine advantage and the only one you gain. They have precise knowledge of how embedded you are, often from data you gave them voluntarily and correctly. And your alternatives exist in theory, in a slide, unrefreshed since the original evaluation.

The uncomfortable part is that most of your room to move exists in month four and is gone by month ten, which is roughly when anyone starts thinking about it.

Four things done early

Diarize it at signature. Not the renewal date. Renewal minus six months, with a named owner who is not the person most invested in the relationship going smoothly.

Keep the measurement running. The baseline you established before the vendors arrived, and the benchmark you wrote into the contract. Evidence of value is the only argument at renewal that is not a threat, and it is the only one that works when you have no credible way to leave.

Keep one alternative warm. An hour a year with the runner-up. It costs almost nothing, it makes a second quote obtainable in days rather than months, and it keeps you current on what the category can do now, which after two years may be considerably more than what you bought.

Refresh the switching cost. A number, from the leave test, updated once a year. Without it you cannot tell whether a proposed increase is worth accepting, and you will end up deciding on how the number feels.

Ask for things that are not price

Renewal is the best moment in the whole relationship to collect the terms you did not get the first time, because the vendor wants a clean renewal and non-price terms cost them less than a discount.

  • The benchmark clause, the deprecation notice and the export terms you traded away in round one
  • A commitment re-baselined to your actual usage rather than the forecast you got wrong
  • Price protection for the following term, so you are not doing this again from the same position
  • A unit price that reflects the fact that their input costs have almost certainly fallen since you signed

That last one is the two-line model from the cost lesson, and this is the moment it pays. If you tracked what you would be paying at something nearer list, you can tell whether the uplift is a correction of an introductory price or an increase on top of one.

The pressure from your own side

Worth naming, because it catches people who handle the vendor side well.

Your operating team does not want disruption. Your sponsor has moved on to something else and does not want this back on their desk. And somebody will say, accurately, that there is no capacity for a re-evaluation this quarter.

All of that is true and none of it is an argument about price. It is the condition the renewal number was set against, and a vendor with a decent account team knows the state of your capacity roughly as well as you do. The six months of preparation exist precisely so that the renewal does not require a re-evaluation.

One thing to do differently

On the day you sign, put an entry in the calendar at renewal minus six months, with a named owner and three items: pull the measurement, call the runner-up, refresh the switching cost.

Three hours of work, done once, eighteen months before it is needed. It is the highest-return thing in this entire series and it is skipped almost universally, because on signature day the renewal feels like somebody else’s problem and by the time it is yours the useful window has closed.

In Practice: The Other Side of the Table | Lesson 13: Exit Rights and the Leave Test

Somebody in the approval meeting will say that you can always switch later. It is usually said to close down a risk discussion, it usually works, and in most organizations it has never once been tested.

Eleven months to leave

Composite from a few operations-heavy deployments: a rail and freight operator, maintenance scheduling and incident triage across a large asset base.

Two years in they decided to move, for reasons that were mostly commercial and entirely reasonable. Illustratively, the migration took about eleven months and consumed roughly three times the annual license in internal effort.

The vendor did not obstruct. The data came out in a week, in a clean format, exactly as the contract said it would.

What did not come out was two years of accumulated fit. The thresholds somebody had tuned in month four. The exception rules that had grown to cover the seventeen situations the original design had not anticipated. The routing logic that assumed one product’s way of scoring severity. Most of it lived in a configuration interface, none of it was documented, and the two people who understood why it was set that way had both moved on.

The data was portable. The knowledge was not, and nobody had ever counted it as an asset.

What actually holds you

Roughly in order of how hard each is to move, which is close to the reverse of how much attention each gets in a contract negotiation.

  • Tuning and configuration. Thresholds, prompts, rules, weightings. Lives in a screen, rarely documented, exportable in no meaningful sense even when the vendor cooperates fully.
  • The shape of the work. Your process quietly reorganized itself around the product’s assumptions. Undoing that is a change program, not a migration.
  • Derived artifacts. The evaluation set, the corrections your users made over two years, the labeled examples. Often the most valuable thing you created during the contract, and often not clearly established as yours.
  • Integration surface. Connectors, identity pattern, reporting. Real work, but at least it is visible work that somebody can estimate.
  • Raw data. The thing everybody negotiates hardest for, and the least of the five.

The leave test

Before signature, write one page answering four things.

What we would get back, in what format, in how long. What we would have to rebuild rather than move. Who understands the configuration and whether that understanding exists anywhere outside their head. And what we would run on while we migrated, because the answer is rarely nothing.

Then do the version almost nobody does. During the pilot, ask for a full export of your data and your configuration, and time it.

A vendor who produces a clean export in a week is telling you something true about how they think about customers. A vendor who needs a professional services engagement to answer the request is telling you something else, equally true, and much better learned in week six of a pilot than in month twenty-six of a contract.

It also has a useful side effect. Asking during the pilot is a neutral, technical request. Asking during contract negotiation reads as distrust and gets handled by a different department.

What to write down

Four terms, in decreasing order of how easily you will get them: export format and timeframe stated explicitly rather than on request; ownership of derived artifacts established as yours; configuration included in what is exportable; and a transition assistance period at rates agreed now rather than at whatever they quote when you are leaving.

The third is the one that gets waved through as a technicality and is the one the rail operator would have wanted most.

Some of this is fine

Worth saying plainly: a product you cannot easily leave is often a product that has become genuinely useful. Deep fit and high switching cost are the same phenomenon viewed from two directions, and an organization that has embedded a tool into how work happens has usually got the value it paid for.

The goal is not zero switching cost. That would mean you never adopted anything properly.

The goal is knowing the number. A buyer who can say switching would take us about nine months and cost roughly this much can make a rational decision at renewal, including the decision to stay and pay more. A buyer who has never worked it out negotiates as though they could leave in the spring, then discovers in week two that they cannot, having already made a suggestion they now have to walk back.

One thing to do differently

During the pilot, request a full export of your data and your configuration, and time how long it takes to arrive.

You will learn more about your future switching cost from that one request than from the entire exit rights section of the contract, and you will learn it while you still have three vendors and no commitment.

In Practice: The Other Side of the Table | Lesson 12: Contracting for Something That Changes Under You

You are about to sign a contract for a product that will not be the same product in six months, using a template written for software that shipped twice a year and changed when you accepted an upgrade.

Nothing in this lesson is legal advice. It is the commercial shape to hand to the person who does give it, because your legal team will draft what you ask for and they are not going to know to ask for these on their own.

The change that breached nothing

Composite from a few archive-scale evaluations: a media and publishing group, automated content classification and rights checking across a large back catalogue.

They deployed, then spent about three months tuning their thresholds until the review queue was a size two editors could handle. Good outcome, sensibly done.

Then an update on the provider side changed how the underlying model behaved. Nothing broke. Illustratively, precision moved a few points one way and recall a few points the other, which is the sort of change that is invisible in aggregate and very visible in a queue. Their carefully tuned thresholds were now set for a system that no longer existed.

They found out roughly six weeks later, when an editor mentioned the queue felt heavier. No term of the contract had been breached. No term of the contract covered it. Their own vendor had not been told in advance either.

Five terms worth asking for

Notice of material change to the underlying model. Vendors resist the word material, and fairly, because it is vague. Offer a test instead of an adjective: any change of model family or version, plus anything they announce publicly as a behavior change, plus anything they themselves detect as moving output distribution.

Deprecation notice with a floor. How long you get before a version you depend on is withdrawn. Ask for a stated number of months. Ask separately for the right to remain on a prior version during a validation window, which is worth a great deal in regulated work and very little elsewhere, so do not spend negotiating capital on it if you do not need it.

A benchmark written into the agreement. Almost nobody does this and it is the most useful of the five. Agree a small set of your own held-out cases and an acceptance threshold at signature. Re-run it quarterly. If the result falls below the threshold, you have a defined remedy, even if the only remedy you can win is a termination right.

Without it, the sentence available to you in month eight is that it seems worse than it used to be, which is an opinion, and you will be having an argument rather than exercising a right.

Your data out of training, in terms that survive a product change. Most vendors will give you this readily. What varies is whether it covers the derived artifacts from the previous lesson, and whether it binds their providers as well as them.

What happens if their provider relationship ends. Many vendors in this category are built on capability they license. Ask what happens if that arrangement changes, whether they can serve you on an alternative, and how long that would take. The answer tells you how much of the product is actually theirs, which is useful well beyond the contract.

What you will actually get

Not all five. Possibly two. So rank them before you walk in, because the order in which you concede is decided in the room otherwise, and in the room the unfamiliar clause always goes first.

For most buyers the benchmark and the deprecation notice are worth more than the price concession you would trade to keep them. Procurement will not see it that way, because a discount appears in the savings number and a benchmark clause appears nowhere. That is a reporting artifact rather than a judgment, and it is worth naming out loud before the negotiation rather than after.

One tactical note. Ask for these early, in the first commercial conversation, framed as how we work rather than as demands. A clause introduced in week two is a requirement. The same clause introduced in week nine, after the shortlist is public and your sponsor has told the board, is a problem you are creating for a deal everyone now expects to close.

The list you already have

If you have been keeping the running list from your reference calls, the answers to what would you put in the contract if you were signing again, this is where it earns its keep.

Those answers tend to be narrow and specific in a way that generic templates are not. A named support contact. A cap on the annual uplift. The right to add users mid-term at the original rate. Notice on a change to how consumption is counted. Every one of them came from somebody who learned it at their own expense, and there is no cheaper source of contract language anywhere in this process.

One thing to do differently

Put a benchmark in the contract. Twenty of your own cases, an agreed threshold, re-run quarterly, with a stated consequence if it fails.

It takes an afternoon to assemble and it converts the most likely failure in this category, quiet degradation that nobody can prove, from a disagreement into a clause.

In Practice: The Other Side of the Table | Lesson 11: Diligence That Is Not a Questionnaire

You have a security questionnaire. It runs to several hundred rows, it was written for hosted software, and the vendor will complete it in two days using answers they have given ninety times before.

What comes back tells you the vendor can complete a questionnaire. That is a real signal about organizational maturity and it is not the same thing as having done diligence.

Two weeks to answer a simple question

Composite from a few evaluations in devolved organizations: a research university group, several faculties, federated IT, a purchase covering research administration and grant documentation.

The questionnaire came back complete. Certifications attached, everything in order, no red flags. Procurement signed it off in a week, which was fast and felt like a win.

About nine months later a faculty raised a query about where a particular category of data had been processed during the previous quarter. Nothing had gone wrong. Nobody had been breached. But a subprocessor in the chain had changed, the notice had gone to a shared procurement mailbox that nobody monitored, and it took roughly two weeks to assemble an answer to a question that should have taken an afternoon.

The questionnaire had asked whether the vendor used subprocessors. It had not asked how the university would find out when the list changed, and that is the question that mattered.

Why the form misses

Four structural reasons, none of which involve anyone cutting corners.

It asks about controls in general rather than about your deployment in particular. It is answered by a compliance function rather than by the people who operate the system. It captures a point in time, and the product you are buying changes monthly. And it was written for a category where the software you license is the software you run, which is not the arrangement here.

That last one matters most. Most products in this category sit on capability the vendor does not own, served from infrastructure they do not run, and the questionnaire has no row for that.

Five questions instead

Run these as a conversation, forty-five minutes, with the vendor’s engineering lead in the room rather than their compliance team. Insist on that. The whole value is in the follow-up questions, and a compliance function cannot answer follow-ups.

One. Where does our data go, every hop, and how will we be told when that list changes?

Not whether they use subprocessors. The list, the notification mechanism, the notice period, and which address it goes to. The mechanism is the part everyone forgets and the part that failed at the university.

Two. What of ours is retained, for how long, and what is derived from it that survives deletion?

Deleting source data does not necessarily remove what was built from it. Indexes, embeddings, caches, logs, evaluation sets, corrections your users made. This is the question with the widest range of answers in the industry right now, which is exactly why it is worth asking.

Three. Who at your company can see our data, in what circumstances, and can we see that access?

Support debugging is the usual route and it is entirely legitimate. You want to know the path exists, what triggers it, whether it requires customer approval, and whether the log is visible to you or only to them.

Four. What changed in the last twelve months that you were not obliged to tell customers about?

This surfaces the entire class of change that sits outside contractual notice provisions. It is also an excellent question for a reference call, where you will sometimes get a more complete answer.

Five. Show me your last incident and the write-up.

Not whether they have had incidents. Every operation running at scale has. A vendor who produces a post-incident review, even heavily redacted, is showing you how they operate more convincingly than any certificate. A vendor who says they have not had one is either very new or not counting the same things you would.

Keep the form

None of this is an argument for skipping the questionnaire. Send it. Your own audit function needs it, a vendor who cannot complete one is telling you something real about their maturity, and comparing completed forms across three vendors does occasionally surface a genuine difference.

The mistake is treating a completed form as a finished investigation. The form is the floor. The forty-five minute conversation is the diligence, and it costs less than the week your team will spend reconciling three completed spreadsheets.

One thing to do differently

Ask question two in writing, and keep the written answer.

What is derived from our data, and what survives deletion. It is the question where answers vary most between vendors, it is the one your data protection colleagues will come back to in year two, and a written answer given during evaluation is worth considerably more than a verbal reassurance you half remember.