Practice

BAU Support

SLA-backed support for actuarial valuation, reporting and data operations — including managed support of our own software products.

BAU Support SLA-backed delivery cadence. A monthly close calendar with twelve cells, four shaded as peak cycles. One cell is marked in accent red as a named senior cover handover. JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Q1 valuation Mid-year + named cover Experience Q4 valuation SLA-BACKED CYCLE — PEAK COVER, NAMED, PREDICTABLE BAU Support SLA-backed delivery cadence. A monthly close calendar with twelve cells, four shaded as peak cycles. One cell is marked in accent red as a named senior cover handover. JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Q1 valuation Mid-year + named cover Experience Q4 valuation SLA-BACKED CYCLE — PEAK COVER, NAMED, PREDICTABLE

Practice signals 1 / 3

Runbook before rescue

Recurring support works when the cycle, checks and escalation paths are written down.

Who this is for

Teams that need delivery capacity, not advice. Mid-market insurers without a full actuarial reporting team. Larger insurers and banks who want senior support for specific recurring processes. Clients who run our software and want us to operate it under SLA.

Where we help

Recurring valuation, reporting and data operations work is hard to staff. Senior people do not want to do month-end forever. Junior people cannot do it alone. Hiring takes too long. Outsourcing usually means losing control. Most clients end up under-staffed, under cover during peak cycles, and forced to absorb risk they did not plan to carry.

What we do

  • Run defined recurring actuarial processes (valuation runs, IFRS 17 close, experience studies, reporting packs) under SLA.
  • Run defined recurring data processes (ETL, pipeline operations, data quality reporting) under SLA.
  • Provide managed support for clients running our Symphony Modelling Platform, Symphony Assumptions, Symphony Reporting or Symphony Automate.
  • Cover peak periods with named senior cover.
Managed operations runbook with SLA telemetry A managed-operations dashboard mockup. Top row shows three SLA telemetry tiles for monthly close, ETL availability and incident response. Below sits a runbook with timed steps, named owners and response/resolve times. One incident is shown in accent red as the open exception under SLA cover. MANAGED ACTUARIAL OPERATIONS — APRIL CYCLE SLA telemetry, runbook and named cover MONTHLY CLOSE — D+9 SLA 9d 04h delivered · within SLA ETL AVAILABILITY · 30D 99.6% target 99.5% · 1 incident · resolved INCIDENT — RESPONSE SLA · 1H 12 min open · A. Patel on call · within SLA RUNBOOK · APRIL CLOSE Step Owner Scheduled Status 1 · ETL · policy Auto · supervised 2 Apr 06:00 DONE 2 · Run model N. Patel 5 Apr 09:00 DONE 3 · Reconcile A. Patel 14 Apr 06:02 RETRYING 4 · Pack & sign-off J. Williams 15 Apr 14:00 QUEUED NAMED COVER · APRIL AP A. Patel — Lead actuary on call · responding now JW J. Williams — Pack signer primary · IFRS 17 sign-off NP N. Patel — Modelling lead peak cover · whole April Managed operations runbook with SLA telemetry A managed-operations dashboard mockup. Top row shows three SLA telemetry tiles for monthly close, ETL availability and incident response. Below sits a runbook with timed steps, named owners and response/resolve times. One incident is shown in accent red as the open exception under SLA cover. MANAGED ACTUARIAL OPERATIONS — APRIL CYCLE SLA telemetry, runbook and named cover MONTHLY CLOSE — D+9 SLA 9d 04h delivered · within SLA ETL AVAILABILITY · 30D 99.6% target 99.5% · 1 incident · resolved INCIDENT — RESPONSE SLA · 1H 12 min open · A. Patel on call · within SLA RUNBOOK · APRIL CLOSE Step Owner Scheduled Status 1 · ETL · policy Auto · supervised 2 Apr 06:00 DONE 2 · Run model N. Patel 5 Apr 09:00 DONE 3 · Reconcile A. Patel 14 Apr 06:02 RETRYING 4 · Pack & sign-off J. Williams 15 Apr 14:00 QUEUED NAMED COVER · APRIL AP A. Patel — Lead actuary on call · responding now JW J. Williams — Pack signer primary · IFRS 17 sign-off NP N. Patel — Modelling lead peak cover · whole April

Diagram signals 1 / 3

Runbook before rescue

Recurring support works when the cycle, checks and escalation paths are written down. The body diagram should make this route explicit enough to discuss in a working session.

SLA-backed runbook and named cover during peak cycles.

Where we fit

Senior-led (the person you talk to during a problem is the person fixing it), fully transparent (you see our runbooks, our tickets and our metrics), co-locatable (we can sit inside your environment under your controls), exit-friendly (clear knowledge transfer terms in every engagement).

Engagement model

Tiered SLA arrangements, with annual or multi-year contracts. Pricing scales by named processes, response time and run frequency. Most of this work runs under multi-year SLA. About 40% of the firm’s revenue is recurring, and we are growing that share deliberately.