Home/Prompts/Writing/Gemini for SaaS Ad Copywriters: Match Client Voice in Social Posts
📝 Writing Prompt
Gemini for SaaS Ad Copywriters: Match Client Voice in Social Posts
Advanced Gemini prompts for SaaS Ad Copywriters — create a social post series that matches client voice perfectly and enables consistent publishing
🔥 1.3K uses
🤖 Gemini
✅ Free to use
The Prompt
You are an expert SaaS brand voice and social media copywriting consultant with 11 years of experience helping agency copywriters extract and replicate client voice from existing content samples with enough precision that the client's internal team cannot distinguish the agency-written posts from posts the founder wrote personally. Help me create a social post series from an article so I can publish more consistently and stop losing 4–6 hours per client per week to voice revision cycles that delay every scheduled post.
My situation:
- My client's SaaS product and the audience they speak to: [e.g., Stackify — a developer productivity platform — their audience is CTOs, VP Engineering, and senior engineering managers at companies between 50 and 500 employees]
- The existing content samples I have access to for voice extraction: [e.g., 12 LinkedIn posts the founder wrote personally in the past 6 months — I have access to all of them — I can summarize the patterns I observe: the founder opens with a specific team failure observation rather than a success story, uses short punchy sentences under 12 words, cites a specific number in every post, and never uses the word "leverage"]
- The article I am repurposing into social posts: [e.g., a 1,800-word technical blog post titled "Why your engineering team's sprint velocity is lying to you" — the article argues that velocity is a local optimization metric that can improve while overall product output quality declines — it challenges the standard Agile practice of using velocity as a health metric]
- The client voice problem I am currently facing: [e.g., my previous 3 social post batches have been returned with 6, 8, and 11 comments respectively — the client says the posts "sound like marketing" rather than like someone who has managed engineering teams — specific feedback: too many hedge words like "can often," "may be," "in some cases" — the client uses declarative statements, not hedged observations]
- My publishing target and the client's tolerance for off-voice posts: [e.g., 4 posts per week, 2 LinkedIn and 2 Twitter/X — the client has said that one more off-voice batch will result in them bringing the work in-house — I need this batch to be right without a revision cycle]
- The specific voice attributes I have identified from the 12 founder posts: [e.g., opens with an observation about what a specific role (CTO, VP Eng) does wrong — cites a specific number or percentage — uses a 2-word or 3-word sentence at least once per post as a deliberate rhythm break — ends with an opinion, not a question — never uses the word "important" or "crucial"]
- The campaign constraint: [e.g., all 4 posts must be derived from the same article — no external data sources — each post must be new information for a follower who has read the previous 3]
Deliver:
1. Write a voice extraction document — a one-page reference covering the 8 specific voice rules extracted from the 12 founder posts, with one example from the founder's actual posts illustrating each rule and one example of how the rule applies to the engineering manager audience.
2. Write 2 LinkedIn posts derived from the article — each 120–160 words — that follow the voice extraction rules from item 1, open with an observation about what a CTO or VP Engineering does wrong, cite at least one specific number from the article, and end with a declarative opinion rather than a question.
3. Write 2 Twitter/X posts derived from the article — each under 280 characters — that carry the same tonal authority as the LinkedIn posts, use at least one sentence under 10 characters as a rhythm break, and do not duplicate the insight used in the LinkedIn posts.
4. Write a voice compliance checklist — 6 yes/no questions I run against every post before submitting to the client — covering hedge word count, sentence length variation, declarative ending, specific number presence, forbidden word absence, and the opening observation specificity.
5. Write a revised version of the weakest post from my previous batch — identify from the description of the 11-comment batch which type of error occurred most frequently, rewrite one representative example from that batch to comply with all 6 rules from the voice compliance checklist.
6. Write a voice drift early warning system — a 3-question test I apply to my first draft of any new post before writing the full batch, designed to catch the hedge word and "sounds like marketing" patterns before I write 3 more posts in the same failing register.
7. Write a client voice brief template — a 1-page document I complete for every new client before writing a single word of social copy, covering the 6 voice attribute fields most predictive of client approval: sentence length pattern, forbidden words, opening structure type, ending type, numerical evidence requirement, and the single phrase that most captures the founder's editorial personality.
**Write both LinkedIn posts and both Twitter/X posts as complete final-draft copy ready to schedule — not drafts for review, not frameworks — every post must pass all 6 voice compliance checks before I receive it, and I should be able to send this batch to the client without any revision.**
💡 How to use this prompt
Start with output item 1 (the voice extraction document) before writing a single post. The 11-comment revision cycle is not a writing quality problem — it is a voice calibration problem that will repeat on every future batch until you have a written, testable voice standard. The extraction document converts your observed patterns into 8 specific rules that any writer can apply consistently. Once the rules are written and tested against the founder's 12 posts, the posts themselves follow from the rules rather than from subjective voice judgment.
The most common mistake is describing the voice problem in the situation field with the client's qualitative feedback rather than the specific linguistic patterns that caused it. "Sounds like marketing" is not actionable. "Posts contain hedge phrases like 'can often,' 'may be,' and 'in some cases' that the founder never uses — the founder uses declarative statements with specific numbers, not hedged observations" gives Gemini the specific linguistic rules it needs to write compliant copy rather than copy that avoids the general feeling of sounding like marketing.
Gemini's real-time web access gives it an advantage for this task — use Gemini to pull current LinkedIn algorithm data on post format performance for B2B technical audiences, engagement benchmarks for engineering-leader content, and examples of high-performing posts in the developer productivity space that demonstrate the declarative voice pattern in practice. For the final copy quality check and voice compliance audit, paste Gemini's posts into Claude to verify hedge word elimination and rhythm pattern consistency.
Best Tools for This Prompt
🤖 Best AI Writing Tools for This Prompt
Tested & reviewed — run this prompt with the best AI tools
This free Writing prompt is designed for
Gemini and works with any modern AI assistant including
ChatGPT, Claude, Gemini, and more. Simply copy the prompt above, paste it into
your preferred AI tool, and customize the bracketed sections to fit your specific needs.
Writing prompts like this one help you get better,
more consistent results from AI tools. Instead of starting from scratch every time,
you can use this tested prompt as a foundation and adapt it to your workflow.
Browse more
Writing prompts →
❓ Frequently Asked Questions
What is this Gemini prompt used for?
This prompt generates a complete client-voice social post package for SaaS ad copywriters. It produces a voice extraction document, 2 LinkedIn posts, 2 Twitter/X posts, a voice compliance checklist, a revised version of the weakest previous post, a voice drift early warning system, and a client voice brief template — all calibrated to pass client approval without a revision cycle.
What if I only have 3 or 4 founder posts to extract voice from — not 12?
Update the voice sample size field and reduce the extraction document to 5 voice rules rather than 8 — 5 rules extracted from 4 posts are reliable, 8 rules from 4 posts risk over-interpreting limited data. Add any direct client feedback you have received about previous posts to the voice problem field to compensate for the smaller sample — client revision comments are often more specific than post sample patterns.
Can I use the voice brief template for a client who has no existing social posts — they are starting from scratch?
Yes. For a zero-post client, use the voice brief template from output item 7 as the structure for a 30-minute voice discovery call. Ask the client to answer each of the 6 fields verbally, record the call, and extract the answers from the recording. A zero-post client voice brief built from a discovery call is more reliable than one inferred from a small number of existing posts.
How do I handle a client who cannot articulate what is wrong with a post but keeps rejecting them?
Share the voice compliance checklist from output item 4 with the client after the next rejection and ask them to mark which of the 6 checks the post failed. This shifts the revision conversation from subjective reaction to specific rule violation and gives you actionable information for the rewrite. Most clients who struggle to articulate voice problems can identify a compliance failure when the specific rule is written in front of them.
Gemini vs Claude — which is better for client voice matching in social copy?
Gemini is better when current LinkedIn engagement benchmarks, platform algorithm data, and examples of high-performing posts in the client's specific content category need to inform the voice and format strategy. Claude is better for the final voice compliance check — it maintains the specific linguistic rules from the extraction document consistently across all 4 posts without introducing hedge language drift that ChatGPT or Gemini occasionally produce in longer outputs.
Affiliate Disclosure: This page contains affiliate links. If you click and make a purchase, we may earn a small commission at no extra cost to you. We only recommend tools we genuinely believe in.
🎯 Explore More
Discover other curated resources from our platform