We start with the problem, not the technology.
Probatus Labs is an independent product and engineering company. We work on financial and operational problems that are expensive but not visible — the ones that do not appear as a single line in any report.
Those problems have a particular shape. They are made of small, individually reasonable decisions repeated at volume: a price adjusted for a good reason, a document re-keyed because the format did not match, a reconciliation done by hand because two systems disagree. No single instance is worth anyone’s attention. The accumulation usually is.
Our work starts in B2B distribution, where this is most measurable: transaction-level pricing and margin analysis, and the quoting and document workflows that sit around it.
Find → Prove → Fix
Most software projects begin with a decision to build and work backwards to a justification. We work in the other direction, and the order is the whole method.
- 01FindEstablish what is actually happening — in the transaction data, or in the process as it runs today rather than as it is documented.
- 02ProveQuantify it. How often it happens, what it costs at that frequency, and the evidence behind the claim. If we cannot answer this with numbers, there is no project.
- 03FixBuild the smallest system, workflow or control that closes the gap — and only when the number justifies it. Sometimes the honest answer is that it does not.
Four things we hold to.
Evidence before build. The assessment is a deliverable in its own right, not unpaid pre-sales work. That is the only arrangement in which “do not build this” is advice we can afford to give.
Your systems stay where they are. We start from an export or a walkthrough. Nothing is installed, integrated or migrated to get a first answer, and nobody has to hand over system access.
The smallest useful system. A focused workflow that ships in weeks beats a platform that ships in six months, because the six-month one is specified against a business that has already changed.
Findings are evidence, not verdicts. An anomaly is not automatically an error. We surface where the numbers deserve attention; your team decides what is actually wrong.
Saif Ullah, Founder
I’m a full-stack engineer with over four years across four companies, building integrations, data pipelines and internal systems on React, TypeScript, Node and MongoDB. Probatus is the work I’d rather be doing: finding the expensive, invisible problems inside business data and proving what they cost before anything gets built.
Probatus is deliberately small. One person reads every message, handles every dataset, and does the analysis. That is a constraint, and it is also why an outside firm can be trusted with a transaction export.
Based in India. Working with distributors and partners in the UK, the Gulf and India.
Working with consultants and agencies
You own the system of record and the client relationship. We investigate the exceptions. If you already serve distributors, the useful first step is not a partner programme — it is testing this on one client’s data and seeing whether the output is worth anything to both of you.
Have a problem worth investigating?
Tell us how the workflow works today, where it hurts, and what you have already tried.
20-minute conversation · No ERP integration required