You’ve seen the Twitter threads: “I wrote 50 blog posts with AI this week.” You’ve also read those posts. They’re terrible.

The good news: AI can genuinely cut a blog post from 4 hours to 30 minutes — but only if you stop using it as a generator and start using it as a co-writer. Here’s the exact workflow that works.

The 30-minute breakdown

PhaseTimeWhat you do
Research & angle8 minYou + AI
Outline5 minAI drafts, you fix
First draft10 minAI writes, you steer
Edit pass5 minYou only
Polish & publish2 minYou only

The trick isn’t “let AI do everything.” It’s letting AI do the slow parts and keeping the parts that matter to you.

Step 1: Pick the right tool for the job (1 minute)

Different tools, different jobs:

  • Research + first draft: Claude (Sonnet 4 or Opus). Best at long-form, nuanced writing.
  • Quick outlines + brainstorming: ChatGPT (free tier works fine).
  • Fact-checking + sources: Perplexity. It cites sources you can verify.
  • Final polish: Grammarly or Hemingway, not an LLM.

For this workflow, we’ll use Claude as the primary tool and Perplexity for fact-checks. Both have free tiers that handle this entire workflow.

Step 2: Lock the angle before writing anything (7 minutes)

This is where 90% of bad AI posts go wrong. They start with a topic (“write about productivity AI tools”) instead of an angle (“why most productivity AI tools waste more time than they save”).

Use this prompt to find your angle:

I want to write a blog post about [TOPIC].
My audience is [WHO].
The 3 most common takes on this topic are [LIST OR ASK ME].
Help me find an angle that is either:
(a) the opposite of common wisdom but defensible, or
(b) a more specific, actionable take than what's already out there.

Give me 5 angle options. For each, tell me what the headline would be and what the core argument is.

Pick the angle that makes you slightly nervous. That’s the one with a real reader.

Real example we used for this post:

  • ❌ “How to write a blog post with AI” (boring, 10,000 already exist)
  • ✅ “How to write a blog post with AI in 30 minutes without it sounding like AI” (specific, addresses real reader pain)

Step 3: Outline with AI, edit ruthlessly (5 minutes)

Once the angle is locked, ask Claude or ChatGPT for an outline:

Write an outline for a blog post titled "[TITLE]".
The angle is [ANGLE].
Audience is [WHO].
Goal: reader finishes with [SPECIFIC ACTION OR TAKEAWAY].

Format: H2 sections with 1-2 bullet points under each describing what goes in that section.

Constraints:
- Open with a hook that earns attention in the first 2 sentences
- No "in today's fast-paced world" intros
- Each section must answer a specific question the reader has
- End with one clear next step

Then delete a third of the outline. AI loves to add filler sections (“In conclusion…”, “The future of…”, “Why this matters…”). Cut anything that doesn’t directly serve the reader’s goal.

Step 4: First draft — section by section (10 minutes)

Don’t ask AI to write the whole post. The output is always longer, blander, and less useful than if you write section by section.

For each H2 in your outline:

Write the section titled "[SECTION NAME]" for a blog post about [TITLE].
- Length: 150-250 words
- Tone: Conversational, specific, slightly opinionated
- Include 1 concrete example or scenario
- Do NOT use these phrases: "in today's world", "leverage", "robust", "delve into", "navigate the landscape"
- Open with a sentence that's a claim or question, not a setup

The forbidden-phrase list is the secret sauce. Without it, AI produces beige content instinctively.

Pro move: Add this to every prompt: “Write like a smart friend explaining this over coffee, not a marketing department.”

Step 5: The edit pass — this is your job (5 minutes)

AI cannot do this step. You have to.

Read the draft out loud. Anywhere you stumble, rewrite it. Anywhere a sentence sounds like it could appear in any AI post on any topic, kill it.

Look for these AI tells and rip them out:

  • “It’s important to note that…”
  • “When it comes to…”
  • “In conclusion…”
  • “The key takeaway is…”
  • Lists of three where every item is the same length and structure
  • Generic “tips” that don’t commit to anything specific
  • Hedging language (“might be a great option for some users”) — replace with opinions

Add yourself back in:

  • One personal anecdote, even tiny (“I tried this last Tuesday”)
  • One specific number or example AI couldn’t have known
  • One opinion AI would have softened

These three additions take 5 minutes and are the entire difference between “AI slop” and “actually written by a human who used AI.”

Step 6: Polish + publish (2 minutes)

Run the final draft through Hemingway Editor (free, web-based). Aim for grade 8 or below. Cut adverbs, simplify sentences flagged as hard to read.

Don’t bother with Grammarly Premium for this — the free tier catches everything that matters.

Headlines: Use the formula [Specific outcome] in [Specific timeframe] (without [common objection]). The post you’re reading right now uses it.

Meta description: 150-160 characters, includes the primary keyword, ends with a curiosity gap or specific promise.

Publish.

What to never let AI do

  • Conclusions. They’re always generic. Write your own.
  • Headlines. AI headlines are SEO mush. Write your own.
  • Anecdotes. AI invents these. Don’t let it.
  • Numbers and stats. AI hallucinates these. Verify with Perplexity or skip them.
  • Opinions. AI hedges. Have a take.

The 30-minute reality check

Will every post hit 30 minutes? No. The first few will take you an hour while you’re learning the prompts. By post 5, you’ll be at 45 minutes. By post 10, 30 minutes is realistic.

The bottleneck isn’t typing speed — it’s angle clarity. Spend the 7 minutes upfront. The rest of the workflow rewards it.

Tools we mentioned (and our take on each)

If you want a deeper comparison of the writing AIs themselves, our ChatGPT vs Claude comparison covers which one to pick for which job.

Try this workflow on your next post and let us know how long it actually took you. We’re collecting timing data from readers — drop us a line via the contact page.