The best tools get built by the people using them.

We met at Asana during the companys AI push. Ethan started there as a rep, then spent three years on AI: leading global AI adoption and helping bring AI Studio to market with enterprise customers. Ben was a Technical Solutions Architect the whole time, building the GTM AI workflows and agents that Asanas own teams used millions of times internally. Mark was at Asanas Work Innovation Lab for a few years, running AI Insights research on how teams actually get work done with and without AI.

One thing kept coming up. The tools that actually get adopted are the ones built by practitioners who obsess over the experience. Cursor and Claude Code won because engineers built them for engineers. We think the same is true for customer-facing work. If a tool fits into how people actually work, they use it. If they use it, the data gets better. And then everything downstream improves for everyone, managers included.

No matter what happens with AI, the person on the other side of the call still matters. Were building the tool we wished we had back when we were the ones doing the work: the reps scrambling before every quarterly review, the builders shipping agents at scale, the researchers trying to figure out what actually worked.

Ethan DeWaal
Ethan DeWaal

Co-founder & CEO

Led global AI adoption at Asana. Started as a rep, then helped build and bring AI Studio to market with enterprise customers.

Ben Graney Green
Ben Graney Green

Co-founder & CTO

Led Technical Solutions Architecture for Asanas biggest customers. Built GTM AI workflows and agents used millions of times at Asana.

Mark Hoffman
Mark Hoffman

Co-founder & Chief Research Officer

Led AI Insights at Asanas Work Innovation Lab. Earned a PhD in computational social science at Columbia, then taught social network analysis at Stanford.

What were building

Relationships are a graph, not a database.

CRMs got bloated. They ended up serving managers more than the people who fill them out. Relationships form a graph: who knows whom, what they've agreed to, and what's at stake. That graph should build itself from the conversations your team is already having.

Designed for calm and confidence.

Most tools for this work add noise. We want Enzo to be the opposite. You open it before a call and feel ready, not overwhelmed. That sounds simple but it takes real discipline to build.

Insight you didn't know to ask for.

Killing busywork is table stakes. What we care about is the moment Enzo surfaces something that would have taken you three hours to find: a blocker from a past meeting, a pattern across accounts, a signal you couldn't have searched for. Research-grade pattern recognition, in the moments that matter.

Were hiring soon. If this is the kind of problem you want to work on, reach out.