How Much Does an MGA Platform Cost to Build in 2026?
$70,000 to $500,000 is the honest range for a custom managing general agent and program business platform, and the number that moves it furthest is how many carrier papers you write on.
On this page
$70,000 to $500,000 is the honest range for a custom managing general agent and program business platform, and the number that moves it furthest is how many carrier papers you write on. Each paper is a separate authority grant with its own conditions, a separate bordereau mapping profile with its own validation rules, and a separate money settlement. One paper is a system. Four papers is the same system plus three more of everything that has to reconcile, which is why an MGA at modest premium volume can end up spending more than a larger one with a single carrier.
The bands a program business build falls into
A first release covering the canonical risk and transaction model, the delegated authority grid with referral logging, and automated bordereaux for your two or three largest carriers runs $70,000 to $150,000 and ships in 14 to 20 weeks in Digital Heroes delivery experience. A full program platform adding quote and bind with rating, a surplus lines tax and fee engine, third party administrator claims ingestion, carrier statements, profit commission and program level profit and loss runs $200,000 to $500,000 phased over 8 to 14 months.
What separates the bands is whether the system proves compliance or runs the business. The first band ends the monthly bordereau rebuild and gives you an audit trail a carrier's review team will accept, which is often the whole reason the project gets funded. The second band takes over pricing, money and claims, and it is a materially larger commitment in both build and maintenance.
Most MGAs should take them in that order and should resist the temptation to start with quote and bind, which is the shiny part. An underwriting workbench sitting on top of a transaction model that cannot produce a clean bordereau just makes bad data faster.
What drives an MGA build up
- Carrier paper count. Each additional paper is a mapping profile, a validation rule set, a settlement arrangement and its own authority grant. Budget real money per carrier, not a configuration line.
- Surplus lines across multiple states. Tax and stamping fee rules vary by state, depend on home state determination, change on effective dates and must be versioned so a July rate change does not retroactively rewrite March. This is genuine ongoing work rather than a table you populate once.
- London market placement. Coverholder reporting standards have their own discipline and their own field expectations, and satisfying them is a distinct profile rather than a variation on a domestic template.
- Product diversity. A trucking program and a habitational program share almost no data fields. Two genuinely different products means two schemas, two rating approaches and two sets of underwriting questions.
- Migration of in force policies. The most underestimated line in this category. Converting live policies with their mid term endorsement history is slow because the carrier reconciles against that history, so it has to be reproduced transaction by transaction rather than as an opening balance.
What keeps the number down
Start with your two or three largest carriers and add the rest later. The first mapping profile is expensive because it forces the canonical transaction model and the mapping layer to exist. The fourth is inexpensive because it is configuration. MGAs that insist on all carriers in release one pay full price for every one of them.
Keep quote and bind out of the first release unless you are launching a genuinely new program. Your underwriters already have a workflow that functions. What they do not have is an authority grid that stops a new hire binding a risk your carrier excluded in the last amendment, and that is cheap by comparison.
Build the mapping layer as configuration from the first day. If a carrier changing a bordereau column requires a code deploy, you will be back in Excel within eighteen months and you will have paid for the privilege. Ask for this explicitly and test it during acceptance by asking the team to add a column while you watch.
Finally, do not rebuild rating you already licence. If you pull rates from a third party product, call it. Reimplementing someone else's rating tables is expensive, fragile and the errors surface as premium disputes.
A worked example that adds up
An MGA writing roughly $85M of gross written premium across four carrier papers, two products covering commercial trucking and habitational, surplus lines business in fourteen states, one London market placement, and a single third party administrator handling claims.
- Canonical risk, policy and transaction model with full premium component breakdown: $34,000
- Authority grid with versioned carrier agreements, referral routing and approval logging: $29,000
- Bordereaux generation with per carrier mapping profiles and pre submission validation, three carriers: $37,000
- Migration of in force policies including mid term endorsement history: $28,000
First release, $128,000 over about eighteen weeks. Phase two adds quote and bind with rating at $58,000, a surplus lines tax and stamping engine covering fourteen states at $42,000, a coverholder reporting profile for the London placement at $26,000, third party administrator claims ingestion with snapshot based movement derivation and a status crosswalk at $44,000, carrier statements with cash settlement and trust reconciliation at $39,000, profit commission computed on the treaty year at stated valuation dates at $27,000, and program level profit and loss at $23,000, a further $259,000. Programme total $387,000 across roughly twelve months.
The migration line at $28,000 looks small next to the others and it is the one most likely to move. If your endorsement history lives in policy documents rather than in structured exports, expect it to double, and find that out before anyone quotes a fixed price.
How the spend phases
Roughly 33 percent lands in the first release, and the sequencing is set by your reporting cycle rather than by convenience. Never cut over cold. Run generated bordereaux in parallel with the existing spreadsheet for two or three cycles and reconcile line by line, which is how you find the undocumented adjustments the old process was quietly making. Only when two consecutive cycles match to the cent do you send the generated file as the official submission. Budget that parallel period as real cost.
Carrier onboarding is sequential rather than parallel and it is calendar rather than engineering. Each carrier has to see a sample file, comment on it, and accept it, and that round trip takes as long as it takes. Start it early and expect the first carrier to consume more elapsed time than the next two together.
Claims ingestion should follow at least one clean premium cycle. Deriving movement from third party administrator snapshots is delicate work and it is easier to validate when the premium side is already reconciling, because you can isolate which half of a discrepancy is yours.
Profit commission comes last for a reason. It draws on both premium and loss data at a stated valuation date, and computing it on data that is still settling produces a number you will have to restate in front of a carrier.
The ongoing costs nobody quotes
- Support and enhancement cover, 15 to 20 percent of build cost. On a $387,000 programme that is $58,000 to $77,000 a year, and it should include someone who can turn round a carrier template change inside a reporting cycle.
- Surplus lines rate and rule maintenance, $10,000 to $30,000 a year. State tax and stamping rules move, filing requirements change, and each revision must be versioned by effective date so historic periods stay reproducible.
- New carrier onboarding, $15,000 to $45,000 each. A new paper means a new authority grant modelled, a new mapping profile, a new validation set and a new settlement arrangement. It is cheaper than the first one and it is not free.
- Hosting and archiving, $8,000 to $24,000 a year. Policy, bordereau and claims history has to be retrievable for years, and the raw inbound files should be retained immutably alongside the derived records.
- Annual carrier audit support. Not a software line, but plan for it. The system reduces the effort enormously and somebody still has to sit with the auditor.
Comparing a build against your current renewal
Work it out with your own invoices. Take what you pay annually for your agency management system seats and any policy administration licence, then add the fully loaded cost of the person or people who produce bordereaux, reconcile carrier statements and rebuild formula chains when a template changes. In most MGAs that labour line is larger than the software line and it is concentrated in one person, which is a separate risk.
Then price the thing that does not appear anywhere. Estimate what a carrier data quality remediation request costs you in senior time, and what a program running for two years on an unverifiable ceding commission would cost if the correction went the wrong way. We have seen exactly that situation persist because nobody could disprove the spreadsheet.
Criticise the incumbents on grounds you can verify rather than on price. Ask an agency management system vendor how a decrementing binder limit is modelled and how a referral is logged with an approver. Ask a policy administration vendor how the same policy renders into two different carriers' bordereau formats without a services engagement. Ask any of them what a full export of your transaction history, including premium components, looks like on exit. Those answers describe the ceilings you will hit.
When buying beats building
If you run one program on one carrier's paper and that carrier gives you access to their policy system and produces the bordereau for you, use theirs. You have no multi paper mapping problem and no authority reconciliation problem, and a custom build would be a vanity project. Put the money into distribution instead.
If your total book is small enough that one person produces the reporting in a day a month, and that person is not a flight risk, buy nothing and change nothing. If your actual need is distribution reach and data visibility rather than delegated authority administration, Novidea is a sensible answer and it is a different category of product from what this guide prices.
Keep Ivans for appetite and download connectivity regardless of what you build. It solves a distribution problem that is entirely orthogonal to authority control, and rebuilding it adds cost without reducing carrier risk.
Build when two or more of these are true. You write on three or more carrier papers. A carrier or a Lloyd's managing agent has asked you for a data quality remediation plan. Your profit commission is disputed or unverifiable. You operate surplus lines across several states. Or you are launching a new program and the carrier's diligence now includes your systems, which it increasingly does. At that point the coordination between authority, policy, money and reporting is the business itself, and it should not live in one person's workbook.
If you would rather scope this before committing budget, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- Organizations that scaled intelligent automation report an average cost reduction of 32% (up from 24% in 2020), and respondents expect an average 31% cost reduction over the next three years. Source: Deloitte (2022) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- Acquiring a new customer is five to 25 times more expensive than retaining an existing one, and research by Frederick Reichheld of Bain & Company found that increasing customer retention rates by 5% increases profits by 25% to 95% - underscoring the ROI of support that keeps customers. Source: Harvard Business Review / Bain & Company (2014) →
Frequently asked questions
How much does a custom MGA platform cost to build in 2026?
Between $70,000 and $500,000 in Digital Heroes delivery experience. A first release with the risk and transaction model, the delegated authority grid and automated bordereaux for two or three carriers runs $70,000 to $150,000 in 14 to 20 weeks. A full platform adding quote and bind, tax and fee calculation, claims ingestion, carrier statements and profit commission runs $200,000 to $500,000 over 8 to 14 months. Our worked four carrier example totalled $387,000.
What does an MGA platform cost to run annually?
Budget 15 to 20 percent of build cost for support, so $58,000 to $77,000 on a $387,000 programme, and insist it includes turning round a carrier template change inside a reporting cycle. Add $10,000 to $30,000 a year for surplus lines rate and rule maintenance, since state tax and stamping rules move and each revision must be versioned by effective date. Hosting and archiving runs $8,000 to $24,000.
How much does adding another carrier paper cost?
$15,000 to $45,000 for each carrier added after the platform exists, covering the authority grant modelled as versioned data, a mapping profile, a validation set and the settlement arrangement. The first carrier is far more expensive because it forces the canonical transaction model and the mapping layer into existence. If a new column from a carrier requires a code deploy rather than a configuration change, the mapping layer was built wrong.
How long does an MGA build take and what slows it down?
A first release ships in 14 to 20 weeks. The largest schedule risk is migrating in force policies with mid term endorsement history, because the carrier reconciles against that history and it has to be reproduced transaction by transaction. Programs with clean structured exports move quickly. Programs whose endorsement history lives inside policy documents move much slower, and that discovery work is not optional.
Why can we not just use Applied Epic or Vertafore AMS360?
Because they model a broker placing business with a market and earning commission, not an agent exercising someone else's underwriting authority. There is no object for a decrementing binder limit, a referral trigger, a breach, or a contractual reporting obligation back to the paper, so those get faked in spreadsheets. Ask the vendor directly how a binder limit decrements and how a referral approval is logged, and the ceiling becomes obvious.
What does the surplus lines tax and fee engine cost?
Around $42,000 for fourteen states in our example, covering rate tables by state and effective date, home state determination, stamping fees and versioning so a mid year change does not retroactively rewrite earlier periods. The build cost is the smaller half. Ongoing maintenance at $10,000 to $30,000 a year is what keeps it correct, and skipping that maintenance is how filings go wrong quietly.
How should we move off spreadsheets without missing a reporting cycle?
Run the generated bordereaux in parallel with the existing spreadsheet for two or three cycles and reconcile line by line, which is how you find the undocumented adjustments the old process was quietly making. Only send the generated file as the official submission once two consecutive cycles match to the cent. Budget that parallel period as real project cost rather than treating it as overhead, because someone has to do the reconciliation.
What does profit commission calculation add, and why is it last?
About $27,000, and it comes last because it draws on both premium and loss data at a stated valuation date. Computing it while either side is still settling produces a number you will restate in front of a carrier. The valuation date matters more than the arithmetic, since the same treaty year produces different commission depending on when you measure it, and that is what disputes are almost always about.
Should a single carrier MGA build at all?
No. If you write one program on one paper and the carrier's own policy system produces your bordereau, you have neither a multi paper mapping problem nor an authority reconciliation problem, and the money belongs in distribution. The build case begins at three or more carrier papers, or when surplus lines across several states, a disputed profit commission, or a carrier data quality remediation request enters the picture.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
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.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
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 Ishaan.
Shopify Plus Tech Lead · Delhi · 2 posts on the site
Published · Last updated .
