Approach
Prove it on one line before you commit to four
Underwriting transformation fails when the first measurable result arrives eighteen months after the budget was approved. We invert that. One class, in production, on your data, with a genuine exit before any wider commitment.
Delivery
Five phases, and you can stop at the third
Each phase produces something you can evaluate. Nothing is contingent on a promise about a later stage.
- 01
Requirements
Two to three weeks with your underwriters, actuaries, operations and IT security. We map one line end to end: intake channels, appetite, rating basis, referral and authority structure, documents, reporting and the integration points that matter.
You get the target architecture and a written scope with agreed success criteria.
- 02
Proof of value
We configure and deploy that line into your environment, on your own data, used by your own underwriters. Not a sandbox with sample records.
Success criteria are agreed in advance and typically cover submissions processed end to end, validated ingestion of your pricing output, a measured change in time to quote, and confirmation that four eyes and authority controls behave as your governance requires.
- 03
Acceptance gate
You decide whether to continue. If you stop here, nothing further is owed.
If you continue, everything built in the proof of value carries directly into production. Nothing is rebuilt to satisfy a phase boundary.
- 04
Rollout
Remaining lines are configured and deployed one at a time, against the pattern the first line established.
Each has its own scope, its own go live and its own acceptance. The programme never becomes a single large bet.
- 05
Run and evolve
Support, security patching, regulatory change and platform updates are ours to carry.
Product improvements built for the wider platform arrive in your instance at no additional cost, and a configuration allowance covers the changes underwriting will always want once a system is real.
Commercial model
A product you license, configured as if it were built for you
Carriers are usually offered a rigid product or a custom build. We think both are the wrong shape, and we have taken a deliberate position on it.
Pricing is scoped to the lines in question and shared during the requirements conversation. We do not publish rate cards, because a proof of value on one class and a four line rollout are not comparable commitments.
What you get
- A single tenant deployment in your own cloud region, with your database and your keys.
- Configuration to your lines, appetite, rating basis, authority structure and documents.
- A fixed fee proof of value with agreed success criteria and an acceptance gate.
- Fixed fee per line for rollout, so budget is predictable line by line.
- An annual platform subscription covering support, security, regulatory change, updates and an included configuration allowance.
- Source code escrow and continuity protection, so a dependency on us is never a single point of failure.
Why we license rather than hand over code
- Owning a codebase means owning security patching, regulatory change, incident response and the permanent engineering capability behind all three.
- For most carriers that internal cost exceeds the saving on the vendor line, and it competes for the same scarce technology headcount as everything else.
- Under a licence, platform investment is shared across our customers. Your configuration and your data are never shared with anyone.
- Improvements built anywhere on the platform reach your instance without a change request.
- Escrow and a clean exit path give you the protection ownership was meant to provide, without the operating burden it actually carries.
Governance
Run the way your programme office expects
No surprises at steering, because nothing is hidden between them.
Weekly working group
Delivery team and your subject matter experts, with a visible backlog.
Fortnightly steering
Progress against the agreed success criteria, not against a task list.
Named escalation
A single accountable route, with defined response commitments.
RAID log
Risks, assumptions, issues and dependencies tracked openly by both sides.