Two people working out a decision tree on a whiteboard

Four questions, not a list of forty-six

Build the questions your agency would ask anyway, once, as a flow. Every producer then asks them the same way, and the answers narrow the whole library down to the applications this client actually needs.

The problem is not the forms. It is knowing which forms.

A new producer faced with a library of insurance types either asks the client to choose — which they cannot — or picks what they picked last time. Neither is a process, and both leave gaps that turn up at renewal.

What answering one looks like

A commercial client, four questions in. Each answer is doing two things: narrowing what gets recommended, and deciding what gets asked next.

  1. Is this for a person or a business?

    Business

    Splits the whole tree in two, and filters which insurance types can appear at all.

  2. Do they own or lease the premises?

    Lease

    Rules out one property application and rules in another.

  3. Do they have vehicles on the road?

    Three vans

    Adds commercial auto, and asks a follow-up it would otherwise skip.

  4. Do they hold a trade licence?

    Yes — contractor

    Adds the licence bond, which is the one most often forgotten.

What it recommendsGeneral liability · Property (tenant) · Commercial auto · Licence bond

Four applications, started together, sharing every answer they have in common — which is where the ask-once questionnaire takes over.

The client cannot tell you which forms they need. That was never their job.

They can tell you they lease the unit, that two vans are on the road, and that one person does the books. The flow turns those answers into the applications — so the newest producer in the office asks what the most experienced one would have asked.

You build it, and you can change it on a Tuesday

01

Drag the questions into place

A visual editor: question nodes, answers as the lines between them, and insurance types as the ends. No rules language, no support ticket to change a question.

02

Personal, business, or both

A flow carries a category, and the insurance types it can reach are filtered to match. A personal-lines flow cannot accidentally recommend a commercial policy.

03

Your flows, not ours

Flows belong to your agency. Two agencies on the same platform ask entirely different questions, because they sell to entirely different people.

04

And a producer who already knows can skip it

The wizard has a straight path: pick the type and go. The flow is there for the ones who need it, not as a toll gate on everybody.

It narrows the paperwork. It does not give advice.

The flow decides which applications to start, from questions your agency wrote. It does not recommend cover, it does not price anything, and it is not a substitute for a licensed person looking at the risk. What it removes is the blank page, not the judgement.

Build one and see

The demo drops you into an agency with flows already in it, so you can walk one as a producer and then open the editor and change it.

Try it free