X rewards two things: a hook that stops the scroll in under two seconds, and a thread that earns the next tap. Most people spend 80% of their time on the body and 20% on the hook — it should be the other way around. Clico flipped that ratio for me without adding extra steps.
Here's the exact workflow I use inside X's compose box.
My step-by-step workflow
Study what's already working (5 minutes).
Before writing anything, I open a few high-performing threads in my niche and hit double-⌘. Clico's page summarizer pulls out the structure: how the thread opened, where the engagement spiked, and what the final CTA looked like. I'm not copying — I'm pattern-matching.
Speak the raw idea first.
The best tweets sound like something you'd actually say out loud. I hold ⌘ and speak my thought — unfiltered, no editing. Clico transcribes it and shapes it into a first draft. The voice stays mine because I haven't had time to make it generic.
Draft the thread inline with ⌘+O.
I press ⌘+O directly inside X's compose box. Clico reads the page context and knows I'm writing for X — not a Notion doc or a Gmail reply. I prompt it: "Turn this into a 5-tweet thread. Each tweet under 280 characters. Hook first, payoff last."
Write the hook last.
After the thread body is done, I use ⌘+O again: "Give me 4 alternative opening tweets. Each should create a knowledge gap or make a counterintuitive claim." The best hook is almost never the first one you write.
Cut every tweet by 20%.
I highlight any tweet that feels padded and use Clico's highlight-to-search to flag weak phrasing. Then I rewrite: remove the setup, keep the punch. On X, every wasted word costs you a reader.
End with a reason to retweet, not just a question.
I use ⌘+O one final time: "Write a closing tweet that gives people a reason to share this — a one-line summary they'd want their followers to see." A good final tweet is a retweet prompt in disguise.
Why this works
Retweets come from clarity + surprise. Clico keeps the drafting fast enough that the original insight survives — you're sharpening a real observation, not assembling filler. The inline workflow means you never lose the thread of thought switching tabs.
Closing tip: your first tweet draft is almost always too long and too safe. Write it fast with Clico, cut it hard, then post before you talk yourself out of it.
🔗 https://tryclico.com/?utm_source=indiehacker&utm_medium=referral
The “write the hook last” point is underrated, most people do the opposite and end up anchoring the whole thread around a weak opener.
The voice-to-draft step is interesting too. Feels like that’s what actually preserves authenticity, not the tool itself. Most AI-written threads lose that because they start from text, not thought.
Curious if you’ve noticed differences in performance between spoken-first threads vs fully written ones. Feels like that could be the biggest lever here.
The hook-last approach is underrated — most people write the hook first then get attached to it even when it's weak. Your workfThe hook-last approach is underrated — most people write the hook first then get too attached to it even when it's weak. Your workflow of drafting the body first and then generating 4 hook alternatives is spot on.
One thing I'd add: the consistency layer matters just as much as the craft layer. You can nail the hook formula, but if you only post when inspired, the algorithm never gets enough signal to amplify you. I've been experimenting with building a 30-day content queue in one sitting using AI tools like AlphaTweet (alphatweet.pro) so the writing work doesn't have to compete with distribution pressure. The creative quality actually improves when you're not writing under "I need to post something today" anxiety.
Great breakdown on the inline workflow — the detail about the tool reading page context is exactly the kind of UX thinking that separates good AI tools from generic ones.low of drafting the body first and then generating 4 hook alternatives is spot on.
One thing I'd add: the consistency layer matters just as much as the craft layer. You can nail the hook formula, but if you only post when inspired, the algorithm never gets enough signal to amplify you. I've been experimenting with building a 30-day content queue in one sitting using AI tools like AlphaTweet (alphatweet.pro) so the writing work doesn't have to compete with distribution pressure. The creative quality actually improves when you're not writing under "I need to post something today" anxiety.
Great breakdown on the inline workflow — the detail about ⌘+O reading page context is exactly the kind of UX thinking that separates good AI tools from generic ones.