Fixed-price engagement
A fixed-price review before you commit to a rebuild.
Two weeks. We read your codebase, infrastructure and delivery process, then hand you a written assessment: what to modernise first, what to leave alone, what it will take, and where the risk actually sits.
Who it is for
Teams with a platform already carrying users and revenue, deciding what to do next before committing budget. You know something has to change. You are not certain what, or in what order, or what it costs to be wrong.
It is not for greenfield ideas. If nothing is built yet there is no codebase to read, and a normal call is worth more to you than a paid review. Start there instead.
What the review covers
Current architecture and dependency mapping
What the system actually is now, not what the diagram from three years ago says. Services, data stores, the integrations you depend on, and the coupling nobody documented.
Technical debt hotspots and failure modes
Where the debt is concentrated, and what it costs you in practice. The modules every change has to pass through, and the ones that break in ways that are hard to diagnose.
What to modernise first, and what to leave alone
Most of a legacy platform is fine. We name the parts worth spending on and the parts where a rewrite would buy you nothing, with the reasoning behind both calls.
Risk register
What breaks first under load. What has no rollback path. What depends on a version that stopped receiving patches. Ranked, so budget goes to the top of the list.
Estimate range per recommended piece of work
Every recommendation carries a range, not a single number. You can take that range to your board, or to another firm, and it still holds.
What you receive
- A written assessment document, yours to keep whether or not you engage us further
- A prioritised modernisation sequence, with what to leave alone and why
- A walkthrough call where we present the findings and answer the awkward questions
How it runs
Scope and price, in writing
A short call to see the shape of the system. We confirm the fixed price and what is in scope before any work starts. No hourly drift.
Two weeks of reading
Codebase, infrastructure, deployment process, and the repositories you would rather we did not look at. We ask questions as they come up instead of saving them for the end.
Findings, then the walkthrough
You get the document first, so you have read it before we talk. The call is for the argument, not the summary.
Price
One fixed price, confirmed in writing before work starts. It does not move once agreed, and it does not depend on what we find.
Book a call and you will have the number the same day.
Review or audit?
If you mainly want an expert read on your architecture and codebase, start with the review. If you are planning a migration or modernisation programme, the Platform Audit covers the wider ground: cloud readiness, security and compliance posture, DevOps maturity, and how your integrations hold together.
See what the Platform Audit addsStart with the review, not the rebuild.
Two weeks, a fixed price, and a written assessment you keep either way.