Services

Software, built the way we build our own.

We take on a small number of client engagements at a time and staff each one with the team that ships our own products. Here is what we take on, how an engagement runs, and what working with us is like.

Senior onlyThe people on the first call are the people who write the code.

A demo every weekFrom week one. No long silences and no big reveal at the end.

You own everythingCode, infrastructure, documentation and the accounts they live in.

Estimate in writingFixed scope or a monthly arrangement, agreed before work starts.

01 — What we take on

Four kinds of work. Each starts with a written estimate.

AI systems

Agents, retrieval, model integration and the evaluation harnesses that keep them honest. Built to hold up in production, because ours has to.

Good fit: a team with a working product that needs AI features it can trust, or an AI feature that works in the demo and fails in the field.

LLM agents and workflows Retrieval and search Evaluation and observability Model routing and cost control

Product engineering

Web and mobile applications end to end: architecture, backend, interface and deployment. One senior team from the first call to the first release.

Good fit: a company that needs a product built properly, without assembling and managing its own team first.

Web applications Mobile apps APIs and integrations Cloud architecture

First versions for founders

A working first version with scope agreed before we start. Weeks, not quarters. You see progress every week and own everything we write.

Good fit: a founder with a clear problem, early users to put it in front of, and a date it has to be real by.

Scope and estimate up front Weekly demos Production deployment Full code ownership

Run and improve

For software that already exists, ours or anyone’s. We take over the codebase, keep it healthy and ship a steady stream of improvements on a monthly arrangement.

Good fit: software that earns money and deserves better care than it is getting.

Codebase takeover Monitoring and reliability Feature roadmap Monthly reporting

02 — How an engagement runs

Three stages, in order. Each ends with something you can read, run or reject.

011–2 weeks

Discover

We learn the domain, agree scope and success criteria, and put an estimate in writing. If we are not the right team, we say so here.

You get: a written scope, estimate and plan you can take anywhere.

02Weekly cycles

Build

A working demo every week. You talk to the people writing the code, not an account layer. Scope changes are re-estimated in the open, never absorbed silently.

You get: running software every week, in a repository you own.

03Handover or retainer

Run

We deploy to your infrastructure, hand over documentation and access, and either train your team or stay on to operate what we built.

You get: documentation, access, and a team that knows how it works.

Team: Senior engineers and designers only. The people on the first call are the people who build.
Cadence: A working demo every week from week one. No long silences, no big reveal at the end.
Ownership: Everything we write is yours: code, infrastructure, documentation and the accounts they live in.
Pricing: Fixed scope with a written estimate, or a monthly arrangement for ongoing work. Agreed before we start.
Communication: A shared channel with the actual builders. Questions get answered by the person who knows.
After launch: We hand over cleanly and train your team, or stay on to run what we built. Your choice.

Start here

Tell us what you are trying to build.

Two or three sentences is enough to start. We reply within two working days with questions, an honest read on fit, and what a first step would look like.

Start a project [email protected]