Financial services

Explainable answers from portfolio risk to customer behavior.

Product, risk, and finance teams ask in plain language. Every answer uses your governed metrics and shows each step and source.

Book a demo
Question
Completed
Summarized the loan book by month
2s
Built a scenario planner on the Loan book by month block
3s
Originations€12.1Mper month by month 12
Credit losses3.1%annualized default rate
Net interest income after losses, 12 months€8.7M
+0.0% vs baseline
€0.85M€0.72M€0.59M
M1M4M7M10M12

The baseline assumes originations keep growing 2.1% a month and defaults stay at 3.1%, the averages of the last three months.

Definitions and access, set once by your data team.

Your data team defines metrics like chargeback rate once, in YAML kept in Git, along with who can see which portfolio.

How the semantic layer works

models/transaction.yml

models:
  transaction:
    name: Transaction
    sql: |-
      SELECT t.*
      FROM core.transactions t
      JOIN core.portfolio_access a
        ON a.portfolio_id = t.portfolio_id
      WHERE t.is_test = false
        AND a.user_email = '{{user_email}}'
    primary_key:
      - transaction_id

Policies and runbooks say how to read the numbers.

Your risk policies and incident reviews already say how to read the numbers. Supersimple applies them as visible steps and cites them.

Merchant risk policy v3

Escalate any merchant above a 0.9% monthly chargeback rate.

Chargeback rate > 0.9%
Risk data dictionary

Use Portfolio Region for regional reporting. Merchant Country is only the registration address.

Uses Portfolio Region
Postmortem: 3DS degradation

Step-up checks were skipped for Visa card-not-present payments from September 9 to 11.

[1]Cited in the answer

What would your team ask first?