Skip to content
All articles

Review AI content like a manager, not a copy editor

Most founders review AI drafts at the comma level. The output that compounds comes from a manager-style review focused on strategy and judgment.

Jared Castronova
ai content founders review b2b-saas

Most founders reviewing AI-generated content are doing it wrong. They open the draft and start hunting for typos. They flip tenses. They split long sentences. They fix line breaks. Forty-five minutes later they’ve moved a few commas and not changed the strategic value of the piece at all.

The output that compounds for content engines comes from a different mode. Review AI drafts the way a manager reviews a junior employee’s work: strategy first, judgment second, taste third, typos last (if at all). The agent can handle the copy-editing layer. The agent cannot decide whether the piece should exist in the form it’s in.

This is the practical extension of the framing I covered in AI agents are your new employees. If the agent is an employee, your job is to manage the output, not proofread it.

What copy-editor review looks like (and why it fails)

The copy-editor review is the default mode for anyone who’s been writing professionally for a while. You read every sentence. You catch the awkward phrasing, the missing article, the slightly off-key word choice. You polish.

For human-written work, this is the right mode. The writer made strategic decisions you trust, and your job is to carry them clean to the page.

For AI-generated work, copy-editor review wastes your time. The output is already smooth at the sentence level (smoother than most humans’ first drafts, in fact). The gap shows up one layer above: did this piece make the right choices about angle, source, and stance?

Dan Shipper at Every has been writing about this gap for the past year. The bottleneck in AI-augmented work is whether the person reviewing it has the taste to push back at the right level. The writing is already fine.

The three review modes (and when each is right)

A manager-style review has three distinct passes. Most founders skip the first two and only do the third.

Pass 1: Strategy review. Is the angle right? Does this piece take a stance worth taking? Does it argue for something the founder actually believes? If the answer to any of those is no, the rest of the review doesn’t matter. Kill the draft, regenerate with a sharper brief, save the typo-hunting for later.

Pass 2: Judgment review. Does the piece cite sources that actually back the claims? Does it use the founder’s voice (per the decision-based voice doc)? Does it include the structural elements your content requires (internal links, external citations, a real CTA)? This pass catches the things that make AI content read like AI content: vague attributions, fake-sounding stats, missing inline citations, generic close-outs.

Pass 3: Taste review. Does it read like the founder would actually say it out loud? Is there a single line that’s too polished to be human, too clever to be honest? Cut those lines. They’re the AI tells.

Sentence-level edits, if you need them at all, come after these three. By the time you’ve done passes 1-3, the prose either holds up or you’ve regenerated. Most of the time the prose is fine; the issue is upstream.

Will Larson has written a lot about management review patterns for engineering work, and the framework transfers almost directly to content. Review the decisions, then the execution. Most managers reverse the order and produce worse output.

The five-question manager review

The actual checklist I run on every AI-generated draft before it ships:

  1. What’s the one thing this piece is saying? If I can’t summarize the argument in a single sentence, the piece doesn’t have a strong enough angle. Regenerate.
  2. Who would disagree with this, and why? If nobody reasonable would disagree, the piece is generic. Regenerate with a sharper position.
  3. What’s the strongest external proof point cited? If the answer is “none” or “a vague reference to ‘experts say,’” the piece is weak. Add real sources or regenerate.
  4. Where is the founder’s actual voice on the page? If the piece could have been written by any marketer in the category, it’s not a JAC piece. Tune the prompt or rewrite the opening manually.
  5. What’s the specific action the reader takes after reading? If the close is “exciting times ahead” or “let me know what you think,” that’s a draft. Rewrite the close.

If a piece passes all five, ship it. The prose is fine. If it fails any of them, the fix is upstream of the typos.

The shift in time allocation

Founders running content engines with this review pattern spend their time differently than founders who don’t. The copy-editor mode eats 45 minutes per piece. The manager mode takes 10. The leftover 35 minutes goes into the briefing layer: writing sharper prompts, capturing better source material, tightening the voice doc.

Reforge has documented this time-allocation shift in their work on AI-augmented marketing teams. The pattern is consistent: the teams shipping the most compounding output spend less time editing and more time briefing.

How to switch this week

Three concrete moves:

  1. The next time an AI draft lands in your inbox, set a 12-minute timer. Run the five-question manager review. Make a decision: ship it, regenerate it, or rewrite the opening manually. Don’t touch the commas.
  2. If you regenerated, look at what you changed in the prompt. That’s the piece of feedback to fold into your voice doc or your brief template for next time.
  3. After two weeks of this, audit your time. Most founders find they’re spending half as long per piece and the pieces are getting more replies.

If you want help setting up the briefing and review layer of a content engine that produces work you actually want to ship, book a call. The review pattern is one of the smaller pieces, and it’s the one that compounds fastest.

Jared Castronova is the founder of JAC Growth Marketing, where he builds AI-powered GTM systems for B2B companies.

Want a content engine that publishes for you?

See how it helps you