CRM insurance: what to require and what it costs

A CRM for an insurance agency is the system for lead capture, producer pipeline, close ratios, drip outreach and renewal reminders. The agency management system is the record for active policies, endorsements, ID cards, commissions, accounting, ACORD forms and carrier download. As of October 2026, Dynamics 365 Sales Professional lists at USD 65 per user per month, paid yearly, and Odoo lists a 25-hour Success Pack at USD 3,060 for a new customer. If producers need pipeline tasks and the agency system already holds the policy, put the CRM beside that system. If you need download, comparative rating or commission payables, keep the book of record in the agency system.

What a pipeline CRM handles and what the agency system keeps

EZLynx draws the same line in a 26 March 2026 article: the CRM runs capture, pipeline, close ratios, email, text and renewal reminders, and the agency management system runs the policy lifecycle. That split is the useful starting point for a 20- to 100-person independent agency.

Applied Epic is a cloud, browser-based agency management system for personal lines, commercial lines and benefits. The same page describes native prospecting and pipeline, quoting, accounting, policy management, and insurer connectivity through Ivans for submissions, servicing and policy data. Applied also says integrated sales automation can track new business and renewals inside the agency system, so an agency does not have to buy a separate sales system, and that 7 of the 10 largest insurance agencies are standardized on Applied Epic, citing Business Insurance Top 100. The product page publishes no license price.

HawkSoft markets an agency management system with retention alerts, a sales-funnel lead module, cross-sell reports, and reports for close ratio by producer, policies per client, commissions by carrier and retention. That product page does not publish a license price.

AgencyBloc sells AMS+ for individual health, group benefits and senior products in Grow, Accelerate and a third package, and sells Commissions+ separately with pricing based on transaction volume. The public pricing page lists carrier-statement import, rate tables, bonus and override tracking and agent statements, and asks buyers to request a price. No dollar amount is published.

AgencyZoom is the opposite shape: a priced sales layer that still assumes an agency system. Its pricing FAQ says "Does this replace my AMS? No, AgencyZoom acts as an extension to your AMS." Integration with the agency system may require extra cost. Onboarding is described as 2 to 4 weeks, and a 14-day trial is offered.

People shopping this category already separate the two bills. A thread titled "How much do other insurance agencies pay for their CRM software?" includes a comment, "AgencyZoom+Hawksoft. We're around $1k a month or so.", and another, "Ezlynx 4 users about $500/mo". Those comments describe small teams and date from April 2024. They are not 2026 invoices, and they do not describe a 20- to 100-person agency. Use them only as a reminder that agencies often pay for a sales tool and an agency system at the same time.

Another brokerage thread puts the storage problem cleanly: "If you need document management with insurance-specific structure (policy numbers, renewal dates, coverage fields as native properties), you won't be forcing a generic CRM to behave like something it wasn't designed to be." Read that as a scoping rule. Native policy fields are a configuration decision. Carrier download and commission accounting are a product decision.

Which insurance workflows fit Dynamics 365 Sales or Odoo

Use two columns when you score a product. Pipeline work is leads, stages, producer goals and renewal tasks. The system of record is the policy, the carrier transaction and the money you owe a producer.

• New-business stages (Dynamics 365 Sales or Odoo CRM: Fit. Both products are built around leads and opportunities. · Agency management system: Often included, as Applied Epic's pipeline shows.)
• Producer goals and forecast (Dynamics 365 Sales or Odoo CRM: Fit. Odoo CRM includes revenue forecasts. Dynamics includes opportunity management. · Agency management system: Close-ratio and policies-per-client reports are sold with the AMS, as HawkSoft markets them.)
• Renewal tasks (Dynamics 365 Sales or Odoo CRM: Configurable. Odoo plans the next step with scheduled activities. A Dynamics reminder that needs Power Automate is an extra license. · Agency management system: Applied Epic says new business and renewals can be tracked inside the AMS.)
• Policy number and term (Dynamics 365 Sales or Odoo CRM: Configurable as fields on the account or opportunity. Staff still need a rule for which system they open first. · Agency management system: Native policy record, including term and endorsements.)
• Carrier download or real-time rating (Dynamics 365 Sales or Odoo CRM: Out of scope. Neither vendor documents a native Ivans or download connector. · Agency management system: In scope. Applied Epic cites Ivans. EZLynx places download and real-time rating in the AMS.)
• Endorsements, ID cards, ACORD forms, certificates (Dynamics 365 Sales or Odoo CRM: Out of scope. · Agency management system: In scope on the EZLynx definition of an AMS.)
• Commission statements and producer payouts (Dynamics 365 Sales or Odoo CRM: Out of scope. Odoo CRM does not list producer commission accounting. · Agency management system: In scope. AgencyBloc prices Commissions+ on transaction volume, separately from AMS+.)
• How long you keep the file (Dynamics 365 Sales or Odoo CRM: Configurable only as the retention schedule you set. The legal period comes from your state, province or carrier contract. · Agency management system: Keep the policy file in the AMS when that system is the book of record.)

Odoo CRM, as the single free app or inside a paid plan, provides a Kanban opportunity pipeline, scheduled activities that plan the next step from a sales script, email logged on the pipeline, quotations, lead assignment automation and revenue forecasts. Subscriptions is a separate app for recurring revenue. None of those CRM features is carrier download, comparative rating, ACORD forms or producer commission accounting.

Dynamics 365 Sales includes lead, opportunity, account and contact management, plus quotes, orders and invoices. That set covers a producer chasing a new commercial account and sending a quote. It does not document comparative rating, ACORD certificates or a commission payable to a sub-producer. Salesforce's insurance CRM page describes an insurance CRM as software that centralizes policyholder data and interactions. Its Financial Services Cloud pricing page is more specific about insurance scope, and it still publishes no dollar amount: Digital Insurance is an add-on on Core and Advanced editions and is included in Max editions. Policy Administration, Group Benefits and Claims Management are usage-based add-ons that require Digital Insurance. Financial Services Cloud for Insurance Brokerage is available with Advanced and Max editions and includes the corresponding Sales Cloud and Service Cloud. The page says to contact sales at 1-800-664-9073.

Creatio's glossary, dated 22 January 2026, says general CRMs such as Salesforce, HubSpot, Zoho and Pipedrive often need heavy customization, while insurance platforms cover more out of the box. Zoho's insurance page presents leads, claims assignment and multiple policies in one system, which is a configuration story beside the carrier-download and commission boundary EZLynx describes. HubSpot's insurance page claims a free CRM for leads, workflows and book-of-business tracking, plus agency-system connections through an API, native integrations and Zapier. The page does not price paid hubs, and it does not say policy admin or commissions move out of the agency system.

For a single-entity agency that already runs Applied Epic, HawkSoft or a similar system, Dynamics 365 Sales or Odoo CRM is a pipeline and renewal-task layer. We configure that layer in our CRM implementation work, with the agency system left as the book of record unless you have deliberately chosen a configured policy object and accepted the missing download. A configured policy object can show a number, a term and a coverage note to the producer. It does not replace Ivans, ACORD or the commission statement.

What 20 users and 50 users cost at list price

Assume two desks. The first has 20 people who each need a full CRM seat. The second has 50 people on the same rule. Producers, account managers and the principal are included. A receptionist who never opens the pipeline is not. Prices below are list prices as of October 2026. Microsoft says the figures on its pricing page are informational and the checkout price can differ.

US list prices, paid yearly, are USD 65 for Sales Professional, USD 105 for Sales Enterprise and USD 150 for Sales Premium, each per user per month. Sales Premium includes 1,000 Copilot Credits per user per month. Microsoft Relationship Sales is Sales Enterprise plus LinkedIn Sales Navigator, priced as variable, with a 10-seat minimum.

• 20 full users (Professional, per year: USD 15,600 · Enterprise, per year: USD 25,200 · Premium, per year: USD 36,000)
• 50 full users (Professional, per year: USD 39,000 · Enterprise, per year: USD 63,000 · Premium, per year: USD 90,000)

The 20-user Professional total is 20 times USD 65 times 12. The 50-user Enterprise total is 50 times USD 105 times 12. Premium is the same math at USD 150. Professional already includes the lead, opportunity, account, contact, quote, order and invoice features Microsoft lists. Premium adds 1,000 Copilot Credits per user per month. None of the three editions adds carrier download. The pricing page does not publish a custom-table limit, so have Microsoft show any extra tables on your own tenant before you assume Enterprise is required.

Canadian list prices on Microsoft's Canada page are CAD 88.20, CAD 142.50 and CAD 203.50 per user per month, paid yearly, plus applicable tax.

• 20 full users (Professional, per year: CAD 21,168 · Enterprise, per year: CAD 34,200 · Premium, per year: CAD 48,840)
• 50 full users (Professional, per year: CAD 52,920 · Enterprise, per year: CAD 85,500 · Premium, per year: CAD 122,100)

Those Canadian totals are the monthly list times 12 times the user count, before tax. A 20-user Professional desk is 20 times CAD 88.20 times 12. A 50-user Premium desk is 50 times CAD 203.50 times 12. If you have a cross-border team, price each user on the agreement Microsoft will invoice. Keep the USD column and the CAD column separate, because tax sits on the Canadian list.

Odoo is a range, not a single list. One app is free for unlimited users on Odoo Online. The Standard plan is all apps on Odoo Online. The Custom plan adds Odoo Studio, multi-company, the external API, and the option of Odoo.sh or on-premise. Odoo.sh hosting is not included, and implementation services are not included in the subscription. The same page showed Standard at USD 24.90, USD 31.10 and USD 38.90 per user per month, and Custom at USD 49.00, USD 61.00, USD 61.10 and USD 76.20, because yearly and monthly prices and a 12-month discount for the initial users were both on the page. A footnote says the discount is valid for 12 months for the initial users ordered. A Light User is listed at USD 8.90 and is not a full CRM user. Those Odoo figures are in US dollars. A Canadian agency should get the CAD figure from Odoo before signing.

If you treat every visible figure as a monthly rate, a year of Standard for 20 full users spans USD 5,976 to USD 9,336. Custom for those 20 users spans USD 11,760 to USD 18,288. Standard for 50 full users spans USD 14,940 to USD 23,340. Custom for 50 spans USD 29,400 to USD 45,720. The low end is the smallest figure on the page times users times 12. The high end is the largest. Year two can move when the 12-month initial-user discount ends. Confirm which toggle applies before you put a number in the budget.

AgencyZoom's independent-agency plans are Essential at USD 149, Growth at USD 199 and Pro at USD 349 per month, each including up to 7 users. Additional seats require contacting sales. At the published cap, Pro is USD 4,188 over twelve months for as many as 7 users. A 20-user or 50-user agency cannot multiply USD 349 by headcount, because seats 8 through 100 are not on the page. The page labels an annual option "Annually -20% Discount" while the plan cards show those monthly figures. Ask for the annual invoice. A separate Allstate captive track is USD 99 per month for a single location and USD 129 per month for multiple locations, including a comp calculator with chargebacks and renewal automation. That track is for an Allstate captive, not for an independent agency on the other tab.

Applied Epic, HawkSoft and AgencyBloc stay in a quote-only row. Applied Epic and AgencyBloc, linked above, do not publish a per-user or per-agency license fee, and HawkSoft's product site does not either. Salesforce Financial Services Cloud, including the insurance brokerage and policy-administration add-ons, is also quote-only. Ask each vendor for a written quote and set it next to the Dynamics and Odoo list math.

What the license does not include

The cheap seat is the wrong seat when another system has to talk to the CRM. Odoo says an external API call is one that outside software initiates against Odoo, using JSON-RPC or XML-RPC. Calls that Odoo itself initiates to a payment, delivery, VoIP or bank service are treated as part of the Standard plan. An agency system or carrier-download feed that queries Odoo sits on the Custom plan. Standard is the wrong tier for that integration even though the user price is lower. Hosting on Odoo.sh is extra on top of Custom.

On Dynamics, quotes, orders and invoices are inside the Sales license. Power Automate and Power Apps require additional licenses. A renewal-reminder flow built in Power Automate, or a custom policy app built in Power Apps, is not inside the USD 65 or USD 105 seat. Budget those licenses when the workflow needs them. The pricing page does not state a custom-table cap for Sales Professional, so do not let a bidder invent one. Ask them to show the tables, the flows and the license each flow consumes, on your tenant.

Relationship Sales is a different bundle: Enterprise plus LinkedIn Sales Navigator, variable price, 10-seat minimum. It is a prospecting bundle. It is not an agency management system.

A free starting point exists, with a hard edge. Odoo Online gives one app to unlimited users at USD 0. If that app is CRM, you get the pipeline, activities, quotes and forecasts. Subscriptions and the external API require a paid plan. One agent in a CRM thread said, "I use the free CRM provided by my FMO. I use the CRM from my leads, commission, communication with clients…everything." That can be enough for a single producer whose field marketing organization already stores the book. It is a weak plan for a 20-person agency that must keep its own renewal dates, producer splits and multi-carrier records. HubSpot's insurance page claims a free CRM for leads and workflows. Treat the free tier as pipeline hygiene, then price the paid tier and the agency system beside it.

The same trap shows up in seat mix. A Light User at USD 8.90 is not a producer seat. Seven AgencyZoom users at USD 349 a month do not cover employee number eight. Fifty Dynamics Premium seats at USD 90,000 a year still leave Power Automate, the agency-system license and implementation hours outside the total.

What setup costs beyond the subscription

License math is the smaller argument once policy fields, a book import or an API enter the scope. Odoo publishes the only implementation prices in this set, as Success Packs. Companies under 50 employees usually buy those packs from Odoo. Companies over 50 employees usually use a partner. A 50-person agency is on that line, so ask which path Odoo will sell before you compare quotes.

New-customer prices, with the 15 percent new-customer discount applying to the first pack only, are:

• Starter (Hours: 4 · New customer: USD 493 · Returning customer: USD 580)
• Basic (Hours: 25 · New customer: USD 3,060 · Returning customer: USD 3,600)
• Standard (Hours: 50 · New customer: USD 5,950 · Returning customer: USD 7,000)
• Custom (Hours: 100 · New customer: USD 10,625 · Returning customer: USD 12,500)
• Pro (Hours: 200 · New customer: USD 21,250 · Returning customer: USD 25,000)

A pipeline-only CRM for an agency under 50 employees can land in the 25-hour or 50-hour pack: USD 3,060 or USD 5,950 for a new customer, USD 3,600 or USD 7,000 for a returning customer. That hour count fits stages, activities, a sales script and a first round of training. It does not fit a historical book import, custom policy fields and an agency-system API.

A book-of-business import plus custom policy fields plus an API is at least the 100-hour or 200-hour pack: USD 10,625 or USD 21,250 for a new customer, and USD 12,500 or USD 25,000 for a returning customer. Customizations and developments sit in the larger packs. Extra monthly charges apply for maintenance of extra modules. Above 50 employees, Odoo points you to a partner. Ask each bidder for a rate card, a named team, the hours in phase one, and a separate line for data migration.

AgencyZoom's own onboarding is 2 to 4 weeks, and the product still assumes an agency system underneath. That is a useful comparison for calendar length, not a substitute for the Success Pack when you are configuring Odoo. Dynamics 365 has no public services price on the Sales pricing page. Price the partner statement of work the same way you price the Odoo packs: hours, named people, and what is excluded.

Inside the Flectic Accelerated Delivery Framework, our target for a first usable phase is 8 to 12 weeks. That target is ours for a phase of pipeline, renewal tasks and an agreed set of fields, with carrier download and commission payables left in the agency system. What a 50-user CRM implementation costs walks through a similar seat count for a general sales team. An agency adds the boundary work those generic estimates skip: which fields are copied from the agency system, how often, and who fixes a broken policy number.

For a Dynamics 365 Sales phase, the practical sequence is short.

1. Write the workflows that stay in the agency system: carrier download, rating, ACORD and certificates, commission statements, producer payouts.
2. Write the workflows the CRM will own: lead capture, stages, producer goals, renewal tasks.
3. Decide whether policy number and term are fields the producer can see, or whether every policy question still opens the agency system.
4. If the agency system initiates calls against Odoo, price Custom and leave Standard out. On Dynamics, keep the Sales seat in the comparison. Add Power Automate or Power Apps only when the build is a reminder flow or a custom policy app.
5. Ask every bidder to price data migration, retention setup and training as their own lines. A CRM RFP requirements template is a workable checklist for those lines.
6. Under 50 employees on Odoo, compare the quote with the published pack hours. Over 50 employees, require the partner rate card before you accept a blended implementation figure.

Which records you must keep, and who enforces that

Privacy and retention are part of the CRM decision because the pipeline will hold names, phone numbers, dates of birth and notes about coverage. The rules below are the ones you can cite. They are not a national insurance-file statute.

United States

For a person engaged in providing insurance, Gramm-Leach-Bliley Act privacy and safeguards standards are enforced under state insurance law by the state insurance authority of the state where the person is domiciled, under 15 U.S.C. 6805(a)(6). Section 6805(a)(7) gives the Federal Trade Commission enforcement only for a financial institution not already covered by paragraphs (1) through (6).

The FTC Safeguards Rule, 16 CFR 314.1, applies to financial institutions over which the FTC has jurisdiction under GLBA, meaning institutions not subject to another regulator under section 505. The examples in that section are mortgage lenders, finance companies, tax preparers and similar firms. The section does not list insurance companies or agencies. An independent agency should take its safeguards questions to the insurance department in its domicile state, and should read the carrier and network agreements it has already signed. Do not assume a federal safeguards checklist written for a finance company is the exam your agency will face.

New York is a specific retention rule, and it is a New York rule. 11 NYCRR 243.2 requires an insurer to keep a policy record for six calendar years after the policy is no longer in force, or until the examination report that reviewed it is filed, whichever is longer. The record includes term, rating basis, application, forms, declaration pages, endorsements and the information needed to reconstruct solicitation, rating and underwriting. Claim files have the same six-calendar-year period after the file is closed. The insurer must require, by contract or otherwise, that a person authorized to act for it, including a managing general agent or administrator, keep those records the same way. The insurer remains responsible if that person fails.

If you are an agency appointed by a New York insurer, ask whether your agency agreement already passes that duty to you. If you only write business in other states, do not copy six years onto the CRM retention setting and call it national law. Ask each state where you are licensed what the department expects, and match the CRM deletion job to the strictest duty you have. Store the policy file in the system you told the carrier you would use. A renewal task in the CRM can point at that file. It should not become a second, shorter archive that someone deletes at month 18.

Canada and Quebec

The Office of the Privacy Commissioner of Canada says PIPEDA applies to private-sector organizations that collect, use or disclose personal information in commercial activity. Alberta, British Columbia and Quebec have private-sector laws deemed substantially similar, so activity inside those provinces is generally exempt from PIPEDA. Personal information that crosses a provincial or national border in commercial activity is still subject to PIPEDA.

PIPEDA principle 5 says an organization may keep personal information only as long as needed for the identified purposes, must set retention and destruction procedures, and should set maximum and minimum retention periods that account for legal requirements. The Commissioner's page does not set a fixed number of years for insurance policy files. Do not import New York's six calendar years into a Canadian retention schedule. Write the purposes on the CRM (renewal contact, commission dispute, certificate request) and set the clock from those purposes plus whatever your provincial insurance regulator and your carriers require. Get that period from the regulator and the contract, then configure it.

Quebec goes further for any agency that is an enterprise there. The Act respecting the protection of personal information in the private sector, as updated to 12 August 2026, requires an enterprise to name a person in charge of personal-information protection, to publish governance rules that cover keeping and destruction, and to run a privacy impact assessment before acquiring, developing or overhauling a system that collects, uses, keeps or destroys personal information (sections 3.1, 3.2 and 3.3). Information used to make a decision about a person must be kept at least one year after the decision (section 11). Communicating personal information outside Quebec, or having someone outside Quebec keep it, requires a privacy impact assessment and a written agreement (section 17).

A CRM purchase is the kind of project section 3.3 describes: you are acquiring a system that collects and keeps personal information. Name the privacy officer before go-live, write the destruction rule, and complete the assessment. If the host, the support team or a backup sits outside Quebec, section 17 is a contract workstream, not a footnote. The one-year minimum after a decision is a floor for that decision record. It is not a maximum, and it is not a substitute for the insurance-file period your carriers impose.

How to choose a CRM without a second book of record

Three buying situations follow from that split.

The agency system already holds the policy, and producers need pipeline and renewal tasks. Buy a CRM or a sales extension beside the agency system. AgencyZoom's published plans price that pattern up to 7 users and tell you, in their own words, that they do not replace the agency system. Dynamics 365 Sales or Odoo CRM can do the same job for a larger desk, at the list prices above, as long as download stays in the agency system.

The agency wants one database for prospects and in-force accounts, and it will accept a configured policy object with no carrier download. That is a project: Dynamics 365 Sales on the Enterprise tier when you need the fuller sales product, or Odoo on the Custom plan when an outside system must call the API. Scope it in phases. Phase one is pipeline, renewal tasks and the fields a producer looks up every day. Later phases can add document links back to the agency system. They should not quietly become a second policy admin tool.

The agency needs download, rating, commission payables or ACORD. Stay on an agency management system. Applied Epic, HawkSoft and AgencyBloc are built for that job and do not publish a list price, so compare a written quote against your lines of business. A CRM still helps the producers. It does not become the book of record.

Whichever path you are on, the buying tests are named people, hours, references, a phase plan and who owns the configuration when the project ends. Partner badges do not answer those tests. Ask for two agencies of similar headcount, the hours they used, and whether the bidder's staff or your staff can change a field after go-live.

Bring the fit-check answers, your user count and the name of the current agency system. We will tell you which of the three paths matches the book you have, which seats you can skip, and what a first phase should cost before you sign a license for every employee in the building.

How Flectic can help

At Flectic, we set up Dynamics 365 Sales for sales teams of 20 to 100 people in the US and Canada, with lead routing, stage rules and a forecast rolled up from the pipeline. A fixed-price first phase delivers a working pipeline before you commit the full budget. See the Dynamics 365 Sales implementation for the full list of what the first build covers. The next step is to book a free discovery call with Flectic.

Sources

Dynamics 365 Sales pricing (United States), Microsoft, October 2026

Dynamics 365 Sales pricing (Canada), Microsoft, October 2026

Odoo Pricing, Odoo, October 2026

Odoo CRM, Odoo, October 2026

Odoo Success Packs, Odoo, October 2026

CRM Software for Insurance Vs. AMS, EZLynx, March 2026

Applied Epic, Applied Systems, October 2026

AgencyZoom pricing, AgencyZoom (Vertafore), October 2026

AgencyBloc pricing, AgencyBloc, October 2026

What is Insurance CRM?, Salesforce, July 2026

Financial Services Cloud pricing, Salesforce, October 2026

Full Guide to CRM Software for Insurance Agents, Creatio, January 2026

Insurance CRM Software, Zoho, October 2026

CRM for Insurance Agents and Agencies, HubSpot, October 2026

How much do other insurance agencies pay for their CRM software?, Reddit, April 2024

Best CRM to use for an insurance brokerage?, Reddit, October 2026

CRM for insurance agents, Reddit, October 2026

15 U.S.C. 6805, Cornell Law Institute, U.S. Code, October 2026

16 CFR 314.1, Cornell Law Institute, eCFR text, October 2026

11 NYCRR 243.2, Cornell Law Institute, New York codes, October 2026

PIPEDA in brief, Office of the Privacy Commissioner of Canada, October 2026

PIPEDA principle 5, Office of the Privacy Commissioner of Canada, October 2026

Act respecting the protection of personal information in the private sector, LégisQuébec, August 2026