One message, multiple readers
The software vendor's core pitch gets tailored language for a startup CTO and a manufacturing IT manager separately, instead of one flat version trying to speak to both at once.
Coming soonCopywriter
Write for a specific audience
The business tailors the same core message to different customer types instead of writing one generic version for everyone.
Works with
What it does
How Lekha handles this
The user defines a target audience (age range, role, pain point, or a saved persona), and Lekha adjusts vocabulary, examples, and emphasis in the generated copy to speak to that group specifically. Multiple personas can be saved and reused across future requests.
A B2B software vendor writes one cold-email draft for "IT decision-makers" and it lands flat with a startup CTO and a legacy-systems manager at a large manufacturer alike, because those are genuinely two different readers with different pain points, even though both technically fit the same job title. One generic version tries to speak to everyone and actually speaks to nobody specifically.
Audience persona targeting lets a business define a specific reader — age range, role, pain point, or a fuller saved persona — and adjusts vocabulary, examples, and emphasis in generated copy to speak to that group directly. Multiple personas can be saved and reused, so a sales team working several segments doesn't rewrite from zero for each one.
Where write for a specific audience happens
Lekha runs this directly on the platforms your customers already use — no separate app for them to install.
- WordPress
- Google Docs
- Notion
- Canva
How it works
Step by step
- 01
Define or select a persona
Set demographics, role, and specific pain points for a target reader — "IT decision-maker at a mid-size manufacturer" — either freshly or by picking from personas already saved by the team from an earlier campaign.
- 02
Copy generation adjusts to the persona
Vocabulary, examples, and what gets emphasised shift to match that specific reader's likely concerns, rather than producing the same general draft regardless of who's actually meant to read it, whether a startup CTO or a manufacturing plant's IT manager.
- 03
Multiple personas stay saved and reusable
A sales manager sets up a persona once, and every rep generating outreach from it draws on the same definition, keeping a team's messaging coordinated rather than each person interpreting the audience differently across dozens of separate cold emails.
- 04
The same core brief, several versions
One underlying message can be generated against different saved personas in turn, producing genuinely different-feeling drafts for a startup CTO and a manufacturing IT manager from the same starting brief, without rewriting the pitch itself from scratch each time.
Why it matters
What you get out of it
A coordinated sales team
Every rep generating from the same saved persona produces outreach that feels coordinated, rather than as many different interpretations of the audience as there are people on the team.
Personas built once, used repeatedly
A persona defined for one campaign carries over to future requests, saving the effort of re-describing the same target reader from scratch every time a new draft is needed.
The detail
What to know before you rely on it
A persona is a simplification of a real group of people by design, and the risk that comes with any simplification is that one built from thin, assumed, or biased input — a stereotype about what "IT decision-makers" or "working mothers" supposedly care about, rather than actual observed detail — produces copy that leans into the stereotype rather than genuinely speaking to the real diversity of people who fit the label. A persona is only as good as the specificity and honesty behind it, and a vague or assumption-heavy one doesn't just produce weaker copy, it can read as tone-deaf or reductive to the people it's meant to reach.
This is why a persona, once created, deserves a review step before it's marked ready for broad, repeated use — someone who understands the target audience checking whether its stated pain points genuinely reflect that group, rather than a generic guess dressed up as a defined persona. A persona used once in a single test campaign is lower-stakes than the same one reused across every rep's outreach for months, and review effort should scale with how broadly it's going to be used.
A persona also has no access to information the business hasn't fed it — it shapes vocabulary and emphasis, not facts, so a persona-tailored email is still exposed to the same thin-brief hallucination risk as any other generated copy, and checking specific claims against what was actually supplied remains necessary regardless of how well-targeted the tone feels for its intended reader.
Industry use cases
Where this earns its keep
10 industries where Lekha applies this directly.
Lekha writes vehicle listing descriptions, service-reminder messages, and seasonal offer copy that highlight features without inventing specifications the dealer didn't provide.
A used-car dealer pastes the make, model, year, and mileage for a new arrival, and Lekha drafts a listing description plus a short social caption, both flagging that any claim about condition or history beyond the given facts needs the dealer's own confirmation before posting.
See the automotive playbookLekha drafts outreach emails, LinkedIn posts, and case-study-style copy that stay consistent with the company's brand voice across every salesperson sending them.
A sales manager sets up a persona for "IT decision-maker at a mid-size manufacturer," and every rep on the team generates cold-email drafts from the same persona so outreach feels coordinated rather than ad hoc.
See the b2b sales playbookLekha drafts marketing copy for financial products while automatically routing any statement about returns, rates, or guarantees to a compliance reviewer before it can be published.
A regional NBFC drafts a loan-product social post, and Lekha flags the line mentioning an interest rate range as a regulated claim, holding the post in a pending-review queue until the compliance officer confirms the number matches the current approved rate sheet.
See the banking and finance playbookLekha writes product descriptions, Instagram captions, and seasonal campaign copy in a consistent brand voice across a growing catalog.
A skincare brand uploads its full product line as a spreadsheet with ingredients and benefits per item, and Lekha generates a description and a caption for each product in one bulk run instead of one at a time.
See the beauty and cosmetics playbookLekha drafts course-description copy, enrollment email sequences, and SEO blog content aimed at parents and students researching options.
A test-prep institute asks Lekha for a blog post targeting the keyword "best online coaching for class 10 boards," and Lekha returns a structured draft with headings and an FAQ section, with any specific outcome claim about pass rates flagged for the institute to verify before publishing.
See the education playbookLekha drafts patient-facing communication and clinic marketing copy while routing any health-outcome claim to a licensed staff member for sign-off before it goes live.
A physiotherapy clinic drafts a social post about a new treatment offering, and Lekha flags the phrase implying guaranteed pain relief as a health claim needing review, holding it until the treating physiotherapist approves the wording.
See the health and wellness playbookLekha writes product and catalog descriptions, seasonal sale copy, and social captions that match the shop's visual brand.
A furniture retailer uploads a new collection's specs and Lekha drafts descriptions for the e-commerce listing plus a matching Instagram caption set, keeping material and dimension details exactly as supplied.
See the home decor and furnishing playbookLekha writes property listing descriptions, neighborhood guides, and follow-up email copy without fabricating amenities or pricing details not provided.
A broker pastes a property's square footage, bedroom count, and location, and Lekha drafts a listing description and a short email to interested buyers, both built strictly from the supplied facts.
See the real estate playbookLekha drafts service-package descriptions, appointment-reminder copy, and promotional posts while keeping any wellness-outcome claim flagged for owner review.
A day spa asks Lekha to write copy for a new facial package, and Lekha drafts the description but flags a line implying a specific skin-improvement result as needing the owner's confirmation before it's used in an ad.
See the spas and salons playbookLekha writes destination descriptions, itinerary summaries, and seasonal package promotions in multiple languages for a mixed domestic and international audience.
A tour operator asks for a Kerala backwaters package description in both English and Hindi, and Lekha produces two natural-reading versions rather than a literal translation of one into the other.
See the travel and tourism playbookMore from Lekha
Everything else it handles
Learn and apply brand voice
The business gets copy that consistently sounds like them, in every language, without re-explaining tone in every prompt.
Learn moreGenerate copy for any channel
The business drafts a usable first version of an ad, caption, email, or product description in seconds instead of starting from a blank page.
Learn moreAdjust tone per piece
The business can dial a single draft from formal to playful (or vice versa) without rewriting it from scratch.
Learn moreWrite in Hindi and Hinglish
The business reaches Hindi-speaking and code-mixed audiences with copy that reads naturally, not like a literal translation.
Learn moreTranslate existing content
The business turns one piece of English copy into ready-to-use versions in other languages without hiring a translator for routine content.
Learn moreWrite seo-ready articles
The business gets a blog post or landing page draft built around a target keyword, ready to publish with minimal editing.
Learn moreQuestions
Straight answers.
Can a persona end up reinforcing a stereotype instead of genuinely reflecting our audience?
Yes, if it's built from thin or assumed input rather than real, specific detail about the actual audience — a persona based on a stereotype about a role or demographic will produce copy that leans into that stereotype rather than speaking to the real range of people who fit the label. A persona deserves review by someone who genuinely understands that audience before it's used broadly across a team's outreach.
How much detail does a persona actually need before it's useful?
More specific is generally better — a persona built from real observed pain points and role details produces more genuinely tailored copy than one defined by a vague demographic label alone. A thin persona doesn't just underperform, it risks producing copy that leans on assumption rather than a real understanding of the reader it's supposed to be speaking to directly.
Should a persona used just once for a small test get the same review as one used team-wide?
Not necessarily to the same degree, but the review effort should scale with reach — a persona reused across every rep's outreach for months carries more consequence if it's flawed than one tested once in a small, contained campaign. The wider a persona's intended use, the more worthwhile a proper review by someone who knows the actual audience becomes before rolling it out broadly.
Does targeting a persona make a factual claim in the email more trustworthy?
No — a persona shapes vocabulary, examples, and emphasis, not the underlying facts in the draft, so an email tailored to a specific persona is still exposed to the same risk of an invented or unverified detail as any other generated copy. Checking specific claims against what was actually supplied in the brief remains necessary regardless of how well the tone matches its intended reader.
The rest of your stack
It plugs into what you already run.
Lekha connects to your tools
No rip-and-replace — write for a specific audience works alongside the systems already running your business.
- X
- MailChimp
- Webflow
- Shopify
- OpenAI
- Google Drive
- Figma
Coming soon