One Product, Three Market Stories

A startup that has just found its voice at home tends to assume the hard part is over. The pitch works, the deck converts, and turning it into three more languages looks like a job for a vendor. Then the same product, described in the same way, lands flat abroad. The words were right and the story was wrong — because a story is a claim about what the buyer should worry about, and different markets worry about different things.

Take a scheduling tool for shift-based teams, built in Shenzhen and now selling in three markets. The American version of the story is about upside. Managers there respond to speed, growth and competitive edge, so the headline promises that you will fill a rota in ten minutes and open your next location sooner. The proof is a customer who doubled their number of sites in a year. Risk is barely mentioned; ambition does the selling.

In Germany the same headline reads as noise. The buyer's first question is not how fast the tool is but whether it is compliant, and whether the vendor will still exist in five years. So the story starts elsewhere: working-time rules encoded in the product, data held in Frankfurt, a documented process for deletion requests. The customer proof is not growth but four years without a single payroll dispute. Certainty is the benefit being sold.

Japan changes the shape again. The decision is rarely one person's, so the material has to survive being forwarded to people you will never meet, which rewards thoroughness over punch. Reliability and after-sales support matter more than features; the question behind the question is what happens when something breaks at nine at night. The reference customer is a long-established firm, and the proof point is a support record, not a growth curve.

What must not change is the underlying truth. If the product genuinely is fast, well-governed and dependable, then three stories are simply three honest angles on one object. If it is only fast, the German version is a lie with a nice cover, and the first support failure will expose it. Localisation is a choice about emphasis, and emphasis is only legitimate when every version could survive being read side by side.

Finding the right emphasis is research, not intuition, and it is cheaper than most founders assume. Read the customer reviews your competitors receive in each market and note what people complain about; complaints reveal the local fear far more reliably than praise reveals the local desire. Then ask ten buyers what would have had to be true before they signed. The pattern in their hesitations is your headline, already written by the market.

The organisational trap is that headquarters keeps ownership of the message and local teams are given permission only to translate it. That produces material nobody in the market would have written, defended by people who have never sold there. A better arrangement fixes the claims and the evidence centrally, then lets each market choose which claim leads and which proof point carries it. Consistency lives in the facts, not in the sentence order.

There is a version of this that goes too far, and it is worth naming. A brand that becomes unrecognisable across borders loses the compounding benefit of being one brand, and a team that rewrites everything locally will spend more on messaging than on the product itself. The discipline is to keep one product, one set of proofs, and three doors into it — chosen deliberately, and reviewed whenever the market's fear changes.