Treefrog Consulting · 2026-11-10
The test of a pricing platform is not the annual report; it is the phone call with the broker. Can an underwriter change a layer or an attachment and see the new price, expected loss and marginal PML before the broker has finished the sentence? Anything measured in minutes rather than seconds pushes pricing back into spreadsheets, where the platform's value evaporates.
Every deal should be priced against the book as it stands: marginal 1-in-100 PML, capacity used, return on capital, by zone and peril, updating as terms change. Platforms that roll up overnight tell you what you did yesterday. Deal selection rules — appetite encoded by zone, peril, counterparty and return threshold — should screen submissions automatically, and a what-if scenario generator should let you stress the portfolio before you commit.
Exceedance curves gross and net of retro, exposure maps with peak zones, event-level portfolio analysis, cat bond tracking where relevant. These should be interactive and customisable, and the underlying data should be yours to query directly, not locked behind the vendor's reports.
The most important question in 2026: does the platform run without its own user interface? A pricing engine, loss models and roll-up exposed through an API can sit under your own underwriting workbench, a low-code tool, Power BI, or a Foundry Workshop app. Your underwriters keep the screens they designed; the platform does the mathematics. A platform that insists on its own UI will fight every integration you attempt.
The new benchmark is an MCP server. With one, any MCP-capable assistant — Claude, ChatGPT, Copilot or an agent you build — can create and renew deals, change terms, run analyses, roll up the portfolio and produce the report, as the signed-in user with a full audit trail. Ask vendors whether their AI assistant can take actions or only answer questions about the help pages.
Can you add your own risk metrics, fields, screens and loss distributions? Can you export everything? Does it support custom add-ins in a real language such as C# or Python? Treefrog's Foundation platform was built around these answers — headless, with an MCP server, live portfolio impact and a database you can query — because we spent years building bespoke pricing systems for Bermuda reinsurers and ILS managers before we built a product.
One whose pricing engine, loss models and portfolio roll-up are available through an API without using its own screens, so you can put your own workbench, Power BI or a Foundry app on top.
Under a second for a layer or term change, including marginal portfolio impact. Minutes means underwriters go back to spreadsheets.
Model Context Protocol, an open standard that lets AI assistants take actions in software. A pricing platform with an MCP server lets your assistant price, renew and analyse deals, not just answer questions.
Yes. Foundation was first adopted by ILS managers and is used by reinsurers and brokers for deal pricing and portfolio roll-up.
Thirty minutes with a senior engineer. You leave with a scoped first build and a clear read on build vs buy, whether or not you hire us.