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
Lead to bound policy in one pipeline. Accountability scoring flags cooling leads, duplicate detection keeps your book clean, and campaign attribution ties marketing spend to revenue.
Explore sales ➝
Claims
Incidents, claims, assets and recoveries on one record. Every call, note and task on a single timeline — no more chasing context across five tabs.
Explore claims ➝
Underwriting
Issuance, endorsements, renewals and fleet changes — all versioned, all audited. Configurable approval flows route referrals without waiting on engineering.
Explore underwriting ➝
Case Management
Stage-based workflows with dynamic, stage-aware forms. Built-in approvals on any case, service-provider network linked to the record, live updates when colleagues edit.
Explore cases ➝
Configuration, not engineering projects
New field, new approval flow, new product line — admin-time work, not a six-month release cycle. Meta is metadata-driven from the ground up, so the platform bends to your business, not the other way round.
Configuration, not releases
New field, new approval flow, new product line — admin work, not a six-month project. Your business team reshapes the platform without a developer ticket.
Configuration, not releases
Configuration, not releases
New field, new approval flow, new product line — admin work, not a six-month project. Your business team reshapes the platform without a developer ticket.
One record, one audit trail
Sales, claims, underwriting and case management on the same data model. Field-level history on every change — actor, timestamp, before and after.
One record, one audit trail
One record, one audit trail
Sales, claims, underwriting and case management on the same data model. Field-level history on every change — actor, timestamp, before and after.
Real-time by default
When a colleague edits the record you're viewing, you see it immediately. Live updates are the baseline, not a premium feature.
Real-time by default
Real-time by default
When a colleague edits the record you're viewing, you see it immediately. Live updates are the baseline, not a premium feature.
Built for the insurance graph
Policy, account, contact, claim, endorsement — all related, all queryable in one step. No stitching joins together to answer a basic question.
Built for the insurance graph
Built for the insurance graph
Policy, account, contact, claim, endorsement — all related, all queryable in one step. No stitching joins together to answer a basic question.
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
Mail, calendars, contacts, files, mapping, signatures, customer messaging and cloud infrastructure — Meta slots into the stack your team is already using.
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 — 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.