The year-end planning deck has a new row in it, somewhere between headcount and travel, and the row says "AI." Your boss reads it aloud in the Thursday meeting and then looks up and asks, pleasantly, "So what did it actually save us this year?"
You have the invoice for the licences. You have a general feeling that the team writes first drafts faster than it used to. You have one very good story about a report that took an afternoon instead of two days. You do not have a spreadsheet, because nobody set one up in January, and in January nobody asked.
I'd resist the urge to dress it up. The honest answer is better than the impressive one, and it is also easier to write. A manager who says "it made us a lot faster across the board" gets one follow-up question and then has nothing underneath the number. A manager who says "here are three things we do differently, and here is what I can't tell you yet" tends to get a nod and a budget conversation that goes fine.
The good news is that you do not need to rebuild the year from memory. You need a short answer with three parts, written down before the question gets asked again.
Why a single number backfires
Everyone wants one figure, and I understand why. A figure fits on a slide, and a slide travels upward without you.
The trouble is that a made-up figure has to be defended, and you will be the one defending it. Somebody will ask how it was measured. Somebody in finance will multiply it by the number of people on your team and by an hourly cost, and the result will look wonderful and will be wrong in a way that is hard to take back.
There is also a quieter problem. Time saved is rarely a clean subtraction. The hour you saved on drafting may have gone into checking, and the checking is real work. Some of the saved time went into more output rather than into getting hours back. Some of it went into a task the team now does that it simply skipped before. All of that is fine, and none of it fits in one tidy percentage.
So I would not try to produce a precise number. I would produce a range you believe, attached to a task your boss can picture.
The one move: a three-part answer
Write three short paragraphs. Each one answers a different question your boss is really asking.
Part one: time saved on named, recurring tasks. Pick two or three jobs that happen every week or every month, and name them. For example, the weekly status summary, the first pass at customer replies, or the notes and follow-ups after meetings. Say roughly how long each took before and roughly how long it takes now, with the checking included, as a range. If you do not know, say "I think" and give the range you would defend over lunch.
Part two: quality or speed changes you can point to. This is the part with no clock in it. Something got better or faster, and a person outside your team could notice. Proposals go out the same day rather than the next. Fewer corrections come back from the people who read your reports. A new hire got up to speed on the process quicker because the team had written things down for the tool. Pick one or two and name them. If you cannot name one, say so, because that is also true and useful.
Part three: one thing the team stopped doing. This is the one I would never leave out. Any manager can say what was added. The one that earns trust is a line like "we no longer write the monthly summary by hand" or "we stopped asking the vendor for the second round of edits." It shows that AI replaced work rather than only adding to the pile.
After those three, add two sentences that carry most of the weight. First, what you don't know yet. Second, how you will find out.
What it sounds like
Here is the shape. The figures below are an example, so replace them with your own, and if you do not have them, use words.
What AI saved us this year: [team], [year]
Time. On the weekly status summary, we went from [an hour or so] to [about fifteen to thirty minutes], including the read-through. On first drafts of customer replies, [two or three people save somewhere between a few minutes and a quarter of an hour per reply]. I'd call the overall effect [a few hours a week across the team], and I would not put a tighter number on it than that.
Speed and quality. [Proposals now go out the same day we receive the request.] [We get fewer back-and-forth corrections on the monthly report.]
What we stopped doing. [We no longer write the meeting follow-ups by hand.]
What I don't know yet. I don't have a clean before-and-after for [the tasks we only started using it on in the spring], and I haven't tracked how much time the checking takes. The licence cost is [amount], so the honest comparison is that the time saved looks larger than that cost, and I can't yet prove it to the minute.
How I'll measure it next year. Starting in [month], [one person] will log the time for the three recurring tasks above for [two weeks each quarter], so we have our own numbers by the next review.
Read it again as the boss. It is short, it names real work, it admits the gap, and it ends on a plan. Nobody can poke a hole in a paragraph that already contains the hole and a way to fill it.
When the boss pushes for one number
It will happen, probably in the same meeting. Do not give in and invent a figure on the spot. I would say this:
"If you need one number for the deck, I'd say it's in the range of [a few hours a week for the team]. I'd rather give you a range I can stand behind than a precise figure I'd have to walk back. By next review I'll have measured it properly."
Then stop talking. The pause that follows is usually shorter than you fear, and it is almost always followed by "that's fine."
If your boss's boss is the one asking, the same three parts work. They tend to care most about part three, the thing you stopped doing, because it sounds like a decision rather than a hope.
A few ways to make the honest answer stronger
Name the people. "Maria's team stopped hand-writing the weekly summary" is more believable than "the team improved." Ask the people who did the work to give you their own estimate in one line, then use the range they give you rather than your own memory.
Count the checking. If your team spends time reading what the tool produced and fixing it, include that. It is part of the real cost, and saying so makes everything else you claim easier to believe.
Leave out the tasks where it didn't help. Mention one if it is useful to your boss. A manager who says "we tried it on contract summaries and it wasn't worth it, so we dropped it" sounds like someone who runs a careful operation. That is exactly the impression you want when the money question comes up.
What this gets you
By Friday you can have a half-page that you could hand to your boss, forward upward, or read aloud. You will not have a number you are afraid of, and you will not be the person who says "I'll get back to you" in the room. Next year, the question will arrive on a day when you already have the log.
Write the three parts tonight, while the year is still in your head. Then enjoy the Thursday meeting, because for once you will know what you are going to say.
P.S.
If you'd like a structured way to see where your team stands before next year's tracking starts, The AI Readiness Self-Audit walks through it on a few pages. ($19. The three-part answer above works on its own.)
This was a free one. There's a new one every week.
What's signal in the AI noise — and the move to make about it. No hype, no vendor pitch, no link dump.
Aiden Vector is an AI-assisted publication; this content is produced by AI under human editorial direction.