Working together

Engagement models

Six ways to work with us, and how to tell which one you need.

The shape of the contract matters as much as the work inside it. Fixed scope suits a problem that is already understood, and punishes one that is not. A dedicated team suits a product that keeps moving. Below is what each model actually commits you to, what it costs you when it goes wrong, and the questions that decide between them.

What's Included

Fixed scope, fixed price

One agreed deliverable, one price, one date. Works when the requirements are genuinely settled and can be written down. Everything not written down is a change request, which is the deal you are making: certainty on cost bought with rigidity on scope.

Phased build, priced per phase

The same discipline without pretending the whole thing is knowable up front. Each phase is scoped, costed and approved on its own, and each one leaves something usable behind. You can stop at the end of any phase and still own something that works.

Dedicated team

Engineers assigned to your product and nobody else's, working your backlog and your cadence. Billed monthly per person rather than per feature. Suits a product that will keep changing after launch, where the requirement is capacity rather than a deliverable.

Staff augmentation

Individual engineers added to a team you already run. Your process, your standards, your tickets. We handle contracts, payroll and replacement; you handle the work. Suits a team that knows exactly what it needs and needs more hands to do it.

Advisory engagement

A short, scoped piece of thinking that ends in a written plan rather than a repository: an assessment, an architecture review, a build or buy decision. Priced on its own so it stays useful even if the answer is that you should not build the thing.

Support and maintenance

For something already live, ours or somebody else's. Agreed response expectations, a named person who knows the system, and a monthly budget for the small changes that otherwise queue for a quarter. Separate from any build, so neither starves the other.

Frequently asked questions

What You Get

Tangible outcomes delivered to your business from day one.

You own the code, the repository, and the cloud accounts from the first commit
Scope agreed in writing before anything is invoiced against it
Changes priced and approved before they are built, never after
One named person accountable for delivery, not a rotating queue
Working hours and overlap agreed in writing, not assumed
Notice periods instead of lock-in, and a documented handover either way

Send Inquiry

Regarding: Engagement models
What are you looking for? optional, pick as many as apply

By submitting this form, you agree to our Privacy Policy and Terms of Service.