👋 Hi there!
I've been making software products and leading teams for decades. I love building things that solve problems for people, and I'm proud to call myself an engineer.
I've worked at every size of company you can imagine: bootstrapped startups where I was the entire engineering team, mid-stage companies figuring out how to scale without losing their minds, and global public companies where a single decision winds through seventeen meetings before anyone writes a line of code. Each one taught me something the others couldn't.
The thing I keep coming back to: the hard part of building software is never the software. It's the space between people. The misread priority. The update that never made it to the person who needed it most. The meeting that could have been a sentence. I spent years watching talented teams slow themselves down with their own coordination overhead, and I started to think there had to be a better way.
Now the problem is getting much bigger. AI is automating execution fast – agents build agents, and natural language is replacing interfaces. As execution disappears as a bottleneck, coordination becomes the real constraint. Agents need the same real-time context and coordination that people do, and most enterprises can't scale AI agents past a pilot because of it. The failure mode is always the same: autonomous work drifts expensively from what the team actually needs.
That's why I founded Steady — with people I trust: remote-work veterans from Sapient, Basecamp, and GitLab who'd seen the same problems from different angles. Steady keeps plans connected to progress and teammates – human and AI – connected to each other through shared, real-time context. No meetings, no dashboards, no chat thread archaeology. Teams are starting to work alongside agents as teammates, not just personal assistants. We're building the system that makes that work.
Before building Steady, we codified the thinking in Continuous Coordination — an open-source set of principles for structured async coordination. It's the intellectual foundation underneath the product. If you're trying to make a distributed team run well, start there.
I also write The Steady Beat, a weekly newsletter for people running teams. If you're managing sprints, driving a roadmap, or just trying to make sure the right work gets done, it's for you.
If any of this resonates, I'd love to hear from you.