There is a whole category of product whose ideal outcome is that the customer never touches it. Wills. Life insurance. Disaster recovery. The fire extinguisher behind glass. This year I added one to the pile: Trustbourne, a digital dead man’s switch. It’ is an encrypted vault that releases to the people you name when you stop answering check-ins.
Every normal brand instinct is wrong here. You cannot sell delight: the moment of delight is a funeral. You cannot sell engagement, because engagement means the customer keeps logging in to a thing that reminds them they will die. You cannot sell habit either. The product’s whole job is to sit still and work later, when nobody is watching and you’ are not there to fix it.
What’ is left is trust, and trust is annoyingly hard for a brand to say. So most of this category says it badly, in one of two ways.
The two failure modes
The first is fear. It converts a small number of people and repels everybody else. Worse, it poisons the exact resource the category runs on. “What happens to your family if you die tomorrow?” is a sentence that makes the reader distrust the sender more than they worry about the risk. If you are willing to frighten me to get a subscription, you are not the party I want holding my documents.
The second is comfort. “Peace of mind.” “Secure your legacy.” “Protect what matters most.” These phrases are unfalsifiable, which means they cost nothing, which means everyone uses them and they carry no information. I could paste any of them onto any competitor’s site and nobody would notice.
The third path is narrower and a lot duller to write: describe the mechanism plainly and let the reader supply the emotion. They’re better at it than you are, and they already know the stakes, or they wouldn’t be on the site.
The sentence we wrote as the spine of our launch messaging is:
Your family should not need your password, laptop, or recovery phrase to know what matters.”
No death vocabulary, no reassurance adjectives. It is entirely concrete, and every reader finishes the emotional work in their own head, about their own family, better than I could have written it for them.
Naming: the search term cannot be the brand
“Dead man’s switch” is what people type into Google. As a name above a door, it is appalling. It comes from railway safety and spy thrillers—it puts a corpse in the first three words, and nobody wants a corpse in the name of the company holding their bank details.
So we split the two jobs. The grim term lives in body copy, headings and articles, where search engines and search-minded humans find it. The brand does the opposite job. Trustbourne is trust plus bourne, an old English word that means both a boundary and a small stream. It sounds like something that was already there before you arrived and will still be there after you leave, which is precisely the quality you want in custody. Deliberately, it sounds a little like a bank and a little like a place.
The rule generalizes: in a fear-adjacent category, name the company after the institution you want to feel like, and keep the grim technical term for the pages that have to be found rather than trusted. SEO and brand then stop competing, because each has its own place.
Talking about encryption without sounding like a scam
This is the part we got wrong first.
Security language and scam language share most of their vocabulary. “Military-grade encryption.” “Absolute security.” “Unhackable.” Readers who care about security have learned to treat those phrases as warning signs. Absolutes are the tell, and the people you most want as customers are the ones they repel fastest.
Our first draft of the security copy still said “Military-grade encryption. Absolute security.” Two claims, neither testable, both asking the reader to take our word for it.
We replaced it with a simple rule: make the narrower claim, because a narrow claim can be checked.
The security page now says that file contents are encrypted in your browser before upload, that unencrypted file contents never touch our servers, not even temporarily, and that there is no master key, because each vault has its own release key. Same subject, and every sentence is something a reader can hold us to. It is also harder to write, because you have to know what your system actually does before you can describe it that narrowly. Vague security copy is often a symptom: the people writing it were never told, or never asked.
The page then says the unflattering part in the same breath. File names, folder names, and sizes are stored as ordinary metadata, because the service cannot function otherwise. And it splits the product honestly. In the default mode we hold a per-vault release key, which means we could technically decrypt your files, but don’t; access controls, audit logging, and policy prevent it. In the higher tier, no release key exists on our servers at all, and the page puts it as “Not ‘won’t,’ can’t.”
Admitting the limits of the default mode felt, at the time, like handing a competitor ammunition. In practice, a claim a reader could disprove is worth more than one they cannot.
The touchpoint nobody designs
The copy a Trustbourne customer reads most often is not on the website. It is the check-in, the scheduled message asking whether they are still there. Homepages get workshopped for weeks. The automated message that carries the entire product usually gets written once, quickly, by whoever built the feature.
That is the wrong way around, for a structural reason. A check-in only works if it gets answered, and brand voice works against that. Warmth reads as marketing, marketing gets ignored, and an ignored check-in walks the customer toward a release nobody wanted. The register that works is the one banks use for fraud alerts: name the mechanism, name the consequence, give one action and skip the decoration.
Ours reads: “This is your regular Trustbourne check-in. Click the link below to let us know you’re okay.” Then the date of the next check-in, and one sentence on what happens if there is no answer: reminders first, and after the interval we contact your trusted contacts to check on you. The final warning, two days before release, is blunter still. It gives the release date in capitals, one link to stop it, and three lines on what happens if you don’t respond.
The same logic applies to the people named in a vault. They never chose the product, and they will read our message on the worst day of their year. Their release email says whose vault it is, why it is available now, how to open it, when the link expires and what to do if it does. There is no upsell and no logo doing emotional work.
If you work in a category like this, audit the transactional and automated copy before you touch the homepage. That is where the brand gets tested, on the days the reader is least inclined to be charmed.
Price as a durability signal
In continuity products, cheap is a negative signal. If you promise to be there in fifteen years and charge €12 a year, an attentive buyer does the arithmetic and concludes you won’t be. The customer is not really paying for storage. They are betting on your survival, and a low price tells them how you rate your own odds.
Trustbourne’s regular price is €99 a year for Core and €199 for Plus. Those are not big numbers, but they are not free-tier numbers either, and the copy doesn’t apologize for them. Annual billing is presented as the operating model rather than a payment preference—the vault has to stay alive, monitored, and ready through a year in which nothing happens, which is most years.
Recipients never pay, and that is deliberate. The people you name are the one audience who never chose this product, and they meet the brand at the moment they can least deal with a checkout form. Charging them would be easy money, and a lousy way to meet someone while they’re grieving.
The two-person plan follows the same logic. Two people who plan together still get two separate accounts, vaults, contacts, and release rules; the only thing shared is the bill. A “family plan” would have been easier to sell, and it would have implied that a couple is one legal and emotional unit. Inheritance doesn’t work that way, and neither do most couples.
Saying what happens when you fail
The promise at the heart of the category is simple: we will still be here when you are not. Any brand making that promise has to answer the obvious follow-up, and most don’t.
So the answer is on our security page: EU-only storage with no US cloud providers, at least twelve months’ notice if we ever shut down, an encrypted export for every user, and tools to decrypt it locally without us.
Naming your own mortality is the strongest trust move available in a business built on someone else’s, and it costs very little. Most companies skip it because it feels like advertising a risk. The risk is already in the buyer’s head, though. Answering it openly shows you have thought about the question longer than they have, which is what they are buying.
Beyond Trustbourne
If you work on a product people buy against an event they are trying not to picture (insurance, backup, security, estate planning, health), six rules carry over:
- Describe the mechanism and let the reader supply the feeling. The reader supplies the feeling more accurately than your copywriter can.
- Make claims narrow enough to check, and publish the unflattering limit next to the flattering claim. Checkability is the security signal that survives a skeptical reader.
- Use the grim term where people search, and save the brand name for the door. They do different jobs.
- Let price carry durability. Cheap reads as temporary in any category that promises permanence.
- Say what happens when you fail. The doubt already exists, and answering it openly beats being suspected of avoiding it.
- Fix the automated copy before the homepage. The message customers read most is transactional, and that is where the promise gets tested.
None of this will make the product fun. What it can do is earn the one thing the category actually sells: the reader believing you will still be standing on the day the thing they are avoiding arrives.
Frank Louwers is the founder of Trustbourne, an EU-based digital handover service.

Leave a Reply