I Spent 6 Weeks Building an App That Sends Messages After You Die

Estate planning covers your money. Nothing covers your words. So I spent 6 weeks building one.

Most people who think about death don’t think about their messages. They think about their will, their assets, maybe their pet. They don’t think about the things they never said.

That gap is why I built LastSend.

What This App Is And Why I Made It

LastSend is a digital legacy app. You record messages while you’re alive. The app delivers them to your loved ones after you die. Text, photos, voice recordings, video. Anything you want them to have.

I started building it because of a question I couldn’t shake. If something happened to me tomorrow, what would my parents have? My sister? Friends I haven’t talked to in months? They’d have a phone full of texts and a few photos. They wouldn’t have what I actually wanted to say.

Estate planning solves the boring part of dying. It moves your bank accounts, decides who gets the house, handles the legal mess. None of that touches the emotional layer. Nobody opens a will and feels seen by it. The will doesn’t say I love you.

So, I built the thing that does.

I’m not a death tech expert. I’m not an estate lawyer. I’m a builder who saw a gap in how we use technology around mortality and decided to fill it. Six weeks from concept to live on Google Play. Most of what I learned came after I shipped, when people I’d never met started signing up.

How It Actually Works

The mechanics are simple by design. The app should not feel complicated when you’re thinking about dying.

You record messages. Each message has a recipient. You can attach text, photos, voice notes, or video. You decide whether the message gets delivered automatically after your death or on a specific date.

The app pings you for a check-in on a schedule you set. Daily, weekly, monthly. As long as you’re checking in, nothing happens. You’re alive. Your messages stay where they are.

If you stop checking in, the app does not just dump your messages on your contacts. That would be cruel. It contacts your trusted contacts first via SMS. They confirm whether something has actually happened. Only after this human verification does delivery start.

There’s a fifteen-day grace period after confirmed death before the app cleans up your account. Time for your family to grieve, find what they need, and not have to think about you closing your accounts.

The whole flow exists to solve one specific problem. People die suddenly. Most don’t get to write goodbye letters. The ones who do, write them and then have nowhere reliable to put them. LastSend is a reliable place.

The Technical Choices Nobody Asks About

I built LastSend in six weeks. The frontend was a React app wrapped in Capacitor for Android. That part is normal.

The backend is the weird part. There isn’t one. Or rather, there isn’t a traditional one.

Instead of building API routes, I architected the entire backend as workflows in n8n, an open source automation tool. Forty plus workflows handle everything. Payments, push notifications, media processing, trusted contact verification, the death confirmation flow, the fifteen day grace period, account cleanup. Every business rule lives in a visual workflow I can audit at a glance.

This was a deliberate choice. I’m not a senior backend engineer. I’m a builder who knows automation tools deeply. I leaned into what I knew. If you’re curious about the architecture, I wrote a separate post about replacing my entire backend with n8n that explains the tradeoffs.

The whole stack runs on a single server that costs me eight dollars a month. The same server runs sixty plus other workflows for client projects. I ship apps without venture funding because I picked tools that match my skills.

What I Got Wrong About Users

I assumed LastSend would attract older people. People with grown kids. People in their fifties and sixties starting to think about their legacy. That’s who I built the marketing voice for.

The actual users are mostly in their twenties and thirties.

They’re not thinking about death because they’re old. They’re thinking about it because they’re new parents recording messages for kids who might lose them. They’re thinking about it because they have a parent with cancer and want to record their voice while they still can. They’re thinking about it because they live alone in a city far from anyone who’d know if something happened.

Death tech is not a senior product. It’s a quiet anxiety product for people in stages of life that don’t have language yet. New parents, immigrants far from family, people in physically risky jobs, people with chronic illness. Nobody wants to put it on their LinkedIn that they think about dying. So nobody talks about who actually buys legacy apps.

I’m still figuring this out. I built the product before I understood the user. I’m doing the talking-to-users phase that should have come first.

The Part Where I’m Honest About The Business

LastSend is live. It has real users. It does not yet have paying users.

I am not making money from this. The free tier is generous because I wanted people to actually use it before I started taking their money. That decision was emotional, not strategic. Six months in, I see the cost of that choice clearly. People use what they pay for. They abandon what’s free.

The next phase is figuring out which features should be paid and which stay free. I’m thinking video messages should require a subscription. Maybe multiple recipients. Maybe scheduled delivery dates beyond the standard “after death” trigger. None of these are decided.

What I learned about indie hacking through this project is mostly about myself. I’m better at building than at deciding what to charge for. I’m more comfortable with empathy than with monetization. I think a lot of solo builders have the same gap.

If you’re building something in death tech or any space that touches grief, I’d love to hear how you thought about pricing. The line between charging for emotional value and feeling exploitative is real and I don’t have it figured out yet.

What I’d Do Differently

If I started LastSend over today I’d do three things differently. I’d talk to twenty potential users before writing a line of code. I’d design the paywall before designing the free tier. I’d write more publicly about the building process so the audience exists before the product needs it.

The technical part of building LastSend was the easy part. The hard part is everything around the product. Distribution, pricing, audience, the emotional positioning of asking people to think about death and trust me with their final words.

Six weeks of building. Six months of figuring things out after. The math of indie hacking always tilts more toward the second part than you expect.

If you’ve ever thought about what you’d want to leave behind for the people you love, I’d be curious what you’d write first.

Originally published at https://lastsend.app.