Brit has integrated its cyber proposition into Acturis Package, the module brokers use to build bundled commercial lines placements. The change, announced October 19, 2026, is small in mechanical terms and large in conversational ones: a broker quoting a commercial package now encounters Brit’s cyber product inside the same workflow, before the placement is complete, rather than having to start a separate process to raise it.
Brit first went live on Acturis in May 2026, via CyberNow, a standalone cyber route. That launch served brokers who were already looking for cyber. The package integration is aimed at the other kind of renewal — the one where cyber was never on the agenda, and where a separate process was all the excuse the conversation needed to wait another year.
The gap the prompt is aimed at
More than 60% of UK small and medium-sized enterprises have no cyber insurance, according to GlobalData’s 2025 UK SME Insurance Survey. Uptake is lowest among the smallest businesses — precisely the firms most likely to be insured through a commercial package placement rather than a bespoke programme. The protection gap, in other words, sits exactly where the package workflow runs.
Access is not the only barrier, and nobody in this story claims it is. Research published by Markel UK in October 2026 found that nearly four in ten UK SMEs without cyber insurance believe they face a low risk of attack. The same research found all 16 brokers in its sample — a deliberate mix of account executives advising smaller SMEs and senior specialist brokers, including multiple members of the BIBA Cyber Committee and its chair — reporting difficulty comparing cover across providers. Removing a layer of friction does not settle either of those problems. It removes one layer of them.
What actually changes at renewal
A standalone cyber placement asks the client to say yes twice: yes to the conversation, and then, later, yes to the cover. Every step between those two yeses is a place to defer — a diary problem, a budget meeting, a “next renewal.” A prompt inside the package workflow collapses that into one decision made while the package is being built, in the room, against the rest of the programme the client is already buying. Declining is still possible. It just becomes an active choice instead of a default outcome.
That is the whole mechanism, and brokers should be clear-eyed about it. “This is particularly important as demand continues to grow among firms of all sizes for protection against cyber risks, amid an increasingly volatile market landscape,” said Adelle Gruber, Brit’s class underwriter for cyber. Growing demand is the carrier’s framing. The broker’s version is simpler: the question now gets asked at the one moment in the year when the client is already deciding what risk to carry.
What the prompt does not do
A workflow prompt is not advice, and three parts of the cyber conversation still belong entirely to the broker.
The limit. A limit chosen to close a screen is not a limit sized to a client. The number has to come from the client’s revenue, its dependencies, and what an interruption actually costs it per day — the dependent business-interruption question this desk keeps coming back to, most recently in the aggregation lesson in SIMEX26: one provider’s outage reaching thousands of balance sheets at once is the loss scenario a package limit has to survive.
The comparison. Brit is not the only insurer on the Acturis cyber panel — CFC, Cowbell, and Markel all have a presence on the platform, and a panel exists so that brokers have a choice at the point of quotation. But Markel’s own broker sample says comparing cover across providers is the hard part, and a prompt inside one workflow does not compare wordings, sublimits, and exclusions for you. The habit this desk flagged in the aggregation lesson in SIMEX26 — premium easing while terms quietly narrow — applies here in full.
The exposure conversation. The prompt knows the client buys a package. It does not know which systems the client runs, which vendors can take it down, or whether its cyber hygiene survives an underwriter’s follow-up questions. That inventory is still a conversation, and it is still the broker’s.
When the prompt appears: the by-hand list
None of this requires new process — it requires having four things in the file before the renewal meeting starts, so the prompt lands on a prepared conversation instead of an improvisation.
- The dependency shortlist. The client’s two or three vendors whose failure stops the business — the systems the dependent-interruption grant will actually be tested against.
- Today’s position, stated plainly. Whether the client currently has no cyber cover at all (the GlobalData majority), a standalone policy the package prompt must not quietly duplicate, or an expiring limit set in a different market.
- A limit with a reason attached. Not the default on the screen — a number the broker can defend in one sentence, tied to interruption cost per day and the recovery the client could not self-fund.
- The declination, documented. If the client still says no, the file should show the question was asked inside the package build and answered on the record — the same evidence trail that protects the broker when the uninsured loss arrives.
The honest limit of the move
Embedding cyber in the package workflow raises the question earlier and more often. It does not answer it. The risk the move creates is the opposite of the one it solves: a client who would never have bought cyber through a separate process may now buy a thin version of it by default — a low limit, a sublimited dependent-interruption grant — without the conversation that makes the cover worth having. Whether the prompt becomes protection or paperwork is decided by what the broker does in the thirty seconds after it appears.
The general lesson travels even where this specific platform does not: covers get discussed in the order the workflow presents them. A cover that requires its own process will be deferred by busy people acting in good faith. A cover that appears while the package is being built gets a decision. Brokers do not choose the workflow their platforms hand them — but they can notice which questions it asks, and be ready with answers for the ones it doesn’t.