AgencyBloc vs BenefitPoint for Benefits Teams 2026

Key Takeaways

• AgencyBloc still sells a health, senior, and benefits system. The management product in that suite is now named AMS+. BenefitPoint still sells under that name, inside Vertafore's AgencyOne. It was not shut down or renamed.

• Neither vendor prints a license price on the pages checked for this guide. Treat both as quote-based until a written quote names users, package, and what sits outside the first signature.

• The split that matters is the book. AMS+ publishes Medicare paperwork, individual records, and a commissions package beside the CRM. BenefitPoint publishes group-plan setup, renewal tracking, and revenue matching, and it names AMS360 and Sagitta as neighbors.

• Review scores are not one sample. The head-to-head review page shows a higher ease profile for AMS+ on a smaller, mostly small-business set of reviews, and a larger review set for BenefitPoint.

• A plan PDF still needs a person. Vertafore's own release says a user reviews and approves the extracted plan before it is final. A file move in Zapier, Make, or n8n does not remove that check.

• Pick the record that wins when a group, a plan, and a commission figure disagree, and get that rule in writing before anyone imports a book.

Start with the book, not the logo

An employee-benefits operations lead is choosing the record the service team will trust when an employer asks what renewed, what changed, and what the agency expects to be paid. An agency management system, for this job, is that shared record of employers, members, plans, renewals, documents, and commissions.

TL;DR: choose AgencyBloc AMS+ when the book is individual health, Medicare, or senior business with group cases beside it, and choose BenefitPoint when the book is employer benefits inside a brokerage that already runs, or plans to run, the Vertafore stack. Both license prices are quote-based.

BenefitPoint was not renamed and was not discontinued. Vertafore bought the company from Trident Capital on September 12, 2006, and Mergr's buyer note says more than 20,000 agencies and 1,000 carriers rely on Vertafore, according to Mergr (2006). The product page still sells BenefitPoint as the benefits system and places it inside AgencyOne, next to AMS360 and Sagitta. A property-and-casualty management system is a pairing question, which is why how AMS360 compares with AgencyBloc and how Applied Epic compares with AgencyBloc are separate decisions from this one.

AgencyBloc did change the name a buyer will see on the management-system line. The company still operates under its own name. Its history page describes the fuller system as AMS+, inside a Plus Suite that also holds commissions, quoting, and marketing tools. That is packaging, not a shutdown. Shops that need a different health-agency system, rather than this head-to-head, can start from other AgencyBloc options for insurance agencies.

The category choice comes before the feature grid. A Monday file that is employer renewals, plan documents, and carrier statements needs a system that is serious about plans and revenue. A Monday file that is a Medicare scope form, an ACA consent, an individual policy, and a downline commission needs a system that stores those objects. Many agencies do some of both. The expensive miss is buying the group system for a Medicare desk, or the Medicare suite for a regional benefits practice that already lives in AMS360.

Group shape belongs in that same first pass. A single employer, a chamber plan, and an association arrangement do not produce the same census. If association business is in the book, settle the term before you map fields, using what an employer association health plan is. Neither product page is a legal opinion on those plans. The operations question is whether the record can tell an association case from a single-employer case without a side spreadsheet.

Who this is for

This comparison is for the person who owns the service calendar at an employee-benefits agency: the operations lead, the benefits manager, or the principal who still runs renewals. You are close to a choice. You want to know which system holds the book, what stays manual, and what a public page will not tell you about price.

It is also for a mixed health shop that sells individual and senior products and is being pushed toward a pure group system, and for a benefits team being pushed toward a health CRM. Those are different operating jobs. The pages below are the public evidence for splitting them.

Red flags: you run personal lines only and have no group, individual-health, or senior book to put in either system; you need the carrier's own portal and hope one of these products replaces the carrier; you will not sign without a public multi-year price list, because neither vendor publishes one.

Before the first demo, write five lines: the book that must be the system of record, the book that may stay in a neighbor tool, who reconciles carrier money, who may mark a renewal complete, and which of those steps each vendor includes in the quote.

How we evaluated these tools

The weights follow the week an operations lead actually has, not a feature bingo card. Book structure is 25% because the wrong object model becomes a second database inside a quarter. Carrier revenue and producer pay are 20% because a missed statement is the loss a principal will fund a project to stop. Renewal calendar and plan changes are 20% because that is the week the team runs out of hours. Medicare forms and ACA paperwork are 15% because they dominate some agencies in this search and barely touch others, so they can swing the choice without being allowed to hide a weak group record. Handoff to the rest of the stack is 10% because exports and permissions decide whether a second tool helps. A dollar price you can read before a call is 10% because it is a real buying test, and on these two public pages it does not separate the vendors.

The demo-check column is our question count, not a score the vendors earned. Book structure gets 4 questions: group, individual, carrier, and policy status. Revenue gets 3: expected amount, received amount, and producer split. Renewals get 3: date, plan change, and the document that proves it. Medicare and ACA paperwork gets 3: scope of appointment, consent, and attestation. Handoff gets 2: an export you can actually download, and the permission required to write back. Price clarity gets 1: whether a dollar amount is on the public page.

The weights sum to 100%. A strong ease score can still fail the book-structure questions. Review-site dollars are left out of this weighting on purpose. Any seat price that does not appear on the vendor's own pricing page is not used below. Reviewer math is reported later as reviewer math, separate from these weights.

Who owns each product, and what the name means now

AgencyBloc's history page says the firm was founded in 2008, reports a Customer count: 6,500+ agencies, cites an average 25% client-growth rate across four years before Resurgens Technology Partners invested in September 2021, says it acquired FormFire in July 2022 and then shaped the management system now called AMS+, reports 7.7 million workflow events and 106 million Commissions+ entries supported in 2024, names Mike Lamb as CEO from September 2025, and notes a March 2026 Cloud CRM award for AMS+, according to AgencyBloc (2026). Those are the company's figures, not an outside census. They show a product that is still being packaged and shipped.

Our read of that packaging: AMS+ is the core record, and commissions, quoting, and marketing sit as sibling products. A demo that stays inside the CRM can leave the commissions quote unsigned. Ask for one proposal that states which siblings are in the first contract and which start later.

BenefitPoint's owner is Vertafore, as the 2006 acquisition established, and the product is still on sale. The operational difference from AMS+ shows up in the work the two public pages choose to describe, which is the next section, not in a discontinued-product footnote.

The desk work, side by side

On July 27, 2026, Vertafore described a plan-setup assistant inside the BenefitPoint module of AgencyOne. That release says setup time falls by a Setup time cut: up to 70%, states 90% accuracy, says the user reviews and approves the result before the plan is final, and says BenefitPoint is trusted by 10 of the top 15 benefits brokerages and supports more than 4 million employee benefit plans, according to Vertafore (2026). The assistant is current. It does not remove the reviewer. If your standard is a plan that files itself with nobody looking, this release does not say that.

AgencyBloc's pricing comparison lists a health, senior, and benefits CRM; electronic scope of appointment, ACA consent, and ACA attestations; an appointment scheduler; Rx Collect; lead and texting tools; and quoting connections that include Connecture, Ease, Employee Navigator, Lead Advantage Pro, SunFire, and HealthSherpa for Medicare. Commissions+ is listed for carrier import, rate tables, advances, overrides, agent statements, and missed-commission identification. Quote+ is listed for medically underwritten, community-rated, and ancillary quotes, proposals, and enrollment forms. BenefitPoint's product page centers renewals, plan data, revenue visibility, and connections to AMS360, Sagitta, and RiskMatch. It does not lead with Medicare scope forms. The dollar and package facts for those rows are in the pricing section, on the pages just cited for each vendor's own claims.

Pricing checked against the public pages

Pricing checked October 10, 2026.

AgencyBloc's pricing page publishes three AMS+ columns and marks automated servicing workflows as Basic on one column and Premium on the other two, with no dollar license fee on Grow, Accelerate, Elevate, Commissions+, or Quote+, and it prices Commissions+ from transaction volume and Quote+ from the volume of groups quoted, while websites are an additional cost with no dollar shown, according to AgencyBloc (2026). BenefitPoint's product page offers a sales conversation and does not publish plan names or dollar amounts. Both are quote-based. A three-year total cannot be computed here, because there is no public seat price, minimum, or discount to multiply.

G2's BenefitPoint review summary adds timing that is easy to misuse as a price. It lists a Payback report: 5 months and a time to implement of 1 month, according to G2 (2026). Those are averages from reviewer answers, not a Vertafore project plan and not a dollar return. The head-to-head page used below does not print a matched AgencyBloc implementation month, so this guide does not supply one. Ask both vendors for a written go-live range that names data conversion, and keep that range off the license line.

Our read on cost is about the quote inputs. For AgencyBloc, ask how many users, which of the three AMS+ columns, whether Commissions+ volume and Quote+ group volume share the first signature, and what the website add-on costs. For BenefitPoint, ask whether the plan assistant, AgencyOne, AMS360, or Sagitta is required, included, or quoted separately. Until those answers are in writing, the honest total is quote-based on both sides.

What the review scores can and cannot prove

G2's head-to-head page lists an AgencyBloc rating: 4.7 of 5 from 41 reviews and a BenefitPoint rating of 4.2 of 5 from 101 reviews. Small-business reviewers are 92.5% of the AgencyBloc reviews and 37.6% of the BenefitPoint reviews. Reading AgencyBloc first, meets-requirements, ease of use, ease of setup, ease of admin, and quality of support are 9.0 versus 8.2, 9.3 versus 8.1, 9.1 versus 8.1, 9.3 versus 8.6, and 9.0 versus 8.6, according to G2 (2026).

Capterra's AgencyBloc page, updated September 28, 2026, also shows 4.7 from a wider set of 129 reviews, according to Capterra (2026). That second 4.7 does not change the G2 count of 41, and that Capterra page is not a matched BenefitPoint sample. Our read: AMS+ looks easier inside a review pool that is overwhelmingly small-business. BenefitPoint's ease scores sit on a larger pool that is not mostly small firms. Watch a new processor complete one renewal in each demo. Read 4.7 and 4.2 beside the 92.5% and 37.6% shares, because the reviewers are not the same mix of agencies.

Which operations lead should choose which system

Choose AgencyBloc AMS+ when the book that pays the payroll is individual health, Medicare, or senior business, even if group cases sit beside it. The public package list is built for that mix: scope forms, ACA consent and attestations, Rx Collect, Medicare quoting links, and a commissions product that talks about agent statements and missed carrier money. Best fit is a health-agency operations lead who wants one vendor family for the client record, the producer pay run, and small-group proposals. Primary evidence is the history page and the pricing page linked above.

The limits are the other side of that fit. Dollar prices are unpublished. Commissions and quoting are separate package rows, so a CRM-only quote can understate the operation. A regional benefits brokerage already on AMS360 is not the shop this packaging describes. If nobody sends a scope of appointment or works a turning-65 list, the Medicare rows are a weak reason to switch. A standard go-live length is not printed on the pages checked here, so the quote has to name who converts the book and who signs the first commission run.

Choose BenefitPoint when the book is employer benefits and the pain is plan setup, renewals, and carrier revenue, especially if AMS360 or Sagitta is already the agency system. Best fit is a benefits operations lead who wants the benefits record beside the Vertafore management system rather than a second CRM for individual policies. Primary evidence is the product page and the July 27, 2026 release linked in this guide. Vertafore describes the product as the benefits layer.

The limits follow that scope. The product page does not lead with individual Medicare administration, so a senior-market shop should not assume scope forms and prescription-data collection are included. License price and package names are unpublished. The reviewer-reported 1 month to implement and 5 months to payback are G2 averages, and a messy conversion does not inherit them. The plan assistant still requires a person to approve the plan. The 80% of largest brokerages figure cited with the product page below, and the 10 of the top 15 on the July release, are two different vendor statements about large firms. They are not one market-share number.

A mixed agency should name a winner before it buys both. The split that usually survives contact with a real book is BenefitPoint, or the incumbent benefits system, for employer groups, and AMS+ for individual and senior records, with one of them declared the commission system of record. Two renewal dates for the same client is what "use whichever" produces. If the group book is the only book, AMS+ is extra. If the individual book is the only book, BenefitPoint is extra.

A renewal week, with the arithmetic shown

Vertafore's product page says AI mapping saves Time saved per plan: 45 minutes, and the same page lists 2.4 million active accounts, 70,000+ brokers and independent agents, 3.25 million current plans, and an FAQ statement that 80% of the largest benefits brokerages rely on BenefitPoint, according to Vertafore (2026). The 3.25 million current-plan figure and the more-than-4-million supported-plan figure are different published measures. The 80% claim and the 10-of-15 claim are different vendor statements. Keep each pair separate.

Here is an illustration, not a measured agency result, for a desk that renews 15 employer groups and touches 4 plans on each, which is 60 plans. Using the published 45 minutes per plan, 60 times 45 equals 2,700 minutes, or 45 hours, of mapping time the product-page claim would take off typing. The separate up-to-70% setup claim is a different statement, so it is not stacked on the 45 minutes. The release's 90% accuracy claim is why the remaining work is review: checking 1 plan in every 5 is 12 plans out of 60. If the approved PDF also has to land on an AgencyBloc group, the notes call can carry that file in attachment_note_1_file_url_1 against the group's entity_id, and the renewal is not done until a person confirms the note. The 15 groups and 4 plans are this illustration's inputs. The 45 minutes, the up-to-70% ceiling, and the 90% accuracy claim are the published figures.

Put the 45 hours into the project request as a question. Ask Vertafore which documents qualify for the 45-minute mapping claim, and who corrects the 12 plans in a one-in-five sample. If AMS+ is the record, ask what a person still types after the file is attached. The hour count is only as good as the document types in your own renewal pile.

The handoff after the system is chosen

The system of record does not collect the carrier PDF by itself. A proposed workflow from US Tech Automations starts when that PDF hits a watched mailbox. The flow matches the employer name to the group already stored, and the output is a review task that holds the file, the plan year it thinks it found, and the commission basis a person must confirm. Nothing is written into AMS+ or BenefitPoint until that person marks the task checked. Prerequisites are a forward or export of the carrier file and a named reviewer. This is a configurable design. It is not a claim that an agency is running it, and it is not a measured time saving.

After approval, the configurable US Tech Automations flow can file the document. On an AgencyBloc record the prerequisites are an API SID and key from AgencyBloc and the group id the match already resolved. The write targets that group and the approved file, and a second look confirms the note came back before anyone calls the renewal complete. On a BenefitPoint record the prerequisite is the export or service access Vertafore has enabled for that firm, and the review point is the plan itself before it is final. If either permission is missing, the flow stops at the task list.

Zapier, Make, and n8n can support this pattern when someone configures them. They can keep a run history, retry a failed step, branch on an error, and store audit evidence. The buyer has to design and own observability, idempotency, escalation, access controls, and the upkeep when a carrier changes the file layout. A proposed US Tech Automations design can set the group match, the hold for human review, and the single write that follows approval, with those same prerequisites and with the exception path assigned to a person. The connector tools are the right choice when the agency has staff who will own that design and the volume is one file type the team already understands.

When NOT to use US Tech Automations

Stay inside BenefitPoint or AMS+ when the renewal checklist, the commission match, and the document already live in that product and the only request is a saved view. Stay with one Zapier, Make, or n8n scenario when a single spreadsheet leaves a single mailbox and a person checks every row. Skip an added orchestration layer when the firm has no API or export permission and no one is assigned to review exceptions.

Mistakes that show up in the second demo

• Treating BenefitPoint as the Medicare CRM because both products sit near benefits work. Its published story is employer plans, renewals, and revenue.

• Treating AMS+ as a module of AMS360. AgencyBloc is a separate company. Pairing the two is a project, not a login setting.

• Reading the 4.7 and the 4.2 without the 92.5% and 37.6% small-business shares. Those shares describe who wrote the reviews.

• Carrying a review-site dollar into the budget. The vendor pages checked on October 10, 2026 do not print one. The contract number is quote-based.

• Stacking the 45 minutes per plan on the up-to-70% setup claim. They are two vendor statements with different wording.

• Letting an extracted plan become final with no reviewer. The same release that states 90% accuracy says a person approves the plan.

• Buying both systems without naming which date wins when a group renewal and an individual policy disagree.

Terms that change the contract

• AMS. The agency's system of record for clients, policies, and the work around them. AMS+ is AgencyBloc's current name for that system.

• System of record. The database the team trusts when two screens disagree. Name it before you connect anything else.

• Group. An employer or other organization case, as distinct from an individual policy. Association business can look like a group and still follow different rules.

• Scope of appointment. The Medicare permission step AgencyBloc lists as an electronic form. A group-benefits page does not, by itself, prove the form is stored.

• Revenue reconciliation. Matching expected pay to the carrier statement. BenefitPoint's product page describes this tracking. Commissions+ describes missed-commission identification.

• Quote-based. No public dollar amount. The price exists only in a vendor proposal.

• AgencyOne. Vertafore's name for the platform that holds BenefitPoint beside its other agency products.

• Human approval. The step the BenefitPoint release still requires, and the step any serious file-to-record flow should require, before a plan or a note is final.

Questions to settle before you sign

Is BenefitPoint discontinued or renamed?

No. It still sells as BenefitPoint, and the July 27, 2026 release describes it as a module of AgencyOne. Vertafore has owned it since the September 12, 2006 acquisition.

Is the AgencyBloc in this search a retired brand?

No. The company is still AgencyBloc. The management system in the current packaging is AMS+, with Commissions+ and Quote+ listed as companion products.

Do either vendors publish a license price?

No. Both the AgencyBloc package page and the BenefitPoint product page checked for this guide are quote-based, so a comparison that prints a seat price is not using those pages.

Which system fits a Medicare-heavy book?

AgencyBloc AMS+. The public package comparison lists senior and individual health workflows, electronic Medicare and ACA forms, Rx Collect, and Medicare quoting connections. BenefitPoint's product page does not lead with that work.

Which system fits a group desk already on AMS360?

BenefitPoint. Vertafore presents it as the benefits record that connects with AMS360 and Sagitta. Adding AMS+ in that building means a second record unless individual business is deliberately split out.

What should we do with the one-month implementation figure?

Treat the 1 month to implement, and the 5 months to payback beside it, as G2 reviewer averages for BenefitPoint. Ask Vertafore whether your conversion looks like the reviews behind those averages before either number becomes a deadline.

When is a connector tool enough on its own?

When one known file moves from one mailbox to one system you already own, retries and an error branch are configured, and a person checks every row. Several carriers, two records, and an approval step are a larger design than a single scenario.

Take this into the renewal meeting

Pick the system that matches the book you will renew next quarter, demand a written quote that names packages and neighbor products, and keep a person on the plan before it is final. The license comparison stays quote-based on both sides until those quotes arrive. For the file-to-record handoff around that choice, see how US Tech Automations configures this.