Guidewire vs Applied Epic: Carrier or Agency, 2026
Key Takeaways
Guidewire is a property-and-casualty core for the company that holds the risk. Applied Epic is an agency management system for the company that holds the client relationship.
They are not substitutes. A carrier shopping for policy, billing, and claims is in a different purchase from an agency shopping for clients, commissions, and service work.
The real overlap is an MGA or a firm that both places business and administers it. That firm may need one of these products, or both, for different records.
Neither vendor publishes a license fee on the pages reviewed for this guide. Treat both as quote-based and compare scope, not a sticker price.
Applied TAM is the older agency system, not a former name for Applied Epic. Applied's US migration hub points those agencies to Applied Epic or EZLynx.
A handoff between a carrier claim file and an agency client file is a third decision. It is not solved by picking a single logo.
Guidewire and Applied Epic keep different records
Guidewire is the core-system family a property-and-casualty insurer uses to quote, issue, bill, and pay claims, and Applied Epic is the agency management system an independent agency or brokerage uses to run clients, policies, accounting, and daily service. The short version is this: buy Guidewire when your firm must keep the policy, billing, and claim record, and buy Applied Epic when your firm must keep the client and the commission ledger. Buying one as a stand-in for the other leaves the job you actually have undone.
The search pairs them because both names show up in insurance software short lists. The buyers do not. A technology lead at a carrier is choosing how the company records risk it has taken. An operations lead at an agency is choosing how the firm records customers it serves and money it must split with carriers. An MGA sits between those jobs. Guidewire's own core-products page describes InsuranceNow as an end-to-end platform for regional and super-regional insurers and MGAs, while InsuranceSuite is the core it aims at mid-sized and large insurers. An MGA that binds, rates, and administers policies is closer to that core decision. An MGA or wholesale broker that only places business with carriers is closer to an agency desk. Some groups do both and will end up with two systems of record, plus a controlled handoff between them.
Applied Epic has not been renamed or withdrawn on the US pages reviewed here. Applied TAM is a separate, older agency management system. Applied tells US agencies that TAM's architecture will soon no longer receive Microsoft support, and it names Applied Epic and EZLynx as the two go-forward management systems. The same hub says TAM agencies migrated: 157 in the prior year and states a Claimed setup time: 6-8 weeks to get set up in a new system, according to Applied Systems (2026). That is Applied's published migration claim, not a promise that every Epic project finishes on that calendar, and it is not a statement that TAM already has a US sunset date.
The channel these agency buyers operate in is large and still a distribution business, not a carrier balance sheet. The 2026 Agency Universe Study estimates Independent agencies: 37,000 and Average staff: 9.9 people, up from 8.2 in 2024, and it puts the share reporting a revenue decline at 8%, down from 12%, according to IIAT (2026). Those firms are the natural Applied Epic audience. They are not, by those facts, a natural audience for a carrier policy-administration core.
Who this is for
This comparison is for a technology or operations lead at an insurance agency, an MGA, or a small carrier who has both names on a short list and needs to know which purchase is real. It is also for the person who inherited a "pick an insurance system" task without being told whether the firm owes claims or owes commission statements.
Use this sequence before you sit through product tours. Name the legal entity that pays the claim. Name the legal entity that produces the commission statement. If those names differ, you are shopping for two records or for a handoff, not for one logo. If they are the same carrier, start with Guidewire's InsuranceSuite or InsuranceNow, not with an agency desk. If they are the same agency, start with Applied Epic or another agency management system, not with PolicyCenter. If you are leaving Applied TAM, stay inside the agency-system decision and read the TAM-to-Epic migration guide before anyone proposes a carrier core.
Red flags: you want one database to be both the statutory policy record and the agency commission ledger; you will not continue the purchase without a public sticker price; you only need a comparative rater, a client portal, or a submissions form and do not need a system of record.
How we evaluated Guidewire and Applied Epic
We weighted six questions a buyer can answer from public pages, then we refused to score either vendor on a star scale we did not measure. The weights sum to 100 points. They favor the record each product keeps, because a feature list cannot repair a wrong system of record. Line fit, money movement, implementation load, and the integration path share the rest. Public evidence beats anonymous price talk. Where a vendor does not publish a fee, the cell says quote-based.
| Criterion | Weight | Points of 100 | Rationale |
|---|---|---|---|
| System-of-record match | 25% | 25 | The wrong record makes later features irrelevant |
| Buyer type | 20% | 20 | Carriers, MGAs, and agencies are different firms |
| Line coverage | 15% | 15 | Personal, commercial, and benefits are not all in every product |
| Money movement | 15% | 15 | Carrier billing and agency trust accounting are different jobs |
| Implementation load | 15% | 15 | Public pages describe delivery models, not one shared timeline |
| Integration path | 10% | 10 | Both describe APIs, and neither replaces the other's database |
Our reading of those weights is separate from the vendor claims below. A 25-point weight on the record means we would rather see a plain fit on policy administration than a long list of screens. A 10-point weight on integration means an API matters after the record is right, not before. Nothing in the table is a customer ranking, a test result, or a market-share award.
The record each product actually keeps
Guidewire InsuranceSuite, on the vendor's core-products page, brings together PolicyCenter, ClaimCenter, and BillingCenter through Guidewire Cloud for the full insurance lifecycle, and that page also lists PricingCenter and UnderwritingCenter. PolicyCenter is described as the path from quote to renewal. ClaimCenter is described as first notice of loss through settlement. BillingCenter is described as direct, agency, installment, and usage-based billing. InsuranceNow is the other core on that page, aimed at regional and super-regional insurers and MGAs, marked US only, single-currency, and English only, with a more modest IT expectation. Guidewire reports Insurers on Guidewire: 540+ in 40 countries and Implementations: 1,600+, and it places InsuranceSuite at a direct written premium typically of $300 million and above, while noting customers below $100 million, and InsuranceNow typically at $300 million and below, while noting customers above $1 billion, according to Guidewire (2026). Those premium bands describe the carrier's book, not a software fee.
Applied Epic, on its product page, is an agency management system for prospecting, pipeline, market access, personal and commercial quoting, accounting, digital payments, reporting, and policy management, with P&C and benefits in one platform. Epic Benefits is described as capturing plan information, rates, coverages, eligibility, stop-loss, and TPA data. The page also describes an API, granular security, and browser access. That is a distributor's desk. It is not a carrier rating engine, a claim reserve system, or a statutory policy admin core.
| Decision | Guidewire | Applied Epic |
|---|---|---|
| Primary buyer | P&C insurer; InsuranceNow also names US MGAs and regional insurers | Independent agency or brokerage |
| Record it keeps | Policy, claim, and billing for the risk bearer | Client, policy, accounting, and pipeline for the distributor |
| Named applications | PolicyCenter, ClaimCenter, BillingCenter, plus PricingCenter and UnderwritingCenter | One AMS from prospecting through accounting, with benefits workflows |
| Benefits desk | Not described as an agency benefits system | Epic Benefits for plans, rates, eligibility, stop-loss, and TPA data |
| Money job | Direct, agency, installment, and usage-based billing | Agency accounting and digital payments |
| Delivery note | InsuranceSuite through Guidewire Cloud; InsuranceNow marked US only | Browser-based cloud AMS on the product page |
| Public license fee | Quote-based | Quote-based |
| Integration claim | Cloud API and a marketplace of connections | API, data lake, and insurer connectivity from the AMS |
The rows above are public product facts. Our reading is narrower: if the row you care about is "record it keeps," stop and match it to your firm before you compare screens. A proposed workflow from US Tech Automations sits above those two records and does not replace either one. Trigger: the carrier exposes a new or updated claim, either through a Guidewire Cloud API search or as a scheduled file. Action: match policy number to the agency client and flag any miss. Output: a review queue a person accepts or rejects before the agency system is written. Prerequisite: the carrier must grant API access or send the file, and the agency must allow a reviewed write or a return file. This is a configurable design, not a reported deployment and not a measured result.
The money figures behind the two buyers
Carrier economics and agency economics are both public, and they explain why these products are priced by quote. For 2025 the US property-and-casualty industry reported Net premiums written: $976,779 million and a Combined ratio: 92.9%, against $938,658 million and 96.9% in 2024, according to NAIC (2025). The same snapshot, in millions of dollars except for ratios, is the source for every cell below.
| Measure | 2025 | 2024 | Published change |
|---|---|---|---|
| Net premiums written ($ millions) | 976,779 | 938,658 | 4.1% |
| Net premiums earned ($ millions) | 958,726 | 908,913 | 5.5% |
| Combined ratio | 92.9% | 96.9% | -4.0 pts |
| Loss ratio | 66.5% | 71.2% | -4.7 pts |
| Expense ratio | 25.8% | 25.3% | 0.5 pts |
| Net underwriting gain ($ millions) | 68,742 | 25,269 | 172.0% |
That is the scale of the risk-bearing industry Guidewire sells into. It is not a software price, and it is not an agency's revenue. Agency buyers should use the channel study instead. The arithmetic-gap column below is subtraction of the two published figures, not a third statistic the study printed on its own.
| Measure | 2024 | Later study figure | Arithmetic gap |
|---|---|---|---|
| Average staff | 8.2 | 9.9 | 1.7 |
| Agencies reporting a revenue decline | 12% | 8% | 4 points |
| Average marketing budget | $14,300 | $20,600 | $6,300 |
| Agencies reporting AI use | 15% | 46% | 31 points |
An operations lead can put those published figures on one page before arguing about brands. Average staff moved from 8.2 to 9.9, a gain of 1.7 people, and the average marketing budget moved from $14,300 to $20,600, a gap of $6,300, which is $6,300 divided by $14,300, or about 44% more budget, according to IIAT (2026). Average carrier appointments moved from 17.2 in 2024 to 19.7 in 2025, a gain of 2.5 appointments, according to IA Magazine (2026). Those extra appointments still do not turn an agency desk into a claim system of record: a carrier-side search on Guidewire ClaimCenter filters the loss date by sending dateCriteria.chosenOption set to LossDate, and that object lives on the carrier claim, not in the agency book.
Pricing checked in public
Pricing checked October 9, 2026. Guidewire's core-products and PolicyCenter pages invite a sales conversation and do not list a license fee, an implementation fee, or a per-user price. Applied Epic's product page and Applied's US TAM migration hub do the same: contact sales, no license fee. Both products are quote-based. Third-party estimates are not used here.
| Cost question | Guidewire | Applied Epic |
|---|---|---|
| Public license price | Quote-based | Quote-based |
| Public implementation fee | Quote-based | Quote-based |
| Price page found | Not published | Not published |
| What the quote must cover | Which Centers, InsuranceSuite or InsuranceNow, countries, lines | Users, locations, lines, benefits, payments, and connectivity |
| Who should request it | A carrier, or an MGA evaluating a core | An agency or brokerage choosing an AMS |
| Date checked | October 9, 2026 | October 9, 2026 |
Our reading of that table: a total-cost comparison that starts from a guessed monthly fee is not a comparison. Ask each vendor to price the scope in the row above, in writing, including implementation, data conversion, and the interfaces you will actually turn on. Then compare those quotes to the record you need. A lower quote for the wrong record is still the wrong purchase.
Guidewire for the company that holds the risk
Guidewire fits a P&C carrier that needs its own policy, billing, and claim record, and it is the core an MGA should evaluate when the MGA administers business rather than only placing it. InsuranceSuite is the page's answer for mid-sized and large insurers that can stay involved in implementation and operations, with global availability, multiple currencies, and multiple languages. InsuranceNow is the page's answer for US regional insurers and MGAs that want pre-configured lines and a lighter IT load. Guidewire reports PolicyCenter customers: 155+ in 20 countries and an R&D share of product revenue: 35% or more, and it says the research team is 700+ people with 10,000+ partner professionals and more than 800 consultants, according to Guidewire (2026). The same core-products page says the platform's compliance alignment includes SOC 2, ISO 27001, and GDPR.
The limit is the buyer, not a missing screen. An agency that does not hold the risk does not become a better agency by installing PolicyCenter. Guidewire does not publish a standard implementation duration on the pages opened for this guide, so any month count you hear in a sales meeting is a project estimate, not a published product fact. InsuranceSuite's own selection table expects a mature IT group that can stay in the work. InsuranceNow is described as quicker to launch because lines are pre-configured, and it is still a core system with a quote, not an agency desktop. Self-service claim screens, agent portals, and rating models sit around that core. They do not turn it into Applied Epic.
Applied Epic for the company that holds the client
Applied Epic fits an independent agency or brokerage that wants one system for P&C and benefits, with quoting, pipeline, documents, accounting, and insurer connectivity in the daily desk. Applied Systems says Largest agencies on Epic: 7 of 10 on the Business Insurance Top 100, and the same page says the G2 four-star share: 91% comes from its 2024 G2 review note, according to Applied Systems (2026). That is a vendor's report of outside lists and reviews, not a measurement we repeated. It is still evidence that large US agencies standardize on this AMS, which is a different fact from carrier core share.
The limit is the same record test run in reverse. Applied Epic does not become a carrier policy admin system because an agency is large, and it does not become ClaimCenter because a CSR keys a loss notice. Agencies that are choosing among agency systems, not among carrier cores, have a different short list: Applied Epic versus AMS360, Applied Epic versus EZLynx, and other Applied Epic alternatives. Submissions software that sits beside the AMS is its own decision, covered in Applied Epic versus Indio. On implementation, use Applied's 157 migrations and 6-8 week setup claim only as the vendor's statement about TAM moves. Ask for a written plan that names data conversion, branch structure, benefits, and which interfaces go live in the first release. Do not treat that hub statistic as your project's duration until the statement of work says so.
A reviewed handoff above both systems
The reverse direction is a second proposed US Tech Automations workflow, and it is still a design you configure, not a switch that is already running. Trigger: a bound endorsement or renewal appears in an Applied Epic export, or through the Epic API once the agency has been approved for access. Action: map the changed fields into a submission packet and stop on any field the carrier has not agreed to accept. Output: a packet a person at the agency, the MGA, or the carrier approves before any write toward PolicyCenter. Prerequisite: an Epic credential or a scheduled export, plus Guidewire credentials that the carrier controls if a later write is in scope. A retry has to recognize a packet already queued so the same endorsement is not sent twice. No result in this design is a live customer outcome.
Zapier, Make, and n8n are a fair alternative for that handoff. Configured with care, they can keep run histories, retries, error branches, and an audit trail of what moved. The buyer then owns observability, idempotency, escalation, access control, and the maintenance of every connector when a vendor changes a field. A proposed US Tech Automations design can put the carrier claim lookup and the agency update on one reviewed path instead of a chain of separate zaps: the same prerequisites apply, a person still approves the write, and a duplicate check stops a second activity when the first one already exists. The general connectors are not a lesser class of software. They are a build you operate yourself.
US Tech Automations is a poor fit when the only job is a monthly loss-run file a CSR already saves, when a certified carrier download already posts the transaction into the agency system and a person checks the exceptions, or when neither side will provide an API credential or a file export. In those cases the report inside the system you already pay for is the simpler tool. Adding an orchestration layer on top of a closed system only creates a second place for the same unresolved gap.
Common mistakes before the contract
Treating this search as a feature bake-off. The first cut is which firm holds the record.
Using MGA status as a reason to skip that cut. Placing business and administering a policy are different jobs, and InsuranceNow is aimed at the second one.
Pasting a third-party monthly price next to either product. Neither vendor published a license fee on the pages checked on October 9, 2026.
Calling Applied TAM a nickname for Applied Epic. TAM is the older system Applied is moving agencies off, toward Epic or EZLynx.
Expecting ClaimCenter to produce a commission statement, or expecting Epic to set case reserves for a carrier.
Letting an integration write straight through, with no person on the mismatch queue and no duplicate check.
Glossary for this decision
AMS. Agency management system. The agency's record of clients, policies, accounting, and daily work. Applied Epic is this kind of system.
PAS. Policy administration system. The carrier's record from quote through endorsement and renewal. PolicyCenter is this kind of system.
MGA. Managing general agent. A firm that may have authority to underwrite or bind for a carrier, which is why it sometimes looks at both products.
FNOL. First notice of loss. The moment a claim starts. ClaimCenter is built to take the claim from that notice through settlement.
DWP. Direct written premium. The premium volume Guidewire uses when it describes who InsuranceSuite and InsuranceNow are typically for. It is not a software price.
Agency bill and direct bill. In agency bill, the agency collects premium and remits the carrier's share. In direct bill, the carrier bills the insured. BillingCenter and Epic accounting sit on opposite sides of that split.
System of record. The database that wins when two screens disagree. This purchase is mostly a choice of which database is allowed to win.
Questions to close before you request quotes
Are Guidewire and Applied Epic substitutes?
No. Guidewire keeps the carrier's policy, billing, and claim record, and Applied Epic keeps the agency's client and accounting record. A short list that treats them as two flavors of one product will send the proposal to the wrong buyer.
Who should choose Guidewire?
A P&C carrier that must administer its own policies and claims should evaluate Guidewire, and so should an MGA that binds and administers business rather than only placing it. Use InsuranceSuite when you match the mid-sized or large, multi-country profile on Guidewire's page, and use InsuranceNow when you are a US regional insurer or MGA in the band that page describes.
Who should choose Applied Epic?
An independent agency or brokerage that needs one desk for clients, policies, accounting, quoting, and benefits should evaluate Applied Epic. If the comparison is really Epic against another agency system, use the AMS360, EZLynx, and alternatives articles linked above rather than a carrier-core proposal.
How much does either product cost?
Both are quote-based. The Guidewire and Applied pages opened for this guide do not list a license fee or an implementation fee. Pricing checked October 9, 2026.
Does an MGA have to pick only one?
No. An MGA that administers policies evaluates a core such as InsuranceNow or InsuranceSuite. An MGA that only places business evaluates an agency system such as Applied Epic. A group that does both can keep both records and should design the handoff on purpose.
Is Applied TAM just the old name for Applied Epic?
No. Applied TAM is an older agency management system. Applied's US hub says its architecture will soon lose Microsoft support, points agencies to Applied Epic or EZLynx, and states that 157 TAM agencies migrated in the prior year.
Can Zapier, Make, or n8n connect a carrier core to an agency desk?
Yes, if you configure them. Those tools can store run history, retry a failed step, branch on an error, and keep an audit trail. Your team still designs idempotency, escalation, access control, and upkeep, and a person should approve any write into the system of record.
Pick the product that owns the record your firm is accountable for, ask that vendor for a written quote against the scope in the pricing table, and keep the other name only if a second record is truly yours. Where the work is the reviewed pass between a carrier claim file and an agency client file, see how US Tech Automations configures this.
About the Author

Helping businesses leverage automation for operational efficiency.