Symphony Modelling Platform

What it improves

Most projection work is still split across a vendor engine for the regulated runs and a sprawl of Excel and Python for everything else (management views, what-ifs, ad-hoc product work, smaller portfolios). The Excel layer is unversioned, untested and impossible to fully reproduce.

What it does

• Configurable cashflow projection for life, health, general and reinsurance products.
• Reinsurance treaty, expense, commission and fee cashflows handled as first-class concepts.
• Multiple reporting bases run from the same source (e.g. statutory, IFRS 17, embedded value, internal).
• Reproducible runs, with full input, parameter and version history.
• Straightforward migration path. First projection results from your own data have typically landed inside four to eight weeks on engagements we have run — actual timing depends on scope, source-system access and the team’s review capacity.
• Sits alongside the actuarial engines and data platforms you already operate, and does the work they do not.
• Shares the common architecture across the platform: API, lineage, role-based access, observability.
• Available inside Excel, on the web, and via the API — actuaries work in the tool they already know, with full audit trail back to the platform.

Controls and audit

Every run is reproducible from a versioned set of inputs. Every parameter change is captured. Every output is traceable to the configuration that produced it. Roll any input or parameter back to a prior version and re-run — nothing is overwritten.

Engagement model

Deployed inside an engagement, on your environment, with documented handover. We do not licence this as a standalone product. Migration is deliberately easy. A first product family has typically landed inside 6 to 10 weeks on engagements we have run — environment, configuration, parallel-run against the existing process, sign-off, then progressive rollout — actual timing depends on scope, source-system access and the team’s review capacity. If you want to take the component forward at the end of the engagement, you take it — full source, docs, supported handover.