Cycle Time as a North Star

There is one number I watch more closely than almost any other when a new Mercury implementation goes live: average submission-to-bind cycle time.

It sounds operational, and it is. But cycle time is also the cleanest proxy I know for whether a core system is actually working for the underwriters who live in it every day. If submissions are piling up, if producers are chasing quotes by phone, if the same risk is being re-entered into three different tools before it gets to a decision -- the cycle time number tells you before anything else does.

When we designed the Mercury Policy and Claims Administration System, we did not approach underwriting workflow as a series of isolated screens. We approached it as a single, configurable pipeline: submission comes in, the rating engine calculates the premium against the filed plan, third-party data calls fire through the API layer without the underwriter leaving the screen, and the work item lands on the right queue with the context already attached.

That sounds like a small architectural decision. It is not. It is the difference between an underwriter deciding on a risk in fifteen minutes and an underwriter chasing information across tabs for two hours before the real judgment work even begins.

Our clients who use Mercury's configurable workflow have told us about hours reclaimed per underwriter per week. I trust that number more than I trust a marketing promise, because it comes from people watching their queues shrink in real time. But the more important reclaimed asset is attention. Experienced underwriters have judgment that no platform replaces. What the platform can do is clear away the noise so that judgment gets applied to the risks that actually need it.

The same principle applies to our MGA clients running multi-carrier programs. A producer submitting a risk to an MGA does not want to know which carriers get the submission, in what order, through which secondary portal. They want quotes back quickly. Mercury's multi-carrier quoting takes one submission and runs it against participating carriers through the API layer, then surfaces comparable quotes in a single screen. The rekey is gone, and with it the largest single contributor to cycle time in that distribution channel.

None of this is magic. It is deliberate architecture, applied to a problem the industry has been working on for decades. What I think the Mercury Platform gets right is refusing to treat underwriting cycle time as a downstream byproduct of other choices. It is a design goal, and every feature we ship gets measured against it.

If you are evaluating a core system and you are not already tracking cycle time by line, by underwriter, and by producer, that is where I would start. You cannot shorten what you do not measure. And once you are measuring it, the conversation about what a modern platform actually has to deliver becomes a lot more concrete.

-- Sean Pitcher, CEO, Quick Silver Systems, Inc.