Read it, price it, bind it.
The document, the record it changes, the workbook that prices it and the event that moves it on. Emails, tasks, files and the whole decision trail are already on the page.
One screen, all the way to bind. Everything the file needs to be read, priced and decided, on the record it belongs to.
Changes arrive as a proposal.
A document or a broker email lands as staged edits in plain language: Add Coverage, Update Limit, Remove Exclusion. Apply them together, or one at a time.
Every value keeps its page.
Click an extracted field and the document scrolls to the page and lights up the box it was read from, with the confidence beside it.
The whole file, not just the fields.
Emails, calls, notes, tasks, files and related records on the same page, with details, activity and changes in the rail.
One button moves it forward.
The next event is the button, and the button says Bind. It shows the status it lands on and the workflows it will run before you send it.
“The file, the numbers and the decision are finally on one screen. We retired the spreadsheet we had been keeping next to the policy system.”
Every quote can be reconstructed. Rates live in effective-dated books, versioned alongside the rest of your configuration and promoted the same way.
Rate books.
A book is a timeline of effective-dated versions, each pinning immutable rate table versions. A version takes force on its date and the next version's date closes it. You never set an expiry.
Workbooks.
The pricing logic that turns a submission into a quote. Rate tables inline themselves onto the workbook's inputs, so a formula reads a base loss cost, a territory factor and a deductible factor by name.
Test, then release.
Point the workbook at a real record and re-run it while the formulas are still unsaved. Nothing is written. When it prices the way you meant, cut a release and deploy it to dev, UAT or production.
The lifecycle is yours to draw. Statuses, events, guards and timers are configuration, so a product follows the path you modelled and cannot skip a step nobody noticed.
Statuses and events
Draw the path on a canvas. Submitted, Quote Sent, Bound, Issued, In Force, Expired, and the events between them.
Guards that branch
One event can lead to several statuses. Prioritised conditions pick the target, and a fallback catches the rest.
Transitions on a timer
Place coverage in force on its effective date, expire the term on its expiration date, and open the renewal ninety days out.
The term does not end at bind. Endorsements, audits and rewrites run as their own flows on the policy, without moving it out of the status it is resting in.
Endorsements
Open a chain, give the change an effective date, and it lands on the timeline in date order. Slot one in behind an existing endorsement and the later items are rebased on top, each keeping the change it introduced.
Premium audit
Reconcile premium against actual exposure at the end of a term. The audit runs on a copy of the active version and is never promoted over it, so the policy's own status and term are untouched throughout.
Rewrites
Reissue a version in place. The revised copy takes over as the active version and inherits the lifecycle position of the version it replaced, so the policy does not appear to move.
Renewals
Ahead of expiry the expiring version is copied into the next term: lines, coverages, exposures, conditions, blankets and rate factors. The term is derived by day count, so an eighteen-month policy lands exactly.
One file, every surface.
The record an underwriter works in is the same record documents land on, workflows act on and reporting counts.
Bring a live submission.
Send an ACORD 125 and the rate pages you price it from. We will build the workbook, quote it on the call, then endorse it before you go.
Usually 30 minutes, with an underwriter on the call.