Before you commit to a system you didn’t build.
The site loads. The tests pass. Nothing is down. None of that tells you whether what the system claims is true — and you are about to put money behind it.
Nothing has to be broken for something to be wrong
The faults that cost the most do not look like faults. No alert fires. No test fails. Every page returns 200. The system is up, and what it says about itself is not true.
That is a different question from whether it works. It is whether what the system claims — in its payment path, its integrations, the obligations wired into its code, and the things it tells customers — matches what it actually does.
Four found in one day, in our own systems
These are ORIONPATH’s own production systems, on 27 September 2026. Ours is the honest example to use: it shows the kind of thing this work turns up, and it admits our own estate had them.
- A withdrawn price, still being advertisedOur own marketing site served a screenshot showing a setup fee we no longer charged. The visible page said free. The image said 99. Both had loaded correctly for weeks.
- A payment account that could not take a paymentBilling was wired to an account whose charging was not enabled. Test mode worked perfectly and nothing in the application was broken. The first real customer would simply have been unable to pay.
- A working integration with its API switched offCorrect code, a valid token, passing tests — and the API disabled in the cloud project behind it. Two scheduled messages would have failed with a 403 that nobody was watching for.
- An unsubscribe that nothing ever calledThe code that honours an unsubscribe request was complete and tested. Nothing in the system called it. A legal obligation wired to a function that never ran.
Not one of those would have shown on a status page. Four systems, four ways to be up and wrong, one day.
The ones worth most cannot be found from outside
Of those four, exactly one was visible from outside: the screenshot. Anyone could have seen it.
The other three needed a payment dashboard, a cloud console and the source. No crawler reads those. Nothing you can point at a domain reads those. They are reachable only with access, and access comes after an engagement starts.
That is the reason this is worth paying for rather than pointing something free at the URL. A scanner finds the cheap half. The half that decides whether you should sign is inside.
What it is, and what it costs
- Price
- From EUR 950
- A floor, not a quote. What it takes depends on how much system there is.
- What this is
- Technical due diligence on a live system: what it claims, read against what it does.
- What you get
- A written list of what was found, where it is, and what each one means for the decision in front of you. Plain language.
- What it needs from you
- Read access to the source and to the accounts the system actually depends on — payments, cloud, mail, whatever is wired in.
- What we will not promise
- What will be found. We have not seen your system, and a number promised before looking is a guess.
Tell us what you’re about to take on
A few lines is enough: what the system is, and what decision is waiting on it. If it is not something we can help with, we will say so.
Thanks. Your message is with us, and we will reply.
That did not send.
Please try again in a moment.
Something is missing.
Please check your name, email address and message, then send it again.
Get in touch at orionpath.io/diligence#contact.