Proposal audit
Estimation realism. Line items open to negotiation. Visible and hidden cost layers.
Independent IT project audit. Vendor proposal review, project scope, technical architecture, and risk, before you sign a contract you don’t fully understand.
The most expensive technology decisions are the ones already made. The decisions land before anyone independent gets a chance to challenge them.
A larger scope does not mean a better project. It means a larger invoice.
Your vendor optimises for their revenue. Nobody on that side of the table optimises for your budget.
Sometimes the best recommendation is to stop the project. The board knows. Your lawyer knows. You are the one nobody told.
Based on benchmarks from 24 audits. Indicative only. Pre-contract projects with stack overengineering and scope creep typically run 32–48% above necessary cost.
Indicative only · benchmarked against 24 anonymised audits · actual diagnosis requires proposal review
Two trajectories of the same hypothetical project. Numbers are illustrative, drawn from the median pattern across recent audits.
A finding inside a week. A recommendation you can act on.
Proposal, scope, architecture, business context. Mutual NDA signed before any material changes hands.
Component-by-component review. Cost validation against benchmarks. Architecture stress-test against actual load expectations.
Written diagnosis with line-item recommendations. One unambiguous verdict at the end: proceed, renegotiate, simplify, or stop.
90-minute session. I walk through findings in plain business language. Decision support for the harder calls.
Identities under NDA. All figures verified by clients post-engagement. Available in full upon a countersigned NDA.
| § | Sector | Stage | Diagnosis | Verdict | Outcome | Saved |
|---|---|---|---|---|---|---|
| 01 | Fintech · B2C | Pre-contract | Microservices premature · DB choice mis-sized | Renegotiate | Stack simplified · vendor retained | −38% · 4 mo |
| 02 | SaaS · B2B | Pre-contract | No market validation · proposed scope speculative | Stop | Project not started · pivot to discovery | $1.20M avoided |
| 03 | E-commerce · DTC | In-flight | Vendor mis-aligned with domain · scope inflation | Replace vendor | New vendor · 40% scope cut | $620K · 5 mo |
| 04 | Logistics · enterprise | Pre-contract | Proposal adequate · benchmarks within range | Proceed | Contract signed unchanged | Confirmed |
| 05 | HR Tech · SaaS | In-flight | 22 microservices for 80 req/s · maintenance bleed | Re-architect | Migration to modular monolith | −2 FTE · stability ↑ |
| 06 | Media · streaming | Pre-contract | Custom CMS proposal · no business case vs SaaS | Reframe | Headless SaaS adopted · integration only | $740K · 8 mo |
| Totals · last 24 months · 6 of 24 audits shown | ∑ 2.58 M + $1.20M avoided | |||||
Estimation realism. Line items open to negotiation. Visible and hidden cost layers.
What corresponds to a real business need. What can be deferred or removed without impact.
Whether the proposed system fits the actual scale. What has been over-engineered.
Vendor selection. Lock-in exposure. Domain alignment. Dependency map.
Budget creep. Slipping timelines. Where cost is still avoidable from here forward.
Decision support for organisations that need experienced technical judgement. Monthly retainer, not a full-time hire.
Selected names from a career inside software houses, as engineer, tech lead, and decision owner on technical matters.
Fifteen years inside software houses. I know exactly how proposals are built, where margins are buried, and which decisions get rushed past clients who have no one technical at the table.Today I sit on the other side. Yours.
A story about fintech, support queues, and the kind of engineer companies don’t know they need yet.
Read on SubstackIt needs to make them optional.
Read on SubstackTwo days. Ten dollars in tokens. Six-figure software contracts replaced over a weekend.
Read on SubstackSend the proposal, scope, or project brief. Independent IT audit response within 48 hours, NDA-first.