InsureFlow
A broker platform for Canadian specialty lines. A submission is accepted, referred or declined the moment it lands. From there the file moves through signature, binding, issue and payment as one governed record — and a broker cannot step around any part of it.
Six stages
One record
One flow, and no way around it.
Every risk moves through the same sequence. The stage names below are the words the system itself prints on the record, not a marketing summary of them.
Enforced
Not documented
The part a capacity provider actually cares about.
Delegated authority is only worth what you can prove about it. In most brokerages the limits live in a policy manual and depend on people remembering them under pressure.
While a risk is referred, the system shows no premium at all — and the broker cannot release their own referral.
What the system does
- Decides accept, refer or decline at submission
- Prints the referral reason on the record, verbatim
- Withholds every premium figure on a referred risk
- Records who reviewed it, and when
- Recalculates a mid-term adjustment pro-rata for the days remaining
- Opens renewal on a fixed window, 60 days before expiry
What a broker cannot do
- See a premium on a risk that has been referred
- Release their own referral — only an underwriter can
- Change a premium the decision has set
- Sign a proposal on the client's behalf
- Bind anything that has not been signed
These are not settings that can be switched off in a busy week. They are the shape of the software.
rules
As data
Appetite, written down for once.
Every class carries its own eligibility questions, referral triggers and decline conditions. They are configuration, not code, which is why a new class does not mean a new build.
Triggers that fire on the answer, not the reader
A prior theft on a personal articles risk forces underwriter review. A lithium battery risk where the applicant is the manufacturer or the importer is referred individually, every time. The rule does not depend on whether anyone noticed the answer.
Declines with reasons attached
Where a risk falls outside appetite, the record carries the numbered reasons rather than a bare refusal. A broker can take that back to the client, or back to the market, without a phone call.
Depth where the class demands it
Some classes need eleven questions. A farm risk needs closer to seventy — heating, wiring, distance to a fire hall, tank data, livestock, agritourism, environmental exposure. The form goes as deep as the risk does, and no deeper.
Configuration
Not code
The classes that still run on email.
Canadian MGAs write the risks standard markets avoid, and most of that work still moves by attachment, spreadsheet and phone call. These are the shapes the platform is built for.
A class is added as configuration — appetite, questions, rules and documents. Not as new software. Ten are configured today.
After the bind
Most of the work happens after the policy is issued.
Quoting gets the attention. Servicing is where the hours and the errors actually are, so it is built out rather than bolted on.
What it is not
Yet
What InsureFlow does not do.
A vendor who only lists strengths is asking you to find the gaps during implementation. These are ours, stated before you ask.
Rate versioning
Premiums are produced by the platform, but a quote does not yet pin a numbered rate version you can reproduce years later. If you rate against filed tables and need that lineage for an audit, it is a build, and we will say so before you sign.
Carrier bordereaux
Policy and billing data is exportable, but scheduled bordereaux in a carrier's own format are not generated today. For a binder that reports monthly, that gap is worth costing before anything is signed.
Cancellation methods
Mid-term cancellation is recorded on the file; the return premium is calculated by the broker rather than by the system. Our return premium worksheet does that arithmetic in the meantime, and it is free.
Payment processing
Payments are recorded, not taken. There is no card processor behind the platform today, so money still moves the way it moves in your office now.
Canada
Canadian, as a requirement rather than a preference.
The platform and its data are built to stay in Canada. That is a design constraint we hold ourselves to, not a claim about a hosting region we happened to pick.
Bring one risk
Bring a live submission.
Send one real risk and your appetite guide. We will configure the class and take it from intake to bound while you watch, using your rules rather than a demo dataset. If you would rather start smaller, the two-week operations diagnostic is on the main record.
IQ Spark Consulting Services Inc. builds software and provides training and advisory services. This page describes a software platform. It is general information only — it is not insurance advice and it is not an offer of coverage. Appetite, limits, deductibles and referral rules are configured by the organization operating the platform, and policy wordings are always the authority.
© 2026 IQ Spark Consulting Services Inc. · info@iqspark.ca