No open roles right now
We are a small senior team and we hire rarely. When we do, we start with the people who already introduced themselves. This page covers how the work runs, what we select for, and what happens when you write to us.
Working here
There is no account layer and no bench. Every engagement is staffed by the people the client meets on the first call.
We build AI systems for mid-market firms with no internal AI team, and we stay on to run them. That means short distance between a decision and its consequences. The system you design is the system you deploy, explain to the client's security team, and answer for after launch.
Nothing ends in a slide deck. The deliverable is a running system in the client's environment, with real users, and the write-up that lets someone else operate it.
What we look for
We do not hire to a growth target. We hire when the work needs another senior person, and we select for the same three things every time.
The deliverable here is a running system with real users, in the client's environment. Nothing gets counted as done before it runs.
Readouts, case studies, and handover notes carry the work. If a decision is not written down, it did not happen.
Baselines before launch, evaluation sets, audit records, and human gates on consequential actions. That is the standard on every build.
Introductions
Write to [email protected] with what you have shipped and what you want to build next. Links to work we can read or run beat attachments.
Every introduction gets read. The ones that fit the standard above stay on file until a role opens.
Hiring here starts from this file, not from a job board. If a role fits you, you hear from us directly.
When a seat opens we go to the people we already know. One email about what you have built is enough.