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.

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 item | How it is usually charged | Who sets it |
|---|---|---|
| Subscription or licence | Annual, often linked to DWP managed, multi-year terms | Vendor quote |
| Cloud hosting | Included in SaaS subscriptions, separate for self-hosted versions | Vendor quote |
| Implementation | Fixed price or time and materials by a systems integrator or the vendor's services team | Integrator quote |
| Product configuration | Each product, state and form set configured and tested | Integrator quote, often per product |
| Integrations | Billing, claims, payments, data vendors, agency systems | Integrator quote |
| Data migration | Converting the in-force book from the old system | Integrator quote |
| Internal team | Product owners, business analysts, testers from your side | Your salaries |
| Upgrades | Major version upgrades, especially if heavily customised | Integrator 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
| Scope | What is included | Cost | Timeline |
|---|---|---|---|
| Discovery | Product and rating analysis, filed forms review, data model, integration list, fixed estimate | $3k to $8k | 3 to 5 weeks |
| Focused PAS for one product | Product 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 stages | Facade, slices, migration and reconciliation, parallel running | $40k to $150k+ | 6 to 18 months |
| Support and change | Fixes, rate and form updates, new states, small features | $1.5k to $8k per month | Ongoing |
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
| Module | What it does | Share of build effort (typical) |
|---|---|---|
| Product configuration | Coverages, limits, deductibles, eligibility rules and forms per product, state and effective date | 15 to 20 percent |
| Rating engine | Versioned rate tables and factor rules as filed, with a rating worksheet stored for every quote | 15 to 20 percent |
| Quote, bind and issue | Underwriting questions, referrals to underwriters, binding, policy number issue | 15 percent |
| Mid-term changes and renewals | Endorsements with pro-rata premium, backdated changes, renewal offers, cancellations and reinstatements | 15 to 20 percent |
| Documents | Declarations, certificates, notices and letters from templates, stored as issued | 10 percent |
| Broker or agent portal | Quotes, submissions, documents and commission statements | 10 to 15 percent |
| Audit, roles and reporting | Append-only history, underwriting authority, premium and in-force reports | 10 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 years | Custom build with us | Licensed 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 subscription | None | Vendor quote, often linked to DWP, every year |
| Hosting | Assumption A: your own cloud account, billed by AWS, Azure or Google | Included in SaaS, or your cloud account if self-hosted |
| Upgrades | None forced; you own the code | Vendor 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.
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
| Signal | Points to licensed | Points to custom |
|---|---|---|
| Products and lines | Many, standard | One or two, unusual |
| States | Most of the US | A handful |
| Premium growth | Steady | Fast (licence fees would grow with it) |
| Engineering team | None, and no plan for one | In place or planned |
| Differentiation | Price and service | Product 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 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.
LinkedInRelated 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.