Home / Who we work with
Built for growing small MGAs, live in your production in 30 days.
We work with one kind of MGA, on purpose. This page describes that MGA in plain terms, the profile, and the triggers that force the issue. Then we scope it, build it, and hand it to you: 30 days operating in production, on real submissions. The monthly rate starts after the trial.
You've built something real. The systems didn't keep up.
Our pattern is proven on one profile: the growing established small MGA. If most of this reads like your Monday morning, you're who we built for.
Roughly $10M–$50M GWP
Big enough that carrier partners expect real reporting and real controls. Not so big that you have an IT department to throw at the problem.
8–30 people, several hats each
Underwriters who also chase documents. A controller who also assembles the bordereaux. A COO who is also, reluctantly, the IT department.
1–3 programs, one of them moving
One program is scaling, or a new one is launching. Either way, there's a date attached to it, and the date was not your idea.
Zero or one technical staff
Maybe an ops-minded analyst who's good with formulas. Nobody whose whole job is systems. Most vendors size their pitch to a buyer with an IT team. We size ours to you.
An AMS, spreadsheets, and willpower
The AMS does what it does. Spreadsheets do everything else. The current truth of any given submission lives in an email thread, and everyone knows it.
The founder or COO decides
No procurement committee, no scoring matrix, one or two people who will personally live with the result. That's exactly the buyer we want, because we'll live with it too.
The triggers we see, again and again.
Nobody modernizes on a quiet Tuesday. Something external forces the issue, in our experience, almost always one of these six.
A carrier wants better data
Your carrier or fronting partner has raised the bar, cleaner bordereaux, on their schedule, in their format. The spreadsheet assembly line can't hit it, and they've noticed.
A program launch has a real date
The program is signed and the paper is committed. "We'll sort the systems out later" just quietly became a countdown, and every week of drift is now visible to a partner.
Producers drift to faster quotes
Your best producers place business where quoting is fast. Nobody announces they're leaving, the submissions just start arriving somewhere else first.
An error reached a carrier
A re-keyed number or a missed exclusion got all the way through. Nobody was careless, the process simply has too many hand-offs to be safe at your current volume.
Submissions outgrew the inbox
Intake by email triage worked when volume was small. Now submissions go quiet in someone's folder, and the first signal is a producer calling to ask what happened.
You've been burned before
A previous implementation failed or stalled, and you're rightly skeptical. That's what the 30-day trial is for. You run the real system on real submissions before you commit to it.
You are renting a back office
The processing went offshore because hiring locally did not pencil. It works, and it costs less than staff, but the work leaves your building, comes back re-keyed, and every question about a file becomes an email thread across a time zone.
What does re-keying cost you?
Four numbers you already have, turned into hours per month and an annual budget line, computed in your browser, from your inputs only.
Run your numbers →Rented back office
The work leaves the building.
- Files re-keyed by people who cannot see your record
- Status lives in an email thread, not in the system
- Cost scales with volume, because it is priced per hand
- An exception waits for the next working day somewhere else
In-house, on your core
The work stays where the record is.
- Prepared against your own record, so nothing is re-keyed
- Status is the record, readable by anyone who needs it
- Audited at every step, with a named approval on the file
- A person owns every decision that touches rating or binding
Every one of these has the same shape underneath: mundane, redundant work that repeats hundreds of times a month. That work moves to the AI Operational Workforce (intake, chasing, matching, assembly) running with feedback loops that correct it as it goes, while a person owns every decision that touches rating or binding.
Scope, infrastructure, go-live, then it is yours to run.
Four stages, each one scoped before it starts. The third one puts a working system into your live operation; the fourth is us running it behind you.
-
Fixed fee
Scope
Your intake-to-issuance flow turned into a build plan, with a quote against it. Two to three weeks, and yours to keep either way.
-
Quoted first
Infrastructure
The build itself (portal, workflow, or reporting) standing up alongside the systems you already run, not on top of them.
-
30 days
Deploy · GTM · Go-live
It goes into production and you operate it for 30 days on real submissions. Your own people, your own carriers. The monthly rate starts after the trial.
-
Ongoing
Run & support
Hosting, monitoring and senior support behind everything we build, with your data yours, and no clause that changes who owns the book.
Roughly three to five focused hours a week from one decision-maker: answering questions about how your book actually runs, and approving what we put in front of you. We do not run a project you have to staff.
Three steps. Each one earns the next.
It starts with a free 60–90 minute mapping session: your intake-to-issuance flow on one page, yours to keep either way. If it makes sense to go further, a fixed-fee Assessment over 2–3 weeks turns that map into a phased plan with a Phase-1 quote. Then one scoped build, running alongside what you have, never instead of it on day one.
If this sounds like your MGA, run the real thing for 30 days.
Bring us your messiest workflow. We scope it, build it, and stand it up in your production, then you operate it for 30 days on real submissions, with your people, before you pay anything. The monthly rate starts after the trial.