Why I Built SNAB

People ask me why I built SNAB. They expect a founder story about spotting a market opportunity, doing customer research, building an MVP. The usual playbook.

The truth is simpler and more embarrassing. I built SNAB because I was drowning.

The Breaking Point

By 2024, I was managing myself as a freelancer, my family’s household, a small team of contractors, and two volunteer organizations. Five entities. All with their own tasks, deadlines, documents, decisions, and people who needed things from me.

I had Notion for work. Apple Reminders for personal stuff. A shared Google Sheet for the family. WhatsApp groups for the volunteer boards. And a notebook — an actual paper notebook — for the stuff that did not fit anywhere else.

Every morning I woke up with that specific kind of anxiety where you know you are forgetting something important, but you do not know what. So you just carry the weight of it all day.

I was not disorganized. I was over-organized. I had too many systems, and none of them talked to each other. Every tool I tried solved one slice of the problem and ignored the rest.

The Question That Changed Everything

One night — late, tired, after putting the kids to bed and then spending two hours on volunteer board emails — I asked myself a question that would not leave me alone:

Why do I need a completely different system for every part of my life, when every part of my life needs the same things?

My family needs to plan things, track tasks, store documents, and make decisions. My business needs to plan things, track tasks, store documents, and make decisions. My sports club needs to plan things, track tasks, store documents, and make decisions.

The activities are identical. Only the context changes.

Building Backwards

So I started mapping it. Not from the tool side — what features should an app have? — but from the pattern side. What are the actual functional domains that every entity requires?

It took months of obsessive scribbling, false starts, and restructuring. But eventually the pattern emerged: 13 domains, 4 pillars. The same skeleton, every time, for every entity.

Once I had the pattern, the app became obvious. Not another productivity tool that tries to be everything. A system built on the actual structure of how life works. You capture input. It flows through the pattern. Decisions become clear. Actions become trackable. Nothing falls through the cracks, because the structure does not allow it.

The Name

SNAB stands for the four pillars: Structure, Navigate, Act, Build. It is the sequence. You cannot navigate without structure. You cannot act without direction. You cannot build without doing the work first.

Most people try to start at Act — just doing stuff, reacting, firefighting. That is why they feel overwhelmed. They skipped the first two steps.

Why It Matters

I did not build SNAB to create another app. I built it because I believe the pattern is real, and once you see it, it changes how you think about everything you manage.

Your life is not a collection of unrelated responsibilities. It is a set of entities, all running the same operating system, all needing the same 13 things. And you are the one running all of them.

SNAB is just the tool that makes that visible. The pattern was always there.