The more context you share, the more accurate your quote. Nothing here is mandatory beyond an email address — a two-line description is enough to start a conversation, and we will ask for the rest on the call.
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.
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.
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.
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.
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:
Prefer to talk first? The contact page has our direct line and address, and the services page breaks down what each of the six capabilities covers before you commit to a call.