Mercury Configurable Rating: Test One Change Two Ways

When I look at a rating change, I want to see two quotes. The first should move by exactly the amount the product owner expects. The second should stay put. A demo that shows only the first quote answers half the question: it shows that the new rate applies somewhere, but not whether it applies where it belongs.

Mercury includes configurable rating. For a small carrier with a product manager and a few people who know the rating worksheet by heart, those two quotes make a useful starting point. You can evaluate the capability against arithmetic your team can check, rather than asking everyone to take a premium on a screen at face value.

Put the rule on one sheet of paper

Consider a fictional program with two territories, North and South. For this exercise only, the base amount is $500. North currently uses a factor of 1.10. The proposed change takes it to 1.20. South uses a factor of 1.00 and is outside the change. Leave fees, minimum premiums and other adjustments out of this first example so there is only one reason for a result to move.

Write down the expected results before the demonstration. At the old factor, North comes to $550. At the new factor, it comes to $600. South comes to $500 both times. These are invented figures for checking the calculation, not Mercury defaults or proposed rates for an actual product.

  • North: same inputs except for the revised factor; expect a $50 increase.
  • South: same inputs and same factor; expect no change.

Watch the quote that should stay put

Bring both examples to a Mercury demonstration. Ask the presenter to walk through how the rule would be represented for your program and to show what happens to each quote. Give someone other than the person driving the demo the worksheet. That person should be able to say what number they expect before the result appears.

Suppose North comes back at $600, as expected, but South also rises by $50. Showing just North would have made the exercise look complete. South tells you to pause and check whether the proposed change was applied more broadly than intended. If North stays at $550 instead, check which factor the example actually used before drawing a conclusion about the calculation.

Add one complication from your own book

Once the simple case makes sense, replace one simplification with a rule that matters to your business. For example, suppose your worksheet calls for a minimum premium. Choose a sample where the calculated amount falls below that minimum. Write down both the calculated amount and the amount you expect to quote. Ask to see how that example would be handled for your program.

The distinction matters when a final premium looks right for the wrong reason. A minimum can mask a difference in the underlying calculation. Keeping both numbers on the worksheet lets the product owner ask a precise question: did the factor produce the expected amount before the minimum was considered? It is easier to resolve that question with one example than with a stack of unexplained totals.

Leave with examples your team can use again

Keep a copy of the inputs, the expected amounts and the reasoning behind each one. Note which cases you saw demonstrated and which still need an answer. A colleague who misses the meeting should be able to pick up the worksheet, calculate the two original quotes and explain why only North changes. If they cannot, improve the description of the rule before adding more cases.

You do not need to prepare an entire rating manual for a first conversation. Choose one change your team understands well, one quote inside its scope and one just outside it. Explore Mercury and schedule a configurable rating demo with Quick Silver Systems. Bring the worksheet; start with the quote that should stay the same.

Mercury Configurable Rating: Test One Change Two Ways
P&C Insurance System Overlay

SCHEDULE A DEMO