Label every product claim: live, seed or roadmap
AI-written sales copy blends what you sell today with what you plan to sell. A three-label rule keeps the promises honest for people and AI.
4 min read Provecta Group
Ask an AI to write a sales email about your product and give it your product notes. Watch what it does with the roadmap.
It will take "we plan to add WhatsApp ordering later this year" and write "order easily on WhatsApp". It will take "we deliver in Nairobi and are adding Kisumu" and write "delivery across Kenya's major cities". It is not lying in any sense it understands. It is writing persuasive copy, persuasive copy is written in the present tense, and nobody told it which sentences were promises about the future.
Salespeople do the same thing under pressure, which is partly why AI does it. It learned from a great deal of sales copy.
Why it matters more than it looks
An overclaim in a sales email feels small. The client signs, finds out the feature is not there yet, and either waits or complains. But the damage runs deeper in some businesses than others. If what you sell is trust, every overclaim spends some of it. A client who catches one overstatement will discount everything else you said, including the parts that were true.
AI makes the volume problem worse. One salesperson overclaiming on one call is a coaching conversation. An AI drafting fifty follow-up emails a week from the same blended notes repeats the same overclaim fifty times, in writing, with your name on it.
The three labels
On 15 July we finished a sales and spokesperson training guide for Karibu, the Kenyan property platform we build. One rule sits at its centre: every person who speaks for Karibu separates what is live, what is seed, and what is on the roadmap, and never presents one as another.
- Live means a customer can use it today, in production, without special arrangement.
- Seed means it exists and works, but runs on sample or starter data, or for a limited group. It is real, and it is not yet at full scale.
- Roadmap means it is planned. It may have a target date. It does not exist for customers yet.
The reason it went to the centre of the guide is simple. Karibu sells trust in property information. Overclaiming would undermine the product itself.
The labels work for AI for the same reason they work for people. They turn a blurry set of product notes into facts with a status attached. A model that is told "only describe Live items in the present tense, describe Seed items with their limits, and describe Roadmap items as plans, if at all" has a clear rule to follow. Without the labels, it has to guess, and it guesses toward whatever sounds most appealing.
Putting it in your company memory
The labels are only useful if they live somewhere everyone, and every tool, reads before writing. In practice that means one product-facts page with a line per feature:
| Feature | Status | Limits | Last checked | Owner |
|---|---|---|---|---|
| Online booking | Live | Nairobi branches only | 10 July | Ops lead |
| Payment reminders by SMS | Seed | Piloting with 20 clients | 1 July | Product |
| Customer app | Roadmap | Target Q1 next year | 1 July | Owner |
The rows above are an illustration, not a real product. Yours will have your own features. The columns are the point.
Anyone drafting with AI pastes or links that page and adds one sentence to the instructions: "Use the status column. Never describe Seed or Roadmap items as fully available." Anyone reviewing a draft checks every product claim against the status column. When a feature moves from seed to live, one person updates one row, and every future draft picks it up.
What labels cannot fix
They cannot stop a salesperson saying something on a call that was never written down. They do not make the review step optional either, because a model can still slip, especially in a long email where the instruction sits far above the sentence it is writing.
They also depend on someone being honest when they fill in the status column, which is a cultural question more than a technical one. If the product team marks things live before they are ready, the labels just launder the overclaim.
One case the three labels handle badly: a feature that is live for some customers and not others, depending on their plan or location. A fourth label? A separate column? Either can work, and we would rather leave that question open than pretend there is one right answer.
Count your overclaims
List every feature or service your sales team mentions in a typical pitch. Mark each live, seed or roadmap, and be strict. Then read your last five AI-drafted sales emails and highlight every claim that describes a seed or roadmap item as if it were live.
Count the highlights. That count is a fair measure of how far your written sales story has drifted from what you actually deliver.
Find out where your sales process leaks revenue at pgco.world/tools/revops-audit, or book 20 minutes at pgco.world/book.