Senior people stay close to the work.
Every engagement is run by the partner who scoped it. You work directly with the people responsible for the design, the build and the delivery, and they stay accountable for it long after launch, with no account layer in between.
Leadership
PlaceholderPortrait of Caleb Okai
Caleb Okai
Partner · Engineering and platform
Caleb leads engineering and platform. He owns architecture, infrastructure and the technical direction of every engagement, and is the person clients work with on how a system is built and how it will hold up.
PlaceholderPortrait of Jesse Jones
Jesse Jones
Partner · Design and quality
Jesse leads design and quality. He owns the interface standard the team builds against and the testing approach behind every release, and works directly with clients on how a product looks, behaves and is verified before it ships.
How we work
We scope before we quote.
Every engagement starts with a call and a written scope. You get a fixed price for fixed work, and no hourly surprises three months in.
We build to be maintained.
Code is written to be read by whoever comes next, including your own team. Documentation is part of delivery, not an invoice line you can decline.
We say no when we should.
We take on a limited number of engagements at a time. If your work is not a fit, we say so and point you at someone it suits better.
We stay after launch.
Most of the value in software is created after the first release. Maintenance is a service we sell rather than a favour we grudgingly do.
Let’s build something real
Tell us what you are working on. The more context you give, the faster we come back with something useful.