Skip to content

Cost & pricing · 6 min read

Policy Administration System Cost in 2026: Licence vs Custom Build Over Five Years

Policy administration system cost: licensed suites are quote-based, custom builds run $80k to $200k+. Five-year cost comparison with labelled assumptions.

Zohaib KhalidZohaib KhalidCEO & Co-founder, Innovation InsightPublished
Two people talking across a table with a laptop, hands gesturing

Short answer

A custom policy administration system costs $80k to $200k+ to build with Innovation Insight, plus $1.5k to $8k per month for support. Over five years that comes to roughly $152k to $584k+ before hosting. Licensed platforms such as Guidewire, Duck Creek and Socotra do not publish prices; quotes are usually tied to premium volume, and implementation often costs as much again. Custom suits one or two narrow products; licences suit multi-line carriers.

Two very different price models

Comparing a licensed policy administration system (PAS) with a custom build is awkward because the cost shapes differ. A licence is an annual fee that grows with your premium, plus an implementation project. A custom build is a large upfront project plus a smaller ongoing team, and the cost does not grow with premium. Which is cheaper depends mostly on how many products, states and lines you write, and how fast premium grows.

Licensed platforms: what we can and cannot tell you

No major PAS vendor publishes a price list, so any figure you read online is either a leaked quote or a guess. What is public is how pricing is structured. Guidewire's annual report says it generally prices core subscriptions on the direct written premium (DWP) the platform manages, with some cloud products priced on usage (Guidewire Form 10-K, FY2026, checked October 2026). Expect the following line items in any licensed proposal:

Line itemHow it is usually chargedWho sets it
Subscription or licenceAnnual, often linked to DWP managed, multi-year termsVendor quote
Cloud hostingIncluded in SaaS subscriptions, separate for self-hosted versionsVendor quote
ImplementationFixed price or time and materials by a systems integrator or the vendor's services teamIntegrator quote
Product configurationEach product, state and form set configured and testedIntegrator quote, often per product
IntegrationsBilling, claims, payments, data vendors, agency systemsIntegrator quote
Data migrationConverting the in-force book from the old systemIntegrator quote
Internal teamProduct owners, business analysts, testers from your sideYour salaries
UpgradesMajor version upgrades, especially if heavily customisedIntegrator quote

Ask every vendor for the five-year total, not the year-one fee, and ask how the fee changes if premium doubles. The cheapest year-one proposal can be the most expensive by year five for a fast-growing MGA.

Custom build: what it costs with us

ScopeWhat is includedCostTimeline
DiscoveryProduct and rating analysis, filed forms review, data model, integration list, fixed estimate$3k to $8k3 to 5 weeks
Focused PAS for one productProduct configuration, rating engine with versioned rate tables, quote-bind-issue, endorsements, renewals, cancellations, document generation, broker portal, audit log$80k to $200k+6 to 12 months
Replacing a legacy PAS in stagesFacade, slices, migration and reconciliation, parallel running$40k to $150k+6 to 18 months
Support and changeFixes, rate and form updates, new states, small features$1.5k to $8k per monthOngoing

A focused PAS sits at the lower half of $80k to $200k+ when it covers one product in a handful of states with a simple broker portal. It moves to the top and beyond with several products, complex rating (dozens of factors, territory tables, schedule rating), billing built in rather than integrated, and many integrations. The policy administration system development page lists the modules in detail.

What a custom PAS includes, module by module

ModuleWhat it doesShare of build effort (typical)
Product configurationCoverages, limits, deductibles, eligibility rules and forms per product, state and effective date15 to 20 percent
Rating engineVersioned rate tables and factor rules as filed, with a rating worksheet stored for every quote15 to 20 percent
Quote, bind and issueUnderwriting questions, referrals to underwriters, binding, policy number issue15 percent
Mid-term changes and renewalsEndorsements with pro-rata premium, backdated changes, renewal offers, cancellations and reinstatements15 to 20 percent
DocumentsDeclarations, certificates, notices and letters from templates, stored as issued10 percent
Broker or agent portalQuotes, submissions, documents and commission statements10 to 15 percent
Audit, roles and reportingAppend-only history, underwriting authority, premium and in-force reports10 percent

Billing is often integrated rather than built, using an existing billing system or a payment provider with instalment schedules. Building billing inside the PAS adds a ledger, instalment plans, commission and cancellation for non-payment, and usually pushes the build to the upper end of the range. Claims stays a separate system on almost every project; see our claims management software cost post.

Five-year total cost: a worked comparison

The custom side below uses only our published ranges. The licensed side has no numbers because the vendors do not publish them, and we will not invent them. Use it as a checklist to fill in from your quotes.

Cost over five yearsCustom build with usLicensed platform
Build or implementation (year 1)$80k to $200k+Implementation quote from integrator
Support and change (years 2 to 5, 48 months)$72k to $384k ($1.5k to $8k per month)Included partly in subscription; change requests quoted by integrator
Licence or subscriptionNoneVendor quote, often linked to DWP, every year
HostingAssumption A: your own cloud account, billed by AWS, Azure or GoogleIncluded in SaaS, or your cloud account if self-hosted
UpgradesNone forced; you own the codeVendor upgrades; cost depends on customisation
Five-year total excluding hosting$152k to $584k+Sum of your quotes

Assumptions, labelled so you can change them: (A) hosting is excluded on both sides because it depends on your volume and region; for a single-product PAS it is usually a small share of the total. (B) Support runs for 48 months after a 12-month build at our published monthly range; most clients sit in the lower half once the system is stable. (C) No major scope additions; each new product or state is quoted separately. (D) Your internal team cost is the same on both sides and excluded.

The question that usually decides it: in five years, how many products and states will you write? One or two products in a handful of states favours custom. Many lines across most states favours a licensed core, because product configuration tooling is what you are paying for.

Hidden costs on both sides

  • Rate and form filings: every rate change must be implemented exactly as filed, by state and effective date. Budget for it on either path.
  • Data migration: converting an in-force book costs the same whether the target is licensed or custom; see our insurance legacy modernization guide.
  • Security evidence: carriers and reinsurers ask for a security programme aligned to the NAIC Insurance Data Security Model Law and often a SOC 2 report from vendors.
  • Key-person risk: a custom PAS needs documentation and a team that can be replaced; a licensed PAS needs people who know that vendor's configuration tools, who are scarce and expensive.
  • Exit cost: leaving a licensed platform means another migration; leaving a custom vendor means handing over code you already own.

Questions to ask before you sign either way

  • Licensed: what is the five-year total at today's premium and at double it, and what is excluded from the subscription?
  • Licensed: how many of your configurations will survive the next major upgrade without rework?
  • Custom: who owns the code and the cloud account from day one, and is the rating engine documented well enough for another team to take over?
  • Both: how will rate changes be tested against the filing before they go live, and who signs that off?

How to choose

SignalPoints to licensedPoints to custom
Products and linesMany, standardOne or two, unusual
StatesMost of the USA handful
Premium growthSteadyFast (licence fees would grow with it)
Engineering teamNone, and no plan for oneIn place or planned
DifferentiationPrice and serviceProduct design, data, distribution

Our relevant work

We have no published insurance policy administration case study yet. Adjacent first-hand work: Solas, a multi-tenant operations platform where a central record links clients, items, estimates with expiry dates, estimate-to-invoice conversion and PDF export, which is close to the quote-to-bind-to-document shape of a PAS; and Paint Nite, a platform rebuilt beside a live legacy system with sync services and a checkout built as an atomic pipeline with per-state tax rules. For the rest of the decision, read our insurance software development guide, the claims management software cost post, or the custom software development cost guide.

Need a number for your project?

Send a short brief and get a written estimate.

A senior engineer replies within one business day. No sales call required.

Zohaib Khalid, CEO & Co-founder, Innovation Insight

Zohaib Khalid

CEO & Co-founder, Innovation Insight

Zohaib leads strategy, client partnerships and delivery at Innovation Insight. He has spent a decade turning founder briefs into products that ship and still reviews every proposal that leaves the company.

LinkedIn
FAQ

Related questions.

How much does a policy administration system cost?

A custom PAS for one or two products costs $80k to $200k+ to build with us, plus $1.5k to $8k per month for support. Licensed platforms are quote-based and commonly priced on direct written premium, plus implementation.

Why do PAS vendors not publish prices?

Because the fee depends on premium volume, modules and lines, and deals are negotiated. Ask for a five-year total and how the fee changes as premium grows.

Is a custom PAS risky for regulators?

No more than a licensed one, if rates and forms are implemented as filed, data is effective-dated and auditable, and the security programme meets the state's version of the NAIC data security law.

How long does a custom PAS take?

Six to twelve months for one product in a handful of states, after a three to five week discovery. Each additional product or state adds configuration and testing time.

Can we start custom and move to a licensed core later?

Yes, if the custom system is built with clean APIs and ACORD-style data names. Migration is then a data conversion project rather than a rebuild of every channel.