Six rungs. One ladder. 

It runs in your cloud, on your API accounts, under your keys. We use business or enterprise tiers where the provider's terms exclude training on your data, and we put that in writing. During a build we see what a screen share shows us and nothing more. Anything that must never leave your tenancy is identified in the Survey and designed around, not discovered later.

No, and we will not imply otherwise. We are two people, and a certificate from a two-person firm would be theatre. What we do instead is answer your security questionnaire properly, build to least privilege by default, and have the person who did fifteen years of production engineering own that decision. If your procurement genuinely requires a certified vendor, we are the wrong choice and we will say so on the first call.

You do, from the first commit. Code, prompts, system instructions, orchestration logic, evaluation sets, documentation and runbooks, in your repository. There is no license to revoke, no platform to be locked into, and nothing to hand back if you stop working with us.

It will be. Providers deprecate model IDs constantly, sometimes with days of notice. We pin versions rather than tracking whatever is newest, and we keep an evaluation suite so that swapping a model is a measured decision rather than a hopeful one. On a retainer, migration is included. Without one, we will still tell you it is coming.

Because something is watching. The evaluation suite runs on a schedule and you get the trend, so slow quality drift shows up as a line going down rather than as a customer complaint. Alerting covers failure, cost spikes, and upstream schema changes, which is the failure nobody expects: the API did not break, it just started returning a slightly different shape.

Both of us are across every engagement, and everything is documented while we build rather than afterwards, so either of us can step in. The code and the accounts are yours from day one, so the worst case is that you have a working system and full documentation and need a new builder, which is a normal problem rather than a crisis.

Yes, and the documentation is written for that on purpose. The requirements, architecture and acceptance criteria are vendor-agnostic. Some clients take the Blueprint entirely in-house. Some take it in-house and come back for the one part nobody wanted to own.

Model and third-party costs sit on your accounts, so you see them directly and they stay yours. For a single workflow it is usually a small monthly number rather than a meaningful line item, and we report cost per run as part of the build so it is never a surprise. We will give you the estimate before you commit, and we would rather over-estimate it.

The Build carries a shipping guarantee: in production in 30 days or you do not pay for the build. We do not guarantee results, because results depend on your data and your team, and anybody promising otherwise is selling you something. What we guarantee is the part that is in our control.

Regularly. We are two generalists, not a sector practice. The industries listed are where we have shipped, which shortens discovery, but the thing we are actually good at is learning an operation quickly and building for it. If we would be slow in your domain, we will tell you before you pay us.

We hold three active engagements at most, so it depends on what is running. A Survey can usually start within two weeks. If we cannot start when you need us, we will say that rather than sit on your enquiry.

No. Fixed-scope work is fixed scope. Retainers and embedded work are month to month with 30 days notice from either side, and the rate is held for the engagement.