Why personas, why now

A carrier doesn't have a single buyer for an intelligent document processing platform. It has a buying committee — and the committee has a defined sequence of conversations, each driven by a different role asking a different question.

Get the personas right and the deal moves predictably. Get them wrong — talk ROI to the systems VP, talk integrations to the COO, talk feasibility to the CUO — and the deal stalls in a quiet way that nobody bothers to explain. This chapter is the map of who is who, what they care about, and where in a typical 9-to-15 month carrier sales cycle each one becomes the controlling voice.

Three things to internalize before the personas:

• Carriers buy in committee, not by champion. A single enthusiastic head of underwriting cannot pull a deal through alone. Even an MGA needs at least three internal advocates (a business sponsor, an ops owner, an IT signoff) before legal will pick up the redlines.
• The buying committee is sequenced, not parallel. The problem identifier surfaces the pain. The CIO/COO sponsor the budget. Business and tech leaders pressure-test the value case. End users sign off on usability. Procurement closes. Skipping a stage doesn't accelerate the deal; it kills the deal six months later.
• Each persona has its own KPIs. A combined ratio improvement matters to the COO. A submission-to-quote cycle matters to the head of underwriting operations. A platform compatibility matrix matters to the systems VP. The same product story is told in different vocabularies depending on the room.

The buyer intersection

Every carrier buying committee has three buyer archetypes pulling in three different directions. A deal closes when all three are satisfied. The three archetypes:

How the three intersect

The Problem Identifier opens the door. They feel the pain every day — the submission queue is six weeks behind, the loss-run extraction team is at 22 FTEs, the CAT spike crashed the FNOL routing. They are not the budget holder, but they are the one who first says "we need to look at this."

The Tech & Ops Buyer (CIO or COO) sponsors the initiative once the Problem Identifier brings it to them. They allocate budget and resources, but they need a value case good enough to bring to the CFO and board. They evaluate not just this purchase but its fit with the broader transformation roadmap.

The Business Buyer is the CUO or CCO whose P&L gets credit for the improvement. They are sometimes a champion, sometimes a skeptic, sometimes absent until late in the cycle. Their question is always: "Is this going to help my underwriters / adjusters or get in their way?"

The buying committee map

A typical carrier IDP / AI platform purchase moves through seven distinct stages. Each stage has a different leading role, a different question, and a different set of artifacts the vendor needs to put on the table. This is the master map; treat it as the timeline against which to sequence content, demos, references, and procurement work.

Two patterns worth knowing

The seven stages are not strictly linear. Two common variations show up routinely.

• The Tech Feasibility re-loop. When IT raises a concern after the Value Discussion is closed, the deal stalls until that concern is resolved. The CIO will sometimes call a "feasibility pause" lasting weeks. Sellers who pre-engage IT during the Problem Arises stage avoid this almost entirely.
• The Procurement compression. If a deal has carried real momentum through stages 1–6, Procurement often becomes a 30–45 day window rather than a 90-day grind. Carrier procurement is most aggressive when there's no internal urgency to close, so building the urgency upstream is the play.

COO — the operations sponsor

The Chief Operating Officer is the most common executive sponsor for an IDP deployment at a P&C carrier. They are accountable for cost-to-serve, cycle time, and the quality of work coming out of the operations function. They sit on the Buyer Intersection on the technical-and-ops side and almost always need to be in the room before budget moves.

CIO — the technology sponsor

The Chief Information Officer co-sponsors most carrier IDP deals alongside the COO. The CIO controls integration sequencing, security review, and architectural fit. A deal can have full operations buy-in and still stall for a quarter if the CIO has not been engaged early.

Head of Underwriting Operations

The Head of Underwriting Operations is usually the deal's first true champion. They sit between the underwriting business and the systems team, and they are the one measuring submission velocity, clearance accuracy, and underwriter productivity day to day. When this persona is enthusiastic, deals tend to close. When they are skeptical, they will not be overridden.

Head of Claims Operations

The claims-side counterpart to the underwriting-ops head. Owns the FNOL pipeline, claims routing, leakage controls, and the operations response when a CAT event sends volume through the roof. Often a quieter buyer than the UW Ops head — claims teams have lived through more failed automation pilots — but a high-value one once engaged.

Head of Underwriting Systems

The systems-side counterpart to the UW Ops head. Owns the underwriting workstation, the rating engine integration, the data pipelines into the policy admin system. The technical interlocutor on Tech Feasibility — they will write the integration architecture, run the build-vs-buy analysis, and own the rollout.

Head of Claims Systems

The claims-side counterpart to the UW Systems head. Owns the claims platform (typically Guidewire ClaimCenter, Duck Creek Claims, or a custom stack), the FNOL routing, and integrations with adjusters, vendors, and reinsurers. Same engagement pattern as UW Systems but with an even higher bar on data lineage and audit.

Transformation Executive

The Transformation Executive is a relatively newer persona at carriers — typically created in the last five to seven years as carriers built standalone transformation offices. They sit alongside the COO and CIO, often reporting to the CEO directly, with a mandate to identify and prioritize cross-functional transformation initiatives. When this persona is the lead sponsor, deals tend to move faster and budget tends to be more elastic.

The discovery playbook

The personas above are the map. The discovery playbook is the order in which you should be opening doors during the early stages of an opportunity. A few principles to anchor on.

1 · Find the Problem Identifier first

Almost every deal starts with a Head of UW Ops, Head of Claims Ops, Head of UW Systems, or Head of Claims Systems calling a peer at another carrier and asking what they're using. That person is the entry point. If you cannot identify a Problem Identifier in the first three meetings, you do not yet have a real deal — you have an interesting conversation.

2 · Map the buying committee explicitly

By the end of discovery, you should be able to name each of the seven roles in the committee map and the specific person in that seat at the prospect. If you cannot, the deal is at risk regardless of how positive the Problem Identifier sounds.

3 · Sequence the sponsor conversations

The CIO and COO almost never agree to sponsor in the same meeting. The Problem Identifier needs to broker each one separately, and the order matters: at a carrier focused on a cost program, COO first; at a carrier focused on modernization, CIO first; if a Transformation Executive exists, them first regardless.

4 · Engage IT before Value Discussion closes

The single most common deal-killer at carriers is a late Tech Feasibility surprise. A 30-minute call with the Head of Systems before the CIO pitches the COO is worth more than three demos to the business.

5 · Bring different content to each room

This is the table at the heart of the committee map. The COO does not want a feature demo; the Head of Systems does not want an ROI calculator; the CUO does not want an architecture diagram. Match the artifact to the role.