How to Scope a Content Project When AI Is Part of Your Process
Lee Harris·
Project scoping for content work before AI was reasonably straightforward: research, outline, draft, revisions. Each stage had a rough time estimate based on piece length and topic complexity. The total was the production time. Multiply by your hourly equivalent and add overhead.
AI changes the time distribution between stages without reducing the total time as much as it appears to. Brief writing takes longer than pre-AI outlining. Drafting takes less time. Editing takes comparable time. Revisions are unchanged. The total reduction is real but smaller than the drafting time savings suggest, and the distribution of effort is different from what clients may expect.
What scoping needs to account for now
Brief development time. A complete AI brief takes 15 to 25 minutes per piece to write. For a project of 10 articles, that is three to four hours of brief development before any drafting begins. Pre-AI workflows buried this in the outlining step, which was often shorter. The brief is now a more explicit and time-intensive step.
Generation and first-pass review. Generating a draft and doing the first structural review is faster than drafting from scratch. For a 1,200-word piece, this step is now 45 to 60 minutes rather than two to three hours.
Voice and accuracy editing. Editing time per piece has dropped, but not by the same proportion as drafting time. The accuracy pass is roughly unchanged. The voice pass is faster on a well-briefed piece than on a self-written draft. Total editing time might be 45 minutes rather than 60 to 90. Not negligible.
Client-specific setup. For a new client, the first two or three pieces in a project require additional time to calibrate the system prompt and brief template to their voice and content requirements. This setup time does not appear in per-piece estimates but should appear in project estimates.
Turnaround time
Turnaround is faster with AI, but not as fast as the drafting time reduction implies. A piece that previously required a three-day turnaround might now require one and a half to two days, accounting for the brief development, generation, editing, and the time to review with fresh eyes before sending.
Clients who have heard about AI writing tools often expect faster turnaround than is realistic. "Same-day" is achievable for short pieces with a complete brief and a calibrated system prompt. It is not the default for complex pieces that require research and multiple editing passes.
Setting accurate turnaround expectations upfront prevents the conversation where the client wonders why an "AI-assisted" project took as long as a traditional one. The answer is that the time was redistributed, not eliminated.
Protecting your margins
The risk in AI-assisted project scoping is underestimating based on the drafting time reduction and then absorbing the time in editing, brief development, and revision cycles.
The practical protection: scope at realistic total production time, not at drafting time. A 10-piece project at 90 minutes realistic production time per piece is 15 hours of production, regardless of how that 15 hours is distributed between stages. Quote the total, not the drafting step.
Revision rounds are unchanged and should be scoped the same way they were before AI. AI does not reduce the probability that a client will want changes. It may slightly change the nature of the changes, since AI-assisted drafts sometimes have voice issues the client notices even if they cannot name them. Budget for the same revision allowance as before.
The rate question
Per-article rates that were set before AI are often still defensible after AI, if the output quality is maintained. The rate covers the outcome, not the hours. If the outcome is the same, the rate is the same.
Where the rate conversation becomes necessary is on projects where the scope has changed significantly: where the AI workflow allows you to produce pieces in half the time at the same quality, and the client is doing the arithmetic. That conversation is worth having proactively rather than defensively.
More from this topic
How AI Changes the Math on Per-Article Freelance Rates
If AI cuts production time by half, the per-hour rate on a fixed-price project doubles. What that means for pricing, what to do about it, and why not every client relationship survives the change.
What to Tell Clients Who Ask If You Use AI
The question is coming if it hasn't already. What the honest answer looks like, why transparency tends to hold up better than avoidance, and what clients are usually actually asking.
Building a Content Calendar You Can Actually Maintain Alone
For solo operators who own the whole content operation. How to plan a publishing schedule that accounts for AI-assisted production times, batching, and the weeks where nothing goes as planned.
Taking on More Clients Without Working More Hours
The capacity problem is where AI-assisted workflows earn their place. What a higher-volume practice looks like in practice, where the new bottlenecks are, and what breaks first when you push it.