The business case for opening more distribution partners: what to measure

The business case for opening more distribution partners: what to measure

Craig Hangartner

Saba Gobal, CPCU

Your leadership team wants more MGAs, brokers, TPAs, and software vendors sending business to your Guidewire instance. You are asked to show it pays for itself. Premium projections alone do not carry that case, because they leave out what each new partner costs your team to connect and what arrives once the partner is live.

Most business cases stall at that gap. The upside is a number someone can estimate. The intake cost sits in ticket queues, release calendars, and underwriter inboxes that nobody has counted.

This article names the measures that close the gap, who owns each one, and how to assemble them into a case that a CIO and an underwriting lead will both sign. It uses no industry statistics, only measures you can pull from your own operation.

Why does the business case for more distribution partners stall?

A business case stalls when one side of the ledger is estimated and the other is guessed. Partner premium gets a forecast. Connection and intake cost get a shrug.

Premium projections are the only number in the room

Distribution leads bring the number they can defend, which is expected premium by line, by partner, by year.

That number is real and incomplete. It says what a partner is expected to send. It says nothing about the engineering and underwriting effort needed to receive it.

Intake capacity is the constraint nobody measures

Every new partner sends policy, claims, or billing data in its own format. Someone on your Guidewire team builds and maintains the connector for it.

That work competes with every other change request, so your team’s capacity sets the real ceiling on partner count.

Underwriting workbench vendors see the mirror image from the sender side, since each carrier asks for its own build.

What should a carrier measure before opening more distribution partners?

Measure four things per partner: what it brings, what it costs to connect, what quality arrives, and what it displaces. Each one needs an owner and a data source you already hold.

The Partner Intake Scorecard: four measures, four questions

The Partner Intake Scorecard pairs each question a committee asks with one measure, one owner, and one source.

Measure

Question it answers

Owner

Where the data lives

Partner demand

How much business will this partner send, and in which lines?

Distribution lead

Producer agreements, submission history

Connection effort

What does it take to get this partner live and keep it current?

CIO, Guidewire team

Ticket history, sprint records

Intake quality

How complete is what arrives?

Underwriting operations

Submission logs, referral reasons

Capacity displaced

What does this partner push out of the queue?

CIO and underwriting operations

Backlog, team allocation

Score each candidate partner on all four before comparing any two.

Take the baseline from partners already live

Start from the partners that already send you data. Their history gives you a baseline no estimate matches.

Pull their connection effort, completeness, and underwriter touches into one sheet.

In a cross-platform Guidewire estate, run the same four measures against PolicyCenter, ClaimCenter, and BillingCenter separately.

Give every measure a named owner

A number without an owner gets disputed in the committee room. Assign each measure before you collect anything.

The CIO owns connection effort and release upkeep. Underwriting operations owns completeness, touches, and rework. Distribution owns demand.

Each owner signs off on their baseline before the case moves forward.

How do you measure the cost of connecting a new partner?

Connection cost is the number most carriers cannot state today. Three counts produce it: hours per connector, hours per release, and steps from first call to first live submission.

Four steps to measure connection cost: log connector hours, count release upkeep, map steps to live, flag waits and owners.

Count connector hours from your own tickets

Log the engineering hours booked against each live connector, from first ticket to first live submission. Use ticket history, not recollection.

Record the count by sender type, because the way MGAs, TPAs, and brokers send submission data into PolicyCenter differs from one type to the next.

Count release upkeep per connector

Connection effort does not end at go-live. Guidewire ships three releases a year, and each release puts every connector back on the test list.

Count the hours per release, per connector. This is the recurring half of what maintaining a Guidewire connector involves, and it grows with every partner you add.

Count the steps from first call to first live submission

Elapsed time matters as much as hours. Track each step: specification agreed, mapping reviewed, test passed, production enabled.

Note where each step waits and on whom.

Carriers that onboard agencies and vendors through self-service hand several of those steps to the sender, so record which steps need your staff and which do not.

How do you measure what arrives from a partner?

Quality shows up at the door and in the underwriting queue. Three measures capture it: completeness, underwriter touches, and rework loops.

Completeness at the door

Define completeness the way underwriters do, as mandatory fields present and valid values accepted. Measure the share of submissions that arrive complete, partner by partner.

A clear payload specification gives both sides the same definition to measure against.

Underwriter touches per submission

Touches turn quality into effort. Count how many times an underwriter opens a submission before it is ready to quote.

Log the reason for each touch: a missing field, an invalid value, or an unclear document. The reasons show whether a partner needs a better specification or a firmer intake rule.

Rework loops back to the sender

A submission sent back to the partner costs both sides a cycle. Count the loops per submission.

Add the elapsed days between the request for correction and the corrected return. A partner with many loops carries a hidden cost that premium never shows.

How do you turn the measures into a business case?

Combine the four scorecard measures into a comparison, set the decision rule first, and test it on one partner. The result is a case built on your numbers, not projections.

Four steps to build a business case: price two routes, score all four measures, set the rule first, pilot one partner.

Price the same partner through two routes

Take one candidate partner and score two routes. Route one is a custom connector that your team builds and maintains. Route two is a shared intake route where the sender maps once.

Score both on all four measures using your own hours and your own queue.

Set the decision rule before the data arrives

Agree in advance what result admits a partner. For example, connection effort under a ceiling your team sets, and completeness above a floor underwriting operations sets.

Thresholds written first keep the case honest.

Scope a first pilot: one partner, one line of business

Keep the first test small. Choose one partner and one line of business, run the scorecard, and report the four measures to the committee.

The pilot gives the committee your numbers. It also shows where the scorecard needs adjusting before the next partner.

How InsOps Helps

InsOps builds Yazh (Yaal), a data exchange platform for carriers on Guidewire. Yazh supports dynamic data exchange for insurance between your senders and your core systems. A sender maps its payload once, and Yazh translates it to your Guidewire format.

LiLa, our insurance-trained model, assists with the mapping. A person reviews every mapping before it is used.

The InsOps Integration Gateway delivers inbound data into PolicyCenter, ClaimCenter, and BillingCenter. Guidewire’s own Integration Gateway is a developer framework. Yazh adds a self-service portal, a test harness, and a sandbox beside it, so senders test before real data arrives.

Several capabilities bear on the measures above. Gap rejection catches incomplete data at the door, the portal lets senders map and test on their own, and tenant-specific mapping handles your carrier’s own fields.

If you are evaluating how to build the case for more distribution partners without committing to a connector for each one, contact us to talk through what this could look like for your operation.

Frequently Asked Questions

What is a business case for opening more distribution partners?

It compares the value a new partner brings with the cost of connecting and serving that partner. It rests on four measures: partner demand, connection effort, intake quality, and capacity displaced.

Why do carriers cap the number of distribution partners they take on?

Each partner needs a connector built, tested, and kept current across Guidewire releases. Your integration team’s capacity becomes the limit, not partner appetite.

How do you measure the cost of connecting one partner?

Log engineering hours per connector from ticket history, add the hours per Guidewire release, and record the steps and waits from first call to first live submission. Count by sender type, since MGAs, TPAs, and brokers connect differently.

What are the common challenges in building the case?

The data sits in different teams. Tickets sit with engineering, referral reasons with underwriting, and premium with distribution. One scorecard with named owners removes most disputes, and partners already live supply the baseline.

Which metrics show whether a new partner is working?

Track completeness at the door, underwriter touches per submission, rework loops per submission, and connector hours per release. Compare each against the baseline from your live partners.

How does Yazh assist with opening more distribution partners?

A sender maps its payload once, LiLa assists with the mapping, and a person reviews every mapping before it is used. The portal, test harness, and sandbox let the sender test before real submissions arrive.

What is a realistic expectation for the first business case?

Expect a baseline for one partner and one line of business, built from data your teams already hold. The usual pitfalls are estimating hours instead of counting them and setting thresholds after the data is in.

Craig Hangartner

Saba Gobal, CPCU