The extension notices a booking
Brolly looks for signals like date, location, booking type, participants, and price on supported checkout pages.
Proof-of-concept, not live insurance
When someone books tickets, trips, or experiences online, the Brolly extension can detect the moment and send them here to preview simple protection for the little things that spoil the day.
Booking checkout
Browser-first
Brolly looks for signals like date, location, booking type, participants, and price on supported checkout pages.
The site handles account creation, plan review, careful POC wording, and the protection preview.
Rainfall, delays, closures, or other measurable triggers can be added as the product expands.
Account required
For the POC, this form shows the intended account-first flow. In a live product, this is where consent, identity, notifications, and payout preferences would start.
Redirect landing
Category can stay flexible for now. The important part is that Brolly has enough context to show a clear protection preview before the user commits to anything.
Cover preview
Pick how much rain should count as a spoiled day. Brolly automatically updates the demo payout and price from that trigger.
Demo pricing only. A live version would price the premium from historical weather risk, booking location, booking window, and the selected payout rules.
Member dashboard
The dashboard gives the demo somewhere to go after signup: detected bookings, previewed covers, trigger status, and payout readiness. For POC demos, the rainy-day simulation shows how the experience changes when a trigger is hit.
Booking detected by extension
Account created
Rainfall trigger monitoring
Payout decision preview
Coming later for bookings the extension misses, forwarded emails, or unsupported checkout pages.
Brolly is watching the objective trigger for this booking window.
Trust and POC boundaries
Rain decisions are intended to use recorded weather data for the booking location and time window.
The intended live experience is automatic: Brolly checks the trigger and updates the user without a traditional claim.
Premiums and payouts shown here are demo values, not regulated quotes or offers to buy insurance.
A live product would need underwriting, policy wording, licensing review, privacy controls, and payout rails.
Partner-ready later