Broker-it

Sign in with your Pivotal email

Checking sign-in…

Enquiries

Signed out

Notifications · demo

AmandaAB
Website form check — all clear.

4 enquiries received in the last 24 hours and all were logged. If a business day ever passes with zero enquiries, this banner turns red and Amanda gets a text — an enquiry can never silently vanish again.

Where these numbers come from

Loading the movement ledger…

INSIGHT not connected

Income & premium

Movements on the book

Retention

Pipeline

Breakdowns

Definitions used here — GWP is inclusive of GST; broker fee and commission are both exclusive of GST. Income counts new business, endorsements, upsells, renewals and renewal transfers; a cancellation is shown as income lost, not netted off. Retention counts a renewal transfer as retained — moving a client to a different underwriter is not losing them. Financial year runs 01/07 – 30/06. Year to date is the calendar year. All of these are ours to change — confirm each one with Amanda.

4enquiries · last 24h
3awaiting first contact
11this week
100%logged & accounted for

Website enquiries arrive pre-qualified from the adaptive intake — click one to see exactly what the broker receives. Use Log an enquiry for a phone call or a walk-in so it lands in the same funnel.

0active clients
0policies in force
0renewals · next 30 days
GWP written · 12 months

In the live build this is synced two-way with INSIGHT — the client book is the system of record; Broker-it reads it and writes activity back.

Click a card to open it. Status changes are written to the enquiry and logged on its activity trail, so the whole team sees the same board. Lost enquiries leave the board and stay on the Enquiries list.

The six-week trigger

Amanda: "trigger points six weeks before renewal to create pre-renewal tasks." At 42 days a renewal fires its pre-renewal tasks and starts moving through the email steps below. Anything sitting on TRIGGER DUE is past six weeks with nothing started.

Sending needs the mailbox
ClientPolicyRenewal dateDaysStepAdvance

Every renewal here is a policy in Pivotal's database with a renewal date in the next 120 days. Steps are the sequence Amanda described — pre-renewal email, review, terms to market, terms back, presented, renewed — and advancing one writes to the client's activity trail, so the whole team sees it. No client email sends without a broker approving it; nothing on this screen sends anything.

Why this screen exists

Amanda: "if you cancel a product with one underwriter because you can place it with a different underwriter it actually looks like a cancellation." Here a renewal moved to another underwriter is its own movement type — renewal transfer — and it counts as retained. A real cancellation cannot be saved without a reason.

Record a movement

Saved to this browser only in the preview. In the live build this writes to the movements ledger and the dashboard updates for everyone.

DateClientMovementProductInsurerGWP incl GSTIncome ex GSTDetailSource

Showing the 40 most recent movements. Source is recorded on every row — a figure keyed by a broker is never displayed as though it came out of INSIGHT.

Daily payment check — not running

The routine below is designed but not connected. It needs read access to INSIGHT's receipted/reconciled transactions and a way to produce a certificate of currency per policy — neither of which we have verified access to yet. Until then payments are marked here by hand.

Stub — no INSIGHT access

The routine Amanda described

Check INSIGHT for payments receipted and reconciled since yesterdayRequires: INSIGHT read access (not granted)
Mark the matching policies paid in Broker-itReady — the data model supports it today
Produce the certificate of currency and the receiptRequires: CoC generation in INSIGHT (not verified)
Send the client a thank-you email with both attachedRequires: mailbox access + Amanda's sign-off on sending without a broker press

Steps 1, 3 and 4 are blocked on access we do not have. Step 2 works now.

Before this can run unattended

A certificate of currency is a statement to a third party about a client's cover. Getting it wrong is a real problem, not a cosmetic one.

Confirm the CoC always reflects INSIGHT at the moment of issue, never a cached copy in Broker-it.
Decide whether the thank-you email sends automatically or waits for a broker press. Default in this build: it waits.
Agree what happens on a part-payment or a payment that reconciles against the wrong policy.
Licensee sign-off (BBN) on an automated client-facing email that carries policy documents.
ClientPolicyGWP incl GSTPaymentReceipt refCertificate of currencyThank-you email

Every policy in force in Pivotal's database, with the payment and certificate state the database holds. "Receipt ref" is the INSIGHT reconciliation reference — blank until INSIGHT is connected, and never invented by the app.

ClientTypeInsurerStageLast movement

Click a claim to move it along or add a note. Stage changes and notes are written to the claim and to the client's activity trail. Anything without movement for 5+ business days gets flagged to chase — you hear about the hold-up before the client does.

Triage — clear the inbox into work

Every email is something you clear, do later, hand to someone, or turn into work. Nothing sits in a personal inbox — once it's a work assignment it's on the board, against the client, visible to the whole team. This reads Pivotal's Microsoft 365 mailbox — a sync that has not been built yet, so nothing arrives here.

Mailbox not connected

Select an email.

DueWork assignmentClientTypeStatusNext task

These are the processes Charlotte walked through in Karbon, rebuilt as templates. Starting a work assignment from a template drops in every step with its due-date offset. Edit a template and every future item picks it up.

This is what your client sees

A preview of the client portal inside Broker-it, so you can walk it before a real client does. Live, it sits on its own URL with magic-link sign-in and each client can only see their own file. Anything a client saves here lands in their profile — and every proposal form pre-fills from it.

Live sign-in needs the database + BBN sign-off
Enter it once

Amanda: "I don't want to repeat the same thing all the time… if we send them four forms they're already pre-filled with the client's basic information — ABN, turnover." Load an underwriter's blank proposal form, map it once, and every client's details fill themselves from then on. The client only answers what we don't already know.

Sending needs the mailbox

Form library

FormProductQuestionsAuto-fillable

The app reads the form's own fields and matches them to the client profile automatically. Mapping is a one-off per form — after that it fills for every client. The mapping is saved to the shared library for the whole team; the blank PDF itself stays on the machine that added it until document storage is set up.

Build a proposal

Channels

Direct messages

Messages are saved to the shared database, so the team chats across devices under the same logins. Nothing here is visible to a client.

Import an INSIGHT report

Until the INSIGHT API is available, the dashboard runs on the reports you already run. Export the Business Written Report from INSIGHT and drop it straight in — Excel (.xlsx) or CSV, no converting needed.

This stays in your browser. The file is read locally by this page — it is not uploaded, not sent to a server, and not stored anywhere but this device. Use Clear below to remove it.

Drag the report here or Business Written Report — .xlsx or .csv

What it reads

INSIGHT columnUsed as
Transaction TypeMovement type — New Business, Renewal, Renewal Transfer, Endorsement, Cancellation, Reinstatement
Transaction DateMovement date (drives every period on the dashboard)
Client Name · Policy NumberClient and policy the movement belongs to
Insurer · Class of RiskThe two breakdowns Amanda asked for
Gross Insurer PremiumGross written premium (incl GST)
Broker Fee (excl. GST) · Broker Commission (excl. GST)Income ex GST
Sales TeamBroker the movement is attributed to

The report's "Sales Team :" group headers and the grand-total row are skipped — importing them would double-count the whole book. Every imported row is marked as sourced from an INSIGHT report, so a keyed correction can never be mistaken for system data.

Network charge

Amanda put this at "about 9%" (Loom, 12/08/2026). The dashboard shows the charge and the net to Pivotal alongside gross income, so the income figure is what actually arrives rather than what was billed. The exact basis still needs confirming — whether it applies to commission only or to total income — which is why it's a setting rather than a fixed number.

Users, roles & policy approval levels

UserRolePolicy approval levelStatus

Roles: Owner — full access including income figures and these settings · User — works the book within their approval level · User Admin — manages enquiries, payments and client records, no binding authority. Approval levels cap the premium a user can bind without the Owner's sign-off. In production both are enforced in the database (row-level security), not just on this screen — changes here save locally in the preview.

Your website

Loading…

Change your team, contact details, opening hours, the numbers on the front page and your Google reviews — then press Publish. Your changes are saved as you type, but the public website does not change until you publish.

Preview the site ↗

Publishing takes about a minute to appear on the website. If you have the site open in another tab, refresh it to see the change.

Alerts & service levels

Alert channels:
Renewal reminders at: 906030 days

Settings save locally in this preview.

Notification events

Send a notification when:

These feed the Notifications panel in the top banner (and email/SMS per the channels above). The settings are saved; delivery is not wired yet, so no alert is actually sent — the watcher that raises them comes with the mailbox integration.

One card per platform. Configure opens that platform's settings; Test checks the connection and shows the honest result. Nothing here pretends to be connected when it isn't — an amber card means designed and modelled, but not yet talking to anything.

This is Broker-it — Pivotal’s own system behind the website: the internal side of the enquiry experience.

What's demonstrated

Added from Amanda's voice notes (11/08/2026)

What it isn't yet

Every screen reads Pivotal’s own database over your signed-in account. What is not connected yet: the Microsoft 365 mailbox, SMS alerts, and INSIGHT itself — movements reach Broker-it by importing an INSIGHT report or by a broker keying them.

Not built yet, and deliberately so: the voice assistant and Android Auto mode, the quote-slip/underwriter submission builder, the Shopify sales-by-country workflow, and call intelligence. Each of those depends on a system we don't have access to yet — the phone system, the mailbox, INSIGHT's API, or the underwriter market data. They're specified, sequenced and costed in the feature spec rather than faked here.