The whole risk department, run by humans, AI and deterministic playbooks
A rule refers an application to a case, where an AI task extracts document details for an underwriter to review.
Full-cycle analytics and decisioning suite from application to collections
From written policy to a decision your system receives
Write the policy
Write rule sets, decision tables, scorecards and functions, or upload a PDF or Excel file for the assistant to propose them.
Test the policy
Test parts with chosen inputs, then run current and proposed policies on the same applications to see which decisions change.
Release the policy
Release it with sign-off by roles when the endpoint requires one; the lender's system keeps the same URL.
Receive the decision
Your system sends a JSON document and receives the decision and reason in the same call; data sources run in parallel.
Keep the record
Input and output can be written to the lender's Postgres; decisions waiting for documents or a person are worked as cases.
Industries Decisimo is built for
The assistant proposes. Your team decides.
Upload the policy as PDF or Excel, or paste it. The assistant proposes rules, tables and scorecards. The team sees each proposal as a difference and applies it; nothing runs until it is released.
Ask a questionWhat to read next
Simple, usage-based pricing
From € 500 per month with 50,000 decisions included, then € 0.01 per additional decision. Unlimited rules, models and users. Free trial, no credit card needed.
See pricingQuestions we get asked
What is a credit decision engine?
A credit decision engine is software that runs a lender's credit policy on each application and returns a decision. Decisimo lets the risk team write, test and release the policy itself.
What happens when the policy cannot decide an application?
The policy writes “refer” for an application it should not decide. The lender's system sends it to a case type's endpoint, and an underwriter works it from a role's inbox. The decision is posted back to the lender.