About Slaet

It started as a personal problem

I kept losing thoughts between browser tabs.

Something would surface mid-work. A task, a half-formed idea, the reason behind a decision I'd forget by Friday. By the time I'd found the right app and the right place inside it, the thought was gone.

I tried the usual tools. Notion asked me to build a system before I could write a sentence. Todo apps wanted a due date on a thought that wasn't a task yet. Notes apps kept my thinking in one place and my tasks in another, which is the opposite of how any of it actually happens.

So I built the thing I wanted. Tasks and the thinking behind them, in the one place I already open forty times a day.

What we're building

Slaet is a workspace for tasks, notes, and the context that connects them. It lives on your new tab, so it's there when the thought is, not behind an app you have to remember to open.

That's the whole idea, and most of our decisions come back to it. If a feature makes capture slower, it doesn't ship. If it adds a step between having a thought and writing it down, it doesn't ship.

We're early. There's a lot we haven't built yet.

Built for one person at a time

Slaet is made for individuals. People managing their own work, their own thinking, their own days.

That shapes what we build. Features answer to the person using them, not to a manager who wants visibility into someone else's task list. Nobody using Slaet should ever wonder whether it's working for them or reporting on them.

We're not interested in building a tool where the person typing and the person paying are different people. That's the design constraint, and it's the one that most affects what Slaet becomes.

What we've committed to

Two things we can state plainly:

We don't sell or share your data. Not to advertisers, not to data brokers, not to anyone. There's no version of Slaet where your notes become someone else's product.

Your data goes when you do. Delete your account and your data is deleted with it. No retention games, no dark patterns in the cancellation flow, no thirty day cooling off period designed to change your mind.

We'd rather commit to two things we can actually hold than publish a longer list we'd have to quietly walk back. The fuller detail on what we collect and how it's stored is in the privacy policy.

How this gets built

Slaet exists because I needed it, not because a market research deck said there was a gap.

Everything in it so far comes from the same place: using it every day and noticing what got in the way. Reminders, because writing a task down and then forgetting to act on it is its own kind of failure. Smart time detection, because typing “tomorrow at 3pm” and then hunting for a date picker is absurd. Task sharing, because sometimes the useful thing isn't the task, it's everything you figured out around it.

That's a narrow way to build, and it has a limit. One person's frustrations aren't everyone's.

So the next part matters more. If something's missing, broken, or annoying, tell us. We won't pretend every request gets built. Some things aren't feasible yet, and some would make Slaet slower in ways that hurt everyone else using it. But every request gets read, and the ones we build get chosen because someone actually wanted them.

slaetapp@gmail.com. It's read by the person who builds it.

Where this goes

The ambition is bigger than tasks and notes. Journaling, longer form thinking, the things you want to keep and find years later. That's the direction.

But we'd rather earn that slowly than promise it now. Right now Slaet does a small number of things and we're trying to do them well.

It's the beginning of something. Thanks for being here this early.