Services
When the work is bigger than the API.
Most teams take the core and build. Some need a line of business that does not exist yet, or a book moved off a legacy system. That is a scoped engagement on the same engine — not a fork, not a side door.
New lines of business
Commercial auto, E&S and specialty programs. The ledger, earning, cancellation and cession arithmetic already exist; the work is the intake, schedules and rating shapes for your line. Scoped and quoted before anything is built.
Custom front ends
If you want the headless model but not the build, we write the app against the same public API your developers would use. No private shortcuts into the core.
Filing and state onboarding
Loading rate manuals, rules, forms and territory tables as versioned filings, with effective dating that leaves in-force policies pinned to the version that rated them.
Conversion and migration
Moving an in-force book onto the core with terms, coverages, charges, cash history and earned premium reconciled against your prior system before cutover.
How we scope it
Every request falls into one of three tiers. Knowing which one you are in tells you immediately whether it is a config change, an engagement, or core work.
Tier 1 — Configuration
Rates, rules, pay plans, forms, treaties. You do this yourself in admin; no engagement needed.
Tier 2 — Additive build
New surfaces and integrations on top of the core. Scoped engagement, delivered against the public API.
Tier 3 — Core mechanics
A shape the core does not know yet — a new earning method, a novel cession structure. Comes to us and is built into the core itself, versioned like everything else.
Bring us the program
Send the line, the states, the volume and the timeline. We come back with a scope, a price and what you would own at the end of it.