3-minute guide

Get started with Decisimo in 3 steps

Decisimo now uses a guided onboarding flow.
Tell us about your business, describe the decision you want to automate, and upload any existing policy or decision logic documents. Decisimo uses that input to generate your first decision flow.

1. Tell us about your business

Start with the basics so Decisimo can tailor the setup to your use case.

  • Select your country
  • Choose your company size
  • Estimate your monthly decision volume
  • Pick your industry
  • Add your business model

2. Describe the decision you want to automate

Explain what your flow should decide.

For example:

  • underwriting new customers
  • loan approvals
  • fraud checks
  • pricing decisions
  • eligibility checks

 

You can also upload supporting material, such as:

  • credit policy
  • underwriting manual
  • decision tree
  • rule document
  • other internal logic documentation

3. Let AI build your first flow

Decisimo AI uses your inputs and documents to generate the first version of your decision flow.

From there, you can:

  • review the generated logic
  • adjust rules and decision tables
  • add integrations or models
  • test the flow
  • publish it to staging or production

After your first flow runs, the Introduction Guide shows how to connect PostgreSQL or Supabase and backtest releases.

Decisimo decision engine

Put these checks into a decision flow

Create rules for credit, fraud or collections, then run them on live decisions.

See pricing

Related Articles

  • Decision Engineer: role, skills, and impact in automated decision making

    A decision engineer connects collected data to business meaning, decision logic and outcomes across the lending process. The role links underwriting choices to collections results and turns approved policy into testable automated decisions.

  • What should an anti-fraud team own and what should it buy?

    Anti-fraud is not a product you install once and forget. It is an operating capability built from data, decision logic, traceability, and continuous tuning across the customer journey. Companies can buy parts of that stack, but if they outsource the core logic and enriched data, they often create a lock-in problem that is hard to unwind later.

  • How Decision Making Evolved

    Decision logic moved from hard-coded if-then rules to predictive, data-led methods. Early systems were rigid. Requirements moved faster than code, so static rules fell behind. This article explains that shift, the rise of LLMs and agentic AI, and why deterministic, replayable decisions still matter in finance and insurance.

  • How to test a decision table properly

    Start by defining the table’s purpose. Then iterate. Draft test cases from each condition and action, run them, verify the outcomes, and refine the decision logic until it behaves predictably. Use synthetic datasets and valid value ranges when missing results are acceptable, or use exhaustive, edge-case testing, manually or with a tool, when the table must always return a result.

  • Advanced decision management systems vs BRMS

    Traditional BRMS can execute rules. Modern decision management systems handle more. This article explains why cloud-based decision management is a better fit for fintech, insurance, and e-commerce, with faster decisioning, more flexibility, and stronger support for compliance and real-time data.