Hábil MDW for Insurance and Insurtech

Scenario: rates that change without an IT project · Auto and property insurance

Before: the premium changes by coverage, area, deductible, sum insured, age, term and channel. With the rate in code, every rate or rule adjustment is an IT project, and the agent channel waits for weeks.

What changes: your insurer or your agent channel quotes, issues, collects and invoices policies with its own rules and rates. A rate adjustment is configuration, and it reaches every channel you connect in the same way: the web, the agents and the partners.

Why it is hard: the rate lives in the core system, the payment collection in another system and the invoice in a third, and all three have to tell the same story about the policy.

How Hábil MDW solves it: the rules and steps of the policy are defined in configuration, and the platform takes each policy from the core system to payment collection and to the invoice, with each system's response in view.

Capabilities: Connect your systems · Your business steps · Guarded gateway.

Scenario: the policy from end to end, alongside your core system or without one · Policy management

Before: the core system issues the policy, but everything around it lives elsewhere: the quote in a spreadsheet, the endorsement by email, the receipt at the bank, the invoice with a third party, the policy schedule printed by hand and the renewal notice whenever someone remembers. And for a new insurer, an agency or an intermediary, buying a complete core system is usually a project that takes years.

What changes: the quote, issuance, endorsements, renewal, cancellation and reinstatement follow the same path. Each policy is collected, reconciled and invoiced, its documents are generated and delivered —printed or digital— and the policyholder receives every notice by email, SMS, WhatsApp or Telegram. Each agent's commissions are calculated and paid with the same policy in view.

Why it is hard: the policy lives in the core system, the money at the bank and the invoice in another system; an endorsement changes the premium and all three have to find out at the same time. And each product has its own rules.

How Hábil MDW solves it: alongside your core system, the platform connects to it through the means it already has and takes care of what the core system doesn't do well —payment collection, documents, notices, commissions—, seeking not to touch its logic or its screens. Without a core system, the platform keeps the policy in force with its premium and acts as the policy manager. In both cases, policy, endorsement and product are configuration: the same platform, configured for your industry.

Capabilities: Connect your systems · Your business steps · Guarded gateway · 24/7 operation with a trail.

Scenario: the claim, from first notice to payout · Claims management

Before: the notice arrives by phone, the photo by WhatsApp and the document by email. The adjuster is assigned by hand, the reserve is calculated in a spreadsheet, the assessment waits for papers nobody asked for and the policyholder calls three times to find out how it is going.

What changes: the claim is recorded from the first notice, through whatever channel the policyholder uses, with its documents and photos received and stored; with Hábil AI, also read. It is assigned to the adjuster and the appointment is scheduled; the reserve is recorded when the claim is opened and adjusted along the way; the assessment follows its rules and escalates to a person when needed; the indemnity is calculated and paid with the approval you define, and what can be recovered from third parties or salvage is followed up until it is collected. The policyholder receives a notice at every step.

Why it is hard: each claim brings together many parties —policyholder, adjuster, repair shop or hospital, supplier, third party— and each document has to be valid and on time. A claim without an owner is a lost customer.

How Hábil MDW solves it: the claim is a procedure with stages, papers and deadlines that you define; each piece of evidence stays in a log that is kept for the period set by your policies and the law, with a signature that makes it possible to check that it was not altered, and the claim can be followed on a single page with the case tracker. Claim, coverage and assessment are configuration, not code: the same platform, configured for your industry.

Capabilities: Your business steps · Connect your systems · 24/7 operation with a trail.

Scenario: the agreement with a partner, without running it by hand · Group, affinity and warranty insurance

Before: an agreement with a partner or an extended warranty is a plan with rules, cut-offs, collection and claims that is run by hand or in a development built just for that partner.

What changes: batch issuance, direct-debit collection, the file, the claim and the report to the partner follow the same path. The partner checks what concerns it from its own system, with its own identity.

Why it is hard: each partner sends its files with its own format and its own cut-offs, and the report sent back has to reconcile with what was collected.

How Hábil MDW solves it: each partner's files are translated into the same language, each batch leaves its audit trail, and the partner comes in through the guarded gateway, with permissions only over what is its own.

Capabilities: Connect your systems · Your business steps · Guarded gateway · 24/7 operation with a trail.