Policy Management Software for MGAs: Build vs Buy, Real Costs, and What Actually Breaks
If you are an MGA or program administrator running binding authority through carrier portals and Excel raters at $10 million or more in premium, building usually wins: a focused first release covering rating, policy lifecycle, and bordereaux typically runs $60,000 to $130,000 and ships in 12 to 16 weeks, with full multi-program platforms at $150,000 to $400,000 phased over 6 to 12 months.
Why policy administration makes or breaks an MGA
Walk the floor of a contractor GL program administrator writing $35 million in premium and you will find the real policy administration system: a workbook named GL_Rater_v14_FINAL_USE_THIS_ONE.xlsx, a carrier portal open in the next browser tab, and an Outlook folder called Endorsements Pending. An underwriter prices an artisan contractor risk in the rater, retypes 40 fields into the portal, the session times out at field 33, and she starts over. The policy number comes from a shared spreadsheet that two people have open at the same time. This is not a caricature. It is the standard stack for MGAs between roughly $10 million and $80 million in premium.
The leakage hides in plain sight. An underwriter who should clear 15 submissions a day clears 8 because half the day is rekeying. The operations lead loses the second week of every month to bordereaux. Surplus lines filings run on one person's memory of 22 state deadlines. And the rater itself, the artifact that decides whether your loss ratio holds, is a spreadsheet with no version control, no audit trail, and formulas nobody has tested since the actuary who built them left.
Agency management systems such as AMS360, Applied Epic, and NowCerts record what happened. They do not rate your programs, enforce your binding authority, or produce bordereaux in the formats your carriers demand. The gap between recording policies and administering them is exactly where a custom build earns its keep.
The Excel rater is your real product, and nobody controls it
A real failure mode: version 12 of a rater carries a broken VLOOKUP that underprices wind exposure in coastal counties. It runs for three weeks before the carrier's quarterly rate audit flags 61 policies priced below filed rates. Now you are writing a remediation memo to the carrier that grants your binding authority, and you cannot say with certainty which quotes used which version, because underwriters keep local copies on their desktops.
Off-the-shelf tools do not solve this. AMS360 and Epic are systems of record, not rating engines. Hosted rating vendors such as NetRate will build your rater, but every rate change enters a vendor queue with turnaround measured in weeks, you pay setup fees per program, and your actuary still develops the logic in Excel first, so you maintain two versions of the truth.
A custom build moves rating into effective-dated rate tables in a database. Every quote stores its inputs and the exact table version that priced it. Before any rate change deploys, a regression suite reprices the trailing quarter of quotes and diffs the premiums, so a broken lookup surfaces before it touches production. Underwriters get a clean quote screen with referral rules wired to your binding authority instead of an editable formula grid.
Quote, bind, and issue live in three systems that never agree
The quote exists in Excel, the bind lives in an email thread, issuance happens in the carrier portal, and the AMS record gets created two days later by an assistant working from the email. Then a mid-term endorsement arrives: an additional insured and a payroll increase. Someone computes the pro rata premium by hand, updates the portal, and forgets the spreadsheet, so the next bordereau is wrong and the carrier statement dispute takes a month to unwind.
The portal cannot fix this because it is the carrier's system, built for the carrier's ledger, and it starts at issuance. Your AMS cannot fix it because it hears about everything after the fact.
A custom platform gives each policy one lifecycle record with an explicit status machine: submission, quote, bind, issue, endorse, cancel, renew. Pro rata and short rate math is computed, not hand-keyed. Declaration pages and endorsement forms generate from the record with the correct edition dates. Where a carrier exposes an API, the system submits directly. Where the carrier only has a portal, it produces a field-by-field issuance sheet in the portal's own order, cutting a 25 minute rekeying session to under 5 and verifying the result against what was actually bound.
Bordereaux week eats four working days every month
Three carriers, three inherited Excel templates, premium and claims bordereaux for each. The ops lead assembles them by filtering AMS exports against the policy-number spreadsheet and portal downloads, and the 10th of the month is a hard deadline. One transposed cancellation and the carrier withholds settlement of the account current while everyone re-reconciles.
No agency management system exports in your carriers' formats, and portal downloads routinely miss endorsements and cancellations processed near the cycle boundary.
The custom answer is an append-only transaction ledger: written premium, endorsements, cancellations, taxes, and commission all land there as they happen. Per-carrier templates render straight from the ledger, net remittance comes out with commission and surplus lines taxes already netted, and the monthly close shrinks from four days to an afternoon of review. When a carrier changes its template, you change one mapping, not a month-end ritual.
Surplus lines compliance runs on one person's memory
An E&S book across 22 states means 22 tax rates, stamping fees, diligent effort affidavit rules, and filing calendars. A missed New Jersey filing costs penalties and interest; a pattern of misses puts the surplus lines license itself in question. Meanwhile an outdated form edition attaches to a policy because the forms folder on the shared drive holds three versions of the same exclusion, and now there is E&O exposure on top of the compliance problem.
Filing services such as InsCipher submit filings competently, but they sit downstream of issuance, fed by the same spreadsheets that created the problem.
A custom system puts compliance inside the bind path. Tax and stamping fees compute at quote time from per-state tables. Binding is blocked until diligent effort data is captured in states that require it. Filing batches export per state on their real calendars, and the forms library is keyed to edition dates so a superseded form cannot attach. Compliance stops depending on whether one specific person is on vacation.
New programs take two quarters to launch
A carrier offers appetite for a new class in six states with a 90 day window before they shop it to another MGA. Standing the program up on an MGA suite or a hosted rating vendor means months in configuration queues, and the window closes while you wait. The programs you never launched are the most expensive line item nobody books.
A custom platform treats a program as configuration: clone the nearest existing program, load the new rate tables and forms, map the states and taxes, and launch in weeks with the same audit trail from day one. Add a retail agent submission portal and growth stops meaning inbox triage, because submissions arrive structured instead of as PDFs attached to email.
What this costs and how long it takes
Across more than 2,000 delivered projects at Digital Heroes, a focused first release in this category runs $60,000 to $130,000 and ships in 12 to 16 weeks. That typically covers a rating engine for one program, the full quote-to-issue lifecycle, document generation, and bordereaux export. Complete platforms run $150,000 to $400,000 phased over 6 to 12 months, adding multi-program configuration, an agent portal, carrier connectivity, the surplus lines compliance module, and commission accounting.
What pushes price up in this specific category: the number of rating algorithms and states, the count of distinct carrier bordereaux formats, the size of the ACORD forms library, AL3 or IVANS connectivity, out-of-sequence endorsement handling, and whether a claims intake module rides along. A single-program GL rater is the cheap end; a five-program, 40-state book with three carrier feeds is the expensive end.
Build vs buy: the honest answer
Buy when you are a retail agency, where EZLynx or AMS360 plus carrier portals is genuinely enough, or when you run a single program under roughly $10 million in premium and the carrier's own portal carries the load. Enterprise policy administration suites like Guidewire PolicyCenter and Duck Creek are built and priced for carriers; for an MGA they are seven-figure, multi-year implementations solving problems you do not have.
Build when the signals stack up: three or more programs or carrier relationships, bordereaux measured in days, a rater incident you had to explain to a carrier, a program launch lost to a vendor configuration queue, or operations headcount growing faster than underwriting headcount. Our position after building these systems: past $25 million in premium with binding authority, the spreadsheet-and-portal stack is the most expensive option available. You are already paying for a policy administration system in salaries, premium leakage, and audit findings. You are just not getting one.
How to choose a developer for policy administration software
First, make them whiteboard the data model before you discuss price. A competent team distinguishes policy, term, transaction, and endorsement, uses effective-dated rate tables, and has an answer for out-of-sequence endorsements. A team that proposes one policies table with a status column will fail you in month four.
Second, test integration realism. Ask how they issue when a carrier has no API. The right answer keeps the system as the source of truth with a structured portal handoff, plus a roadmap for AL3, IVANS, or carrier APIs where they exist, and a filing service connection for surplus lines states.
Third, probe audit posture. You need an append-only ledger, an approval workflow on rate changes, and the ability to reproduce any historical premium calculation exactly. Your binding authority and your E&O carrier both depend on this.
Fourth, demand the right delivery shape: one program end to end in the first release, a parallel run against the Excel rater for a month, and acceptance defined as repricing the trailing 90 days of quotes with matching premiums. Code ownership, in writing, from the first commit. Any vendor who resists these four points has told you everything you need to know.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Median SaaS spend reached $9,455 per employee, and organizations leave an average of 36% of their SaaS licenses unused. Source: Zylo (2026) →
- McKinsey argues software developer productivity can be measured by combining system-level metrics (DORA and SPACE) with its own outcome-oriented approach, which it reports deploying across nearly 20 tech, finance, and pharmaceutical companies - a claim that sparked significant debate in the engineering community. Source: McKinsey & Company (2023) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.