Problem: AI saves me 60 to 80% of my time on routine PPC tasks. A Google Ads audit, which used to take me 3–4 hours, now takes about an hour (25–35 min agent run + 30–60 min review). A KW gap analysis, for which I used to set aside half a day, the agent spits out in 25 minutes. With classic hourly billing, it raises a clear question: how the hell do I bill the client so it’s fair?
The standard advice from most specialists is: “Estimate how much time you would have spent on it manually if you didn’t have AI, and bill the client that amount.” I disagree—and in this article, I’ll describe what I do instead, based on 17 agent runs over the last week in my internal app. At the end, I’ll offer how I can help you adopt the same approach if you’re dealing with the same thing.
Why "estimating manual time" doesn't work
This advice has three serious problems:
The client is paying for fiction. If I put “4-hour audit” in the timesheet, but it was actually a 40-minute review of an agent’s work, the client is paying for a situation that never happened. It’s not a lie, but it is dishonest.
Erosion of trust once the client finds out. And they will find out. They see how fast some outputs arrive. They hear about AI on podcasts. At that point, they’ll ask: “how many other things are being billed fictitiously?”
It disadvantages those who use AI honestly. If I bill “manual” time while a colleague who doesn’t use AI bills actual time, the client gets more human-hours from her for the same price. This penalizes the person who automates — legitimately.
Plus, I have a fourth reason that’s harder to articulate: I’ve always built my freelance brand on transparency. “Estimating manual time” goes directly against that.
My approach: a script in Marketak App + the same hourly rate.
In my internal vibecoded app Marketak-app, a timer runs every time an AI agent is triggered. It tracks the start time, end time, client, template, model, and status. These entries go into the same DB table as my manual time tracking. The monthly report shows both side by side.
Key decision: I bill the client for AI time at the same hourly rate as my manual work (for me, that’s 1,200–1,400 CZK/h). An hour of work is an hour of work, whether it’s done by my brain or an agent I’ve set up. A discount would demotivate me from improving the workflow. A markup would be a gimmick. The rate stays.
Tracking has been live since May 21, 2026 — one week in production. The numbers will grow, but they already highlight three things worth your attention.
Data after 7 days of tracking
| Metric | Value |
|---|---|
| Agent runs (completed) | 17 |
| Unique clients | 12 |
| Cumulative AI compute time | 7.5 h |
| Average run length | 26.6 min |
| Median | 29.1 min |
Top 3 templates: audit (6 runs), custom prompt (6 runs), kw-diff (5 runs).
Models: 100% Opus 4.7. No Sonnet, no Haiku.
Three quick insights:
1. I use 100% Opus even for routine tasks. Most guides say “use a cheap model for batching.” I do the opposite—because AI compute is a drop in the bucket in the task economy (you’ll see in the next section) and an hour of my review time is expensive. If Opus cuts the number of iterations from two down to one, it more than pays for itself compared to the compute costs.
2. Custom accounts for 35% of runs. Six out of seventeen tasks weren’t via a template, but an ad-hoc prompt. This means the “AI team” isn’t a production line—templates cover 65% of the routine, the rest are “tasks that are always a bit different.” This has a pricing impact: custom runs cost the client more due to the longer setup.
3. 12 clients / 17 runs = 1.4 runs per client. A realistic baseline for a freelancer with 15–20 active clients. Not every client needs an agent run every week.
Compute vs. review math
Cost breakdown for a typical 26.6-minute audit run at my rate of 1,300 CZK/h:
| Item | Value |
|---|---|
| AI compute (hard cost, Opus 4.7) | 133 CZK |
| Price to the client for the AI run | 577 CZK |
| Plus review entry (30–60 min) | 650–1,300 CZK |
| Total client pays for the audit | 1,227–1,877 CZK |
| Traditional manual audit (3–4 h × 1,300) | 3,900–5,200 CZK |
| Client savings | 60–76 % |
AI compute for the audit costs 133 CZK. The client pays for it within the 577 CZK AI run price. The vast majority of the payment (444 CZK out of 577 + the entire 650–1,300 CZK review) goes toward my expertise in task specification and review — which is what the client hires me for.
This leads to two conclusions:
- The client isn’t overpaying for AI. Compute accounts for 7 % of the total audit price. AI is a multiplier for my expertise, not a replacement for it.
- My hourly rate is justifiable. The 1,300 CZK/h rate covers my investment in templates, prompt engineering, MCP infrastructure, and review frameworks. Without that investment, this pricing wouldn’t make sense.
A bonus the table doesn’t capture: parallelism. Unlike my attention — which is always singular — agent runs can run concurrently. While an audit for Client A is running for 30 minutes, I can fire up a kw-diff for Client B and start reviewing a third output. One person generates output for three clients simultaneously — a ceiling you just can’t hit without AI. That’s why my total capacity is growing, even with lower billing per task.
Marketing debt: where the saved time goes
I don’t pocket the time I save; I reinvest it into my clients’ accounts. For one of my e-commerce clients, over the course of 6 weeks—despite lower overall billing—I’ve managed to:
- Perform a deep-dive product feed audit (dozens of rules in Mergado)
- Rebuild RSAs across 12 campaigns (15 unique headlines per ad group)
- Update GTM for upcoming changes
- Prepare a customer-match list from surface analytics for retargeting
None of these things would have made the cut in traditional billing—they were always on the “someday” list. AI turned that “someday” into reality. I’m upfront with the client: “I’m billing you less this month. Here’s what I did with the time I saved.” The feedback has been great.
Boundaries and oversight
Not everything can be automated. Templates cover ~65% of typical work. Strategy, client communication, creative direction, and custom integrations remain manual. I bill these tasks as traditional work.
Oversight isn’t going anywhere. A 25–35 minute agent run means 30–60 minutes of reviewing the output — going through recommendations, filtering out the ones I don’t accept, and adding comments for the client. This review goes into my manual billing.
Never write without confirmation. An agent can suggest a change in the account, but I always write to the account manually. The reason: misleading ads, poorly set audiences, geo bids — these are risks the model can cause and a client wouldn’t be able to spot. Senior — that’s me. Junior — that’s AI.
What’s going to change in the market over the next 12–24 months
A race to the bottom for certain services. A Google Ads audit for 990 Kč will be a real offer. Some agencies will dump their prices. This will hurt those who don’t use AI effectively and benefit clients who only want routine service.
Premium rates going up for strategic work. A marketer who can combine strategy + AI orchestration + human review will be more valuable than ever. Clients won’t pay for hours, but for access to expertise that knows when to use AI and when not to.
Transparent pricing as a differentiator. Clients will learn to ask: “Do you use AI? How do you bill for it?” Those who can answer honestly (and ideally show tracking, like I do in this article) will be in a better position than those doing it secretly.
The end of hourly billing as the only model. Subscription / retainer + performance bonus + transparent AI tracking will become the new normal for long-term relationships. Hourly rates will survive for ad-hoc projects and audits.
A short prediction: in two years, “how many AI hours are you billing me?” will be just as standard a question as “do you have ISO certification?” is today. You’d better start preparing your answer now.
It's not a question of how, but when!
Got a question? Just drop me a line at [email protected] or via the contact form. For more context, I recommend the article about the marketer’s AI team, where I describe what my AI workflow looks like.