Captive Insurance Management Software: Build or Buy?
The number that decides this is how many captives and cells you administer, and the line sits at about eight.
On this page
The number that decides this is how many captives and cells you administer, and the line sits at about eight. Below eight, with one domicile and no formula based participant allocation, your captive manager's process plus the actuary and the auditor is genuinely cheaper than maintaining software, and buying a risk management information system for loss data covers the rest. At eight or more, or the moment a group captive allocates premium and loss funds across participants by formula, a first release at $60,000 to $130,000 over 12 to 18 weeks starts to earn. Most single parent captive owners fall below the line and should not build.
When is off the shelf genuinely the right call here?
Start with the case that gets confused most often. If your real gap is claims, incident and exposure data, buy Origami Risk or Ventiv and be happy. Both are risk management information systems and both are strong at what they do. Many captive owners rightly run one, and reaching for a build when a risk management information system was the answer is the most expensive mistake in this category.
If you run a single parent captive writing a couple of lines for its own parent, with a stable programme and a few dozen policies a year, buy nothing. Your captive manager's workbook, your appointed actuary and your auditor already form a working process, and the annual cost of that process is lower than the maintenance cost of any system. This is a genuine do not build rather than a hedge.
If you are actually a conventional insurer with a captive attached, Sapiens and similar core insurance administration platforms are built for you. They assume a normal insurer with policies, endorsements and claims at volume, and they will do that far better than anything you commission.
And keep buying your general ledger. A packaged accounting system with a decent dimension model does cell level bookkeeping perfectly well once someone has designed the dimensions properly. Rebuilding double entry accounting because your cells are awkward is a poor trade.
The honest summary of the buy case is that nearly everything a captive touches has a good product behind it except the captive's own administration: participant allocation, cell equity, intercompany cessions, collateral instruments and domicile filings. That is the gap, and it is narrower than software vendors on either side will tell you.
When does a custom build actually pay off?
Five conditions, and you want two or more of them true before spending anything.
First, scale. Eight or more captives or cells is where the arithmetic stops being arithmetic and becomes bookkeeping with dependencies. Change a participant's exposure base and you have changed their premium allocation, their loss fund contribution, their share of the aggregate, the collateral the fronting carrier will require and the figure in their year end statement. In a workbook that is five edits in five places.
Second, formula based allocation with a dispute history. Group captives allocate on experience modifiers, exposure bases and tier movement, and a policy year stays open for a decade while reserves develop. A member's finance director eventually asks what the allocation looked like as at 31 December 2022. A workbook has one state, current, and cannot answer.
Third, collateral posted to more than one fronting carrier. Letters of credit, trusts and funds withheld have expiry dates, notice periods and issuing bank limits, and in a cell structure they attach to a cell rather than the company. The failure that hurts is not a wrong report, it is an expired instrument the fronting carrier finds before you do.
Fourth, more than one domicile. Vermont, Utah, Arizona, Delaware, North Carolina, Tennessee, Cayman and Bermuda each want their own annual return, actuarial opinion, audited financials and premium tax return, on their own dates. Four domiciles is a few hundred dated obligations living in Outlook.
Fifth, and for a management firm this is the real case, capacity. How many captives can one analyst carry today, and what does that number have to be for your growth plan to work. A build that raises captives per analyst is not a cost saving, it is a capacity change.
How do they compare on the things that matter in this industry?
Ignore the feature grids and compare on five points a practitioner can verify.
- Valuation dating. The question is whether recomputing a 2019 policy year in 2026 produces a new stored run plus a variance report, or overwrites what members were told in 2021. Recalculation in place is faster to build and destroys the history that makes an assessment defensible. Test this on any product you are shown, because it is the single design decision that removes most member disputes.
- Cell as a first class dimension. Core insurance platforms represent a protected cell company as a stack of separate entities, which is legally tidy and operationally expensive: separate closes, separate reconciliations and no consolidated position without another spreadsheet. Confirm the per entity configuration and licensing effect against your actual cell count before assuming a product fits.
- Collateral as objects rather than files. Required against posted collateral computed at each valuation, with notice periods generating work items, is either present or it is not. Most systems in adjacent categories hold the document and nothing else.
- Domicile filing content. The mechanism generalises across domiciles and the content does not. Ask specifically which of your domiciles a product already carries templates for, and treat everything else as configuration you will maintain.
- Portability of a decade of history. Open policy years stretch back ten years. Whatever you run, establish now what a full export of policy year, valuation and allocation history looks like and whether your auditor could read it without the vendor present.
What does total cost of ownership look like at your scale?
On the build side the shape is settled in Digital Heroes delivery experience. A first release covering the captive and cell entity model, participant and loss fund allocation with valuation dating, and a collateral instrument register runs $60,000 to $130,000 over 12 to 18 weeks. A firm administering around fourteen captives and cells across three domiciles, with two allocation models and eight open policy years to convert, lands near $118,000. A firm with one allocation model, one domicile and three open years lands nearer $65,000. The full platform, adding intercompany and outward reinsurance accounting, statutory basis financials per cell with consolidation, filing calendars, participant portals and management fee billing, runs $180,000 to $400,000 phased over 7 to 12 months.
Each additional domicile adds roughly $12,000 to $30,000, covering the filing template set, the dating rules from each entity's fiscal year end and the premium tax calculation. Converting eight open policy years reconciled to published member statements was $16,000 in that worked example, and conversion is the part that decides whether anyone trusts the output.
Running costs are modest in infrastructure and less modest in maintenance. Hosting sits at $250 to $700 a month. Support and enhancement runs 12 to 18 percent of build cost a year. On top of that, budget domicile template maintenance, because regulators revise forms and dates on their own schedule, and counterparty file changes, because a third party administrator loss run, a fronting carrier bordereau and a custodian statement will each change layout at some point. With four feeds that happens several times a year.
On the buy side, put your risk management information system renewal on the page, then be precise about what it covers. It is claims, incidents and exposure data. It is not cell equity, intercompany cessions or a collateral register. Two problems, one line item, and the comparison only works once you separate them.
What does the hybrid look like, and when is it the honest answer?
For most readers this is the answer, and it is cheaper than either pure route.
Keep the risk management information system for claims, incidents and exposure. Keep your general ledger for accounting. Keep your actuary's exhibits as the source of reserves rather than rebuilding a reserving exercise your appointed actuary already performs and signs. Then build only the two pieces nothing else covers.
The first is an allocation engine holding valuation dated immutable runs, with variance reporting between runs and member statements generated from each run. That comes in at $35,000 to $70,000 over eight to twelve weeks. It leaves your accounting where it is, and what it changes is that a recomputed 2019 year produces a new run and an explainable variance rather than a rewritten past.
The second is the collateral instrument register: issuer, amount, effective and expiry dates, notice period, attached cell and the reserve basis it supports, with required against posted computed at each valuation. It is the cheapest component in any release and it prevents the most expensive single failure in the category.
Defer participant portals until statements are correct. A portal showing a number members dispute is worse than an email showing the same number, because now they can look at it whenever they like.
Which should you choose, by operator size and stage?
Single parent captive, one or two lines, stable programme. Buy nothing. Manager, actuary and auditor. Revisit if the programme adds fronted lines and collateral.
Two to seven captives, one domicile, no formula allocation. Buy a risk management information system if loss data is weak, and put the effort into the general ledger dimension design rather than into software procurement.
Group captive manager with formula allocation and a disputed assessment. Build the allocation engine only, at $35,000 to $70,000. Do not scope a platform yet. Get valuation dated runs and member statements right, then decide.
Eight or more captives and cells across two or three domiciles. Build the first release at $60,000 to $130,000, starting with the captives that share a structure and adding the odd single parent ones as configuration rather than new engineering.
Management firm across four domiciles with growth limited by analyst capacity. The full platform at $180,000 to $400,000 is defensible, phased over 7 to 12 months, with the filing calendar and fee billing built as one thing because service fees usually track the same schedule of deliverables.
Conventional insurer with a captive attached. Buy core insurance administration. Your volume problem is a product problem.
If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
- 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) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
Frequently asked questions
We already run Origami Risk. Would a build replace it?
No, and it should not. Origami Risk is a risk management information system built around claims, incidents and exposure data, and it does that well. Replacing it to gain captive administration would mean rebuilding something you already have working.
What it does not administer is the captive's own balance sheet: cell level equity, intercompany reinsurance cessions, collateral instruments with call and release logic, or statutory basis financials per cell. The right shape is to keep the risk management information system as the loss data source and build only the administration layer that reads from it.
What does it cost to move off our current administration setup?
The software cost is small and the history cost is not. Whatever you move to has to carry a decade of open policy years with their original valuations, reconciled to the statements members already hold. In our delivery experience converting eight open policy years runs around $16,000, and it is the work that decides whether anyone trusts the new numbers.
Reduce it by converting three valuations per open year rather than every quarter ever produced. The published positions must reconcile. Intermediate valuations nobody circulated are archaeology that adds cost without adding trust.
What happens if our incumbent changes its pricing or per entity model?
Cell structures are the exposed case. If a platform prices per legal entity and your protected cell company is represented as a stack of entities, a change to that model scales directly with cell count rather than with premium or headcount. That is worth testing before your next renewal rather than after.
The practical defence is to know two things in advance: what a full data export contains, and what a costed alternative looks like. An allocation engine at $35,000 to $70,000 on top of your existing accounting is a concrete option to have in hand during a renewal conversation.
How long does a first release take, and what is the slowest part?
Twelve to eighteen weeks for the entity and cell model, allocation with valuation dating and the collateral register. Discovery is two to three weeks of that.
The slowest part is conversion of historical policy years, not engineering. Start it in week three with the actuarial exhibits rather than in week twelve with a data dump. Operations whose actuary already produces clean exhibits per valuation move considerably faster than those reconstructing positions from workbooks.
Do we need a separate accounting file for each cell?
No, and that workaround is why firms end up running twenty five closes with no consolidated position and another spreadsheet on top. Cell should be a mandatory dimension on every transaction, with rules preventing journals crossing cells except through a defined intercompany reinsurance or expense allocation mechanism.
You can often achieve this inside a packaged general ledger with a well designed dimension model, which is a much cheaper answer than a build. Test that first. The build case is about allocation, collateral and filings rather than about bookkeeping.
Can we build only the allocation engine and leave everything else alone?
Yes, and for a group captive manager it is usually the right first move. Valuation dated immutable runs with variance reporting between them, plus member statements generated from each run, comes in at $35,000 to $70,000 over eight to twelve weeks.
It leaves your accounting, your loss data and your filing process exactly where they are. What changes is that recomputing 2019 in 2026 produces a new run and an explainable variance rather than overwriting what members were told in 2021.
How much does adding another domicile really cost?
Roughly $12,000 to $30,000 per domicile in a build, covering the filing template set, dating rules from each entity's fiscal year end, and the premium tax calculation. The mechanism is shared across domiciles and the content is not, so the second costs less than the first and the fifth still costs something.
Each domicile also adds to the annual maintenance line, because regulators revise forms and dates independently. Firms with a wide domicile footprint should price maintenance above the headline percentage rather than at it.
What should we ask a developer before committing?
Ask them to draw captive, cell, participant, policy year, fund year, cession, collateral instrument and filing obligation, and to explain why policy year, accident year and fund year are three different things that coexist on one record. If that explanation does not come quickly, the system will give the wrong answer once a year develops.
Then ask how they handle a retrospective reserve restatement. The correct answer is valuation dated runs with variance reporting, not recalculation in place. Then settle code and data ownership in writing before kickoff, because a captive can outlive three software vendors.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
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.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
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.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
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.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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 .
