You underwrite for carriers, inside limits someone else set
Delegated authority, bordereaux, and producer appointments. Agents keep every bound risk inside the binding authority and every month-end file on time, and your underwriters decide while your program managers clear the exceptions.
Get a free process reviewSee your processes ↓Bordereaux reconcile before month end. Every mismatch is listed with its source row, and the file goes out on time.
Your programs run on your own record. InsureEdge gives an MGA its own headless policy and billing core.
New producers quote in days. Licences are checked state by state, and appointments are filed for you.
Your processes, on one platform
Scroll through the 4 processes we run for MGAs. Damco Workbench does the work on top, and your core keeps the record underneath.
Bordereaux, from partner spreadsheets to a reconciled submission
Partners send premium and claims in their own layouts. The agent maps each one, reconciles every row to the book, and lists each mismatch with its source row.
- Bordereaux accuracy (%)
- Submitted on time (%)
- Hours per run
Producer onboarding
No quote until the producer is licensed for the state and line, and appointed with the carrier.
See it on your core ↗Bordereaux to carriers
Each carrier wants its own format by its own deadline, and the numbers must tie to the premium trust account.
See it on your core ↗Submission to bind, inside delegated authority
The MGA binds for the carrier, but only inside the binding authority agreement. Anything outside it goes to the carrier.
See it on your core ↗We strategize, build, and operate your software until it pays
Most MGAs start with the bordereau: one cycle, one carrier, measured in accuracy and hours per run.
Strategize
We map one of your processes as it runs today, every task, who does it, how long it waits, and pick where agents pay first.
Build
Prototype rounds with your people every week, on the core you run, in your tenant. Agents, rules, and screens.
Operate
We run it with you against the KPIs we agreed, and keep tuning until the number moves. Then we keep it there.
Two platforms let you start from working software
When we build, we start from two platforms of our own. Use them together, one at a time, or not at all: the blueprint works on the core you run.

