Insurance Agency CRM: Build or Buy at Your Seat Count
Two numbers decide this: your seat count in three years, and how many of your commission splits live in a spreadsheet beside whatever you licence. Under roughly 15 seats with three carriers and standard splits, buy, and do it without hesitation.
On this page
Two numbers decide this: your seat count in three years, and how many of your commission splits live in a spreadsheet beside whatever you licence. Under roughly 15 seats with three carriers and standard splits, buy, and do it without hesitation. Past 25 seats with six or more carriers and splits your operations manager holds in her head, a custom layer usually clears its cost inside two renewal cycles. Most agencies reading this fall in the middle, and for them the honest answer is neither pure option: keep a mature agency management system for policy administration and build only the commission and renewal layer on top of it.
When is off the shelf genuinely the right call here?
If you are a personal lines agency with five producers, three carrier appointments and commission splits that fit on one page, buy. EZLynx, HawkSoft and AMS360 exist for exactly your shape of agency, they arrive in weeks rather than months, and a good implementation of one of them will serve you better than a custom system you then have to maintain. We tell agencies this regularly, and it is not modesty about our own trade. It is that a build at that size is funded by producer commissions that should be buying another producer.
The packaged platforms are strong at the part that is genuinely hard to build and cheap to rent. Policy administration is compliance heavy, it changes when regulators change it, and a vendor whose whole business is tracking that change will do it better than your development budget will. Applied and Vertafore carry the same argument at larger scale. The comparative raters sit alongside them and are not worth recreating either.
Buy and stop, too, if your real complaint is reporting. Plenty of agencies arrive convinced they need a system when what they actually need is a renewal report their principal will open. That is a configuration project measured in days, not a platform. Building a second system alongside a first one nobody configured properly leaves you with two systems nobody trusts.
The test worth applying: can a servicing agent tell you, right now, which policies renew in 45 days and who owns each one? If the answer comes back within a minute from the tool you already pay for, your platform is not your problem, and a build will not become one either. What you have is a discipline question, and those are cheaper to fix than a system replacement.
When does a custom build actually pay off?
The build case in this category is narrow and specific, and it almost always centres on money moving rather than on screens.
- Commission reconciliation that nobody can do by hand. Each carrier reports differently, new business and renewal rates differ, and a shortfall buried in a statement does not get chased. Building expected against actual, with the discrepancy on a review screen, runs $12,000 to $30,000 and is the feature principals care about most.
- Splits that live outside the platform. House accounts, a 60/40 producer arrangement, an owner override, a legacy rate you promised in 2019. Every arrangement you handle with a manual credit is a rule the packaged tool cannot express, and roughly $8,000 of build to encode properly.
- Per seat economics at your projected headcount. Not today's. Take your seat count in three years, multiply, and add the rater, the download service and the electronic signature account. That total is what a build competes against.
- A book you cannot see across offices. If a branch manager cannot answer what renews in 45 days without an export, you have a visibility problem that role based access and a live queue fix directly.
One more signal, and it is the strongest one: if a new servicing hire needs a week of shadowing to learn the exceptions your team works around every day, the configuration ceiling is already costing you more than the licence.
How do they compare on the things that matter in this industry?
Judge this on grounds a practitioner can verify, not on feature lists.
- Policy lifecycle modelling. A packaged agency system models the policy properly, with effective dates, endorsements and status. A general purpose sales platform does not, and that is the real reason agencies on contact and deal tools end up in spreadsheets. Between the two agency options this is close to a draw, so it should not drive your decision.
- Commission reconciliation. This is where the gap opens. Packaged tools calculate; they rarely reconcile a carrier statement against expectation in a form your principal can act on. A build does that as its primary job.
- Renewal control. Both can surface a 90, 60 and 30 day queue. The difference is whether the queue is assigned to a named servicing agent by rule and whether a mid term endorsement moves the date automatically.
- Carrier data exchange. Where your carriers support the industry download standard, a packaged system almost certainly already consumes it. A build has to add it, at $10,000 to $25,000, and it is the single highest value integration in the category either way.
- Reporting rigidity and data portability. The two questions to ask any incumbent vendor: can I get a full export of my policy, activity and commission data on demand, and in what format. The answer tells you what your switching position actually is.
What does total cost of ownership look like at your scale?
These are Digital Heroes delivery bands, not a price list, and they assume production grade security because you hold personally identifiable information and financial records.
- Focused first version, $18,000 to $40,000, four to six weeks. Policy records with real dates, a renewal engine feeding a task queue, one carrier or rater integration and basic expected commission.
- Full agency system, $45,000 to $95,000, eight to fourteen weeks. Adds endorsements, claims follow up, multi carrier download, producer splits and reporting.
- Multi branch or brokerage, $100,000 to $200,000 and above, four to seven months. Adds office level access control, migration off a legacy agency management system and bespoke carrier interfaces.
Then the running costs nobody quotes. Support at 15 to 20 percent of build cost a year, because commission runs monthly and a defect at month end is not a next sprint problem. Each new carrier appointment you integrate, $4,000 to $12,000, which for a growing agency recurs annually. Carrier interface changes at $3,000 to $9,000 a year, because statement layouts move on the carrier's schedule. Hosting and record retention at $2,500 to $7,000. Electronic signature charges per envelope, which applications and renewals generate steadily.
On the buy side, the honest comparison includes what sits around the platform: the rater subscription, the download service, the signature account, and the spreadsheets that cost nothing in cash and a great deal in hours. Put your general manager's reconciliation time into that column at loaded salary and the two totals move closer than the invoice suggests.
What does the hybrid look like, and when is it the honest answer?
For most agencies between 15 and 50 seats, this is the right shape and we recommend it more often than either pure option.
Keep your agency management system. It handles compliance heavy policy administration, its vendor tracks regulatory change, and rebuilding that is the most expensive part of any build with the least differentiation at the end of it. Then build the layer where your money and your judgement actually live: expected commission per policy at the correct new business or renewal rate, reconciliation against each carrier statement, producer splits with house accounts and overrides, and a renewal queue assigned by rule rather than by memory.
Costed as its own project rather than a platform, that layer is roughly $9,000 for the renewal engine, $16,000 for expected commission plus statement reconciliation and $8,000 for splits and overrides, sitting on top of a licence you continue paying. Your agency management system fees then belong on both sides of the comparison, which is the part most build cases quietly omit.
Start reconciliation with your top three carriers rather than all of them. In most books a small number of carriers produce most of the discrepancies worth chasing, and proving the pattern on three is what justifies extending it to nine.
Which should you choose, by operator size and stage?
Under ten seats, three carriers, personal lines: buy. EZLynx or HawkSoft, configured properly, and spend the rest on a producer. Nothing in a build beats hiring someone who can write business.
Ten to twenty five seats, standard splits: configure first. Ask your incumbent what a renewal queue by servicing agent looks like in their product and give it one quarter. If the answer is still a spreadsheet at the end of that quarter, move to the hybrid layer rather than a replacement.
Twenty five to fifty seats, six or more carriers, splits with real exceptions: build the commission and renewal layer on top of what you have. This is the band where the arithmetic works most reliably, because both the per seat line and the reconciliation labour are large enough to matter and the policy administration you would otherwise rebuild is already handled.
Multi office brokerage, commercial lines, growth by acquisition: this is the only profile where a full build is routinely correct, because you are carrying two ways of working and two commission structures, and no configuration reconciles those. Budget $100,000 upward and phase migration by moving active policies and the last two renewal cycles rather than a decade of history.
Whatever you choose, settle ownership in writing before kickoff. You should own the repository, the cloud accounts and the right to hire another firm. Your book is your asset, and the system that manages it should not be somebody else's.
If you would rather scope this before committing budget, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 76% of organizations report that less than half their CRM data is accurate and complete, and 37% experienced direct revenue loss attributable to poor data quality (survey of 602 CRM users across the US, UK, and Australia). Source: Validity (2025) →
- 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) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
Frequently asked questions
What does it cost to switch off EZLynx or AMS360 later?
The licence stops, the data problem does not. Budget $8,000 to $35,000 for migration, and treat it as its own line rather than folding it into a build. Ten years of policies, endorsements, activity notes and attachments are rarely as clean as anyone believes. The way to hold it at the low end is to move active policies and the last two renewal cycles into the working system and keep everything older as a read only archive. Before you commit either way, ask your incumbent in writing what a full export contains and in what format, because that answer is your actual switching position.
What happens if our platform raises its per seat price?
This is why the comparison should run on your headcount in three years rather than today. Packaged agency platforms price by user, so your bill grows with the thing you are trying to grow, and a rate change lands on every seat at once. You cannot control the pricing, but you can reduce your exposure to it: a hybrid where policy administration stays licensed and the commission and renewal layer is owned means a seat increase hits a smaller number of users doing a narrower job. Ask for multi year pricing in writing at renewal and treat a refusal as information.
How long does a custom insurance agency CRM take to build?
Four to eight weeks to a first version covering the revenue critical path: policy records with real dates, renewal automation and commission calculation. Claims workflow, multi carrier download and reporting follow in a second phase. A full multi branch build with legacy migration and office level access control runs four to seven months. Agencies that hand over three carrier commission statements, a producer split list and an export of active policies on day one move noticeably faster, because those three artefacts answer most of the design questions that would otherwise take four meetings.
Is EZLynx enough, or do we genuinely need something custom?
For a small agency with standard workflows it is enough, and building past it is not clever. The test is not whether the product frustrates you, it is whether you handle work outside it. List every workflow you currently run in a spreadsheet or a manual credit note: an unusual split, a niche line your carrier reports differently, a servicing routine on a laminated card. If that list is short and your team is not growing, renew. If a new hire needs a week of shadowing to learn the exceptions, the configuration ceiling is already the expensive part.
Do we have to replace our agency management system to build?
Usually not, and we advise against it. If a mature system already handles compliance heavy policy administration well, keep it and build the sales, renewal and commission layer on top through its interfaces. That avoids the most expensive part of any build and keeps administration on a platform whose vendor tracks regulatory change for you. Its licence fees then belong on both sides of the comparison, which is the line most build cases quietly leave out and the one your finance director will find.
What does commission reconciliation actually cost to build?
Between $12,000 and $30,000, with producer splits, house accounts and owner overrides adding roughly $8,000 on top. The system stores an expected commission per policy at the correct new business or renewal rate, then compares it against each carrier statement so a shortfall surfaces on a review screen instead of disappearing. Start with your top three carriers, since a small number usually produce most of the discrepancies worth chasing. This is the single line in the whole build that agency principals consistently say repaid fastest.
Can we run a build alongside our current system during rollout?
Yes, and you should. Phase it by team rather than switching everyone at once: one servicing group works in the new layer for a full month while the rest continue as they are, and you compare the commission output line by line before anyone else moves. Renewals run on dates and commission runs monthly, so a parallel period gives you one complete cycle of evidence. Agencies that attempt a single cutover discover their exceptions at month end, which is the worst possible moment to find them.
Which integration should we pay for first?
The industry download standard, where your carriers support it, at $10,000 to $25,000. It removes hours of manual entry every week and it feeds both policy and commission data, which makes everything downstream more trustworthy. After that, one comparative rater covering most of your quoting volume, at $4,000 to $12,000. Leave accounting synchronisation until the commission figures are proven, because posting numbers you do not yet trust into your ledger creates a reconciliation problem rather than solving one.
How long does it take to build a custom CRM from scratch?
A focused first version takes 10 to 14 weeks in Digital Heroes delivery experience: about 2 weeks of discovery and data modeling, 6 to 9 weeks of build, and 2 weeks of migration and testing. Fully replacing a heavily customized Salesforce setup takes 5 to 8 months. Timelines slip most often on data migration, so insist that legacy data mapping starts in week one, not at the end.
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.
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 does moving our data from Salesforce or spreadsheets into a custom CRM work?
The agency exports your records, writes mapping scripts that translate old fields into the new schema, runs test migrations into a staging system for you to verify, and only then performs the final cutover. Salesforce exports cleanly through its API including notes and attachments; spreadsheets are messier and need a deduplication pass, where we commonly see 10 to 20 percent duplicate contacts. Expect migration to be 10 to 15 percent of total project effort, and be suspicious of any quote that treats it as an afterthought.
We're outgrowing HubSpot's free CRM. Should we upgrade to a paid plan or build our own?
Upgrade inside HubSpot if your problem is limits on contacts, seats, or automation; Sales Hub Professional lists at $90 to $100 per seat per month and solves volume problems well. Build custom when the data model is the problem, for example deals that involve multi-site installations, equipment rentals, or recurring service visits that HubSpot's contact-company-deal structure cannot represent without workarounds. Roughly a third of the CRM projects Digital Heroes takes on replace a HubSpot account the team had bent past its limits.
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.
Can AI features like lead scoring and email drafting be built into a custom CRM?
Yes, AI features are now a standard request: connecting a model API for lead scoring, call summarization, or drafted follow-up emails typically adds $5,000 to $15,000 to a build in recent Digital Heroes projects. The custom advantage is that the AI runs on your full data and your rules instead of a vendor's generic feature, and you are never pushed into an add-on tier the way Salesforce prices Einstein. Start with one AI feature tied to a measurable task, prove it works, then extend.
How many developers does it take to build a custom CRM?
A typical build runs with 4 to 5 people at partial or full allocation: a project lead, one or two developers, a designer, and a QA tester, with design and QA tapering after the middle sprints. Teams larger than six rarely make a CRM ship faster and often slow it down, so do not pay for a bench. On your side, plan for one decision-maker spending 2 to 4 hours a week, because slow client feedback delays more projects than slow code does.
What does it cost to maintain a custom CRM after launch?
Budget 15 to 20 percent of the build cost per year, so roughly $6,000 to $10,000 annually on a $40,000 system, covering hosting, security patches, dependency updates, and a pool of small improvements. Hosting itself is the minor part, typically $50 to $300 a month for companies under 100 users. For comparison, a 20-user team on Salesforce Enterprise pays about $9,900 in licenses every quarter at list price, close to a full year of that maintenance budget.
Will a custom CRM scale as we grow from 10 to 200 users?
Yes, if the data model and hosting are planned for it in discovery, and scaling economics are one of custom's quiet advantages: adding 190 users to a system you own means a hosting upgrade of a few hundred dollars a month, not 190 new licenses. The same growth on Salesforce Enterprise adds about $376,000 a year at list price. Tell the agency your three-year headcount plan up front, because the decisions that make 200 users painless are made before the first line of code.
How does a custom CRM handle GDPR, HIPAA, or other compliance requirements?
Compliance has to be designed in from the schema up: field-level encryption, role-based access, audit logs, retention rules, and for GDPR a working way to export and delete a person's data on request. Custom can actually be the stronger option because you decide exactly where data lives, including keeping it in-country or on your own servers, which off-the-shelf tools do not always allow on lower tiers. If HIPAA applies, confirm the agency will sign a business associate agreement and has shipped healthcare systems before, because that experience is not implied.
Who can build a custom CRM software system?
Digital Heroes builds custom CRM 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 CRM 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 Sofia.
Senior Brand Identity Designer · New-york · 5 posts on the site
Published · Last updated .
