The CRM we built because others couldn't keep up
Meta is an insurance-native platform for sales, claims, underwriting and case management, built for insurers and brokerages who've outgrown their legacy CRM.
Four teams. One record.
Sales, claims, underwriting and case management on the same data model, with the same audit trail, the same live updates, and no handoff gaps between them.
Sales
Follow every lead through to a bound policy in one pipeline, and see which ones are going cold.
Explore sales ➝
Claims
Incidents, claims and recoveries on one record, with every call, note and task on a single timeline.
Explore claims ➝
Underwriting
Issue, endorse and renew policies with every change on record, and route referrals for approval.
Explore underwriting ➝
Case Management
Move every case through clear stages, with approvals and service providers linked to the record.
Explore cases ➝
Customise Meta your way
Add a field to a policy, a step to an approval or a whole new product line whenever you need to. You decide how Meta works, and your own admin makes the change without waiting on developers.
Set up by your team
Add a field, an approval step or a new product line from the admin screens. Your own people make the change, so there's no developer ticket and no waiting for the next update.
Set up by your team
Set up by your team
Add a field, an approval step or a new product line from the admin screens. Your own people make the change, so there's no developer ticket and no waiting for the next update.
One record, full history
Sales, claims, underwriting and case management all work from the same client records. Every change is saved with who made it, when, and what it was before.
One record, full history
One record, full history
Sales, claims, underwriting and case management all work from the same client records. Every change is saved with who made it, when, and what it was before.
Always up to date
When a colleague updates a record you're looking at, you see it straight away. No refreshing, no working from old numbers, and it comes as standard.
Always up to date
Always up to date
When a colleague updates a record you're looking at, you see it straight away. No refreshing, no working from old numbers, and it comes as standard.
Made for insurance
Policies, accounts, contacts, claims and endorsements come already linked. Ask a question about a client and get the answer in one place, without piecing it together from different reports.
Made for insurance
Made for insurance
Policies, accounts, contacts, claims and endorsements come already linked. Ask a question about a client and get the answer in one place, without piecing it together from different reports.
See Meta in action
Automations that carry the work, dashboards that update themselves and conversations that stay on the record.
Automations that move the work for you
Journeys fire on the events that matter (a new claim, a status change, an upcoming renewal) and carry the work forward on their own. Build the flow once and it routes the approval, sends the email and updates the record every time.
- Event-driven triggers, no polling
- Parallel or sequential approvals
- Delegation and recall built in
- Scheduled renewals and follow-ups
- Full audit trail on every step
“We moved our entire book onto Meta in under three months. What used to be a two-week endorsement cycle now closes the same day, and for the first time we can answer a client's question without opening four systems.”
Nicola Iozzo, Chief Executive Officer, MBFS
Integrated with the tools you already run on
Meta slots into the stack your team is already using: mail, calendars, contacts, files, mapping, signatures, customer messaging and cloud infrastructure.
Google Workspace
Google Maps Platform
Microsoft 365
WhatsApp
Enterprise security, switched on by default
The controls a regulated insurer needs aren't a premium add-on. Access, identity and audit are built into the platform from the first login.
Passkeys & MFA
WebAuthn passkeys and authenticator-app codes. No shared passwords.
Access granted per object
Reading, creating, editing, deleting and sharing are separate grants for each record type, so least privilege is the default.
Seeing isn't changing
View-all and modify-all are independent grants per object, so seeing the whole book never implies changing it.
Full audit trail
Every change indexed with actor, timestamp and before-and-after values.
Access ends immediately
De-provisioning a user cuts their sessions on every server the moment it lands, not at their next login.
Queue ownership
Shared work is owned by a real queue with members and rules, not a login the team passes around.