Guidewire vs Federato 2027: Core Suite or Underwriting Tool

Short answer: these sit at different layers

Guidewire and Federato are not interchangeable, and the first decision is which layer of your operation you are buying. A core insurance system, also called a policy administration system, is the record that holds policies, billing, and claims, and most other tools read from it. An underwriting platform decides which incoming submissions deserve attention, how to triage them, and what a quote should look like before a person approves it.

Guidewire fiscal 2026 revenue: $1.475 billion, up 23% according to Insurance Business (2026). That scale points to a core-system business aimed at large insurers, and the public figures we could read do not describe a small-business tier.

Federato started on the underwriting side. Reinsurance News covered its $25 million Series B in June 2023 and described it as "the insurance industry's first RiskOps underwriting platform," according to Reinsurance News (2023). Its own site now lists 6 platform modules, including policy administration, billing and payments, and claims, according to Federato (undated).

That is a change in scope, not a rename. The pages we opened show no sign that either product has been renamed, merged, or discontinued.

The category decision: if you are a carrier or MGA that has to run or replace policy, billing, and claims, Guidewire is the category you are shopping in. If your bottleneck is submission triage and quote turnaround, and you already have a system of record, Federato is the closer fit. Before you sign with it, check whether it expects to hold your policy records as well.

TL;DR: Pick Guidewire when the core record is the problem. Pick Federato when submission decisions are the bottleneck and you can accept a platform that also wants your policy lifecycle. Neither vendor's price is confirmed on the pages we could read, and the public material we could read is not aimed at brokers or agencies.

Key Takeaways

• Guidewire is a core-system suite, while Federato is an underwriting-first AI platform whose public scope now includes policy administration, billing, and claims.

• Federato's pricing page names no plans or prices, and Guidewire's pricing page could not be read, so neither price is confirmed.

• Federato's public pages show no small-business tier and do not list brokers; Guidewire's product pages could not be read, so we make no claim about its tiers.

• Federato's pages describe no APIs or core-system connectors, so ask for an integration list before any demo.

• An orchestration layer that sits above your systems works only if your core system can expose records by API or export.

• Brokers and agencies should not start with either product unless the vendor confirms in writing that it serves their segment.

How we evaluated these tools

We weighted seven criteria by how much each one changes a small insurer's buying decision. The weights are our judgment for an owner or operations lead, not a vendor's scoring method.

We opened each vendor's public product pages and, where they loaded, its pricing page. Figures come from trade press and from vendor documentation we opened. Guidewire's own product, release, and pricing pages returned access or rate-limit errors during this research, and the G2 and Gartner Peer Insights pages did too. Where a Guidewire point depends on those pages, we say so and do not mark it verified. We also left out the dollar estimates that directories and benchmark sites publish for both products. They conflict with each other and are not vendor prices.

Feature matrix: what the public pages support

The matrix records only what we could confirm on pages we opened. A "not verified" cell marks a gap in the public record, not a feature that is missing.

The scope row is where the two diverge. Neither product removes the need for a connecting layer between your intake inbox, your core system, and the people who approve decisions. US Tech Automations positions itself in that connecting layer, and the workflows later in this article show what it would configure and what it would need from you.

What it costs: quote-based pricing and what to ask

Pricing checked November 10, 2026. Federato's pricing page names no plans and no prices, and its calls to action are to talk to sales, so its price is Quote-based. Guidewire's pricing page returned an error during this research, so we could not read its pricing model. We list it as Quote-based (unconfirmed), and you should confirm that on the vendor's site before you plan a budget.

Total cost of ownership cannot be computed from public data here. Ask each vendor to price five lines separately: data migration from your current system, integration build, internal staff time, training, and ongoing support. A bundled quote is hard to compare with another bundled quote, and separating the lines is the simplest way to see what you are actually buying.

Guidewire: best fit, limits, and evidence

Choose Guidewire when the core record is the problem, meaning policy, billing, and claims data sit across several tools and you need one system to carry them. Guidewire reported fiscal 2026 ARR of $1.242 billion, up 19% in constant currency, and said more than 570 insurers in 44 countries run on its software, according to Insurance Business (2026). The same reporting says license revenue fell 7% as carriers move to cloud subscriptions, and that the August 2026 Qusar release added tools for AI agents inside core systems, including for claims summaries and policy changes.

The product and release pages were not readable during this research, so module names, deployment options, and the status of individual features are not verified here. The public figures describe insurers at scale, and we found no published small-business tier or self-serve trial. Treat any deployment-model claim as something to confirm in writing.

We found no published implementation timeline. The length of any core replacement depends on how much policy data must be migrated and how many connected systems must be rebuilt, so ask for a plan that names both before you compare vendors.

This profile fits a carrier planning a multi-year core project with budget for outside implementation help. It does not fit a business that needs a fix within one quarter.

Federato: best fit, limits, and evidence

Federato is strongest, on its own description, for insurers and program businesses with heavy submission volume that want triage and quote drafts in one place. Its policy administration page says submissions are scored against appetite, portfolio strategy, and risk characteristics, and that a draft quote is generated for underwriter review. The same page says "Underwriters remain in control," that every quote can be reviewed, edited, and approved before it is sent, and that every transaction updates one policy record, according to Federato (undated).

Funding round in November 2025: $100 million according to Reinsurance News (2025). The round was led by Growth Equity at Goldman Sachs Alternatives, and the article puts total funding above $180 million. It describes Federato as an AI-powered underwriting platform, and the lead investor said it had built "the full policy lifecycle solution the market has been waiting for." That is an investor's view, not an independent check.

The public pages we opened do not mention APIs, external data sources, or connections to existing core systems. If you run a core system, ask which systems Federato reads from and writes to, and whether it can run beside yours or must replace it. Its pages also show no implementation timeline. They describe preconfigured flows and per-program settings for statuses, routing, approvals, and automation "without custom development," which is a vendor claim we have not checked with a customer reference.

This profile fits an MGA or carrier whose main delay is the submission queue and that can get the integration answers in writing before a demo. The public materials do not describe a broker or agency as the buyer.

Who this is for, and who should choose which

Who this is for: owners and operations leads at carriers, MGAs, or MGAAs who spend their days on submissions, quotes, and policy changes, and who are deciding between a core system and an underwriting layer.

Red flags: you run a brokerage or agency and need a tool built for that work, you need a published price before you talk to anyone, or you have no written appetite rules, so nothing can be triaged against them.

• Choose Guidewire if the core records are the problem and you can commit to a multi-year project with outside implementation help.

• Choose Federato if submission triage and quote turnaround are the bottleneck and you can get its integration answers in writing first.

• Choose neither, or a lighter stack, if your work is agency or broker work. Neither product's public material we could read describes that buyer.

When NOT to use US Tech Automations. A layer like this is the wrong purchase in three cases. If you are choosing a core system for the first time, you need the system of record first, because a connecting layer has nothing reliable to connect to yet. If your intake volume is low enough that a shared inbox, a checklist, and one spreadsheet cover it, the design work costs more than the manual steps it replaces. If you already run Federato's triage across intake and quoting, adding an outside triage rule set duplicates its scoring and creates two sources of truth, so configure Federato first.

Where the manual work piles up: two proposed workflows

US Tech Automations would configure the two workflows below as proposed designs. Nobody runs them in this article, and the inputs are planning assumptions, not measured results.

Proposed submission triage. The trigger is a new submission email with attachments arriving in the underwriting inbox. The action extracts the insured's name, line of business, and requested limits, compares them with a written appetite guide that underwriting has approved, and places the file in a queue with the rule that matched. The output is a triage record plus a flag on any file that needs a person. The prerequisites are read access to the inbox, the approved appetite guide in writing, and an API or scheduled export from the system where files are recorded. The human review points are that an underwriter confirms every recommendation to decline before any notice goes out, and that changes to the appetite guide need management sign-off.

Proposed policy-change check. The trigger is an endorsement or renewal date entered in the policy system. The action exports the changed fields and compares them with the last renewal worksheet. The output is a discrepancy list sent to the account manager. The prerequisites are scheduled export or read API access to the policy system and a defined list of fields to compare. The human review point is that an account manager approves any premium or coverage change before it reaches the client.

Doing it yourself in Zapier or Make, and what you still own

The obvious alternative is to stitch this together yourself in Zapier, Make, or n8n, or to build it in-house. These tools do more than their reputation suggests. Zapier's help center describes Zap run statuses such as Errored, Handled error, and Scheduled, and says Autoreplay retries failed runs caused by temporary problems, with replay available after a fix so data is not lost, according to Zapier (undated).

Zapier webhook throttle: up to 10,000 requests per 5 minutes according to Zapier (undated). A high-volume intake step therefore needs a retry plan rather than an assumption of unlimited calls.

Make's scenario history records each run's status, duration, operations, credits, and transferred data size, with a replay option and a Details view, according to Make (undated). Retention depends on the pricing plan, and the page does not list a number of days.

What you still own with any of these tools is the design. You need to stop a rerun from creating a duplicate record, decide who receives each escalation and how fast, control who can see stored credentials, and fix the flow when a core system's API changes. A proposed US Tech Automations design would name those parts in the configuration: one exception queue with a named owner, a log of which appetite-rule version produced each triage decision, and approval gates on any outbound notice. Those are design choices we would propose, not outcomes we have measured.

A worked example, using hypothetical inputs and no customer data: a small MGA receives 120 submissions a week. If 30% of them, or 36 files, fall outside written appetite, and an underwriter spends 12 minutes reading each one before declining, that is 432 minutes, or 7.2 hours, of reading a week. If the triage rule flags those 36 files and 4 of the flags turn out to be wrong, those 4 files (4 of 36, or 11.1%) still need a person, so the design needs a review queue rather than automatic declines. On the integration side, Zapier's throttle documentation names the error class z.errors.ThrottledError and says a Retry-After header lets a throttled request retry at a set time instead of halting the Zap, so the intake step should expect that error and retry rather than drop the file.

Terms used in this comparison

• Core system: the policy, billing, and claims record that other tools read from.

• Submission: an application package a broker sends to an underwriter asking for a quote.

• Triage: sorting incoming submissions so the best-fit files are handled first.

• Appetite: the classes and risk profiles a carrier or MGA is willing to write.

• MGA: a managing general agent that underwrites and binds coverage under authority from carriers.

• Endorsement: a mid-term change to an issued policy.

• Orchestration layer: software that moves data and decisions between systems you already run, without being the system of record.

Decision checklist before you talk to sales

1. Name the bottleneck: is it the core record, or the decision on each submission?

2. Ask each vendor for its integration list in writing: which systems it reads from and writes to.

3. Ask for a quote that splits migration, integration, training, and support into separate lines.

4. Ask for a reference customer of your size and line of business, and check that reference.

5. Write your appetite rules before any triage tool is configured.

6. Decide which person approves every decline and every premium or coverage change.

Questions buyers ask

Is Guidewire a direct competitor to Federato?

Not directly: Guidewire is a core system, and Federato is an underwriting platform whose public scope now includes policy administration, billing, and claims, so the two overlap mainly on policy servicing.

Does either vendor publish prices?

No, not that we could confirm: Federato's pricing page names no plans or prices, and Guidewire's pricing page could not be read in this research, so both stay Quote-based until you get a written quote.

Are either of these built for a small insurance business?

The public pages we could read for Federato target carriers, MGAs, MGAAs, and the London Market rather than small businesses, and Guidewire's public figures describe insurers at scale. Neither source describes a small-business tier.

Which should an agency or broker choose?

Neither, based on the material we could read; an agency should compare tools built for agency workflows, which this article does not cover.

Can Zapier or Make stand in for either vendor?

For a single trigger and a single action, yes, and it is simpler; for a full underwriting or policy workflow, both leave the design, escalation, and access rules with you.

Does Federato connect to my core system?

The pages we opened do not say, so treat that as the first question for the vendor and get the answer in writing.

Where to go from here

Guidewire and Federato answer different parts of the same operation. Start with the layer where your bottleneck sits, get pricing and integrations in writing, and only then decide whether anything needs to sit above your existing systems. To see how the review points and prerequisites above would be configured for your inbox and core system, see how US Tech Automations configures this.