Work with us
We design agent systems that outlive the next model.
The model you pick today will be replaced within a year. We design the system around it so that the replacement is a configuration change, not a rebuild. Remote, for companies in the United States.
How an engagement runs
Three steps, each one useful on its own
Map the work
We sit with the people who do the work. We list the tasks, the systems they touch and the decisions they make. We mark where an agent pays for itself and where it must not act alone.
Design the system
We draw the parts and the interfaces: which model does which step, which tools connect through the Model Context Protocol (MCP), where your company’s context lives, which skills the agents load, who approves what, and how you measure each part.
Build the first agent and hand it over
We build the first working agent on that design, with your team, inside your tools. You get the code, the runbooks and the evaluations. Your team owns and runs it after we leave.
What every design keeps
Four rules we do not trade
Any model can be replaced.
The design names an interface, not a vendor. A cheaper or better model goes in without a rewrite.
Your context stays yours.
Instructions, procedures and memory live in plain files and in your own stores, not inside one vendor’s product.
Each part gets only the access it needs.
Every tool connection has its own permission. A human approves the actions that cannot be undone.
Each part has a test.
We write evaluations per part, so that you can change one part and know what changed.
Who this is for
Built for teams that ship
Founders, operators and engineering leaders at US companies who want agents in real work, not in a demo. We work as forward deployed engineers: in your tools, with your team, on your problem.
Start here
Tell us about the work
Describe the work you want agents to do. We reply within two business days.