Platform review and technical due diligence for technology founders.
An independent review of what has actually been built, before you raise, hire or scale. Two days or one week, at a fixed fee, from the former CTO and CEO of ResDiary, who still writes code.
Not sure yet? Start with a free scan.
Send the address of your product and Colin will look at what can be seen from outside: hosting, security basics, the third-party code you load, performance, and your public APIs and integrations. You get a short written report, then a 30-minute call to go through it.
The scan only covers what is publicly visible. It will raise questions rather than answer them, and it is not a verdict on your platform. What sits behind the login, in the code and in the team is what the two-day review is for.
If you have a mobile app or the product is behind a login, say so and Colin will ask for a test account. Please do not send passwords through the form.
A focused written report: what stands out, what needs attention first, and a clear view on whether a fuller review is justified. It stands on its own. A board can act on the report without commissioning anything further.
Who it suits
Founders who want an honest read before a raise, a hire or a rebuild, and boards that want a quick independent view.
A hands-on review of what has actually been built, assessed against where the business is trying to get to. A written report and a prioritised list that separates what needs fixing before you go further from what can wait.
Who it suits
When the two-day report says it is worth going further, or before a raise or sale where technical diligence is coming.
Where there is more than one codebase or product, or the ownership questions need real digging, it is two weeks, and you will know that from the scoping call along with the fee.
The full review looks at eight areas. The two-day assessment takes the ones carrying the most risk.
Architecture, and what it will carry. How the system is put together, whether it holds as usage grows, and which decisions will be expensive to reverse later.
Code quality where it matters. Not style. Whether the abstractions are coherent, whether the tests cover the things that would actually break, and whether someone new could work in it without a guided tour.
Security and data handling. Authentication, access control, secrets management, and whether customer data is properly isolated. This is where fast-built products fail most often and most publicly.
Ownership and key person risk. Who owns the IP, what the contracts say, and how much of the system lives in one person's head.
Infrastructure and cost. What it runs on, what it costs now, and what the curve looks like at ten times the load.
Delivery. Whether the team can ship a change safely. Environments, deployment, rollback, and what happens when something breaks at the wrong moment.
AI, on the same terms as everything else. What has been built with it, what the vendors are really delivering, and what the roadmap can actually carry. Assessed as engineering, not as a category of its own.
Diligence readiness. What a technical due diligence process would surface, and what is worth fixing before it does.
How it works
Scoping call. A short call to agree what is in and arrange access.
Fixed fee, paid before work starts. The fee is fixed and agreed on that call. The review starts once it has been paid in cleared funds.
Review and working session. Findings are delivered as a written report and walked through with the leadership team or board in a working session.
What you are left with
A written report and a prioritised list that separates what needs fixing before you go further from what can wait. Where it helps, that includes how to describe the outstanding items to an investor or an acquirer, because the answer is almost never that there is nothing outstanding.
The output is what to do next, not what to buy next. Nothing is sold on the back of a review, and any referral arrangement is disclosed before you act on a recommendation.
Questions
Is the free scan a cut-down review?
No. It only looks at what anyone can see from outside, and it gives you questions to ask rather than a verdict. The review looks at the code, the infrastructure and the team.
What access is needed, NDAs, code access, how quickly a review can start and what happens if it finds something serious are all answered in the questions on the home page.
Start with a call.
Most reviews begin with a 30-minute call to talk through where you are, what is prompting the question, and whether this is the right fit. No agenda required.