The Deliverable Was Always the Receipt — Altvina Altvina Insights

Published July 8, 2026 · Altvina Insights · 6 min read

The Deliverable Was Always the Receipt

When a client asks for the AI discount, one common reason is that they are reading your invoice exactly as it was written. The repair is a page problem, and the whole repair is below.

At some point, possibly this year, a client may ask whether your fee should come down now that AI is speeding up work like yours. Productive's 2025 report Agencies in the AI Era, drawn from a survey of 180 agencies, found that around a third had already been asked for an AI discount, and nearly half expected to hear the question soon. That is one survey of one corner of the services world, so hold the numbers loosely. The direction, though, is hard to miss. The question is in circulation, and it could reach firms like yours.

The instinct when it lands is to prepare a defense. Most of the published advice coaches exactly that: hold the price, restate your value, do not blink. All of it treats the client as an opponent making an opening move.

Clients ask for different reasons, and some really are negotiating. But one common version of the moment, often overlooked, looks like this from the client's chair. They opened your last invoice and saw what service invoices usually say: hours, days, drafts, revisions, preparation. Units of effort, priced. Then they read, more or less everywhere, that effort like this is getting faster. They put the two together, exactly as the page invited them to.

A client in that position is doing something simpler than negotiating. They are reading. Hours were the only legible unit on the page, so hours are what they read. The discount request is their reading handed back to you, and the reading is correct.

The invoice taught them how to read it

Every invoice teaches its reader what the fee is made of. If every line is denominated in time, the lesson is that the fee is made of time, and a fee made of time should shrink when the time does. That conclusion follows directly from the page. Nothing on it ever offered the client another unit to read.

This is worth sitting with, because it relocates the problem. When the request grows out of this kind of reading, the client is not confused, and the client is not squeezing. The page was illegible about what the fee actually bought, and the client read the only thing it said clearly. Before there is a conversation to have, there is a page to fix.

Run the legibility test

Pick any line item from the last invoice you sent. One is enough.

Ask a single question about it: could the client say what that line bought without mentioning time?

If the answer is no, that line is illegible, and a discount request was always a live risk, AI or no AI. Sooner or later something was likely to make the work visibly faster. A tool, a template, a hire who happens to be quick. The page had nothing else for the client to hold on to. AI simply arrived first, and arrived loudly.

Run the test on two or three more lines if you want a pattern instead of a data point. Service invoices tend to lean heavily on effort language, so do not be surprised if most lines fail.

Rewrite one line item: from hours to judgment

Here is the repair pattern. The example is generic, written for this article; it does not come from any client document.

Before: "Market and competitive analysis: research, drafting, and revisions. 24 hours."

After: "Market and competitive analysis: a recommendation on which two offerings to wind down and which one to defend, with the reasoning laid out so the partners can decide once and move."

The before line prices effort, and effort is exactly what the tools are making cheaper. The after line prices a judgment the client could not safely make alone, plus accountability for being right about it. Notice that time never appears. What the client downloads at the end was always the receipt for that judgment; what they bought was the call you made and your name under it.

Notice also what happens to each line when drafting accelerates. The first one loses its justification. The second one does not move, because drafting was never what it priced.

You do not need to rebuild your billing system this week. One line on the next proposal, translated from effort into judgment and outcome, starts teaching the new reading.

To be clear about what this is not: it is not the old sermon about abandoning hourly billing. Keep billing hours if hours are genuinely what a line buys. The question is narrower: whatever the unit, can the client read what they got for it?

The conversation, calmly: what to say when a client asks for the AI discount

If the question has already arrived, the rewritten page comes too late for this round, so here is the conversation. It assumes the request grew out of the reading described above; if a client is simply squeezing, you will usually hear it in how they respond to the first move. Four moves, in words you can adapt to your own register. None of them cave, and none of them bluster.

First, agree with their reading. "You are reading the invoice correctly. We have always shown you effort, and the effort is getting faster."

Second, name what the fee actually priced. "What got faster is production. What you hire us for is deciding what to recommend and standing behind it, and that part did not move."

Third, own the page. "Our invoices made effort the headline. That was our writing choice, and the next one will say plainly what each line buys you."

Fourth, reprice only what honesty requires. "Where a line really was buying hours and nothing else, we will reprice it. Where it was buying judgment, the number holds, and now the page will say why."

That is the whole script.

AI did not write your invoice

It is tempting to file this whole subject under AI problems. It does not belong there.

Invoices were illegible about judgment long before any of the current tools existed. What changed is visibility. Clients everywhere are reading the same stories about work getting faster, which means illegible invoices are being reread, at roughly the same time, with the same question in mind. AI did not break the invoice. It made the illegibility visible at scale.

That is uncomfortable, and it is also useful. A lesson this clarifying usually costs a lost client to learn. Right now it is arriving as a polite question instead.

Everything above is yours to keep. Run the test on your last invoice today. Translate one line on your next proposal. Keep the script for the day the question shows up. And if it already has, there is a good chance the client was asking for something simpler than a discount: a page they could read.

Continue the series

This is part 3 of a 5-part series on Both Columns, Honestly. The full arc:

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.