You have what you think is a good – maybe great – idea for a product improvement. Maybe it’s a new option you want to provide; maybe it’s a brand new coverage or endorsement. But there are skeptics.

In your current system, it’s a big investment to make these changes to begin with. But what happens if – like the skeptics think – your big idea turns out to have unintended consequences? In your current system, that might be such an ugly scenario that you can’t move forward.

But what if your big idea is just what the bottom line needed? In your current system, because of the worry about what it would take to pull the changes, but still reflect and honor them where sold, you and your company may never find out. Another good idea lost before it ever had a chance.

What happens if – like the skeptics think – your big idea turns out to have unintended consequences?

Enter PolicyWriter and Grandfathering. First, making those changes to begin with is a snap. You can even prototype them easily early in the idea/design phase so your business community can more quickly settle on the exact change needed – including how it would look to end users and integrated systems. Then PolicyWriter allows you to easily configure “rollout” of the new big idea. So far so good.

Here’s where you really put the skeptics at ease though: If the changes don’t pan out the way anticipated, Grandfathering in PolicyWriter allows you to easily designate – all via configuration – that the particular new option, coverage or endorsement should be honored and remain on the policies where already sold yet no longer be offered for new policies or for existing policies that don’t already have it.

So let the good ideas roll! Take advantage of the PolicyWriter Challenge to see how fast your big ideas can become a reality.