Why Small Is Better for Family History

3 min read

I was looking at a census record the other night—just a few lines on a page, nothing remarkable at first glance. Names, ages, occupations. The kind of thing you’ve seen a hundred times.

But then it hit me: this wasn’t just data.
It was a snapshot of a real moment in someone’s life. A person who made decisions, had relationships, carried stories forward—whether they meant to or not.

Family history doesn’t feel like software.
It feels like inheritance.

Most tools don’t treat it that way

If you spend enough time with genealogy software, you start to notice a pattern.

Everything is optimized for: - more records\

  • more hints\
  • more engagement

It starts to feel less like you’re building something meaningful and more like you’re feeding a system.

That’s not necessarily malicious—it’s just what happens when products are built to scale.
When success is measured in growth, everything slowly orbits around it.

But family history isn’t a growth problem.
It’s a stewardship problem.

Small changes what you optimize for

One of the reasons I started building HeyFam is because I wanted something that felt different—something closer to the way this work actually feels when you’re doing it thoughtfully.

And the truth is, that’s very hard to do at scale.

Small teams have constraints. But those constraints come with advantages:

  • You stay close to the work
    There’s no distance between the people building the product and the people using it.

  • You can make slower, better decisions
    Not everything has to be optimized for speed or growth.

  • Details matter more
    You notice things. You fix things. You care about how it feels, not just how it performs.

  • Accountability is real
    There’s no abstraction. If something feels off, it’s on us to fix it.

Small doesn’t mean limited.
It means intentional.

Family history is different

Most software can afford to treat user data as interchangeable.

Family history can’t.

This is: - your grandparents’ names\

  • your family’s migrations\
  • the stories that get told (and the ones that don’t)

It’s personal in a way that most software never has to deal with.

And because of that, the priorities should be different.

Not: - “How do we get more engagement?” - “How do we increase retention?”

But: - “Are we helping people preserve something meaningful?” - “Are we treating this with the care it deserves?”

Incentives shape outcomes

As products get bigger, they don’t just grow—they change.

More stakeholders. More pressure. More expectations around revenue and growth.

Over time, those pressures show up in subtle ways: - what gets prioritized\

  • how data is used\
  • what tradeoffs are considered acceptable

Not every decision is made with the same values.

And if you’re building something centered around people’s identities and histories, those differences start to matter.

We chose a different path

HeyFam is intentionally small.

No investors. No pressure to maximize growth at all costs. No need to turn your family history into something it’s not.

That gives us the freedom to focus on things that are harder to measure: - trust\

  • clarity\
  • long-term usefulness

It also means we can build more slowly—and more carefully.

Because this isn’t the kind of product that should be rushed.

What this really comes down to

At some point, everyone working on their family history runs into the same realization:

You’re not just collecting information.
You’re deciding what gets remembered.

That’s a quiet responsibility. But it’s a real one.

And it deserves tools that treat it that way.

Family history works better at a human scale.