Skip to content
Okko Oulasvirta
Financial Services

Underwriting Decision Workspace

Bring the application, the risk data and the pricing guidance together so an underwriter can price and accept — or decline — with the full picture and a clear record.

The decision it supports

Should we accept this risk, on what terms, and at what price?

What changes

More consistent underwriting, quicker quotes on straightforward risks, and time freed for the risks that genuinely need an underwriter's judgement. The underwriter sets the terms; the application assembles and records the basis.

Data domains

  • Customers
  • Accounts and policies
  • Products
  • Risk and exposure
  • Finance and margin

Interactive preview

Underwriting Decision Workspace is described here as an opportunity rather than shown as a working demonstration. The interactive build for this industry is Customer & Risk Decision Workspace — it uses the same primitives, the same governed data model and the same decision-to-action pattern this application would.

We build one flagship per industry properly rather than four shallow ones. The pattern transfers.

The workflow

  1. 01A submission arrives for a new or renewing risk
  2. 02The applicant, the exposure and any prior relationship are assembled
  3. 03External risk data and documents are extracted and summarised with citations
  4. 04Pricing guidance and portfolio appetite are shown for context
  5. 05Terms and price options are proposed, each with its rationale
  6. 06The underwriter sets the terms, refers, or declines
  7. 07The quote and its supporting evidence are recorded and issued

Platform capabilities most relevant here

  • OneLake

    One governed copy of enterprise data that analytics, AI and applications can all build on.

  • Curated business entities

    Agree once what an order, an asset or a customer means — then reuse it everywhere.

  • Ontology

    Encode the vocabulary, relationships and rules your business already works with.

  • AI functions

    Apply language models to business data as a normal part of a data pipeline.

  • Fabric Apps

    Build the application where the governed data already lives, instead of copying it out.

  • Application state

    Remember decisions, assignments and approvals — the things a report cannot hold.

  • Enterprise APIs

    Turn a decision into a change in the system that actually runs the process.

Not every application needs every capability. This is the subset that this decision actually depends on.

Talk about building this