Policies, renewals, and claims on one timeline.
Insurance revenue is mostly retention, and retention is mostly whether someone reached out before the renewal date got close. This pack will model policies and renewals as real objects so that work is scheduled by the system rather than remembered by a person.
Coming soonThe pack is in development. Everything it runs on is live today.
What the insurance pack will install
Coming soon- Policytype, carrier, premium, effective/expiry dates, coverage limits
- Renewalpolicy, due date, quoted premium, status, owner
- Claimpolicy, date of loss, status, adjuster, amount
- Householdmembers, linked policies, total premium, retention risk
- Quotecoverage requested, carriers quoted, premium, decision date
- 1Enquiry
- 2Fact find
- 3Quoted
- 4Presented
- 5Bound
- 6Lost
- Renewal runway
- Cross-sell prompts
- Claim check-ins
- Lapse prevention
Objects with real relationships, a pipeline with real stages, and automations ready to run. Until the pack ships, custom objects and pipelines are live on every plan, so you can build these yourself today.
Three problems. The pack was shaped around them.
Retention is a calendar problem
Every book has renewals that lapsed because nobody called in time. When the renewal is an object with a date, the outreach is an automation with a trigger, and “we got busy in March” stops being a category of lost revenue.
The household, not the policy, is the relationship
Modelling policies without the household that holds them is why cross-sell is guesswork. With both modelled and related, total premium per household, coverage gaps, and retention risk are filterable fields rather than a report someone builds by hand once a year.
A record of who said what, when
Regulated conversations need an audit trail. Every message lands on the record timeline with a timestamp and an author, every field change is kept with who made it, and consent state is tracked per channel.
The pack is coming. The platform is here.
Here is what the shipped platform already does for insurance agencies and brokers. Each module is live today, with a page of its own.
Automations the pack will ship.
Each one will be editable, with a step-by-step trace for every run. The automation builder they run on is live today.
How AI automations workRenewal runway
Renewal tasks and outreach begin 90, 60, and 30 days out, not a week before expiry, with the current premium and claims history already on the record.
Cross-sell prompts
A household with auto but no home cover surfaces as a live segment, and the prompt reaches the right producer with the context attached.
Claim check-ins
An open claim triggers scheduled updates to the client, because silence during a claim is what loses the renewal a year later.
Lapse prevention
A missed payment or an unreturned renewal call escalates through channels rather than being noticed at expiry.
Can this integrate with carrier systems?
Through CSV import today: export from your agency management system and import with column mapping. A public API for scheduled, programmatic syncs is coming soon.
How do you handle sensitive client data?
Role-based visibility limits who sees which clients, every change to a record is kept with who made it, and data is encrypted in transit and at rest. Field-level permissions are coming soon. See the security page for specifics.
Can producers see only their own book?
Yes. Visibility is set by role and enforced in the query engine, so the same views and dashboard scope automatically by producer or team.
Does the AI ever give coverage advice to clients?
No. The AI summarises and drafts for your team; it doesn’t message clients on its own. Anything client-facing is sent by a person (for advice, a licensed producer).
Start free today. The insurance pack is coming soon.
Contacts, leads, pipelines, and automation templates are ready at signup, and anything the pack will install can be built by hand in the meantime.
Free plan · No credit card · Every price on the site