Policy Management for a B2B Insurance Platform
Helping insurance brokers create policies and manage the work that follows.
Understanding the work
At Tigerlab, I helped design Policy Management for the first version of a Broker Management System (BMS). The client’s brokers worked across different markets, using spreadsheets and manual processes to manage their policies.
There was no existing platform to build on. The client described their current workflows, and I worked with the Product Owner and product team to decide how they should work in the first version of the BMS.
My work included mapping flows, exploring ideas through prototypes, designing high-fidelity interfaces and following through during implementation.
Something we could click through and question
Many requirements needed more discussion before they were ready for detailed design. I used Claude to help build low-fidelity HTML prototypes so the team could try a flow, question its behaviour and work through the missing details.
One exploration was a form builder that would let brokers create customised forms for clients.
We ultimately decided not to build the feature. The prototype helped us reach that decision before committing development time.
The form grew. Our approach had to change.
Our early policy creation design used a modal. As we worked through the requirements, we realised the form was more complex than we had anticipated. Different policy types and jurisdictions needed different fields, and brokers wouldn’t always have everything ready in one sitting.
I moved creation to a full page, giving the form more room and keeping the premium summary alongside it. Fields changed according to the policy requirements, while draft saving let brokers enter what they knew and return later.
What happens after creation?
Each policy status required different information and allowed different actions. I designed Policy Details so brokers could see what they knew, what was missing and what to do next.
Key information and status sat at the top, with an alert bar showing what needed attention. Tabs for Summary, Finance, Endorsements and Documents kept everything related to the policy in one place, so brokers could manage it as it progressed.
Adapting shared components to the BMS
Devias Kit gave us a starting point, but its components didn’t always fit the BMS. I maintained and expanded our design system in Figma and Storybook, adjusting existing patterns and adding components as needed.
Alerts were one example. Against the grey page background, their edges needed more definition, and the corner radius felt inconsistent with the surrounding UI. I refined the borders, colours and radius across the alert variants, checking how they looked within Policy Details.
Original
Updated
Alert / Standard V1
Alert / Standard V2
Updating the interface directly in code
My work continued during implementation. With Claude Code’s help, I made some visual and layout adjustments in the frontend, then raised PRs for developers to review.
One example followed our design lead’s update to Account Details. The shared layout needed to carry across to all details pages. Rather than redraw every page in Figma first, I used the updated design as a reference and adapted Policy Details in a separate development branch.
Original
New layout
For changes that didn’t need backend updates, I could help with the implementation and check that the result matched the design. This let me contribute beyond the handoff and reduce the visual adjustments left for frontend developers.
What came out of it
Over six months, I helped define and design the Policy Management experience for the BMS MVP. My biggest contribution was giving the team something concrete to work through together. Prototypes helped us question ideas early, the designs clarified how the workflows should behave, and design QA helped carry those decisions into the product.