Rewrite Content for a Different Audience

This prompt re-targets a piece of writing for a different reader by adjusting the four things that actually change with audience: vocabulary and technical depth, examples and analogies, assumed prior knowledge, and tone. It keeps the core information intact and asks for a short change-note, so you can see and trust what was adapted rather than guessing. Reach for it when good content is landing wrong because it was written for the wrong reader, such as turning an engineering doc into something an executive or customer will actually absorb.

What you can expect back

Rewritten:
When your stock changes in one place, our system updates it everywhere else automatically, usually within a second. You don't have to sync anything by hand or worry about two locations showing different numbers, so you spend less time fixing inventory and more time running your business.

Key changes:
- Dropped jargon (webhooks, asynchronous, eventual consistency) for plain outcomes.
- Replaced the technical mechanism with the benefit: no manual syncing, no mismatched numbers.
- Shifted tone from spec-sheet to reassuring and time/money-focused, matching what founders care about.

Illustrative example — your results will vary by tool and inputs.

Get sharper results

• 01Describe the audience by what they know and what they want, not just their job title, since 'CFO who distrusts vendor hype' yields a sharper rewrite than 'executive'.
• 02Use the change-note as a quality check: if a listed change actually altered the meaning rather than the framing, push back and ask it to restore the fact.
• 03For technical-to-lay rewrites, add 'do not oversimplify to the point of being wrong' so accuracy survives the plain-language pass.
• 04Ask for the rewrite at the new audience's likely reading level explicitly (e.g. '8th-grade reading level') when you need to hit accessibility or readability targets.
• 05If you're adapting for multiple audiences, run the prompt once per audience with the same source text so each version is purpose-built rather than a watered-down compromise.

Adapt it for your case