Free tools

Free writing template

Free LinkedIn post generator

Paste what actually happened, and the tool lays it out as a post you can edit. It is a set of writing templates, not an AI writer, so nothing is invented and every claim in the draft is one you supplied.

Free browser templates and text formatting. No AI service or API key is used. Replace bracketed prompts and review the result. Your source stays in this browser unless you choose Save in Cadencz.

Your editable result

Review the text before using it. Copying and downloading are free.

Create a free account or sign in to save. Your text will come with you. Temporary text stays on this browser for up to 24 hours; keep a copy on shared devices.

What this does, and what it will not do

Five modes share one page. Draft a post arranges your notes and adds a closing question. Opening lines offers three hooks with the specific detail left blank for you. Tighten removes doubled spaces and swaps stock phrases such as "in order to" for "to". Closing line suggests three ways to end. Adapt per platform gives you the LinkedIn draft plus a checklist for reworking it for Threads and Bluesky.

None of it calls an AI model, and none of it summarises. That matters: a tool that rewrites your notes can quietly change a number or drop a caveat, and you would not notice until it was published. Everything here keeps your words and adds structure around them.

The first line decides whether the rest is read

LinkedIn hides everything after roughly 140 characters on mobile behind "see more". Whatever sits above that cut has to earn the tap on its own, which is why the opening-lines mode exists as a separate step rather than something you hope lands on the first try.

Write the post first and the hook second. It is far easier to find a sharp opening in something you have already written than to write toward a hook you picked in advance.

What makes a post worth writing at all

  • One specific thing that happened, with the number attached if you have one.
  • The part you got wrong, which is nearly always more interesting than the part you got right.
  • A caveat you would want if you were reading it: sample size, timeframe, what you have not measured yet.
  • A question you genuinely want answered, rather than one added to farm comments.