An AI-first venture studio
All in on the frontier.
We’re an AI-first lab. We build with AI to do bolder work, faster.
We embrace AI, and we protect what matters.
Six positions behind how we build.
Lead with AI.
We're a lab, and building with AI is the work. Reach for it, test what's possible, move fast — we lean in because it makes the work better.
Know where the data goes.
What matters most is the data — what's inside a prompt, and where it travels once it leaves us. Before sending anything to a third-party model, it's worth a beat to ask what's in it and who can see it.
Using and wiring-in are different.
Reaching for an AI tool in your own work is one thing. Handing an autonomous agent standing access to shared systems — email, calendars, deals, money — is another. Both are welcome; the second just deserves a closer look before it's switched on.
Access is its own decision.
We trust each other — that part isn't in question. Trusting a colleague is simply separate from the access their tools are given. We grant standing access deliberately, one integration at a time, because the tricky parts often sit outside any single person's expertise.
Give agents their own identity.
When a tool starts acting on its own, we set it up the way we'd onboard a teammate — its own account, its own scoped permissions, its own trail — rather than running it on someone's personal access. An automated worker gets the access its job needs, and no more.
We set our own pace.
The lab moves quickly — adopting and automating early is part of the job. That pace is a choice we make here, and it doesn't automatically carry to every context we work in. Each one gets to decide how fast is right for it.
Using AI, vs. wiring AI in
Both sides start the same: a person and an AI assistant. What happens next is the whole difference.
Use AI in your own work and it’s a clear go. Hand an agent a key to email, calendars, deals, or money, and that key is what we look at — set up with its own identity before it turns.
No new standing access. Use freely.
Standing access to systems. Review required.
The how
Stance is the why. Here's the how — the boundary, the handbook, and the backlog we shape together.
We own it, and we keep it current.
Curated on purpose — one place that stays current, instead of scattered docs.