The Challenge
Social media punishes inconsistency more than it punishes mediocrity. Posting three times a week for a year beats posting brilliantly for a month and stopping. That is the entire difficulty for most small marketing teams: not that they cannot write a good post, but that they cannot write one every day forever alongside everything else.
The obvious response — have a model write the posts — has been available for several years and has mostly produced a recognisable genre of content that nobody engages with. It is worth being precise about why, because the reason determines the fix.
Generating from nothing produces the average. Ask a model for "a LinkedIn post about customer retention" and it has exactly one thing to draw on: everything ever written about customer retention. The output is the centroid of that distribution. It is grammatical, structurally competent, and indistinguishable from the forty other posts published that morning by people who typed the same prompt.
Specificity is the thing that gets scrolled-stopped, and specificity has to come from you. A number from your own data, a customer's actual objection, a mistake you made — none of these are in the model's training data. It cannot invent them, and if you ask it to, it will fabricate them.
Volume without a voice actively costs you. An account that suddenly starts posting in a generic register loses the thing that made people follow it. This is a slower failure than a typo and a much more expensive one.
How AI Solves It
The reframe that makes this work: you are not asking a model to create content, you are asking it to change the format of content you already made.
You already produce source material. A blog post. A support conversation that revealed something. A talk. A customer call. A product change and the reason for it. Each of those contains specifics that nobody else has, and each can become several posts across several platforms.
That changes the task from generation, which models are mediocre at when there is nothing to draw on, to transformation, which they are genuinely good at. The model is not inventing an insight; it is compressing yours into 280 characters, or restructuring it for a platform where the first line decides whether anyone reads the second.
The second half is voice, and the trick is to show rather than describe. Nobody can specify their own writing style accurately in prose. But you have twenty posts that worked, and a model can analyse those and extract what they have in common — sentence length, opening patterns, whether you use questions, how you handle links, what you never do. That extracted set of rules, fed back in as constraints, produces output that sounds like you in a way "write in a friendly professional tone" never will.
Third: one idea, many platforms, separate drafts. Cross-posting identical text is visible and reduces reach. The same source material rewritten per platform is not.
Recommended Tools & Models
| Option | Best for | Cost signal | Trade-off |
|---|---|---|---|
| Claude | Voice matching and repurposing | Subscription or API | Best at holding a style guide across a batch |
| ChatGPT | Same, plus image generation in one place | Subscription | Convenient; less consistent voice adherence over long batches |
| Jasper AI | Marketing teams wanting templates | Per seat | Built-in brand voice features; you pay for structure you could build |
| Copy.ai | Short-form volume | Per seat | Fast for variations; weaker on long source material |
| n8n | Automating the pipeline | Self-host or cloud | Worth it once you have a working prompt, not before |
For models: Claude Haiku 4.5 at $1 / $5 per million tokens is more than adequate for reformatting, which is not a hard reasoning task. Use Claude Sonnet 5 for the one-off job of building your voice guide, where judgement matters and you only pay once.
For images, Nano Banana 2 at $0.067 per 1K image is the cost-effective default. Its Lite variant is cheaper at $0.0336 and scores higher on preference arenas than the more expensive Pro tier — but if your images contain text, which social graphics usually do, Nano Banana Pro's text rendering is the reason to pay more.
Step-by-Step Implementation
Step 1: Build the voice guide from your own posts
Collect 10–20 of your posts that actually performed — by your own engagement data, not by feel. Include a few that flopped, labelled as such.
Then ask for analysis rather than imitation:
Below are posts from one account. The ones marked [GOOD] performed well;
the ones marked [POOR] did not.
Identify the concrete, checkable patterns that distinguish them. Focus on:
- typical sentence and post length
- how posts open (first line) and close
- use of questions, emoji, hashtags, links
- formatting: line breaks, lists, capitalisation
- recurring vocabulary, and words that never appear
- what the GOOD posts do that the POOR ones do not
Output a numbered list of rules, each one testable — a person should be
able to look at a draft and say whether it follows the rule. Do not
include subjective guidance like "be engaging".
Posts:
{{posts}}
The output is your style guide. Read it and delete anything that is not true — the model will over-generalise from a small sample. Ten solid rules beat thirty speculative ones.
Step 2: Choose source material, not topics
Keep a running list of things you actually did or learned. A support ticket that revealed a misunderstanding. A number from your own analytics. A decision and the reason behind it. A customer's exact words.
This list is the real bottleneck of the whole system. Everything downstream is mechanical; this part is not, and it is what makes the output yours.
Step 3: Generate a batch with explicit constraints
Turn the source material below into 5 social posts.
STYLE RULES (follow all):
{{voice_guide}}
PLATFORM: LinkedIn
- 1,300 characters maximum
- The first line must work alone; it is all most readers will see
- No hashtags beyond two
- Links reduce reach: put any link in the first comment, not the post
HARD CONSTRAINTS:
- Use ONLY facts present in the source material
- Do not invent statistics, customer quotes, or outcomes
- If a post needs a number the source does not contain, write [NEEDS
NUMBER] rather than inventing one
- Each post must contain at least one specific detail from the source
Return 5 distinct angles, not 5 rewrites of the same angle.
Source material:
{{source}}
The [NEEDS NUMBER] instruction is the important one. Fabricated statistics in marketing copy are the single most damaging output of this workflow, and giving the model a legitimate way to signal a gap is far more effective than telling it not to make things up.
Step 4: Rewrite per platform, do not reformat
Run the same source separately for each platform with its own constraints. The differences that matter are structural rather than cosmetic: a post built around a first-line hook does not survive being shortened, and a thread does not survive being flattened.
Step 5: Edit every post, and expect to
Budget one to two minutes per post. You are looking for three things: a claim you cannot verify, a sentence that does not sound like you, and the opening line. The opening line is worth more attention than the rest of the post combined, and it is where models are most generic.
Step 6: Add images last, and only where they earn their place
Generate images for posts that genuinely benefit — a diagram, a quote card, a product visual. Not every post needs one, and the cost analysis below explains why this is the decision that actually moves your bill.
Step 7: Keep a human on publish
Automate drafting and scheduling; never automate the final send without review. The risk is not a typo — it is a cheerful scheduled post going out during an outage or a public crisis. That has cost more brands more goodwill than every hour of manual review it would have taken to prevent.
Real-World Examples
Before — generated from a topic.
Prompt: "Write a LinkedIn post about the importance of onboarding."
Output: "Onboarding is more than paperwork. 🚀 It's the first impression that shapes an employee's entire journey. Companies with strong onboarding see higher retention and engagement. What's the best onboarding experience you've had? 👇 #Onboarding #Leadership #HR"
Nothing here is false and nothing is yours. "Higher retention and engagement" cites nothing. The closing question is the default template. This post could be published by any company.
After — repurposed from source material.
Source: internal note — "Three of our last five churned accounts never invited a second user. Median time-to-second-user for retained accounts is 4 days."
Output: "Three of our last five churned accounts had one thing in common: they never invited a second user.
Our retained accounts add a second user within about four days, median.
We'd been treating onboarding as a checklist for the person who signed up. It turns out the thing that predicts survival is whether they bring someone with them.
Changed our activation metric this week."
Same subject. The difference is entirely in the source material — two real numbers and one decision. The model did the compression; it could not have supplied the content.
After — the same source, rewritten rather than reformatted.
X/Twitter version: "3 of our last 5 churned accounts never invited a second user.
Retained accounts add one in ~4 days.
We were measuring the wrong activation event."
Not a truncation of the LinkedIn post — a different structure for a platform where the whole thing is visible at once and the reflective paragraph would be dead weight.
Best Practices
Never let the model supply a number. Every statistic must come from your source material. Adding [NEEDS NUMBER] as an allowed output makes this enforceable rather than aspirational.
Refresh the voice guide quarterly using your newest high-performers. Voice drifts, audiences change, and a guide built from last year's posts slowly pulls you backwards.
Generate more than you need and discard. Ask for five, publish two. Selection is where quality comes from, and it costs almost nothing at these prices.
Write the opening line yourself when it matters. For your most important posts, let the model do the body and write the first line by hand. It is the highest-leverage sentence and the one most damaged by averaging.
Keep a "never say" list in the style guide — the phrases that mark generic AI output for your audience. "In today's fast-paced world", "game-changer", "let's dive in". These accumulate; add to the list whenever one slips through.
Disclose synthetic imagery where the platform requires it, and check the requirement rather than assuming. Note that images from Google's Nano Banana models carry a SynthID watermark with no opt-out, which is a fact about your deliverable whether or not you disclose it.
Common Pitfalls
Treating volume as the goal. Doubling output while halving quality reduces reach on every algorithmic platform, because engagement rate is what is measured. More posts that fewer people finish is a net loss.
Cross-posting identical text. Visible, and penalised in reach on most platforms. The rewrite per platform is not optional polish.
Fabricated statistics and invented customer quotes. The most damaging output of this workflow and the easiest for anyone to check. A single invented statistic that gets challenged publicly costs more than the entire time saved.
Losing your voice gradually. This happens without any single bad post. Each one is slightly more generic than the last, and six months later the account sounds like everyone else. The voice guide plus the "never say" list is the defence; periodically reading your posts from a year ago is the detection.
Automating publish. Covered above, and worth repeating because it is the failure that makes the news.
Paying for Pro image models by default. Within Google's Nano Banana family the cheapest model outranks the most expensive one on preference — the premium buys text rendering, not general quality. Pay for it when your graphic has a headline in it, not otherwise.
Measuring Success
Measure engagement rate, never engagement volume. Volume rises with posting frequency regardless of quality; rate is what tells you whether the content works.
- Engagement rate per post, segmented by whether the post came from real source material or was generated from a topic. This comparison is the whole experiment, and most teams never run it.
- Follower growth and unfollows. Unfollows are the early signal that voice has drifted; they move before engagement does.
- Time from source material to published post. The operational metric that says whether the pipeline is actually saving anything.
- Edit distance — how much you change before publishing. If it stays high, the voice guide needs work. If it drops to zero, you have probably stopped reading carefully.
- Posts published per month against your target. Consistency is the mechanism; everything else is optimisation on top of it.
Run the segmented comparison for at least a month before drawing conclusions. Social engagement is noisy enough that a single week tells you nothing.
Cost Analysis
For a batch of 20 posts repurposed from a 2,000-word article, on Claude Haiku 4.5 at $1 / $5 per million tokens (list pricing, August 2026):
- Source article: 2,000 words ≈ 2,660 tokens
- Style guide and platform constraints: ~500 tokens
- Per batch of 5 posts: ~3,200 input, ~400 output
- Input: 3,200 / 1,000,000 × $1 = $0.0032
- Output: 400 / 1,000,000 × $5 = $0.0020
- Per batch: $0.0052 → four batches for 20 posts: ≈ $0.021
Now images, at Nano Banana 2 standard 1K pricing of $0.067 each:
- 20 images: $1.34
Images cost roughly 65 times more than all the text combined. That is the only interesting number in this analysis, and it inverts where most people look for savings. Switching text models saves fractions of a cent. Deciding that twelve of your twenty posts do not need a generated image saves eighty cents — forty times more than any text optimisation available.
Both figures are small in absolute terms, which is the real point: cost is not the constraint on this workflow. The constraint is source material and editorial attention. A team that runs out of things worth saying will not be rescued by cheaper tokens, and one that has plenty to say will find $1.36 a batch irrelevant next to the hours of editing.
Related Use Cases
- AI for Google Business Posts — the same discipline for local search
- AI for Product Descriptions — voice consistency applied at catalogue scale
Related Tools
- Claude — voice guide construction and repurposing
- ChatGPT — alternative, with images in the same place
- Jasper AI — packaged brand-voice tooling
- Copy.ai — short-form variation at volume
- n8n — automating the pipeline once the prompt is settled
Related Models
- Claude Haiku 4.5 — the repurposing workhorse
- Claude Sonnet 5 — for building the voice guide
- Nano Banana — image generation, where the money actually goes