All case studies

Siena Capital Group

Caterina — a portfolio management platform for the insurance-linked securities market.

Client
Siena Capital Group
Product
Caterina
Sector
Insurance-linked securities, capital markets
Platform
Web, light and dark
A Caterina deal page: a market ticker across US, Europe and Asia; an above-normal hurricane season forecast carrying an elevated-risk badge; the Hestia Re 2026-1 deal with its launch, update and priced timeline; and a class structure table showing expected loss, bucket, spread against the bucket average and multiple for classes A to D.
01 — Overview

One place to price a catastrophe bond, and to keep the indices built on it correct.

Caterina is a portfolio management platform for the insurance-linked securities market — where a team follows a catastrophe bond from launch through to pricing, and where the indices built on those bonds have to stay correct when the underlying data moves.

The design problem is density with consequences. A deal page carries live market context, the season’s peril outlook, the deal’s own timeline and a class-by-class table of spread guidance all at once — and it has to be honest about which of those numbers are provisional, because somebody is about to price against them.

What I did

  • Index dashboard concepts, explored as competing options rather than one proposal
  • Light and dark treatments across the platform
  • The Index Impact Workflow, documented end to end with its backend and front-end halves
  • Reports and category layer
  • Design reviews with the team at fixed points
02 — Opportunities

The questions the platform had to answer.

  1. 01How might we put live market context, the season’s peril outlook and one deal’s economics on a single screen without any of them shouting over the rest?
  2. 02How might we make a class structure table scannable, so the outlying spread is the thing you notice first?
  3. 03How might we make it obvious which figures are provisional and which can be priced against?
  4. 04How might we let a data change ripple through every affected index without touching production until a person has approved it?
  5. 05How might we leave an audit trail that still answers who approved what, and why, months later?
03 — Approach

Six areas of design work.

01

Market context, always on

  • A ticker across US, Europe, Asia and currencies sitting above the work
  • Index values carrying their open or closed state, not just a number
  • Movement shown in points and per cent together
02

The deal at a glance

  • Launch, update and priced held on one timeline, each with the note that moved it
  • Issuer, ceding insurer, trigger type, modelling agent, payment dates and data room in a single overview
  • Related deals kept alongside rather than a click away
03

A class table you can scan

  • Class, covered area, expected-loss base, bucket and spread read across one row
  • Movement against the bucket average drawn as a bar as well as a number
  • The multiple carried at the end, where the comparison lands
04

Peril outlook where it belongs

  • The season forecast raised to a banner above the deal rather than buried in a report
  • Named-storm and hurricane projections stated with the landfall threat and whether the science is validated
  • An elevated-risk badge that reads as a status, not decoration
05

Honest about provisional data

  • Placeholder figures labelled as placeholders, with the methodology marked TBD
  • A note explaining that a wedge is structural rather than a valuation signal
  • Provisional and priced never styled the same way
06

Index impact, end to end

  • A standalone workflow that detects price, terms and composition changes, then finds every index they affect
  • Recalculation that runs in staging and never in production until somebody approves it
  • A comparison dashboard that flags material impact, then an audit log recording who approved or discarded it, when, and on what reasoning
04 — Outcomes

Dense, but never ambiguous.

One screen, three jobs. Market context, peril outlook and deal economics coexist on the deal page, each in its own register, so none of them has to be hunted for.

Recalculation without risk. Because the index impact workflow stages its recalculations and stops at an approval, a data correction can be evaluated in full before anything reaches production.

Options, then a decision. Several index dashboard directions were built out and reviewed side by side, in light and dark, rather than one being defended.

05 — Walkthrough

Walkthrough

Next case study

Aquatics Team

A swim club site, designed and built as a concept
2026
06 — Contact

Let’s connect.

If you made it this far, get in touch! I would love to hear from you.

crawford.todd30@gmail.com