.NET & backend
Platform engineering for .NET-heavy estates.
Architecture reviews, modular monoliths, service decomposition, performance work, .NET 9 migrations.
We take on engagements where the technical work is the work — architecture rebuilds, platform engineering, applied AI, system modernisation. Each engagement is led by a Senior Principal and staffed end to end.
Scope is bound at the Epic level — the unit of committed business value. Stories and tasks live inside the team and can be reshaped during delivery, provided the Epic outcome is preserved. The team has authority over the work; the contract has authority over the outcome.
Fees are tied to the outcome committed in the Statement of Work, not to hours consumed. Time-and-materials pricing is used only when expressly chosen — and the SoW always says so when it is.
Four milestones. Kickoff at 30, mid-engagement at 30, pre-handover at 30, acceptance at 10. The closing tenth is the lever that keeps the closing month aligned with handover and knowledge transfer.
Engagements are led by a Senior Principal and staffed by Principals and Senior Consultants. Substitutions require equivalent seniority and written client notification.
The IP framework distinguishes three categories. Each is treated separately. The full text lives in our Master Service Agreement; the summary is below.
| Bucket | Owner | Treatment |
|---|---|---|
| A — Background IP | The disclosing party | Each party retains its prior IP. Background IP incorporated into a deliverable is licensed to the client for internal use. |
| B — Foreground IP | The client, on full payment | On full payment of the SoW, all IP created specifically under that SoW is assigned to the client. |
| C — Client materials | The client | The client retains its materials. We receive a non-exclusive, time-limited licence for the engagement only. |
| When | What | Detail |
|---|---|---|
| Week 0 | Signature & kickoff | Both parties countersign the MSA and SoW. The team mobilises and the engagement workspace stands up. |
| Week 1 | Discovery sprint | First two-week sprint. Confirm Epic boundaries, set working agreements, establish the cadence. |
| Week 2 | Delivery begins | First Epic enters delivery. Sprint cadence is two weeks; review at every sprint boundary. |
| Week 8 | Mid-engagement review | Half-way checkpoint. M2 invoice. Re-prioritise for the second half. |
| Week 14 | Pre-handover | All Epics complete. Deliverables submitted for acceptance. M3 invoice. |
| Week 16 | Acceptance & close | Acceptance window closes; engagement closes; M4 invoice. |
Architecture reviews, modular monoliths, service decomposition, performance work, .NET 9 migrations.
Design system implementation, frontend platform work, performance and accessibility, framework migrations.
Orchestration patterns, model tiering, RAG architectures, agentic workflows, evaluation harnesses.
Pipeline design, infrastructure as code, observability, on-call practices, value-stream mapping.
Warehouse design, pipeline reliability, analytics engineering, instrumentation that stays accurate.
Architecture review boards, ADR practice, technical strategy work, evolutionary architecture coaching.
Most engagements begin with a short conversation, followed by a proposal, followed by signed MSA and SoW. We can move quickly when both sides are aligned.
Start a conversation