Use cases
Family Tree — where it earns its place
On Family Tree —
Somebody in every family is the one who remembers — which great-aunt married which farmer, who emigrated and why. The Family Tree makes you that somebody, gently: each person gets a name, their relation to you, when they were born, and a space for the stories and notes that are the actual treasure. … On this page: three concrete ways the person who actually remembers birthdays reaches for the Family Tree, and the signals that tell you it fits.
When the Family Tree earns its place
As a tracker, the Family Tree keeps name, relation, born, and stories & notes — no more, no less — so the record is small enough to actually read back.
Most tools in this category — personal-CRM SaaS (Folk $19/mo, Clay $149/mo), birthday-reminder apps — solve a version of the same problem, then bill you monthly for the privilege of remembering it. The Family Tree takes the opposite bargain: one file, once, kept.
Three scenarios drawn from family, and personal
The everyday one: you open the Family Tree on a Tuesday morning, log what needs logging, and close it. Two minutes. The record is more honest than the app that pinged you to remind you.
The specific one: — the workflow it names is the record that most needs a home outside a subscription. Some people use only the Family Tree. Some fold it into a Swiss Knife next to five others. Both are correct.
The out-of-band one: months later, you want to look back. The Family Tree still opens because it is a file. There is no login lapsed, no export deadline missed. The record is where you left it.
Signals it fits the person who actually remembers birthdays
You want a relationship log that behaves like a document, not a service. You are comfortable typing your own numbers in. You would rather own the file than rent the log. Weight in the knife: 1. Manual: no manual — the tool is its own instructions.
Signals it fits
- You do this kind of record-keeping more than onceThe Family Tree pays back every time you don't have to reinvent the shape.
- You want it offline, on your own machineNo account, no cloud, no vendor between you and the record.
- You're comfortable with a hand-kept fileThe Family Tree is a document. It behaves like one.
Questions people ask
How do I start recording my family history?
Start with the people you can ask. Add a row per relative — name, relation, birth date — and then get them talking while you fill the stories field. The dates are the skeleton; the anecdotes are the person.
Is this a full replacement for personal-CRM SaaS (Folk $19/mo?
For the working core of what most people use it for — yes. For enterprise features (team seats, integrations, auto-import), no. The Family Tree is deliberately smaller and more honest about its scope.
Who is the Family Tree not for?
The person who actually remembers birthdays's opposite: a team that needs shared cloud state, or someone who wants automation over ownership. Use a SaaS for that; use this for the file.
A relationship log that opens where you left it, on the machine you left it on.