
Ask once. Not once per form.
A commercial client needing general liability, property cover and a licence bond is three applications asking largely the same questions. Insurance Flow asks each one a single time and writes the answer to every form that wanted it.
One answer, four applications, at the same moment. Nothing is retyped and nothing is left to disagree with itself later.
Six questions, asked four times
Here is what a client answers today when three applications and a supplemental all want the same details. Nobody is being slow. The format is.
- Legal business name×4
- Trading address×4
- Entity type×4
- Years in business×4
- Annual payroll×4
- Number of employees×4
And the third time somebody types their payroll figure, it is a slightly different number. That is not carelessness either — it is what happens when you ask the same thing four ways on four days.
What they get instead
A link, and no account
They click it and they are in. No password to choose, no email to verify, nothing to remember next time. Logins are for your staff; clients never have one.
One set of questions, in plain English
Not four forms stacked up. Every field that appears on more than one application is asked a single time, grouped into sections that make sense to a person rather than to an underwriter.
Each answer lands on every form that wanted it
Their entity type goes onto the general liability application, the property application and the bond at the same moment. One answer, four boxes, no retyping and nothing to reconcile afterwards.
It works on the phone they actually opened it on
Which is the whole difference between a form that comes back today and a PDF attachment that gets remembered next Tuesday.

Four fields, then it is their turn
A producer starts an application with almost nothing — new client or returning, personal or business, and how to reach them.
Choosing business keeps the commercial cover on its own record rather than mixed into the owner’s personal file, which is the distinction that causes trouble later if nobody makes it at the start.
Everything after that is the questionnaire above, answered once.
And on your side
The same record, from the desk it is worked at.
- One profile per client
- Every application they hold, in one place, with the answers already shared between them. Add a fourth policy and the questions it has in common are already answered.
- You can fill it in yourself
- Some clients would rather talk. Start the application, work through it on the phone with them, and it behaves identically — the sharing is in the record, not in who typed it.
- Change one answer, change them all
- They move premises. Update the address once on the profile and every application carrying it updates with it, instead of three forms quietly disagreeing.
- Sensitive answers are encrypted
- Dates of birth, social security numbers and medical answers are encrypted at rest and decrypted only for the request that needs them. Sessions time out on their own after nine idle minutes, with a warning before it happens.
More on how that is done, and what is audited:Security →
What is not finished
Insurance Flow is still in development, and one part of this is unbuilt: choosing“send to client” creates the application, but it does not yet send the intake email on its own. Today you send the link. It is on the list, it is not pretending otherwise, and everything else on this page works now.
See it from the client's side
The demo signs you in as an agency with invented clients, so you can send yourself an intake link and answer it as they would. No card, and it deletes itself after a week.
Try it free
