Fixed, quoted after the free review
Ten working days of engineering
Every deliverable, regardless of what follows
| ID | FINDING | SEVERITY | CONSEQUENCE IF UNADDRESSED | EFFORT |
|---|---|---|---|---|
| — | Real redacted finding required | HIGH | Real consequence required | — |
| — | Real redacted finding required | MED | Real consequence required | — |
| — | Real redacted finding required | LOW | Real consequence required | — |
Repository, environments, credentials, ticket history and whatever documentation exists. We read the code before we ask you anything, so the first working session is about what you want the system to do — not about explaining what it currently does.
Output · Access confirmed · scope of the estate agreed in writing
Every service, dependency, data store, scheduled job and third-party integration drawn as it actually is rather than as the last diagram claimed. Each risk written down with a consequence, a likelihood and a cost of leaving it alone.
Output · Architecture map · risk register, ranked by consequence
Where this breaks next, and what it takes down when it does. Run-cost model, capacity headroom against your growth assumptions, and the security and compliance findings that cannot wait behind a rebuild.
Output · Failure-mode analysis · run-cost model · security findings
Sequenced work with its dependencies made explicit, a recommendation on what to repair versus replace versus retire, & a fixed price against a fixed scope for whatever we think should happen next. Presented live, with the engineers who did the work.
Output · Remediation plan · fixed-price proposal · recorded walkthrough
Because it is two to three weeks of senior engineering time, and because the alternative pricing — free, unscoped, performed by someone whose only path to revenue is selling you the build — produces a document you cannot trust.
The industry convention is to price discovery at roughly five to ten per cent of the estimated build budget. On a $300,000 program that puts the audit somewhere near $25,000, and it is the cheapest point at which the program can still be cancelled.
Then that is what the report says, and you keep it. An assessment that can only ever conclude “hire us for the rebuild” is not an assessment, it is a proposal with a longer timeline.
We would rather write a report that saves you a seven-figure mistake and earns us nothing further than write one that wins us a program we do not believe in.
No, and the walk-away clause is contractual rather than a gesture. Every deliverable is yours, in editable formats, with no licensing conditions attached. Clients have taken our remediation plan to their in-house team or to another firm, and that is a legitimate outcome of buying it.
Read access to the repositories, the ability to run the system in a non-production environment, ticket and incident history, and ninety minutes each with two or three people who have worked on it. We do not need production data, and we ask not to be given it.
Number of distinct services and data stores, how many runtimes and languages are in play, whether infrastructure is defined in code or by hand, whether a compliance regime applies, and how much of the institutional knowledge still exists inside the company. We quote the fixed number after the Code & Risk Review, not before.
Yes, and we will sign yours rather than insisting on ours.

Celebrating Our Silver Jubilee - 25+ Years Of Software Engineering Experience | Since 2002
1-416-888-8130
©2002-2026 Webfix, Inc. All Rights Reserved. Webfix™
Design By Founder/CEO – Shahzad Ali
Privacy | Term Of Use | Company Policy | Site Map | Insights