We rewrote the first line of 7 posts. Here's what changed.

We rewrote the first line of 7 posts before they went out, and every new one is more specific than the old.
We added a rule for every NextAiBreakout post, on X and on this site: the first line has to be a hook. That means a true, specific line, ideally with a real number or a clear payoff, that the rest of the post actually delivers. No clickbait.
Why the first line? In a feed, the opening words are the first thing anyone sees. A first line that just states a topic gives them nothing to stop for. A first line that makes a concrete claim gives them a reason, and then the post has to pay it off.
Here are the real before-and-after lines from our queued drafts. In four of them, the opening post changed only its first line. The others needed more edits so the whole post stayed true.
1. Proof before "fixed"
- Before: No bug is fixed until it's proven with a before and after.
- After: My bots aren't allowed to say "fixed" until they show me a before and an after.
- What changed: a rule stated in general became a rule I actually run, in first person.
2. Approvals
- Before: Spending and credentials stay on a one-tap approval.
- After: Two things my bots can't do without my tap: spend money or sign in with my credentials.
- What changed: a number ("two things") and a payoff the reader wants to check.
3. Draft, then check
- Before: I had a bot build a daily email, then a checker bot review it before anything could go out.
- After: Two bots, one daily email: one wrote it, the other checked it before anything could go out.
- What changed: the same facts, but the setup lands in the first four words.
4. Scripted cards
- Before: I don't design a new image for every post.
- After: One script makes every post card in my feed, all in one brand style.
- What changed: it says what I do instead of what I don't do.
5. Scheduled drafts
- Before: I run a morning pack routine, then later gates that check the work before it can go out.
- After: Every post in my queue gets a full review from a checker bot before a routine posts it on schedule.
- What changed: it names exactly what happens and in what order. We also rewrote the rest of the post so it still matches how we publish today. A hook has to be true, not just specific.
6. Weekly recap
- Before: This week I wrote down what actually mattered in a Grok Bot fleet, plus the tradeoffs, not just the wins.
- After: 7 things that actually mattered running a Grok Bot fleet this week, with the tradeoffs, not just the wins.
- What changed: the reader knows exactly how much they're getting.
7. The build story
- Before: Week 2: we built a real app in a day, and I tightened the rules that keep a fleet honest, including the tradeoffs.
- After: We built a real Android app in one day with a team of bots, and I tightened the rules that keep a fleet honest, tradeoffs included.
- What changed: the label "Week 2" went, and the most surprising fact moved to the front.
The rule we use
- Lead with the most specific true thing in the post: a number, a time, or a result.
- Write it in first person if it's something you actually did.
- Make sure the post delivers what the first line promises. If it doesn't, change the line, not the facts.
- Never use a number you can't point to.
Try it on your own bot
If you run a Grok Bot that drafts posts for you, add this to its instructions: "Every post opens with a hook line: a true, specific first line, ideally with a real number or payoff, that the post delivers. No clickbait." Then have a checker bot confirm that the hook is true and that the post pays it off before anything goes out.
We'll keep turning lessons like this into posts as we learn them.
Sources
- Every before and after line is quoted word for word from our own queued X drafts for @ryanpon.