Engagement
How we work together.
Ranges, not a quote. A firm selling projects cannot publish a price table without losing the deals worth having — but silence on money loses trust, so here are the models and the bands.
Engagement
Three ways to work with us, ranges published.
Project
Range TBC
Defined scope, fixed outcome, one delivery team. For a launch with a date attached.
Embedded team
Range TBC · per month
Ongoing capacity alongside your own engineers, with a named lead and a standing roadmap.
Managed infrastructure
Range TBC · per month
We run what we built, with a response commitment in writing. Available on its own.
Straight answers
The questions that decide it.
Answered here rather than on an FAQ page, because these are the objections that stop a project starting.
- Who owns the code and the cloud account?
- You do, from the first commit. Placeholder — confirm your actual arrangement.
- What happens after launch?
- Either we operate it under a managed agreement, or we hand over against a documented plan on an agreed date.
- How quickly can you start?
- Placeholder — your real lead time. Vague answers here cost deals.
- What don't you take on?
- Placeholder — naming what you decline is the most credible thing on this page.
Tell us what's in the way.
A first call is 30 minutes with an engineer, not a salesperson. You'll leave it with an opinion, whether or not you work with us.