We spent the first three months before building a single line of code doing one thing: talking to founders. Not pitching. Not validating. Just listening to how they actually work — not how they wish they worked, not how they tell people they work at conferences. How they actually, honestly, messily work.

And a pattern emerged that we couldn't ignore.

Everyone has a capture problem. Almost nobody has a capture problem.

When we asked founders what frustrated them about their workflow, the top answer was always some version of: "I have too many places where things live." Notion for docs. Linear for tasks. Slack for conversations. Notes app for random thoughts. A browser with 47 open tabs.

So we started building what we thought they needed — a better capture tool. One inbox for everything.

Then one founder said something that stopped us cold. We'd just shown her a prototype and she said: "I don't struggle with capturing things. I struggle with what to do with them after."

"I don't struggle with capturing things. I struggle with what to do with them after."

We went back through every conversation we'd had. She was right. Every single person had told us this — we just hadn't been listening for it. The friction wasn't at the moment of capture. It was at the moment of processing.

The real problem is the gap between thought and action

Here's what actually happens when a founder has an idea. They capture it — in a note, a voice memo, a message to themselves. Then it sits there. Because turning a raw thought into a structured action requires mental effort that most people, in the middle of an already overwhelming day, simply do not have the bandwidth for.

So the thought sits. Then it gets buried. Then it gets lost. Then it gets rediscovered three weeks later, decontextualised, and either actioned too late or abandoned.

This is the insight that changed everything for us. We weren't building a capture tool. We were building a processing tool. Something that sits at the exact moment between "I have a thought" and "I know what to do with it" and does the heavy lifting so you don't have to.

What this means for how Vela works

The experience we're building toward is this: you type or say something raw — "need to rethink pricing before the investor call" — and Vela doesn't just save it. It understands what it is. It creates a task. It asks you one clarifying question if it needs to. It slots it into your day based on what's already there. And it surfaces it at the right moment.

That's not capture. That's thinking with you.

Why this is hard to build and easy to want

We've been working on this processing layer for four months. It's genuinely difficult — not technically, though that's hard too — but because it requires deeply understanding the shape of human thinking and the specific texture of how founders work. What looks like a task and what looks like a note. What deserves its own project and what should just be a checklist item. What needs to be done today and what needs to exist as a permanent reference.

Getting this wrong is worse than not building it at all. A tool that miscategorises your thinking is more disruptive than one that just gives you a blank box. So we're moving carefully, testing with the people on our waitlist, and iterating fast.

What we believe

The next generation of productivity tools won't just be faster or better-designed versions of what exists. They'll be tools that actually participate in your thinking process — not to replace your judgment, but to carry the structural load so your attention can go where it actually matters.

Vela is our attempt at that. And we're building it in the only way that makes sense for something this personal — with the people who are going to use it, from the very first day.