Request a quote. Tell us about your project.
Every engagement is scoped to your goals — share a few details and we'll send a custom proposal, usually within one business day.
Your project details
The more context you share, the more accurate your quote. Nothing here is mandatory beyond your name, an email address and a short description — a two-line description is enough to start a conversation, and we will ask for the rest on the call.
Quoting a specific line item? Pick it from the service catalogue.
Three engagement models
We do not publish packages, because a package forces the work to fit the price rather than the other way round. Every quote lands in one of three shapes, and which one we propose depends on how well defined the work is when you come to us.
Fixed-price project
For work with a definable end state — a platform build, a cloud migration, a CI/CD implementation, an ISO 27001 readiness programme. We scope it in a paid or unpaid discovery phase depending on size, then commit to a price and a date. Change requests are priced separately and visibly, so the number you approved does not quietly drift. This is the right model when you need budget certainty more than flexibility.
Monthly retainer
For ongoing ownership rather than a deliverable: managed DevOps, observability and on-call, continuous security scanning, compliance evidence, dependency and patch management. You get an agreed capacity and response commitment each month, and we carry the operational load between releases. Most clients arrive here after a fixed-price foundation phase, because a platform is worth much less without someone accountable for keeping it healthy.
Dedicated team
For a roadmap rather than a project — engineers allocated to you, working inside your process and your tooling, with priorities set by your product owner. This suits organisations that need to move faster than hiring allows but do not want to outsource the direction of the work. Scale up or down with notice; the team composition is agreed in writing rather than substituted silently.
What to include in your brief
You do not need any of this to get a reply, but each item removes a round trip — and the briefs that get accurate numbers back fastest tend to cover most of them:
- The outcome, not the task. “Releases take three weeks and we cannot roll back” tells us more than “we need a Jenkins pipeline”.
- What already exists. Current stack, cloud provider, repository host, and roughly how many services or environments are in play.
- Any hard constraint. A compliance framework you are being audited against, a data-residency requirement, a launch date tied to something outside your control.
- Who else is involved. Whether there is an incumbent vendor, an internal platform team, or a procurement process we should be scoping around.
- A budget band. Not a number to be held to — a range, so we propose something that is actually buildable within it instead of wasting a cycle.
Quote questions, answered
How do you price projects?
Every engagement is scoped individually. After you share your goals, stack, and timeline, we propose a fixed-price project, a monthly retainer, or a dedicated team — whichever fits best. No fixed packages to squeeze your project into.
What happens after I request a quote?
We review your request and reply within one business day — usually with a short call to confirm scope, followed by a written proposal with timeline and pricing.
Do you support government projects?
Yes. We work in regulated and public-sector environments with data residency, audit-ready documentation, and tender support.
Can I request a custom engagement?
Absolutely. If none of the standard plans fit, request a brief and we'll propose a tailored engagement model.