An agency office with producers working at their own desks

Who logs in, and what they can reach

One client's submission is the easy part. This is the part you have to live with: producers, permissions, carriers, and the question of whether anybody outside your agency could ever see a thing.

Three kinds of login, and one hard wall

ProducerTheir own clients and applications
Starts applications, walks the flow, fills forms in or sends the client a link, and works the unified questionnaire. What they can reach beyond that is set by the agency.
Agency adminEverything in your agency
Adds producers and sets what each can do, builds the flows, builds the forms, manages carriers, and decides the agency-wide switches — including whether anybody may delete a client at all.
UsThe platform, not your data
Super admin exists to add agencies and maintain the shared form library. Agency isolation is middleware on every request, so it is not a matter of somebody remembering to filter.
The agency admin dashboard, showing every application across the agency and which need attention
A producer's own dashboard, showing only their applications

The same platform, two logins. The agency admin sees the whole book; the producer in front sees their own. Neither is a filtered view of the other — the separation is underneath.

Your agency, and nobody else's

Insurance Flow holds several agencies. Yours is separated at the request layer rather than by a query somebody has to remember to write — the check runs before the code that fetches anything does. A producer in another agency cannot reach your clients, your applications, your forms or your flows, and there is no setting that would let them.

Forms are the one deliberate exception, and it is opt-in in the other direction: a form can be yours or it can be part of the shared library everybody starts from. Nothing you build becomes shared on its own.

The things that matter on a Tuesday

01

Deleting a client is off until you turn it on

It is an agency-wide switch, controlled by the admin, and it ships off. Nobody removes a client and their whole history because a button was where they expected a different button to be.

02

Carriers are yours to keep

Who you place with, held in the platform rather than in somebody's head or a spreadsheet on one machine.

03

There is an audit trail

Who looked at what, and when. Not a feature anybody enjoys buying, and the first thing asked for when something goes wrong.

04

Sessions end on their own

Nine idle minutes brings a warning with a sixty-second countdown, then it logs out. Because the screen a producer walked away from has social security numbers on it.

White label

It carries your name, not ours

Your agency name, your URL, your primary and accent colours — set once and applied to the client portal and to anything you embed in your own website.

A client filling in your intake never learns what it is built on, which is the way round it should be.

The agency settings screen: agency name, URL slug, and primary and accent colour pickers with a live preview of the client portal

What is not built yet

Insurance Flow is in development and these are the gaps a buying agency would find in the first week, so you may as well have them now:

  • It does not sync with AMS 360, or any other management system. It sits in front of one.
  • It does not push a submission to a carrier. It produces the forms; sending them is still you.
  • The agency settings page and the producer profile page are unfinished.
  • Choosing “send to client” creates the application but does not yet send the intake email.

Come and prod at it

Half an hour, screen shared, with your own lines of business in it — and an honest answer on anything above that matters to you.

Get in touch