cuttleflow
Systems
Perspective 29 · The economics of delegated authorityNovember 2026 · 11 min read

Many to many

A broker portal built for one insurer assumes the broker deals with one market. No broker does. The system should record the market as it is: many parties, many relationships, and people acting in different roles within them.

Most insurers and underwriting agencies that move their broker business online build a broker portal. The broker signs in, enters the risk, gets a quote and binds. From the insurer’s side the portal works: submissions arrive complete and in one format.

From the broker’s side it is one more portal. A broker deals with many markets, and each of them has built its own.

This piece argues that a portal built around one insurer has the structure of the market wrong. Distribution under delegated authority is a set of many-to-many relationships between brokers, agencies, insurers and capacity providers. A system that records those relationships, and the roles people hold in them, can do things a one-to-one portal cannot. It can also let parties take part without becoming customers.

A market of many relationships

Every party in delegated authority deals with many others, and the numbers are large.

The relationships also run in more than one direction, because one firm often holds more than one role.

Any system for this market has to hold all of that. The question is whether it holds the relationships as data, or leaves them to email and memory.

What the one-to-one portal gets wrong

The first problem is the one brokers complain about. Each portal has its own login and its own form, so the broker enters the same client again for every market.

The survey evidence is consistent. In the Ivans survey, 74% of agents named rekeying as their main workflow problem, 42% cited inconsistent underwriting questions and 37% cited multiple logins. Ninety per cent said friction had led them to reduce business with a carrier (Ivans, 2026). In a UK survey, two thirds of brokers said they visit up to 20 insurer sites a week to produce quotes (Applied Systems, citing Insurance Times).

The deeper problem is the data model. A portal built by one insurer records the broker as a user of the insurer’s system. Four things follow.

  1. The client is recorded by the wrong party. The broker’s client becomes the insurer’s submission. The broker cannot see that client’s other policies in the portal, cannot reuse the answers for another market, and keeps its real client record somewhere else.
  2. The broker cannot compare markets in it. A portal shows one market’s quote. Comparing terms, which is part of the broker’s job for the client, happens outside every portal, in email and spreadsheets.
  3. The broker’s own structure is set up again by every insurer. Head office, branches and authorised representatives are entered separately in each system, often as a flat list of users. When a branch joins another group, or a book moves to another broker, each insurer makes the change by hand.
  4. Each insurer pays to build and run its own portal. Twenty markets build twenty portals for much the same tasks. That is the per-client build cost described in Perspective 27, Platform, not product, repeated across the market.

None of this depends on how well a particular portal is designed. A good portal still holds one relationship, and the broker deals with many.

One market on the screen can be right. One market in the data model is the mistake.

Parties, relationships and roles

The alternative is to record the market as it is. A platform built this way holds three things.

Each party then sees the same records from its own side.

PartyWhat it sees
BrokerIts clients and its whole book, across every market it deals with, filtered by market when it chooses
UnderwriterWork from every broker and channel in one queue, limited to its own authority
AgencyEvery binder it holds, with premium against limits and the reporting due to each capacity provider
Capacity providerEvery agency it backs: premium bound, authority used, referrals and reporting
The broker keys the client once, not once per market Top: with one portal per insurer, a broker links to three separate portals, with three logins, the client keyed three times and quotes compared outside every portal. Bottom: with parties and relationships, the broker holds the client record once and is linked to Insurer A and Agency B by appointments and to Insurer C by a marketplace listing; Agency B is linked to a capacity provider by a binder. The broker keys the client once, not once per market One portal per insurer Broker client in its own system Insurer A portal Agency B portal Insurer C portal 3 logins client keyed 3 times quotes compared outside every portal Parties and relationships Broker client record, kept once Insurer A Agency B Insurer C Capacity provider appointment appointment marketplace listing binder Each line is a record with its own terms: products, commission, authority and what each side may see.
One portal per insurer, compared with one record for each party and one for each relationship.

The client is entered once, by the party that owns the relationship with the client. Every market the broker deals with is a relationship on the broker’s record, not a separate system.

What the model makes possible

Once relationships and roles are data, several things that are separate projects in a portal model become ordinary use of the same records.

None of these needs a new system for each pair of parties. Each is built once and works for every relationship that uses it.

Open to parties who are not customers

A many-to-many model has one more consequence: a party does not have to be a customer to take part.

Any role on the platform can be filled by a guest. A guest works through a link limited to one task and a set period, and every action it takes is logged. A guest is still a party in the model, with a verified identity, not an anonymous visitor. If it later becomes a customer, its history is already attached and nothing is entered again.

RoleWhat a guest can do
Underwriter or marketReceive a risk and quote on a standard template, without joining the platform
BrokerSubmit by email or online form, then view, accept and download documents by link
Capacity providerSee the agencies it backs, read-only, and respond to requests for indicative appetite
Client or memberComplete a proposal or renewal declaration online
Claims handler, assessor or surveyorUpload a report against a claim or a risk
Auditor or regulatorRead the records in scope for a set period
Wording reviewerComment on the standard wordings

Guests are one part of keeping the platform open. Five other choices matter as much.

Two things stay closed. Guests and other systems can prepare work and answer questions, but every quote, bind or decline is made by a named person acting within an authority. And a market’s rating logic is never released: others see the prices and ranges it produces, not how it produces them.

The objections

“Insurers want control of their brokers, products and data.” They keep it. Each insurer decides which brokers it appoints, which products each may write, the questions, rules and rates, and the authority held by each broker and underwriter. Its quotes, policies and decisions stay in its own records. What changes is that the broker’s client record stays with the broker, and the insurer holds the risks brokers bring to it.

“A single-insurer arrangement does not need this.” For the screens, that is true: a broker appointed by one insurer should see one market. For the data model, it is not. The broker will add a second market, a group will buy the brokerage, or the agency will add a capacity provider. In a one-to-one portal each of those is rework; in a shared model each is a new relationship record.

“A shared platform puts confidential data at risk.” A shared platform does not have to mean a shared database. Each party’s records can be held separately, every exchange between two parties can be explicit and logged on both sides, and each market can make its rating, referral and bind decisions in its own records. A one-to-one portal often collects more than it needs: the broker’s client file, its staff list and its branch structure, held by every insurer it deals with.

“Some insurers will still want a portal under their own name.” A platform can provide one. The test is whether it is built on the same parties and relationships, so that the brokers it serves keep their own records and can deal with other markets from the same place.

The market is already moving this way. Lloyd’s built its Blueprint Two programme on a Core Data Record: one standard set of data for a risk that brokers and carriers share, so it can move through the market without being keyed again (Lloyd’s, March 2021).

The questions to ask

When an insurer or agency considers a broker portal, the useful questions are about relationships, not screens.

  1. Whose record is the client: the broker’s, or the insurer’s?
  2. Can the broker deal with its other markets from the same place, or only with this one?
  3. What happens when a relationship changes: a second capacity provider, a brokerage merger, a branch moving to another group?
  4. Is each person’s authority set by product and by relationship, and can a capacity provider see what it needs without a separate report?
  5. Can a broker, market or capacity provider that is not on the system still take part, and join later without its history being entered again?

If the answer to each is a new project, the portal is built for one relationship in a market of many.

Where Cuttleflow sits

Cuttleflow is built on parties, relationships and roles for that reason. Brokers, agencies, insurers and capacity providers each work from their own records, and each relationship between them carries its own terms. Parties that are not customers can take part as guests. The broker workspace, the Cuttleflow Marketplace and the views for capacity providers are uses of the same model, not separate systems.

The underwriter workspace, and the broker workspace for brokers an insurer appoints, are being tested ahead of a first client go-live. The Cuttleflow Marketplace is not yet open for live business, and each class opens only when its conditions, including licensing advice, are met. Capacity provider views, changes of broker of record, the recorded change of role and most guest access are designed and shown in a gated demonstration; they are not yet built.

Sources

  1. Re-keying and workflow friction are costing carriers placement, Ivans survey finds, Risk & Insurance, 28 August 2026, reporting the Ivans 2026 Agency-Carrier Connection Report (more than 700 US independent agents)
  2. Applied & Arch Insurance: building a more digitally connected insurance ecosystem, Applied Systems Europe, citing the Insurance Times Digital Adoption Report
  3. Who owns Australia’s underwriting agencies after a year of deals, Insurance Business, 23 October 2026, citing IB’s Brokers on Underwriting Agencies report
  4. How to place risk at Lloyd’s, Lloyd’s (Australia)
  5. Lloyd’s consults on the first iteration of its Core Data Record under Blueprint Two, Lloyd’s, 11 March 2021

This piece describes a software model in general terms. It is general information, not legal advice. Cuttleflow Pty Limited trading as Cuttleflow Systems is a software provider. It does not hold an Australian financial services licence and does not issue, arrange or advise on insurance. Brokers and underwriters advise, quote and bind under their own licences.

Cuttleflow Systems · Perspective 29 · 33°53′S · 151°16′E · Sydney