A real record of approval
Sign-off happens through a tracked status change rather than a screenshot and a thumbs-up in a chat, giving the spa chain an actual, checkable record of who approved each piece before it went out.
Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenA business with more than one person on marketing can draft, comment, and approve copy in one place instead of over WhatsApp screenshots and email threads.
Works with
What it does
Multiple team members can view a draft, leave inline comments, and mark it as approved or needs-changes, with a clear owner and status at every stage. Role permissions control who can generate, who can edit, and who can give final approval.
A two-person marketing team at a growing spa chain currently approves copy over WhatsApp screenshots — one person pastes a draft into a chat, the other replies "looks fine" three days later after it's already gone out, and there's no real record of who actually signed off on what before a piece of copy reached a customer. As the team grows past two people, this gets slower and less accountable, not more.
This puts drafting, commenting, and approval in one place: multiple team members view a draft, leave inline comments the way a person would mark up a physical page, and move it through a clear status — draft, in review, approved — with role permissions controlling exactly who can generate, who can edit, and who holds final approval before anything actually goes out.
Lekha runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Every piece of copy sits in a clear stage — draft, in review, approved, published — so anyone on the team can see at a glance where a specific piece actually stands without asking around.
Feedback attaches directly to the specific line or section it's about, rather than a general note in a separate chat thread disconnected from the actual text it's referring to, so context never has to be reconstructed from memory later.
Permissions control who can generate a new draft, who can edit an existing one, and who holds final sign-off authority, so approval isn't left to whoever happens to reply first in a chat before anyone with real authority has actually weighed in.
Relevant team members get alerted when a draft moves stage or receives a new comment, so a review doesn't stall simply because nobody happened to notice it was actually waiting on them to respond and move it forward to the next stage.
Why it matters
Sign-off happens through a tracked status change rather than a screenshot and a thumbs-up in a chat, giving the spa chain an actual, checkable record of who approved each piece before it went out.
A comment on a specific sentence stays connected to that sentence, rather than living in a separate chat thread someone has to cross-reference back to the actual draft manually.
Role permissions mean final sign-off sits with whoever's actually meant to hold it, not whichever team member happens to reply first in a chat thread that day.
The detail
This is a workflow and permissions feature, and it carries no copy-quality risk of its own — it doesn't generate or alter text, so there's no hallucination or claims-accuracy concern here the way there is with generation tools elsewhere. What it does instead is make sure a human decision — approval, a requested change, a rejection — actually happens, is visible, and is attributable to a specific person before copy moves toward publishing, a different kind of value than anything about the content itself.
The real risk with a feature like this is scope creep, not accuracy — because a status field, comments, and role permissions resemble the building blocks of a general project-management tool, a team can drift toward using it for task tracking well beyond copy review: deadlines, unrelated to-dos, coordination with nothing to do with a draft moving toward publication. Keeping the boundary at copy review — draft, feedback, approval on a specific piece of writing — rather than letting it sprawl into task management is what keeps this a clean, useful tool rather than a confusing hybrid.
For a growing business, this capability earns its place exactly where informal coordination — a shared chat, a verbal "looks good" — starts breaking down under real volume, and a spa chain moving from two people to five or six marketing staff is a reasonable point to expect that informal system to create visible gaps: a piece approved by the wrong person, a comment nobody saw, a draft that went out without anyone remembering who signed off on it.
Industry use cases
6 industries where Lekha applies this directly.
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 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 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 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 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 drafts a usable first version of an ad, caption, email, or product description in seconds instead of starting from a blank page.
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 moreQuestions
No — this is a workflow and permissions layer that tracks who commented, who approved, and when, but it doesn't independently check the copy's factual accuracy or brand-voice fit itself. Those checks come from the specific tools built for them elsewhere in this suite, like brand guideline compliance checking; this capability is about making the human review and approval process visible and accountable, not about judging the content.
It's deliberately scoped to copy review specifically — draft, feedback, approval on a piece of writing — rather than built as a general project-management tool, and stretching it to cover unrelated deadlines or team to-dos tends to make it a confusing hybrid that doesn't do either job particularly well. A dedicated task-management tool remains the better fit for coordination that isn't actually about a specific draft moving toward publication.
The business sets this up through role permissions, assigning final sign-off to whichever role or person is actually meant to hold that authority, rather than leaving it to default to whoever happens to see and reply to a draft first. This is exactly the gap this feature closes compared to an informal chat-based approval process, where sign-off tends to fall to whoever's fastest, not necessarily whoever's meant to hold it.
There's no fixed headcount threshold, but the practical signal is when informal coordination — a shared chat, a verbal thumbs-up — starts creating visible gaps: a piece approved by the wrong person, a comment nobody saw, uncertainty afterwards about who actually signed off on something before it went out. A two-person team often manages fine informally; a team growing past that point is a reasonable moment to expect those gaps to start showing up more often.
The rest of your stack
No rip-and-replace — collaborate and approve as a team works alongside the systems already running your business.
Coming soon