Here is the number that should bother every agency owner reading this: your AMS probably holds eight to twelve years of policy history, renewal cycles, lost accounts, and client interactions, and the reporting tools built into that system require hours of manual work to surface anything useful from it.
That is not a data problem. It is an access problem. And it turns out the insurance industry has been quietly building the infrastructure to fix it.
What Industry Professionals Are Actually Saying
Before getting into the solutions, it is worth spending a minute on the actual complaints, because they are strikingly consistent across platforms.
On Reddit’s r/InsuranceProfessional, Applied Epic users describe the system as requiring “an excessive number of clicks” and compare the workflow to “data clicking button after button, next, next, next.” A separate thread on r/InsuranceAgent echoes the same frustration, with users noting there is “no way to modify a policy without creating a service summary transaction” and that copying basic details like policy numbers or carrier info from the policy screen requires extra manual steps.
G2 and Capterra reviewers land in the same place. The phrases that come up repeatedly are “poor reporting,” “complex report-building,” and a steep learning curve for anything beyond basic data entry. One Capterra reviewer noted that attachment sorting and search felt worse in Epic than in older systems they had used.
For AMS360 and HawkSoft, the community research shows the same operational clusters even if the platform-specific quotes are less abundant: speed, clicks, workflow rigidity, reporting friction, document handling, and integrations are the consistent pain points across all three platforms.
The sharpest summary comes from a Reddit user who switched from Applied TAM to Epic and said policies that do not download through IVANS create “a TON of manual entry” and made them feel like they had “doubled my work for 0 reason.”
This is the context in which every AI-and-AMS conversation is happening. The frustration is not hypothetical.
The Core Problem: A Data Graveyard With a Login Screen
The issue is structural, not cosmetic. Agency management systems were built to store and process transactions. They are very good at that. What they were not built to do is surface patterns across thousands of records, flag accounts that are drifting toward non-renewal, or tell you which clients are underinsured relative to peers in the same industry segment.
That requires a different layer entirely.
Applied Systems has been public about its own framing of this problem, stating that the most effective AI is embedded in the tools agents already use and trained on insurance-specific data. Their examples include email summarization, account summarization before renewals, cross-sell gap detection, commercial risk enrichment, and an AutoFill feature that reads carrier plan documents and populates fields directly in Epic, cutting manual re-entry.
Vertafore’s RiskMatch takes a similar approach from a data aggregation angle. It pulls data from multiple AMS platforms, normalizes it, applies machine learning, and delivers dashboards and automated email reports covering business intelligence, churn risk, commission benchmarking, and cross-sell identification. That is an analytics layer sitting on top of AMS data, not a replacement for the AMS itself.
The pattern is the same whether you look at Applied, Vertafore, Ennabl, or any of the newer entrants. The AMS stays. The AI connects to it, reads the data, and writes useful outputs back.
By the Numbers: What AI Is Actually Doing in Insurance Agencies Today
Here is a summary of the active use cases based on current industry deployments:
| Use Case | What AI Does | Where It Sits |
|---|---|---|
| Document processing | Extracts policy data from carrier docs and ACORD forms | Inside AMS workflow |
| Renewal analytics | Flags at-risk accounts and renewal readiness signals | Embedded in or connected to AMS |
| Account intelligence | Summarizes account history and identifies cross-sell gaps | AMS or analytics layer |
| Revenue analytics | Benchmarks commissions and exposes churn risk | Multi-AMS data platform |
| Service automation | Drafts emails and handles routine service requests | Embedded assistant |
| Workflow orchestration | Pulls from AMS, enriches data, and writes updates back | API-connected AI layer |
Each of these operates as an execution layer that connects to the AMS through APIs rather than replacing the system of record. That distinction matters a great deal to agency owners who have spent years configuring their current platform.
Strategy 1: Stop Treating Document Entry as a Human Task
The most immediate ROI in insurance AI is usually document processing. ACORD forms, loss run summaries, carrier plan documents, certificates of insurance. These are structured data problems wrapped in PDFs and email attachments, and every hour a producer or CSR spends retyping that information is an hour they are not spending on clients.
Applied Systems’ AutoFill is a working example of this at scale. It reads carrier plan documents and populates the relevant fields in Applied Epic directly, reducing the manual re-entry cycle that multiple users on Reddit and Capterra flagged as one of their biggest workflow drains.
For agencies not running Applied or not yet on a platform with embedded AI, API-connected tools can perform the same function. The workflow looks like this: an email arrives with a carrier document attached, the AI reads the attachment, extracts the structured fields, and posts the data back into the AMS record. The account manager reviews and confirms rather than types.
HawkSoft has published guidance on this approach directly, describing how agencies can scale by layering AI on top of their AMS rather than waiting for the AMS to build every feature natively. The framing is explicit: the AMS is the system of record, and AI is the execution layer on top of it.
If you want to understand where your agency stands on this, the AI Readiness Scorecard at RunFrame walks through the specific workflow bottlenecks that AI can address first based on your current stack.
Strategy 2: Automate the Reports Nobody Has Time to Build
One of the consistent complaints in G2 and Capterra reviews of Applied Epic is that report-building is complex and time-consuming. This is not unique to Epic. It is a structural reality of systems designed to store data rather than present it.
The fix is not to rebuild the reporting module. The fix is to define the ten to fifteen reports that actually drive decisions in your agency, build them once with AI-connected tooling, and automate their delivery on a schedule.
Vertafore’s RiskMatch is a public example of this at the enterprise level, using machine learning to deliver dashboards and automated email reports on retention risk and commission performance across an agency’s full book. For smaller agencies, similar outputs can be generated by connecting an AI analytics layer to the AMS via API and scheduling report delivery without requiring anyone to log in and run queries.
The metrics that matter most for most agencies are retention rate by line and segment, premium per account trend, accounts approaching renewal with no documented activity, and new business source attribution. Most AMS platforms hold all of this data. They just do not surface it automatically.
RunFrame’s AI Operating System connects to existing AMS platforms and builds automated report delivery for exactly these metrics, without requiring a new system or manual query work from your team.
Strategy 3: Build a Live View of Retention Risk and Growth Opportunities
This is where the data value gets largest, and also where agencies are furthest behind.
Most agency owners can tell you their overall retention rate. Very few can tell you which specific accounts are most likely to leave in the next ninety days, which clients are underinsured relative to their industry peers, or which existing accounts represent the highest probability cross-sell opportunity based on current coverage gaps.
That information exists in your AMS. It is buried in ten years of renewal history, loss activity, coverage changes, and service interactions. What it needs is a model that can read across all of those records simultaneously and surface the signals.
This is precisely what analytics platforms like Ennabl are designed to do. Ennabl positions its workflows as a way to leverage data trapped in AMS and CRM systems, unifying and enriching it across platforms so agencies can act on it. Applied Systems describes the same capability in their AI roadmap: cross-sell gap detection and account summarization before renewals, running from data already in Epic.
For agencies not yet using an embedded analytics product, the starting point is usually a clean data export from the AMS, a normalization process that standardizes account and policy records, and a scoring model that flags accounts by retention risk and growth potential. That output feeds back into whatever tool your producers and account managers already use, whether that is a dashboard, a daily email, or an alert in the AMS itself.
The Insurance Agencies page at RunFrame has more detail on how this specific workflow is configured for agencies running Epic, AMS360, and HawkSoft.
Implementation Roadmap: From Data Graveyard to Operating Asset
Most agencies that successfully deploy AI on top of their AMS follow a similar sequence. Skipping steps tends to produce pilots that never scale.
Step 1: Audit your data quality before you build anything. AI models are only as useful as the data they run on. If your AMS has inconsistent account naming, missing SIC codes, or incomplete renewal history, those gaps will show up in your outputs. A data quality audit takes a few days and tells you exactly what you are working with.
Step 2: Pick one use case with a measurable baseline. The fastest path to demonstrable ROI is a single use case where you can measure before and after. Document extraction time, renewal report turnaround, or retention rate on flagged accounts are all clean baselines.
Step 3: Connect via API, not export. Agencies that run AI on manual data exports create a maintenance problem immediately. The data is stale the moment it lands. API connections to your AMS keep the AI layer current and write results back into the system of record automatically.
Step 4: Define the outputs your team will actually use. An AI system that produces outputs nobody looks at solves nothing. Before you deploy, decide exactly which role gets which alert, on which schedule, in which format. Account managers need different outputs than producers, and producers need different outputs than agency principals.
Step 5: Plan for ongoing management. AI deployments are not install-and-forget. Models need to be monitored, outputs need to be validated, and workflows need to adjust as your book and your team change. Fractional AI Ops from RunFrame covers this ongoing management layer for agencies that do not want to hire a dedicated internal resource.
How RunFrame Approaches This
RunFrame connects to your existing AMS via API and layers AI on top of the data already there. The approach does not require switching platforms, running parallel systems, or rebuilding workflows that your team has spent years learning.
The typical starting point for an insurance agency is a combination of automated reporting (so principals get the ten metrics that matter without anyone building reports manually) and retention risk scoring (so account managers see which renewals need attention before they become lost accounts).
From there, document processing automation and cross-sell identification are natural expansions once the data foundation is solid.
If you want to see where your agency stands before committing to anything, the AI Readiness Scorecard takes about four minutes and tells you which use cases are ready to deploy now versus which ones need groundwork first.
Alternatively, if you would rather walk through your specific AMS setup and book of business, you can book a discovery call and get a scoped recommendation based on what you are actually running.
Your AMS is not the problem. The data is there. What has been missing is a layer that reads it, interprets it, and puts the right information in front of the right person at the right time. That layer exists now, and it does not require starting over.
