Policy Management Software: Custom Build or Off the Shelf for an MGA
Buy until your rater becomes a liability.
On this page
Buy until your rater becomes a liability. A retail agency or a single program managing general agent under roughly $10 million in premium is well served by AMS360, Applied Epic or EZLynx plus the carrier portal, and a build would be capital better spent on distribution. The line moves when you carry binding authority across three or more programs and bordereaux takes days every month.
What the off the shelf products actually do well
Be fair to them, because they are good at what they claim. AMS360, Applied Epic, EZLynx and NowCerts are systems of record, and they record beautifully. Client and policy history, ACORD form population, certificate issuance, commission tracking, download from carriers over IVANS, activity and diary management that keeps a service team honest. If your business is placing risks with carriers who issue the policy, that is most of what you need and you should stop reading here.
Vertafore AIM sits a layer up and was built specifically for managing general agents and wholesale brokers, with submission tracking, binder issuance and surplus lines handling that a retail platform never attempts. On the rating side, NetRate will build and host your algorithms properly, and the work is competent. InsCipher files surplus lines taxes across states reliably and takes a genuine compliance burden off one person's calendar. At the carrier end of the market Guidewire PolicyCenter and Duck Creek are real policy administration systems, and for an insurer they are the right answer.
Here is the part vendors will not say and we will. Most program administrators reading this should keep what they have for another year or two. The spreadsheet stack is embarrassing rather than dangerous until a specific set of conditions arrive, and buying software to fix embarrassment is expensive. Wait for the conditions.
Where they stop: the rater is your product and nobody controls it
The workflow generic products model badly is the one that decides your loss ratio. An underwriter prices an artisan contractor risk in a workbook, then retypes forty fields into the carrier portal, and the session times out at field thirty three. The policy number comes from a shared sheet two people have open at once. None of that is the failure. This is: version twelve of the rater carries a broken lookup that underprices wind exposure in coastal counties, it runs for three weeks, and the carrier's rate audit flags sixty one 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.
A system of record cannot help, because it hears about the policy after issuance. A hosted rating vendor helps with the algorithm and hurts with the clock, since every rate change enters a queue measured in weeks and your actuary still develops the logic in a workbook first, so you now maintain two versions of the truth.
The second thing they model badly is the mid term endorsement. An additional insured plus a payroll increase arrives, someone computes pro rata premium by hand, updates the portal and forgets the workbook, and the next bordereau is wrong. The dispute over the carrier statement then takes a month to unwind, and account current settlement is withheld while everyone reconciles.
The third is the forms library. A shared drive holding three versions of the same exclusion means a superseded edition eventually attaches to a policy, and now you have errors and omissions exposure sitting quietly on a file nobody will look at again until a claim. A forms library keyed to edition dates, where an out of date form simply cannot attach to a bound policy, is not a feature anybody demonstrates in a sales meeting. It is the control your professional liability carrier would care most about if they knew to ask.
The arithmetic: per seat costs against a custom build
Agency platforms are quoted per user per month, hosted rating vendors add setup fees per program plus a change fee per rate revision, and filing services charge per filing. Put your own numbers in. Call it $180 per user per month for illustration. Twenty five seats is $54,000 a year. Add two programs on a hosted rater with annual rate revisions and per program setup, plus filing fees across an excess and surplus lines book, and a fifty person shop lands somewhere near $150,000 a year in tooling before anyone rekeys a single field.
A focused build covering one program end to end runs $60,000 to $130,000 and ships in twelve to sixteen weeks, with year two at 15 to 20 percent. Amortised over five years, a $110,000 first release with support carries roughly $38,000 a year.
On that illustration the licence crossover sits near forty underwriting and operations seats. That is the wrong number to fixate on though, and here is the better one. Count the fully loaded cost of the operations headcount doing work the tools do not do: rekeying into portals, assembling bordereaux, reconciling statements, chasing filings. In most program administrators between $20 million and $60 million in premium, that figure is larger than the software line, and it is the number that decides the comparison.
What a custom build actually costs
A focused first release runs $60,000 to $130,000 across twelve to sixteen weeks and covers a rating engine for one program with effective dated rate tables, the full submission to issuance lifecycle with an explicit status machine, document generation with correct form edition dates, and bordereaux export. A full platform runs $150,000 to $400,000 phased over six to twelve months, adding multi program configuration, a retail agent submission portal, carrier connectivity, the surplus lines compliance module and commission accounting.
Data migration lands at 10 to 25 percent of the build. The work is extraction and reconciliation rather than loading: policy data comes from agency platform exports, portal downloads and the rater archive, then loads with original effective dates and transactions intact. Reconcile written premium against carrier statements before cutover, not after.
Year two and onward runs 15 to 20 percent of build cost annually. On a $110,000 first release that is roughly $16,000 to $22,000, covering hosting, rate table updates, form edition changes and small features. Rate changes should become configuration your own team edits rather than billable development, and if a proposal does not say that in writing, ask why.
What pushes the number up: the count of rating algorithms and states, the number of distinct carrier bordereaux templates, the size of your ACORD forms library, AL3 or IVANS connectivity, out of sequence endorsement handling, and whether claims intake rides along.
The four situations where building wins
Regulatory fit. An excess and surplus lines book across twenty two states means twenty two tax rates, stamping fees, diligent effort affidavit rules and filing calendars, and a missed filing carries penalties and interest while a pattern of misses puts the surplus lines licence itself in question. Compliance belongs inside the bind path, with tax computed at quote and binding blocked until diligent effort data is captured, rather than downstream of a spreadsheet.
Scale economics. Past roughly forty seats, or past $25 million in premium with binding authority, you are already paying for a policy administration system in salaries, premium leakage and audit findings. You are simply not receiving one.
A workflow that is your competitive advantage. Program launch speed. A carrier offers appetite for a new class in six states with a ninety day window before they shop it elsewhere. If standing that program up means months in a configuration queue, the window closes. Clone the nearest program, load rate tables and forms, map states and taxes, launch in weeks. The programs you never launched are the most expensive line nobody books.
Integration sprawl across three or more systems. Agency platform, carrier portals, hosted rater, filing service and accounting, with a person in the middle. Each pair you connect is quoted as a project. Once three of those connections exist, own the layer that joins them.
How to decide in a week
A concrete test, five days, no request for proposal.
- Monday: collect every copy of your rater from every desktop and diff them. Count the versions. That number is your risk, stated plainly.
- Tuesday: take the trailing ninety days of bound quotes and reprice them against today's tables. Any premium that does not match is a policy you cannot explain to a carrier auditor.
- Wednesday: time bordereaux assembly properly, including the reconciliation emails, and multiply by twelve.
- Thursday: count the fields an underwriter rekeys from quote to issuance, per policy, and multiply by policies bound last month.
- Friday: list every state where you owe surplus lines filings and name the person who knows each deadline. If it is one person, that is the finding.
If the week points at a build, buy discovery before you buy code. Two to three weeks at a fixed fee produces a written specification covering the data model, the rating tables, the endorsement rules, the bordereaux templates by carrier and the acceptance criteria, which for this category should be repricing your trailing ninety days with matching premiums. Digital Heroes signs that product requirements document before any code exists and contracts through India LLP, US LLC and UK LTD entities, so the intellectual property assignment sits under law your own advisers already read. We are the wrong firm for a retail agency that needs a configured agency platform and a good consultant, and we will tell you that on the call.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Mordor Intelligence sizes the field service management market at USD 6.26 billion in 2026, forecasting USD 9.87 billion by 2031 at a 9.54% CAGR, confirming sustained double-digit-adjacent demand for FSM software. Source: Mordor Intelligence (2026) →
Frequently asked questions
How much does custom policy administration software cost for an MGA?
A focused first release covering one program end to end, meaning rating, the submission to issuance lifecycle, document generation and bordereaux export, runs $60,000 to $130,000 and ships in twelve to sixteen weeks. A full multi program platform with an agent portal, carrier connectivity and surplus lines compliance runs $150,000 to $400,000 phased across six to twelve months. Data migration adds a further 10 to 25 percent.
How long does it take to replace an Excel rater with a rating engine?
A production rating engine for one program normally ships inside a twelve to sixteen week first release, because the rate logic already exists in your workbook. The work is converting it into effective dated tables and proving parity by repricing your trailing ninety days of quotes until premiums match to the cent. Plan roughly a month of parallel running before anyone retires the spreadsheet.
Who owns the source code and the rate tables if an agency builds it?
You should, written into the contract as work made for hire, with the repository under your control from week one and the cloud accounts in your name. At Digital Heroes the client owns the code from the first commit. Walk away from any vendor offering a licence to their platform instead of ownership, because that reproduces exactly the lock in you are trying to leave behind.
What happens if a carrier changes its bordereaux template mid year?
In a custom system you change one mapping, because the templates render from an append only transaction ledger rather than from assembled exports. Written premium, endorsements, cancellations, taxes and commission all land on that ledger as they happen. In a spreadsheet stack the same change means rebuilding a month end ritual, and the first month after a template change is where reconciliation errors cluster.
Can a custom system work with carrier portals that offer no API?
Yes, and that is the realistic case for most program business. The system stays the source of truth and generates a field by field issuance sheet in the portal's own screen order, then verifies the result against what was actually bound. Where carriers do support APIs, AL3 batch or IVANS, those connections replace the manual step one program at a time rather than all at once.
Should we buy Vertafore AIM instead of building something custom?
If your operating model matches what it expects, yes, and it will be cheaper and faster. AIM was designed for wholesale and program business, which a retail agency platform never attempts. The build case appears when rating stays in a workbook regardless, when carrier reporting stays manual, and when program launches wait in configuration queues while a carrier's appetite window closes on you.
What is the difference between an agency management system and policy admin?
An agency management system records what happened to a policy: client, coverage, premium, commission, documents and activity. A policy administration system decides what happens: it rates the risk, enforces binding authority, issues the contract, computes endorsement premium and produces the carrier reporting. The gap between recording and administering is exactly where a program administrator with binding authority leaks money.
Can we build only the rating engine and keep everything else in place?
Yes, and for a firm not ready to commit it is the sensible first move. An engine with effective dated tables, a regression suite that reprices the trailing quarter before any rate change deploys, and a clean quote screen wired to your referral rules solves the version control problem without touching issuance or accounting. It is a fraction of a full platform and it removes your largest audit exposure.
What does it cost to maintain a custom policy administration system?
Plan on 15 to 20 percent of the build cost each year, covering hosting, monitoring, rate table updates, form edition updates and small enhancements. On a $110,000 first release that is roughly $16,000 to $22,000 annually. The arrangement worth insisting on is that rate and form changes are configuration your own team makes, so routine business changes do not arrive as change orders at a day rate.
Will a custom system stand up to a carrier audit of our binding authority?
It should stand up better than a spreadsheet stack, because auditability is designed in rather than reconstructed. Every quote stores its inputs and the exact rate table version that priced it, every transaction sits on an append only ledger, and each rate change carries an approval record. When a carrier asks why a policy was priced a given way, you reproduce the calculation rather than hunting old workbook copies.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Sienna.
Director of Design · APAC · Sydney · 2 posts on the site
Published · Last updated .
