Re-rate, send a payment link, generate the schedule.
A renewal runs through the same rating engine, the same payment surface, and the same templating system as new business. Reminders, lapsed-payment retries, and the wider workflow are wired up with the REST API and webhook events.
Insurance is not a product you can ship in a box. Off-the-shelf SaaS asks you to bend around their software. We don't work that way.
InsureOS is a bespoke service built on shared infrastructure. The platform is the same for every insurer. The setup never is.
We partner with each insurer one by one. We map your rates, build your forms, and wire your integrations, all the way through to production.
Everything we set up is editable from the admin portal. Change rates, tweak forms, adjust rules. No tickets, no waiting.
Independent doesn't mean alone. We're a message away whenever you'd rather have a hand on the wheel.
Once the renewal is re-rated, the platform issues a hosted payment link that your customer pays from any device. Card, bank transfer, or premium-funded instalments through the providers you already run. The receipt and updated schedule fire the moment the gateway clears.
Where the payment gateway supports stored payment methods, the platform schedules the renewal premium to be charged on the renewal date. Customers are notified well in advance with the amount, the scheduled date, and a one-click way to opt out before the charge runs.
Every step of the renewal flow fires an event. quote.rated when the new premium is calculated, payment.scheduled when an automatic charge is queued, payment.succeeded when the gateway clears, document.generated when the new schedule goes out. Subscribe with webhooks and your stack stays in sync without polling.
See automationRenewals re-price on the current rate version effective on the renewal date. The original quote keeps its trace; the new quote gets its own. Hold-rates and freeze-on-prior-version are per-product configuration.
Once the renewal is re-rated, the platform generates a hosted payment link. You send it to your customer through the channel that suits them. Card via Windcave or Stripe, or premium-funded instalments through the providers we already integrate with. Receipts and the updated schedule fire the moment the gateway clears.
They go through the same rating engine as new business. Pro-rata math is built in. A fresh schedule of cover comes out of the same templating system as the original.
Yes. Cancellations use the same primitives: pro-rata refund calculated through the rating engine, cancellation document generated through the templating system, refund triggered through the same gateway adapter.
The building blocks are in the platform. The workflow around them (reminder cadences, lapsed-payment retries, exception routing) is wired up using the REST API and the webhook events. A more opinionated workflow product is on the roadmap.
Online quoting
Embed a real quote-to-bind flow
Automatic rating
Product definitions, rules, tables, explainable factors
Third-party integrations
Plug in the tools you already run
Payment collection
Cards, bank transfers, finance
Document generation
Branded policy docs, certificates, receipts
Automation
Webhooks, events, integrations
APIs
Headless when you need it