A client opened an invoice that was meant to be fully in Latvian, and there, sitting on it like a typo in a love letter, was a single small word in English. The status label. Right next to it, the little menu where you choose how invoice numbers get built was also speaking English, cheerfully, on a page that was supposed to know better. It is a tiny thing. It is also exactly the kind of tiny thing that makes a careful business owner quietly wonder what else you were not careful about.
The first reflex was the obvious one. Find the few stray English words, translate them, and move on with the afternoon. Easy. Honestly, a little satisfying. And it would have been completely wrong, because the stray words were not actually the problem. They were the smoke. The fire was somewhere underneath.
Here is what we found when we looked closer, and it stung a little. In our system, translations were being kept separately for each client, as if every customer owned their own private dictionary. So when a translator carefully filled in the Latvian word for that status label, that word lived inside one client's world and nowhere else. The next client we welcomed aboard started with a blank dictionary and the very same word missing all over again. Every fix had to be carried, by hand, to every customer. Twenty customers meant paying for the same small correction twenty times. We had built a translation tax and quietly handed ourselves the bill.
Translating a word was the easy part. Getting that one word to appear everywhere it needed to was the hidden cost nobody had priced in. And the deeper mistake was a kind of mixed-up thinking. We had been treating language like something each customer personally owns, when really it is something every customer shares. The Latvian word for that status is just the Latvian word for that status. It does not change from client to client. Nearly everything in the system is like that. The rare exception, a specific industry term, one client's preferred wording for a line on a bill, is exactly that: the exception, not the rule. Build everything around the exception and you tax the ordinary case forever. Build for the ordinary case and the exception still fits, as long as you leave a door open for it.
So one evening we rebuilt the whole foundation. Now there is a single shared dictionary that everyone draws from first, with each client free to lay their own private words on top whenever they truly want to. One canonical source. Fix a word once, and it lights up correctly for everyone, instantly. Any customer can still choose their own wording for anything, but no one has to anymore just to read their own invoice in their own language. While we were in there, we also made the tool that hunts for untranslated words dramatically faster, turning a slow grind into something that finishes in moments, and we promoted the part of the system that handles language into the small group of things that simply cannot be switched off. If a business cannot show its own words, it cannot send an invoice, and that should never be optional.
The lasting lesson here is about defaults, and it reaches well past us. Most software you buy proudly advertises personalization. Every customer gets their own settings, their own templates, their own copy of everything. It sounds like a courtesy. Very often it is a tax in disguise. When something is mostly identical across all your customers, storing a separate copy for each one multiplies your upkeep by the number of customers you have. Every typo becomes a chore repeated many times over. Every new label has to be pushed out again and again. Every improvement reaches a few customers fast and others never. Your staff are quietly expected to remember which client has which version, and they will not, and so some customer gets the stale one, and you get the support ticket, and you apologize.
If you run a small business and you are weighing a few tools that all let you customize email templates, service descriptions, status labels, invoice formats, ask a sharper question. Which of these things are genuinely different for each customer, and which are only pretending to be, while in practice they are identical for everyone? That second group is the expensive one. Nobody actually asked for that customization. They are just quietly paying the cost of keeping all the copies in step. Flip the default. Share the thing that is shared. Make per-customer the exception, with a clear door for the few who truly want it. The ones who care will use it and be glad it exists. The rest, the great majority, will silently inherit every improvement you ever make. The most expensive features are usually the ones nobody asked for.