In 2004 we launched a product called My Virtual Time Capsule. The pitch was one sentence: you should be able to leave your family more than a file cabinet. Record the stories, write the letters, name the moments they should arrive, and let the people you love receive them later.
It did not work. We have had twenty-two years to stop making excuses about why, so here is the honest version — three failures, none of which were the idea.
Failure one: we asked people to be online in a way they simply weren't yet
It is worth remembering what 2004 actually looked like. Gmail launched that April with a full gigabyte of storage, and so many people assumed it was an April Fools' joke that Google had to insist it was real. YouTube did not exist — it wasn't founded until February 2005. Cheap, durable cloud storage did not exist either; Amazon S3 arrived in 2006. The iPhone was three years away. Facebook launched the same year we did, but it was locked to college campuses until 2006.
Now consider who our product was actually for. Grandparents. Parents in their fifties and sixties. The people with the most life worth recording were the people least likely to be living online at all — and we were asking them to buy a camcorder, find a capture card, wrestle a video file onto a home computer, and upload it over a connection that was often still dial-up.
We were asking for a new behavior and a new product in the same breath. You only ever get to ask for one.
Failure two: we sold the ending instead of the presence
This one was our own doing, and it is the mistake we would repeat if we weren't careful. We framed the whole thing around death. A capsule that opens when you are gone. Mortality as the sales device.
That framing turns a beautiful idea into a chore — a task on the same list as the will and the life insurance, except without a lawyer's deadline forcing anyone to finish it. Nobody opens a laptop on a Tuesday night to work on their own ending.
The frame that actually works is not departure. It is presence. A grandfather's voice on a wedding morning. A birthday tradition that keeps going. The story behind an heirloom when a grandchild finally thinks to ask. Identical mechanism, completely different reason to sit down and start.
Failure three: we could not have kept the promise anyway
The hardest one to admit. In 2004 we could not have credibly promised to hold a private letter for thirty years and hand it to the right person on the right morning. Storage was expensive and breakable. Encryption at rest, key custody, and account recovery were not things a small company simply had. And a company promising to be standing there in 2034 ought to be reasonably confident it will be standing there in 2006.
With this product, the promise is the product. We had no business making it.
What changed — and it was mostly not the technology
The infrastructure question got boring, which is the best thing that can happen to infrastructure. Durable storage costs almost nothing. Encryption is table stakes. The phone in a seventy-year-old's pocket shoots better video than a 2004 broadcast camera.
But the real change is behavioral. Families already do this. They send voice notes. They keep shared albums. They video-call the grandparents on Sunday. They scan QR codes on menus and headstones without thinking about it. The ritual of capturing a life in small digital pieces is no longer something anyone has to be taught — it is already happening, badly and scattered across four devices and three dead phones.
And the demographic inverted. The generation with a life worth preserving is now the generation that is comfortable online. In 2004 those were two different groups of people. That is the whole difference.
What we are building differently this time
Stages, with proof at each one. The storytelling foundation ships first and is live today: a profile, stories and lessons and milestones, photographs and video kept beside the memory they belong to, visibility you control, a direct link to share, and a QR code so a printed keepsake can lead a family back to the record.
Delivery comes after the safeguards, not before. The Wish Ledger turns a vague intention into something a system can actually execute: a named recipient, a trigger, a payload, and a proof trail. "Every April 20th, keep our lunchtime birthday tradition going" is a wish. "Give her the bracelet from my desk, with the letter that explains why I kept it" is a wish. Those are the things families lose in conversation.
And there is one rule the product will not bend on: exactly what you wrote, exactly when you chose, nothing invented. The temptation in 2026 is enormous — the models are good enough now to synthesize a grandmother's voice saying something she never said. That is the one thing this product must never do. Writing assistance is welcome while you are here to review every word. After activation, the Concierge is deterministic: it carries out the instruction you approved, and it does not improvise, rewrite, or speak as you.
Sealed delivery of private letters stays gated until encryption, key custody, and recovery controls genuinely meet the standard — we can't read your letters, but we should be able to prove we hold them. Until that is built and tested, we don't advertise it as live. That is the correction for 2004: the roadmap is public, and the claims wait for the safeguards.
The lesson we now apply to every build
A product can be completely correct and still fail. Timing is not luck and it is not mystique — it is three checkable conditions. Does the behavior you need already exist, or are you inventing it? Is the infrastructure boring yet, or are you paying to be a pioneer? Can you keep the promise on day one and in year thirty?
MyVTC failed all three in 2004. It passes all three now. Same idea, twenty-two years of patience, and a much shorter list of things we are willing to claim.