Before I built skills, 1 LinkedIn post cost me somewhere between 10 and 50 back-and-forth prompts.
I never counted that at the time. Nobody does. You open the chat, you wrestle with it, something comes out, you move on. It's only when I started logging hours per client that the ratio showed up, and once I saw it I could not unsee it.
If you want to automate content creation with AI, this is the math to do first. Not "how fast can it write." Hours in, assets out, per month. Everything else is a feeling.
TLDR
- The only ratio that matters is hours spent divided by assets that shipped. Most people have never computed it.
- My number per client was 12 hours a month. It went to 3.5. The model did not change. The gate did.
- A coach I work with produced 11 weeks of content in 1 day. That is what the ratio looks like at the far end.
- You can do your own math in 10 minutes and I'll show you how.
- There's 1 number the math misses, and it's the one that decides whether the content works.
Hours In, Assets Out: The Only Ratio That Matters
Here's the exercise. Take the last 30 days. Count every piece of content that actually got published: posts, newsletters, emails, client documents. Not drafts. Shipped.
Now count the hours. Writing, yes, but also the prompting, the re-prompting, the "let me just fix this one paragraph," the Sunday night where you stared at a blank post for 40 minutes. Be honest about the Sunday night.
Divide. For most coaches and consultants I talk to, the number lands somewhere between 45 and 90 minutes per shipped asset, and a lot of that time is not writing. It's the work around the work. The reason the number is so high is the same reason I keep writing about: you're starting from scratch every time, when the material already exists.
Where the 12 Hours a Month Actually Went
When I logged a client at 12 hours a month, I expected the time to be in the writing. It wasn't.
Roughly, and I'm reconstructing this from a log I kept for a few weeks: about a third was producing drafts. A third was checking drafts, reading every line for the thing that sounded wrong. And a third was the loop between the two. Draft, check, fix, re-check. The 10 to 50 prompts per post lived almost entirely in that third bucket.
That's the part people miss when they say AI makes content faster. Drafting was never the slow part. Drafting was 4 hours of the 12. Judging was the other 8, and a faster model does nothing about judging.
From 12 Hours to 3.5: What Changed Was the Gate
The number moved when I stopped checking drafts and started building the thing that checks them.
Every draft now gets read back through fixed questions before I see it. My QA checklists run, I think, 20 to 40 filter points, and they carry the reference library of approved and rejected work so the check is against my client's standard, not a generic one. Anything that fails gets fixed before it reaches me. I audit the gate once a week instead of editing every draft.
12 hours became 3.5. Same clients, same volume, same models. The difference was pass/fail gates, which I've described in what broke across a year of production. The one that broke worst was "I was still the quality gate," and fixing that is where the 8.5 hours came from.
And honestly, I do not think the ratio has a floor I've found yet. A coach I work with knocked out 5 weeks of LinkedIn posts and 6 weeks of newsletters in 1 day last month, then sent me 10 weeks of email campaigns to proofread. 11 weeks of content in a day. My job that morning was a quality gate and a routing step. I read it and passed it to the person who publishes.
Do Your Own Math in 10 Minutes
Grab a notebook or a spreadsheet. 5 lines.
- Line 1. Assets shipped in the last 30 days, by type. Be strict. A draft in a folder is 0.
- Line 2. Hours spent, including the checking and the loop. If you don't know, estimate high. People always estimate low.
- Line 3. Line 2 divided by line 1. That's your cost per asset in hours.
- Line 4. Of the hours in line 2, how many were drafting versus judging? Most people find it's 1 to 2 at best.
- Line 5. Recordings, documents, and program material you already own and haven't touched. Count the files, not the hours.
Line 3 tells you the problem. Line 4 tells you the problem is not the writing. Line 5 tells you the raw material for fixing it is already in a folder. There's a longer version of this check in the free tools, but the 5 lines get you most of the way.
The Number That Math Doesn't Capture
I'd be lying if I ended on the ratio. Hours in, assets out measures efficiency. It says nothing about whether the assets sound like you or whether anyone reads them.
You can get your cost per asset to 10 minutes and ship 60 pieces a month that sound like everyone else. The ratio would look great. The business would not. That's the trap in most "AI content" pitches: they sell the denominator and ignore what's in the numerator.
So do the math, but do it in this order. First make the output pass your standard, which is the reference library and the gate. Then make it fast. A gate that produces work you'd sign is what let me cut 8.5 hours without the output getting worse. Cutting hours first and hoping the quality holds is how people end up with 200 posts and no clients.
If any of this sounds like your last 30 days, it's probably worth a conversation. Or do the 10-minute math, then send me 1 piece of your work. You get a finished asset back in your voice within 48 hours, and you'll see what the numerator looks like when the gate is built right.
FAQs about content production math
How do I calculate my content production cost?
Count every asset that actually shipped in the last 30 days, then count every hour spent on content including prompting, checking, and rework. Divide hours by assets. Most coaches and consultants land between 45 and 90 minutes per shipped piece, with most of the time going to judging drafts rather than writing them.
Does AI reduce content production time?
Only if it reduces the judging time, not just the drafting time. Drafting was about a third of my hours per client. The other two-thirds were checking and re-prompting. A verification loop and a quality gate cut my hours per client from 12 to 3.5 a month. A faster model alone would have cut almost nothing.
How much content can 1 person produce with an AI system?
A coach I work with produced 5 weeks of LinkedIn posts and 6 weeks of newsletters in 1 day, and my own throughput went up 2.5x across 15 clients per cycle. The ceiling is set by how much raw material you have and how good the gate is, not by the model.
What does the ratio miss?
Quality. Hours in, assets out says nothing about whether the output sounds like you or whether it converts. Fix the standard first with a reference library and a gate, then optimize speed. Speed first is how you get 200 posts that nobody reads.