Right length, right channel
A WhatsApp nudge comes back reading like a message a person would actually send, not a trimmed-down email pretending to be casual, and a Google ad respects its character cap without needing a manual trim.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business drafts a usable first version of an ad, caption, email, or product description in seconds instead of starting from a blank page.
Works with
What it does
The user picks a content type (social caption, Google/Meta ad, WhatsApp broadcast, product description, blog intro, email subject line) and fills a short brief. Lekha returns multiple variations sized and formatted correctly for that channel.
A B2B parts supplier needs a quote follow-up email, a two-line WhatsApp nudge, and a product spec sheet blurb — three jobs with three different lengths, three different registers, and three different jobs to do, but most small teams write all three the same way because nobody has time to think about format before typing. The WhatsApp message ends up sounding like an email, and the email reads like a text.
The multi-format generator treats each channel as a distinct brief rather than one draft copy-pasted three ways. Pick the content type — social caption, Google ad, WhatsApp broadcast, product blurb, email subject line — and Lekha returns variations already sized and shaped for that channel's actual constraints, so a Google ad headline respects its character cap and a WhatsApp line reads like a message, not a memo.
Lekha runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Pick from a list — Instagram caption, Meta ad, Google ad, WhatsApp broadcast, product description, email subject line — each carrying its own length rules and formatting norms baked into the request from the start.
Enter the specific details this format needs — the offer, the product, the call-to-action — since a two-line WhatsApp nudge and a full email need genuinely different amounts of information to draft properly, and a brief built for one rarely transfers cleanly to the other.
Lekha returns several versions sized correctly for the channel, so the parts supplier can pick the sharpest one or take a line from each rather than settling for whatever the first draft happened to produce.
Each variation is checked against that channel's character or word limit before it's returned, catching an overlong Google ad headline before it gets pasted somewhere it will simply be cut off or rejected, though this length check says nothing about whether the content itself is accurate.
Why it matters
A WhatsApp nudge comes back reading like a message a person would actually send, not a trimmed-down email pretending to be casual, and a Google ad respects its character cap without needing a manual trim.
The parts supplier gets a usable first version of the quote follow-up instead of staring at a blank composer box while a customer waits on a reply.
Multiple variations mean picking the strongest line rather than living with whatever the single first draft happened to produce for that brief, or mixing the best parts of two or three drafts into one.
The detail
The output is a first draft, and the amount of real, checkable detail in the brief determines how much of it can be trusted as-is. A thin brief — just a product name and "write something good" — gives the model room to fill gaps with plausible-sounding specifics it wasn't actually told, a known failure mode across every format here, not a rare edge case. A quote follow-up that invents a delivery timeline nobody confirmed, or a blurb that states a material the supplier never mentioned, reads convincingly right up until a customer asks a question the business can't back up.
Format rules are checked mechanically — character counts, word limits — but a passed length check says nothing about whether the content itself is accurate or on-brand. A Google ad headline that fits within its character cap can still make a claim about pricing or availability that isn't true, and the format validator has no way to catch that; it only catches length. The two checks are separate, and treating a format-valid draft as ready-to-publish skips the part that matters most before it goes live.
Bulk generation across many products or channels multiplies the same risk rather than reducing it — more variations from a thin brief just means more plausible-sounding gaps to check, not fewer. The practical habit worth building is treating every generated draft as a first pass a human reads before use, particularly wherever a specific number, date, or claim about the business's own product appears.
Industry use cases
13 industries where Lekha applies this directly.
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 playbookA 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 playbookA 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 playbookA 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 playbookA 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 playbookA freelance interior consultant uses Lekha to turn one client project photo caption into a LinkedIn post, an Instagram caption, and a one-line portfolio blurb, all in the same evening.
See the freelancers and consultants playbookA 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 playbookA 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 playbookAn agency managing five retail clients keeps five separate brand-voice profiles in Lekha, so the same campaign-brief-to-assets workflow produces distinctly different-sounding output for each client from the same underlying template.
See the marketing agencies playbookA 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 playbookA restaurant launching a new seasonal menu pastes the dish names and ingredients, and Lekha generates a description for each dish plus a launch-announcement caption, ready to review before the menu print deadline.
See the restaurants and food playbookA 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 playbookA 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
The business gets copy that consistently sounds like them, in every language, without re-explaining tone in every prompt.
Learn moreThe business can dial a single draft from formal to playful (or vice versa) without rewriting it from scratch.
Learn moreThe business reaches Hindi-speaking and code-mixed audiences with copy that reads naturally, not like a literal translation.
Learn moreThe business turns one piece of English copy into ready-to-use versions in other languages without hiring a translator for routine content.
Learn moreThe business gets a blog post or landing page draft built around a target keyword, ready to publish with minimal editing.
Learn moreThe business knows before publishing whether a page is likely to rank, and gets specific fixes instead of a vague score.
Learn moreQuestions
It can, and this is one of the most common failure modes across every format here — a model asked to write convincingly with too little to go on will fill in plausible-sounding specifics you didn't actually give it, like a delivery timeline or a material detail. The fix is a more complete brief, not more variations from a thin one, and any specific claim in the output is worth checking against what was actually supplied before it's used anywhere.
No — the length check and the accuracy of the content are two entirely separate things. A Google ad headline can sit comfortably inside its character cap while still making a claim about price or availability that isn't actually true, and the format validator only checks size, not substance. A human read-through for accuracy still matters regardless of whether the draft passes the length check cleanly.
Yes, though the same brief that works for a long email may be too thin for a punchy ad headline, since different formats genuinely need different kinds of detail to draft well. A brief written with only one format in mind often produces a weaker draft when reused elsewhere without adjustment, so it's worth tailoring the brief slightly per channel rather than assuming one size fits every format equally well.
The business publishing the copy is responsible for what it puts into the world, regardless of how the draft was produced — Lekha drafts from what it's given, but it cannot verify a price, a stock level, or a claim against the business's actual records. Reviewing any specific factual statement in a draft before it's published is the practical safeguard, especially for anything involving numbers, dates, or availability.
The rest of your stack
No rip-and-replace — generate copy for any channel works alongside the systems already running your business.
Coming soon