
Published July 30, 2026 · Altvina Insights · 5 min read
A Client Asked Whether AI Should Make the Work Cheaper
A faster tool does not settle a pricing decision. Use this before you answer a client, change a fee, or promise savings you have not measured.
The short version: Compare the full cost to serve the client before and after AI, then separately assess scope, outcome, speed, assurance, and risk. Your contract and pricing model determine what the client should see. Tool speed alone does not.
The client question is fair:
You are using AI now. Should this work cost us less?
The two easiest answers are both weak.
"No, because you pay for the outcome" ignores the possibility that the work really did become cheaper or materially different.
"Yes, because AI is faster" ignores setup, review, rework, tool cost, risk, and the agreement already in place.
If you do not have the numbers yet, use a holding sentence:
"A fair question. I want to answer it from real delivery numbers rather than a guess, so let me pull those first."
Then pull more than the tool bill.
1. Restate what the client bought
Start with the agreement, not the software.
Write down:
- the promised outcome or deliverable;
- the included scope and exclusions;
- the expected turnaround;
- the review and assurance level;
- who carries error, confidentiality, compliance, and rework risk;
- the pricing model: fixed fee, retainer, time and materials, or another structure.
If AI changed none of those, the client did not automatically receive a different product. If AI changed one of them, name the change before discussing price.
2. Compare total cost to serve
Build the same table for a few comparable pieces of work before and after the workflow changed.
| Cost or effort | Before | After | Evidence |
|---|---|---|---|
| Hands-on production time | Time record or sample | ||
| Prompting, setup, and data preparation | Time record | ||
| Human review and fact checking | Review log | ||
| Rework and error correction | Revision history | ||
| AI and software cost | Invoice or usage report | ||
| Client coordination | Calendar or project record | ||
| Security, legal, or compliance review | Required checks | ||
| Total cycle time | Start and finish dates | ||
| Total direct cost to serve | Hours at direct cost plus tools |
Do not use one unusually good task as the baseline. Use a small repeatable sample.
Here is why. Suppose a job previously took 20 production hours and 4 review hours at an average direct cost of $70 an hour. Direct cost was $1,680.
If the AI-assisted version takes 10 production hours, 2 setup hours, 8 review and correction hours, plus $150 in tools, direct cost is $1,550. The job became faster in production, but total direct cost fell only $130.
If a stable workflow later takes 10 production hours, 2 review hours, and $150 in tools, direct cost is $990. That is a meaningful cost change.
Neither example determines the price by itself. It gives you a defensible cost baseline.
3. Measure what changed for the client
Cost is one input. The client decision also includes:
- Scope: Are they receiving the same work, less work, or more?
- Outcome: Is the result equally useful?
- Turnaround: Does faster delivery matter to them?
- Assurance: Is human review equal, stronger, or weaker?
- Risk: Who absorbs an error, leak, missed fact, or compliance failure?
- Capacity: Are savings being used to improve this engagement or serve more work elsewhere?
A lower internal cost may restore a margin that had been too thin. It may fund stronger review. It may support faster delivery. It may justify a lower fee. Those are business choices, not automatic consequences of using a tool.
4. Apply the pricing model
| Pricing model | What the client can reasonably expect |
|---|---|
| Fixed fee | The agreed fee follows the promised scope and outcome. Discuss a change when the product, risk, or renewal terms change. |
| Retainer | Revisit capacity, response time, included output, and exceptions at renewal. |
| Time and materials | If fewer approved billable hours are worked, the invoice should normally reflect the contract's actual billing basis. |
| Trades or field service | Faster estimating, dispatch, or paperwork may improve response time without changing job labor, material, warranty, or safety obligations. |
Honor the contract first. If the agreement is unclear, fix that before turning a workflow change into a pricing promise.
5. Choose the response you can defend
Use this decision screen:
| What the evidence says | Defensible response |
|---|---|
| Cost, scope, assurance, and risk are materially unchanged | Keep the price and explain what the fee covers |
| Stable cost savings, same outcome, same assurance | Decide whether to reduce price, improve service, shorten turnaround, or restore margin |
| Production is faster, but review or rework grew | Do not claim savings yet; redesign and measure again |
| The client receives less scope or assurance | Change the offer or price rather than hiding the reduction |
| The contract bills actual hours | Follow the contracted billing basis |
A complete reply
Once you have the evidence, the reply can be plain:
"We reviewed the full workflow, including setup, tool cost, human review, and rework. The deliverable, turnaround, and assurance you receive are [unchanged/changed in these ways]. Under our [fixed-fee/retainer/time-and-materials] agreement, we are [keeping/changing] the fee because [specific reason]. We will review the numbers again on [date] after [sample size or milestone]."
The brackets are the work. If you cannot fill them with evidence, keep measuring.
AI can change how work is produced. Price should change only when the economics, agreement, or client value gives you a reason you can explain without bluffing.
This article is for general informational purposes only. It is not financial, legal, or professional advice. Review your contracts and decisions with qualified advisors.
AI assisted with the draft. Altvina is responsible for the final published version.
More from this week
This piece stands on its own. This week's 5 pieces all look at When Busy, Profit, and Cash Disagree:
- Monday: Booked Solid, Less Cash: Find Which Number Changed
- Tuesday: Before You Cut Non-Client Time, Classify It (coming Tuesday)
- Wednesday: Project Contribution Is Not the Same as Project Profit (coming Wednesday)
- Thursday: A Client Asked Whether AI Should Make the Work Cheaper (this post)
- Friday: Fix It Now or Wait: A Decision Table With the Cost of Both (coming Friday)
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.