Excess and Surplus Lines Platform: Build or Buy at Your Line Count
The question that decides this is not premium volume, it is how many lines of business you write and how many states you file in.
On this page
The question that decides this is not premium volume, it is how many lines of business you write and how many states you file in. A retail agency placing occasional non admitted business through wholesalers should never build, because the infrastructure cost sits properly with the wholesaler. A monoline programme underwriter filing in five states can buy a specialist for the one stage that hurts and be finished. A managing general agent (MGA) writing two or more lines, binding on delegated authority and filing in a dozen states is the shape that clears a build, and a first release there runs $100,000 to $220,000 in 14 to 20 weeks.
When is off the shelf genuinely the right call here?
If you are a retail agency placing occasional excess and surplus lines business through wholesalers, do not build any of this. Your wholesaler already carries the submission intake, the manuscript wordings, the stamping and the filing, and that is where the cost belongs. Nothing in this guide argues otherwise for you.
If exactly one stage is your bottleneck, buy the specialist for that stage rather than funding a platform. Send is built for submission intake and triage in the specialty and London markets, and if your problem is that submissions arrive faster than underwriters can read spreadsheets, adopting it costs a fraction of a programme you may not finish. hyperexponential gives underwriters and actuaries a governed environment for their own pricing models, which is precisely the right shape if your gap is pricing governance rather than issuance.
If you also write a meaningful admitted book, Duck Creek and Guidewire remain the correct systems for that half. Applying filed rates, rules and forms consistently is exactly their value, and many carriers sensibly run the admitted and non admitted worlds on different platforms rather than forcing one to pretend to be the other.
The test for buying is whether your pain sits inside one stage. Intake only, or pricing governance only, or admitted policy administration only. If it does, buy the product built for that stage. The build case appears when the whole chain has to share one risk record, and only then.
When does a custom build actually pay off?
The problem worth solving is that admitted platforms rest on an assumption non admitted business does not share. They assume a filed rate, a filed rule and a filed form, and their value is applying them consistently. In excess and surplus lines you are pricing a risk the standard market declined, the rate comes from an underwriter's judgement, and the form is manuscripted for this specific account. Configure a system built on filed rates and you spend the implementation building override paths so underwriters can bypass the rating engine, which raises the obvious question of what the engine is contributing.
In Digital Heroes delivery experience a first release covering submission intake with structured extraction from schedules of values, driver lists and loss runs, an underwriter rating workbench that versions and governs the pricing models rather than replacing them, and quote and binder issuance with subjectivities modelled as tracked objects runs $100,000 to $220,000 over 14 to 20 weeks. A full platform adding clause based manuscript policy assembly, endorsement and cancellation processing, surplus lines tax and stamping at transaction level with state filing, and bordereaux to each capacity provider runs $280,000 to $650,000 across 9 to 18 months.
Build when two or more hold. Your appetite, rating approach and wordings are the product and are therefore not configurable in anyone else's platform. You bind on delegated authority and owe bordereaux in several carrier formats. You file in more than a handful of states and errors have already cost you. Or your underwriters price in personal spreadsheets with no version control, which is a rate adequacy risk sitting on a laptop.
How do they compare on the things that matter in this industry?
On intake, the products are genuinely ahead of most in-house efforts and you should say so. A schedule of values arrives with forty columns and a construction code set from one broker and the same information in a different order with three merged header rows from another. Whether you buy or build, the outcome to aim for is an underwriter opening a triaged submission with total insured value computed, locations geocoded, catastrophe exposure flagged and loss history summarised, rather than spending forty minutes making a spreadsheet legible.
On rating, the design principle is identical either way and it is the one most software teams get backwards. Do not replace the underwriter's spreadsheet. That model carries the pricing judgement that makes the book profitable, it changes as the market turns, and it belongs to the person accountable for the loss ratio. Version and govern it: record the model version, the inputs, the technical price it produced, the price actually charged and the documented reason for the gap. That is the rate adequacy report your chief underwriting officer cannot currently produce.
On policy documents, a form library assuming base forms plus filed endorsements does not describe your business. A manuscript policy is a base wording, a stack of endorsements some written for this account, deletions, sublimits and a schedule, and the issued document must be reproducible years later exactly as issued. Composing it from versioned clause objects with approval status is more work than attaching a form to a record, and it is the reason the platform survives a coverage dispute in year three.
On tax and stamping, the mechanics differ meaningfully between offices such as SLTX in Texas, the Surplus Line Association of California and FSLSO in Florida, each with its own data elements, deadlines and file formats. Calculating at transaction level rather than policy level is the distinction that matters, because every endorsement and cancellation then produces its own correctly signed filing entry.
What does total cost of ownership look like at your scale?
Take an MGA writing commercial property and general liability, binding on behalf of three capacity providers and filing in twelve states. A first release prices at about $182,000 over roughly 18 weeks: discovery, risk data model and rating governance design $22,000, submission intake with schedule of values, loss run and driver list extraction plus triage $46,000, the underwriter rating workbench with model versioning and technical price capture $52,000, quote and binder issuance with subjectivity tracking $34,000, and a broker portal, document store and launch support $28,000.
Phase two over the following eleven months adds clause based manuscript policy assembly at $74,000, endorsement and cancellation processing with pro rata adjustment at $46,000, surplus lines tax and stamping across twelve states at $68,000, bordereaux for three capacity providers at $42,000, rate adequacy and portfolio reporting at $32,000, and modelling the second line properly at $38,000. That is $300,000, taking the platform to $482,000 all in.
Running costs are 15 to 20 per cent of build cost a year, roughly $70,000 to $95,000, and the composition is unusual. The largest recurring line is regulatory rule maintenance, because stamping offices change data requirements and fee structures on their own timetable and your rules must be held as dated configuration so a policy issued last year stays calculable under last year's rules. Second is per carrier bordereaux drift as templates get revised. Third is extraction quality, since brokers change spreadsheet formats and accuracy decays quietly unless someone works the exception queue.
Each additional line of business adds roughly $35,000 to $60,000, covering intake shape, rating inputs, clause library additions and bordereaux fields. That is the multiplier to model before anything else.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. In this market the hybrid is not a fallback, it is what most MGAs should end at.
Concretely: buy the intake stage if intake is drowning you, and buy the pricing governance environment if that is your gap. Then build the layer nobody sells, which is the risk record that carries a submission through to a bound policy with its subjectivities, its clause versions and its filing entries attached. That layer owns the things that are genuinely yours: your appetite and authority controls enforced at the point of bind, your clause library, and your transaction level tax and stamping calculation.
The same logic applies to admitted business. Keep it on Duck Creek or Guidewire. Do not try to make one platform serve both, and do not let a developer persuade you that a single system is cleaner. It is cleaner on a diagram and worse in a renewal season.
Sequence by the order of pain rather than the order of a policy lifecycle. Intake and the rating workbench first, because they change the working day of the people who make you money and buy the political capital for the rest. Filing last, and only after a parallel run of at least one full month with every transaction reconciled, because a missed filing is a penalty rather than a defect report.
Which should you choose, by operator size and stage?
A retail agency placing occasional non admitted business: buy nothing beyond what your agency management system already does, and let the wholesaler carry the rest.
A monoline programme underwriter with one bottleneck: buy the specialist for that stage. Send for intake, hyperexponential for pricing governance. Prove the problem is actually solved before you consider anything larger, because solving one problem properly beats a platform programme you may not complete.
A two line MGA binding on delegated authority in a dozen states: build the first release at $100,000 to $220,000, start monoline on whichever line generates most of your submissions, and file in your top five states properly while handling the tail manually. Manual filing on a handful of transactions a month costs less than engineering rules you exercise twice a year.
A four line MGA filing in twenty states with several capacity providers: expect the full band, treat each capacity provider as an integration rather than a configuration at roughly $14,000 each, and budget claims separately if you handle them, because that is a different system sharing a database rather than a module.
Whatever size you are, take one thing off the table before the first quote. Your wordings and your pricing models are the underwriting business itself. Own the clause library, the rating model definitions and the repository in writing before kickoff, because a developer holding your clause library is holding your ability to write business.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- McKinsey found that tech debt can amount to 20-40% of the value of a company's entire technology estate before depreciation, and CIOs report that 10-20% of the budget for new products is diverted to resolving tech-debt issues. Source: McKinsey & Company (2020) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- 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) →
- WordPress powers 41.5% of all websites and holds 59.2% of the market among sites running a known content management system, making it by far the most-used CMS on the web. Source: W3Techs (2026) →
Frequently asked questions
What does it cost to move off a platform we have already configured?
Ask first what you can export and in what form. The expensive part of leaving is rarely the licence, it is that the configuration holding your appetite rules, clause variants and filing mappings is expressed in a vendor's own model and does not travel.
Protect yourself at contract stage. Insist on structured export of policy records, clause content and transaction level filing history, and test the export during implementation rather than at renewal, when your bargaining position is at its weakest.
What happens if our platform vendor changes its pricing or packaging?
Your exposure is proportional to how much of the underwriting process lives inside the product. An MGA whose clause library, rating model governance and filing rules sit in a layer it owns can change rendering or intake products as a project.
An MGA that configured everything inside one platform faces a rebuild disguised as a renegotiation, and it will be discussing it in the middle of a renewal season. That portability argument is a real reason to own the thin layer even while the platform itself is performing.
How long until underwriters are actually working in a new system?
Fourteen to twenty weeks to a first release, and the sequencing matters more than the duration. Build intake and the rating workbench first so underwriters see a visible win in month four rather than month twelve.
Discovery runs three to four weeks and is heavier than in most categories, because underwriters have to explain how they actually price and that conversation surfaces disagreements between them that nobody has had out loud. Budget for it rather than compressing it.
Is this cheaper than configuring Duck Creek or Guidewire?
Compare on fit rather than on price. Both are built around filed rates, rules and forms, and applying those consistently is exactly their value in the admitted market.
Configuring them for freedom of rate and form means building override paths so underwriters can bypass the rating engine, which is a strange thing to pay for. Keep them for your admitted book, where they are the right answer, and give the non admitted book a platform shaped like the business it serves.
Should we replace our underwriters' pricing spreadsheets?
No, and removing that from scope is one of the largest savings available. Those models carry the pricing judgement that makes the book profitable and they change as the market turns, so rebuilding them as static rate tables spends money to destroy value.
Fund governance instead. Record the model version used, the inputs, the technical price, the price charged and the underwriter's documented reason for any gap. That is a small module and it produces the rate adequacy report nobody currently has.
How much does the tax and stamping work add?
Around $68,000 for twelve states in a typical build, covering transaction level calculation, dated rule configuration, filing file generation and monthly reconciliation against the general ledger. The engine is shared, so the per state increment is rules, mapping and testing rather than a rebuild.
Filing in your top five states and handling the tail manually in phase one is a legitimate reduction. Just insist on a full month of parallel filing before you retire the manual process.
What does delegated authority add to the budget?
Two things, both priced per capacity provider. Bordereaux in each carrier's own format on each carrier's cycle runs around $14,000 per provider, and appetite, limit and authority controls enforced at the point of bind rather than reviewed afterwards is a further module.
Treat each capacity provider as an integration. Three providers accounted for $42,000 of phase two in the worked example, and that figure scales close to linearly as you add capacity.
What is the cheapest credible first release?
Around $100,000 for a monoline programme underwriter: intake with extraction for one submission shape, the rating workbench with model versioning, and quote and binder issuance with subjectivities tracked as objects with owners and due dates.
Be sceptical of a cheaper quote. Below that you are buying a submission log, which has value if intake is genuinely your only bottleneck, but be clear that is what you are buying rather than a platform.
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 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.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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.
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.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
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.
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.
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.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
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 Rohan.
Director of Web Platform Engineering · Delhi · 2 posts on the site
Published · Last updated .
