Our approach
Make product changes with less repeated work.
When a product changes, the same decisions are interpreted and rebuilt again in quoting, pricing, and policy systems, then reconciled through testing. Our approach is to capture the agreed product definition in a model you own and reuse it across the connected systems. The aim is to reduce repeated implementation work and shorten the path to launch.
Agree the product. Reuse the knowledge.
Our Common Models product definition gives your teams a shared reference for coverage, policy changes, rating, and negotiated pricing. Each connected system is checked against the same agreed terms and expected premiums.
01
Coverage choices
What can be offered and on which terms, agreed once, so the same product decision is not re-explained to every vendor.
02
Policy changes
What changed and when it took effect, with the effective dates and prior values needed for the agreed renewal and endorsement scenarios.
03
Rating
The inputs sent to your existing Excel rater or rating service, the rated premium it returns, and the supporting worksheet for review.
04
Negotiated pricing
How negotiated premiums, minimums, fees, and customer-model factors apply after rating to produce the agreed price, with the rated premium and adjustments visible.
We start with the systems you already run and the responsibilities they keep. The work is to agree what carries between them, build the connection, and check that the premiums agree.
Rating and negotiated pricing
Carry the pricing decision forward.
Your existing Excel rater or rating service calculates the rated premium. CovCloud then applies negotiated pricing adjustments, keeping the original result and subsequent adjustments visible. Submit the selected indication to your policy administration system for its required binding workflow.
Underwriters can review negotiated amounts, minimums, and fees alongside the original rated premium. The aim is to preserve pricing flexibility while reducing repeated E&S customizations in the policy system.
Model-Driven Pricing connects your own models to this layer. Their factors apply after systematic rating, within the calculation rules and bounds agreed for your product. The worksheet retains technical premium, model-adjusted premium, and agreed price, with the model version and returned factors available for review. We agree how unavailable or out-of-range results are handled.
AI and expert review
AI drafts. Experts review. Approved rules run.
AI helps turn source material into draft product definitions. Your insurance experts review the meaning, resolve the open questions, and approve the rules. Your rater remains the source of rating logic. CovCloud executes the approved pricing adjustments through deterministic calculations.
Specialist time goes to the decisions only they can make, not to re-reading the same rules for each system. We measure the benefit as total effort and rework through implementation, including the expert review itself.
Common questions
The E&S workbench, in practice
We are building CovCloud around your existing rater and underwriting workflow. Here is how rating, negotiated pricing, comparison, and the policy-system handoff fit together, and what to agree for a pilot.
Who is the E&S workbench for?
For carriers and MGAs whose underwriters move between Excel raters, pricing spreadsheets, and policy systems to develop an indication. CovCloud brings rating, negotiated pricing, and transaction comparison into one underwriting workspace.
Our product focus is General Liability, Commercial Property, Commercial Auto, Inland Marine, and follow-form Excess Casualty, across new business, renewals, and endorsements. The exact coverage, state, and transaction cases are agreed for your program.
Can we keep our existing Excel rater or rating service?
Yes. Your existing rater remains the source of rating logic and supplies the rated premium. We scope the connection around its inputs, outputs, and the cases your team needs to review.
Excel rater conversion is an option where a rating service is needed. It preserves the established rating logic and is checked against approved workbook cases, with response times and the next rate change included in acceptance. Conversion is not a prerequisite for every pilot.
How does negotiated pricing work?
Your rater calculates the rated premium first. Underwriters then apply negotiated premiums and product-specific adjustments in the workbench, within the rules agreed for your product. Minimums and fees are part of that scope.
The original rated premium, subsequent adjustments, and agreed price stay visible for review. The aim is to give underwriters pricing flexibility while reducing repeated E&S customizations in the policy system.
Can we use our own pricing models?
Model-Driven Pricing connects your own models to supply factors after systematic rating. The worksheet retains technical premium, model-adjusted premium, and agreed price, along with the model version and returned factors.
For the pilot, we agree model access, permitted factors, calculation order, bounds, response-time needs, and what happens when a result is unavailable or outside those bounds. Your team supplies the model and reviews how its factors affect pricing.
What does rate and premium comparison show?
It brings selected rates and premiums together side by side: expiring against renewal, or a current policy against a proposed endorsement. The comparison shows the reported values and their differences alongside the applicable terms and pricing basis, including records from different systems.
Missing values and unmatched records are flagged for review. This comparison does not attribute causes, isolate rate effects from exposure or coverage changes, or provide portfolio analytics.
Where does binding happen?
In your policy administration system. The workbench submits the selected indication’s risk details, coverage terms, and pricing results through the connection agreed for your program. Your policy system continues its required validations and binding workflow.
The integration scope includes confirming receipt and making validation failures and pricing discrepancies visible for review. We test that handoff against representative cases with your technology team and implementation partners.
How is the workbench delivered and maintained?
Through a fork-and-build model: you start with your own copy of the workbench codebase and adapt it to your products, raters, and underwriting workflow. Your team controls testing, releases, and which CovCloud updates to adopt. You will never be forced to adopt a new CovCloud version.
Documentation and tools for AI-assisted development help your team maintain and extend it. Codebase licensing, hosting, operations, security updates, maintenance, and support responsibilities are agreed in the written scope.
How do we start and judge whether it is worthwhile?
Start with one existing E&S program, its rater, and representative new-business, renewal, and endorsement cases. We agree what can be demonstrated, what needs configuration or integration, and the acceptance measures, budget, timeline, and time needed from your underwriting, actuarial, and technology reviewers.
Run the same cases through your current workflow and the pilot. Compare time to a usable indication, underwriting effort, premium agreement, repeated data entry, and handoff discrepancies. Include setup and integration effort, then measure one subsequent change to assess the ongoing cost.
Let’s talk about your E&S program.
Tell us where disconnected spreadsheets and policy-system customizations slow your E&S team down. We scope a pilot around your program, rater, and underwriting workflow.
Discuss your project