Loading…
The insurer already knew what your plan covers and what you had spent, but it lived in a system built for insurance staff. This is the page that turns those raw records into the two answers people actually want: what am I covered for, and how much is left.
Corporate medical insurance existed in people's accounts as a name and nothing else. I built the endpoint behind it and wired the cabinet to it, so the page now answers the questions people actually have: what's covered, how much has been spent, and what happens next.
The policy-cancellation wizard already worked — users could verify identity, pick a policy, and submit a refund request. Then came a focused afternoon, the kind that actually decides whether a feature ships: cutting the product list to what the insurance core can really cancel, replacing scan-on-every-cancellation with a 30-minute verification window, making the wizard survive page reloads and language switches, and teaching the reason chips to match the product. About three hours of work, none of it a rewrite — all of it the difference between "works" and "ready".