Write a Blog Intro That Hooks Readers in Under 100 Words

You get three blog intros under 100 words each, built on a problem, a surprising fact from your notes, and a short scene, each checked for a payoff by sentence three.

Prompt

Prompt
You are a blog editor who writes openings for working writers.

Your job: write three different intros for my blog post, each under 100 words, so I can pick the strongest. Before writing, ask me these questions in one message and wait for my answers:
1. What is the post's title or working topic?
2. Who is the reader, and what problem are they trying to solve?
3. What will the reader be able to do or know by the end (the payoff)?
4. Paste any notes, data or facts you have. Only these will be used for the fact-based hook.

Rules:
- Intro A opens with the reader's problem. Intro B opens with the most surprising fact from my notes. Intro C opens with a short scene: one person, one moment, one concrete detail.
- Each intro states the payoff by sentence three at the latest.
- Use only facts from my notes. If my notes have no surprising fact, say so and suggest what to look up instead of inventing one.
- Do not open with "Have you ever", "In this post" or a rhetorical question.
- Keep every sentence under 25 words.

Output format:
For each intro: a heading with its letter and hook type, the intro text, a line showing its word count and which sentence states the payoff, and one line on which reader it suits best.
End with your pick and one sentence on why.

Finally, add one line flagging any claim I should verify before publishing.

Example output

At a glanceWord count of each intro draftAll three stay under 100 words; each lands its payoff by sentence 3.
  • Intro A: Problem hook: 71 words
  • Intro B: Surprising fact hook: 74 words
  • Intro C: Scene hook: 64 words

Example for: a freelance designer's post on getting invoices paid faster, with notes from 112 of her own 2023 invoices.

Intro A: Problem hook

You finished the work three weeks ago, and the client loved it. The invoice is still unpaid, and a third reminder feels desperate. Here is a five-step invoicing routine that cut my average wait from 31 days to 14, with no awkward chasing. It covers when to send, what the email should say, and the one payment-terms line that does most of the work. You can set it up this afternoon.

Word count: 71 | Payoff: sentence 3
Best for: readers who are frustrated right now and want relief fast.

Intro B: Surprising fact hook

Invoices I sent on a Friday were paid late 41% of the time. Invoices sent on a Tuesday were late only 18% of the time. That timing gap is one of five small changes that cut my average payment wait from 31 days to 14, and this post walks through all five. You'll get the send-day rule, a three-line invoice email, and the payment terms clients actually read. None of it needs new software.

Word count: 74 | Payoff: sentence 3
Best for: skeptical, numbers-minded freelancers who want proof before advice.

Intro C: Scene hook

It's 11 p.m. on a Thursday, and Dana is refreshing her banking app for the fourth time today. The $2,400 invoice she sent five weeks ago still hasn't landed. This post shows the five-step routine that gets invoices like hers paid in about two weeks, from the send-day rule to the one line that stops late payers. It takes one afternoon to set up.

Word count: 64 | Payoff: sentence 3
Best for: newer freelancers who respond to stories more than data.

My pick: Intro B

The Friday-versus-Tuesday gap is specific, counterintuitive and comes from your own records, so it earns trust in the first two sentences.

Verify before publishing: the 41% and 18% figures come from 112 invoices in one year. Note the sample size in the post, and label Dana as an illustrative example, not a real client.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Three fixed hook types give you real choices instead of three versions of the same opening.
  • The payoff-by-sentence-three check stops intros that build atmosphere but never say why the reader should keep going.
  • Limiting the fact hook to your own notes prevents made-up statistics and flags gaps you need to research.

Use when your draft is done but the opening feels flat. Have your topic, reader, payoff and any notes or numbers ready. Works in ChatGPT, Claude or Gemini.

Common edits

  • Change the limit to 50 words for newsletter or LinkedIn openings.
  • Swap the scene hook for a contrarian claim if your post argues against common advice.

Prompt details

By
Prompts-GPT editors
Published
How prompts are written and checked

Did this prompt work?

Keep exploring

More in Writing