Third-party platform review
A review of a platform someone else built for you.Independent of the people who built it.
You paid for it, you will answer for it, and so far you only have the builder’s word that it is ready. A supplier, agency or freelancer is not well placed to mark their own work. I form my own view from the code, the running system and the configuration, then tell you in writing what is solid, what is fragile and what to fix first.
Price
Same three tiers, same fixed fee.
From £3,500
- Clarity Audit: From £3,500, 5 business days
- Production Audit: From £6,500, 7–8 business days
- Regulated & Investor-Ready: From £9,500, 10–12 business days
What sets the tier and the fee: how much there is to review, how many moving parts it has, what is at stake if it fails, and what access and documentation exist. A scoping call settles it before you commit. All prices exclude VAT. One fixed fee, agreed in writing before you commit: 50% on engagement, 50% on delivery. Review and remediation are quoted separately.
-630% → +36%
TURNAROUND
Support-agreement profitability in 6 months
Dexus · NTT · Kalibrate · Lancom
ENGAGEMENTS
Plus NDA'd startups and government
Twelve years
ENGINEERING DEPTH
Full-stack to CTO
Who it is for
Who this is for.
This is for you if
- A supplier, agency or freelancer has delivered a platform and you need to sign it off or pay the final invoice.
- You are about to take the platform in house or move it to a new supplier.
- Something about the delivery does not feel right and you want an independent second opinion.
This is not for you if
- You want a dispute settled. The report sets out evidence and recommended fixes; it is not a legal opinion.
- You want the review to keep the supplier happy. It will say what it finds.
What is covered
What the review covers.
The standard review covers the code, data, security, architecture, integrations and infrastructure. These matter most when someone else built it.
Independence from the builder
I form my own view from the code, the running system and the configuration before discussing design with the builder. Until then, questions to them are factual setup only.
Ownership of code and accounts
Whether the repositories, cloud accounts, domains and third-party services the platform depends on are in your name, or sit with the supplier.
FAQ
Common questions before booking.
What do I need to get from the supplier?
Read access to the repositories, a read-only cloud role, a staging environment with seeded data to run against, and any architecture documentation. I change nothing. Please make sure nothing shared contains production personal data.
Will you talk to the supplier?
Only for factual setup questions, such as how to run it, until I have formed my own view from the code, the running system and the configuration. After the report I can walk their developers through the fixes.
Will you fix what you find?
The review does not include changes to the code. Remediation is quoted separately, so you can take the report to the supplier, to your own team, or to someone else.
What do I get, what do you need from me and how does it run?
The same as any other review: a Confidence Report with a verdict, a one-page summary and every finding with its evidence. I need read-only access, nothing is changed, and I do the work myself. Access, process, fees and confidentiality are set out on the main review page.
Get an independent read before you sign it off.
Tell me who built it, what it does and where it stands. I will tell you whether a review fits and which tier.
Book a scoping call