Bestow · Case Study 03

Unifying Three Portals

Underwriters and customer service reps were logging in and out of three separate portals up to ten times a day. I led the design of a single unified platform (one login, one dashboard, built-in messaging) that lifted operational efficiency by 40%.

Role
Product Designer
Team
Product Design
Timeline
2 Months
Pain Point
Multiple Logins a Day
Impact
+40% Operational Efficiency
Website
bestow.com
The Bestow underwriting portal on a tablet

The Problem

At Bestow, the underwriters and customer service representatives who keep life insurance policies moving were working across three separate portals, logging in and out an average of ten times a day. The fragmentation cost each user roughly 30 extra minutes daily, which added up to about 250 hours wasted every month across the team. Beyond lost time, the constant context-switching created confusion, disrupted workflows, and made it harder to serve customers quickly.

For the business, the stakes were just as real: lower productivity, higher operational costs, slower customer responses, and a system that couldn't scale as the company grew. Internally, the project even earned a nickname: “One” Portal To Rule Them All. The goal was clear: one unified portal that eliminated multiple logins, cut navigation time, and streamlined access to every essential tool.

Discovery

I ran a comprehensive discovery phase to understand exactly where the friction lived and how much it was costing:

All of it converged on a clear problem statement:

Users are burdened by the inefficiency of managing three separate portals, leading to wasted time and increased frustration, which impacts productivity and user satisfaction. Data shows a potential for a 40% increase in operational efficiency by consolidating these systems.

The Solution

From cross-functional brainstorming and affinity mapping through wireframes, user stories, and mid-fidelity Figma prototypes, I shaped the ideas into a prioritized roadmap (using MoSCoW to separate must-haves from nice-to-haves) and validated it with stakeholders before development. The unified portal was built around:

The full One Portal To Rule Them All brainstorming board, live from FigJam.

Brainstorming layouts in InVision Freehand: incorporating the Stripe payment element into the billing experience

Brainstorming layouts: exploring how the Stripe payment element could fit into the existing billing experience.

1 Step back - information architecture Before any screen: what are the three merged systems, and how does one flow connect them? No chrome yet, just the shape of the idea. Policies system A Customers system B Claims/Docs system C One record search finds it once Agent acts assistant suggests next step The bet: agents shouldn't have to know which of the 3 old tools a customer's data lives in. One search, one record view, contextual help right where the decision happens - not a bolted-on chat window.

Stepping back to the information architecture: one search and one record view across all three legacy systems, with contextual help where decisions happen.

2 Wireframe - three-pane, assistant baked into the record Structure locked: nav rail, cross-system record list, detail pane with inline assistant suggestions. Customer 360 - search across 3 systems J. Reyes - active Policy · Claim · Ticket J. Reyes - Policy #4471 Overview Policy Claims Docs Assistant: "Renewal is 12 days out - send reminder?"

The locked wireframe from my Claude Design file: nav rail, cross-system record list, and the assistant baked into the record view.

The Make a Payment modal in the unified portal, on a laptop

The shipped Make a Payment flow: settle one missed payment or all of them, with a saved payment method.

The Update Payment Details modal in the unified portal

Updating payment details happens in place, without ever leaving the policy view.

Ways of Working 2023: how the cross-functional team aligned while building the portal.

The Impact

Post-launch performance analysis confirmed a 40% increase in operational efficiency: users spent dramatically less time navigating systems and more time on the work that matters. Follow-up surveys showed a marked improvement in user satisfaction and reduced day-to-day friction, and the integrated communication tools led to better collaboration between teams and faster issue resolution for customers.

The retrospective closed the loop: we documented lessons learned, gathered stakeholder feedback on organizational impact, and built a prioritized roadmap of future enhancements, from additional integrations to improved reporting tools, so the portal keeps getting better.

Want to dig into the full discovery research or the design process behind this project? Get in touch.

Next Project Making It Clear How Athletes Contact Colleges