One record, and the workflows that run it
The modules are not separate tools that share a login. Each owns a stage of a broker's life with your business and writes to the same record, which is what makes the automation possible: a workflow can act on the whole relationship instead of waiting for someone to reconcile four exports first.
What that makes possible. “This broker read two franchise exit guides, ran the trail book calculator, enquired in January, signed in March, and has settled $4.2m since.” That sentence spans four modules. On separate systems it is a data project. Here it is one record.
The platform holds one row per real person. Every module references it, so a broker is the same broker in recruitment, in the commission run and in the portal.
Stages advance, expiries chase, goals recalculate and exceptions escalate without anyone driving them. The work that used to sit in someone’s head sits in the platform.
The modules share a database rather than integrating across one. Nothing is synced overnight and nothing drifts out of agreement, which is what lets a workflow trust the record it acts on.
Your staff work at yourgroup.aggregateiq.com.au. Your brokers log in on your own domain, under your own logo and colours, and never see our name.
Release calculators, enquiry forms and book-a-call widgets to your brokers under your brand, per cohort. You preview everything before it appears and can switch any of it off.
Each module is enabled per business. Start with the one that hurts most and add the others without a migration each time.
Three planes of access
Your team sees your whole business across every module you have switched on, and nothing belonging to any other group.
A broker reads only the rows that resolve to them, on your domain, with the layout you configured for their cohort.
We work in a separate application with mandatory two factor authentication. Reading your data requires a logged, time boxed session with a stated reason.