About Decisimo
Why we exist
The person accountable for a lending decision is almost never the person who can change it. They answer for the outcome at the regulator’s table, and then wait three weeks in an engineering backlog to move a threshold by two points. That gap is where bad policy survives.
Decisimo exists to close it. Rule sets, decision tables, scorecards and the decision flows that connect them are built, tested and released by the people who own the policy — with versions, approvals and a revision history, not with a deployment. Engineering keeps the platform. The risk team keeps the decision.
What the platform actually does is on the platform page.
How we work
The usual way to solve the build problem is with people. A forward deployed engineer sits with you, writes the decision logic, and stays on the invoice. It works, and it also means the vendor ends up owning your policy.
We do it the other way round. The AI assistant drafts the logic and shows you the diff; your team reviews it and approves it before any of it goes live. Nobody from Decisimo has to be in the room for you to change a threshold — or to explain, eight months later, why it changed.
The company
- Legal entity
- Decisimo Ltd, registered in England and Wales
- Company number
- 12245746
- Registered office
- 20–22 Wenlock Road, London N1 7GU, United Kingdom
- Data protection
- ICO registration ZA920573
- Information security
- ISO 27001 certified
- Operational resilience
- Controls aligned to DORA, which has applied since 17 January 2025
- Where it runs
- Regional execution endpoints, in a region you choose. We do not train models on your data.
- Contact
- hello@decisimo.com
- Elsewhere
- LinkedIn · Platform status
- Policies
- Privacy · Terms of Service · Data Processing · Human Rights and Modern Slavery
The controls behind those lines are on the security page, and the governance page maps them to what DORA and the EU AI Act ask you to evidence.
You are always ready to leave
Of everything you assess when you buy decisioning infrastructure, the exit strategy is what matters most, and it is the part we keep simple. Decision results are written continuously into a Postgres database you own, so your decision history is already in your systems. Your decision logic exports as a Markdown file. Execution runs on zero data retention: the data passes through to make the decision and is not kept here.
There is no extraction project to negotiate at the point you have decided to leave. That is deliberate. A vendor who is easy to leave has to stay worth keeping.