Scoped and priced upfront
Agree the scope, fix the price, and named engineers deliver against it. You know who is on your engagement, what the outcome is, and what it will cost.
When Fixed-Price is the right fit
Fixed-price delivery works when the shape of the work is clear before the contract is signed. If you can describe the outcome, the constraints, and the acceptance criteria, the model fits.
Right fit
- Scope is well-defined upfront, with named deliverables and a clear acceptance test
- The outcome is testable: it either works or it does not
- Timeline matters and a known end date has organisational value
- Regulatory overlay requires named-engineer accountability on sign-off
- Budget is approved as a total project cost, not a time-and-materials forecast
Wrong fit
- Open-ended research and prototyping where scope is expected to evolve
- Continuous platform operations or managed services (On-Demand Experts is the better path)
- Discovery-heavy phases where the first deliverable is a problem definition
What we deliver
Scoped, fixed-price Azure builds delivered by named senior engineers, architecture-first, infrastructure-as-code throughout. The packaged Azure track runs as a clear progression: set up the foundation, build out the platform, then run it.
Azure Foundation Starter
Set up the foundation: the governance skeleton, starter guardrails, and the repo you own.
Fixed, EUR 7,000
See Foundation Starter →Azure Platform Build
Build out the platform: all environments, networking, pipelines, and the full governance library.
Fixed, set after a scoping call
See Platform Build →Azure CloudOps
Run it: monitoring, governance, and incident response, by the engineers who build it.
Ongoing, scoped tiers
Read about CloudOps →Foundation Starter vs Platform Build
| Dimension | Azure Foundation Starter | Azure Platform Build |
|---|---|---|
| What it is | The core skeleton, set up once | The full production platform, built out |
| Scope | One management-group structure plus starter rules | All your environments, end to end |
| Policies | A starter set (allowed regions, mandatory tags) | The full policy library, rolled out and enforced |
| Environments | The structure to hold them (starts empty) | Built out across your real environments |
| Networking | Not included | Networking and connectivity |
| Pipelines | CI/CD for the foundation, tested and running | Pipelines across every environment, each change via review |
| Price | Fixed, EUR 7,000 | Fixed, set after a scoping call |
| Time | Around 2 weeks | Scoped to your environments |
| Best when | You want governance fast, or to try us small | You are ready to run production on it |
How a fixed-price engagement runs
Agree the outcome, constraints, acceptance, named engineers, and the fixed price.
Named senior engineers assigned, so you know who delivers.
We build on a review branch, so you see the plan before anything changes.
We deliver, verify, and hand over the repo, runbooks, and a walkthrough.
How we scope
Every engagement starts with a conversation, not a form. We adapt to where you are: some clients arrive with a finished specification, others with a rough goal and a deadline. We work from whichever end you bring. The scoping output (proposal, architecture artefacts, estimation breakdown, named engineers) flexes to what you need to see before you sign.
Change and risk
We accommodate change requests mid-engagement via written addenda. A change request defines the additional scope, adjusts the price if needed, and is countersigned before work starts on the new items. We do not death-march against a specification that no longer reflects what you need.
Rework caused by us: defects or missed requirements that were in scope, is on us and does not attract a change request. Rework arising from specification ambiguity gets a conversation, not a dispute. If scope materially shifts beyond the original brief, we re-quote rather than overrun, and we tell you when we see it coming, not after the fact.
Fixed-Price vs Bench vs Sourcing
Each engagement model suits a different shape of work. The scope shape is the clearest signal for which one fits.
Fixed-Price Delivery
When to pick: Outcome is defined, budget is fixed
Scope shape: Locked upfront
Billing: Fixed price per engagement
Current pageOn-Demand Experts
When to pick: Named engineers, flexible scope
Scope shape: Flexible
Billing: Hourly or retainer
Read about On-Demand Experts →Expert Recruitment
When to pick: Niche skillset we don't have on hand
Scope shape: Discovery
Billing: Per-placement or retainer
Read about Expert Recruitment →What stays with you
Every fixed-price engagement ends with a production-ready handover package. The artefacts depend on the engagement type, but the standard set covers everything you need to operate and extend what we built.
- Terraform or Bicep modules, pinned to a version and ready for your CI/CD pipeline
- Architecture decision records for every non-obvious design choice
- Runbooks for day-two operations: scaling, patching, backup, and recovery
- Audit pack where relevant: configuration exports, policy compliance reports, and change log
- Wiki content in your documentation platform, written for your team
- Post-delivery follow-up window for questions on what was delivered