Legaats
Legaats was a web app where baby boomers and senior citizens could store and share life lessons in video, text, or photo format for future generations. It targeted older adults and families interested in digital legacy and wisdom sharing. The founder stopped pursuing it after slow validation, unclear monetization, weak user empathy, and no clear advantage.
View original storyProduct snapshot
What it was
Let older adults document life lessons and wisdom in video, text, or photo format so families could preserve and revisit them.
Who it was for
Problem / value
Turn personal wisdom and family memories into a shareable digital legacy.
Core workflow
Invite older users, help them create wisdom posts or recordings, categorize the lessons, and share them with relatives or future generations.
Core dependency
The product depended on older adults being willing and able to create digital content regularly.
Product form
Pricing model
The founder did not validate a clear business model; storage-based charging was considered but not proven.
Competitors or alternatives
What happened
Summary
Legaats was a digital-legacy product for people to preserve and share life lessons. The founder interview is best read as an early pivot/stop case where target-user empathy and business-model proof were not strong enough to continue.
Outcome
Legaats did not become a sustained product business.
Core risk
Building for a user group before understanding behavior and payment
Shutdown reason
The public founder material points to weak validation, unclear business model, and limited fit with the target demographic as the main reasons to stop.
Timeline
- The product idea centered on preserving personal lessons for future generations.
- The founder explored the idea but learned that validation and understanding of the target users were not strong enough.
- The founder stopped pursuing Legaats and moved on to a new project.
Before you build
Why it matters
This matters for founders building for users who are older, less reachable, or different from themselves. Surveys and personal conviction are not enough if the real habit, trigger, and payer are unclear.
Primary check
Observe the target users directly, confirm the trigger and payer, and sell a manual version of the legacy workflow.
Checklist
- Run in-person interviews with the exact older-adult segment.
- Offer a paid manual interview or memory-capture service.
- Test whether families will pay before the end user adopts software.
- Who feels the urgency: the older adult, the family, or a professional helper?
- What event triggers action now?
- Can you get paid for the outcome before building software?
Relevant if
- You are building for a demographic you do not personally belong to.
- The product depends on reflective, emotional, or low-frequency behavior.
- You do not yet know whether the end user or family member pays.
Less relevant if
- You already run paid pilots with the exact target users and families.
- The product is attached to an existing service relationship such as elder care, estate planning, or therapy.
Pre-build tests
- Deliver the outcome manually for five families and study where trust breaks.
- Pre-sell a small package through an existing elder-care or estate-planning channel.
Transferable lessons
- Observe the target behavior before building the tool around it.
- Validate the payer separately from the person who emotionally likes the idea.
- Use a manual service to learn language, trust barriers, and timing.