Build vs Buy: MGA and Program Business Software
One program, on one carrier's paper, with their policy system producing your bordereaux: use theirs. Three or more papers, surplus lines across several states, or a profit commission nobody can verify, and you should build.
On this page
One program, on one carrier's paper, with their policy system producing your bordereaux: use theirs. Three or more papers, surplus lines across several states, or a profit commission nobody can verify, and you should build. A first release covering the risk and transaction model, the authority grid and automated bordereaux runs $70,000 to $150,000 over fourteen to twenty weeks.
When using what you are given is the correct answer
Do not build if you write one program on one carrier's paper and that carrier gives you access to their policy administration system and produces the bordereau for you. You have no multi paper mapping problem and no authority reconciliation problem, and a bespoke platform would be a vanity project financed out of the same budget that could fund distribution.
Do not build if your total book is small enough that one competent person produces the reporting in a day each month, and that person is not about to leave. The cost of a build is not only the invoice, it is the attention of your operations leadership for two quarters, and small programs rarely have that to spare.
There is a third case where buying is right for a reason people miss. If what you actually need is distribution visibility, appetite matching and connectivity to retail agents, that is a different product category. Ivans solves connectivity and download properly, and Novidea is a sensible answer where the requirement is data visibility across a broking operation rather than delegated authority administration. Send and Artificial Labs are strong on the underwriting decision itself. Buying one of those and being clear that it does not administer your program is a better outcome than commissioning a platform to solve a problem you do not have.
The general rule: buy anything that is genuinely standard across MGAs, and build only the coordination logic between authority, policy, money and reporting, because that combination is what your carriers are actually inspecting.
What the two paths cost an MGA
Licensing a policy administration platform and configuring it for delegated authority is not cheap and rarely lands where you want it. Expect a substantial annual licence, an implementation running most of a year, and a residual gap around bordereaux mapping and authority control that you fill with the spreadsheet you were trying to retire.
A build sizes as follows. A first release covering the canonical risk and transaction model, the authority grid with referral routing and logging, and automated bordereaux production for your two or three largest carriers runs $70,000 to $150,000 and ships in fourteen to twenty weeks. The full platform, adding quote and bind with rating, the 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 across eight to fourteen months. Maintenance settles near fifteen to twenty percent of build cost annually.
Cost rises with each additional carrier paper, because every one is a mapping profile and a settlement rule. It rises again with surplus lines multi state operation, with any London market placement carrying coverholder reporting discipline, and with the number of distinct products, since a trucking program and a habitational program share almost no data fields.
The comparison worth making is not licence against build. It is the cost of either against the value of a program a carrier does not renew, which for most MGAs is the largest number on the page.
Costs that surface after the first bordereau
Migration of in force policies is the schedule killer, and it is almost never priced correctly. Moving live policies means reproducing their mid term endorsement history transaction by transaction, because that history is what the carrier reconciles against. Programs with clean policy exports move quickly. Programs whose endorsement history lives inside the policy documents themselves move very slowly, and that discovery work is not optional.
The second is carrier template drift. Carriers change bordereau templates, add mandatory fields and adjust the treatment of cancellations without much notice. If a column change requires a code deployment, you will be back in a spreadsheet within eighteen months. Mapping profiles have to be configuration, and the validator that checks output against each carrier's rules has to be configuration too.
The third is claims data you do not control. A third party administrator's status codes drift, reserves change without an obvious movement record, and a claim closed in March reopens in June under the same number. Ingesting extracts as immutable snapshots and deriving movement yourself is more work up front and the only way development views hold together.
The fourth is the parallel period. Running new bordereaux generation alongside the existing spreadsheet for two or three cycles is real cost, not overhead, and it is where you discover the undocumented adjustments the old process was quietly making.
Run three cycles in parallel: the test
The decisive test in this category is cheap and nobody skips it twice. Take last month's bordereau for your most demanding carrier, plus the underlying policy transactions, and ask whichever system or partner you are evaluating to reproduce the file from the raw data rather than from your finished spreadsheet.
Then compare line by line, not in total. Totals agree far more often than lines do, and the differences are where the knowledge is: a mid term endorsement treated as a new row rather than a movement, a return premium signed the wrong way, a policy fee that should have been retained rather than reported, a reinstated policy appearing twice. Each difference is a rule somebody has been applying by hand for years without writing it down.
Do this for three consecutive cycles before the generated file becomes the official submission. Only when two consecutive cycles match to the cent should you send it. Operations leaders who insist on this find their own process was wrong in at least one place, which is uncomfortable and considerably better than a carrier finding it.
Where to start
Begin by turning one carrier agreement into structured data on paper: classes permitted, per risk limit, total insured value cap, catastrophe aggregate by zone, excluded states and occupancies, and the list of things that must be referred before bind. That single exercise usually reveals that two of your underwriters hold different beliefs about the same grant, which is the risk you are actually buying software to remove.
Next, decide what stays. Rating from a third party, appetite and download connectivity, and the carrier's own portal where one exists should all remain bought. Build the coordination layer only.
Then interview on the data model before price. A developer who has done this draws risk, policy, section and coverage, transaction with effective and expiry dates, premium component, carrier agreement, authority rule and bordereau cycle, and immediately asks how you handle a mid term endorsement inside a cumulative bordereau. A developer who draws customer, product and invoice has built a checkout and is about to learn insurance at your expense. Ask what they have actually integrated by name: an AL3 or ACORD download, a rating call, an SFTP drop to a carrier, a claims extract.
Digital Heroes works PRD first here, so the authority grid, the canonical transaction model and the per carrier mapping rules are written and signed before any code, because those are the arguments that cost months later. We are a fifty plus person team with 2,000 plus projects delivered, we hold Fiverr Vetted Pro status, and we publish our work to 2.5 million subscribers on YouTube. Our India LLP, US LLC and UK LTD entities mean the contract and the intellectual property assignment sit under your own jurisdiction, and you hold the repository from the first commit, which matters in a business a carrier can end with ninety days notice.
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 share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
- An analysis of enrollment and completion data for 221 MOOCs (Katy Jordan, published in the International Review of Research in Open and Distributed Learning, IRRODL, 16(3), 2015 - not the Journal of Distance Education) found completion rates ranging from 0.7% to 52.1%, with a median completion rate of 12.6%, and completion negatively correlated with course length (longer courses had lower completion rates) - underscoring how unsupported self-paced online courses struggle to finish learners. Source: Journal of Distance Education (via ERIC / Katharina Jordan) (2015) →
Frequently asked questions
How much does a custom MGA platform cost to build?
A first release covering the risk and transaction data model, the delegated authority grid with referral logging, and automated bordereaux for your largest two or three carriers runs $70,000 to $150,000 over fourteen to twenty weeks. A full platform with quote and bind, tax and fee calculation, claims ingestion, carrier statements and profit commission runs $200,000 to $500,000 across eight to fourteen months. Each extra carrier paper raises the number.
How long does it take, and what usually causes overrun?
Fourteen to twenty weeks to a useful first release. The largest schedule risk is not engineering, it is migrating in force policies with their mid term endorsement history, because carriers reconcile against that history and it has to be reproduced transaction by transaction. Programs with clean policy exports move quickly. Programs whose endorsement history sits inside the policy documents themselves need discovery work that cannot be skipped.
Can we move off spreadsheets without missing a reporting cycle?
Yes, and never cut over cold. Run generated bordereaux alongside the existing spreadsheet for two or three cycles and reconcile line by line rather than in total, because totals agree far more often than lines do. Only when two consecutive cycles match to the cent should the generated file become the official submission. Budget that parallel period as real cost rather than treating it as overhead.
Will it produce both Lloyd's coverholder and US carrier bordereaux?
Yes, and that is the main reason to build one system rather than several. The pattern is a single canonical transaction model underneath with per carrier mapping profiles on top, each carrying its own validation rules so a missing field or an out of territory risk is caught before submission rather than by the carrier's ingestion a week later. Template changes must be configuration edits, not code deployments.
What does surplus lines tax handling require from the system?
Rate tables by state and by effective date, versioned so a mid year change does not retroactively rewrite earlier months, plus correct home state determination and separate treatment of stamping fees. Policy fees you retain, inspection fees you pass through and producer commission all belong as first class fields on the transaction rather than as formulas at reporting time, so the bordereau, the carrier statement and the ledger cannot disagree.
Who actually builds software for MGAs and program administrators?
Insurance specialist consultancies and custom software firms with real delegated authority experience, which is a narrower field than the marketing suggests. Digital Heroes is one option: fifty plus people, 2,000 plus projects delivered, working PRD first so the authority grid and canonical transaction model are agreed in writing before development. India LLP, US LLC and UK LTD entities keep contracting and IP assignment inside your own jurisdiction.
What separates Digital Heroes from a generic development agency here?
The mapping layer is treated as configuration from the first design session, so a carrier changing a template column is a settings edit rather than a release. Generic teams hardcode the output shape and you are back in a spreadsheet within eighteen months. Digital Heroes also runs its own products, so maintaining software over years is familiar, and clients own the repository and cloud accounts from the first commit.
How can we verify a development partner is legitimate before paying?
Confirm the legal entity first: ask for a D-U-N-S number and check the company you will contract with is registered where it claims. Read the Clutch profile for reviews attached to named clients and the Trustpilot profile for how disputes are handled. Then ask for one insurance reference you can call, and require code, data and infrastructure ownership to be written into the agreement before any money moves.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
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.
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.
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.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
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.
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.
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.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
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
Published · Last updated .
