Customer Portal Revamped

Problem Statement

Subsbase's merchants were losing trust in the portal before their own customers ever got to use it. Clients described the experience as cluttered, the navigation as confusing, and the overall feel as unprofessional, hard words for a platform whose core pitch was handling billing reliably.

Underneath the complaints sat three structural problems the original portal could not solve without a rebuild:

• Inefficient navigation. Tabs forced users to hop horizontally across sections to reconstruct a full picture of their account, and nothing persisted visually to tell them where they were.

• Poor information hierarchy. Subscription plans rendered as expandable rows, collapsing critical payment data behind interaction. Users could not scan a list and understand spending at a glance.

• Lack of transparency. The single most common support question, how much do I owe and when, required three clicks and two mental calculations to answer.

Goals

Success meant repositioning the portal from a transactional utility into a product merchants would feel comfortable putting in front of their own customers. Three goals anchored the project:

• Give every user a clear, one-screen overview of subscriptions, upcoming payments, and overdue amounts, before any navigation was required.

• Replace tab navigation with a persistent sidebar so users always knew where they were and could jump between sections in one tap.

• Raise the visual and interaction quality to match market standards for SaaS billing products, closing the professionalism gap clients were flagging.

Research & Analytics

Research combined client interviews, past rejected concepts, complaint-ticket analysis, and competitor benchmarking across platforms like Chargebee, Recurly, and Stripe Billing. Findings showed recurring issues around navigation, clutter, and outdated professionalism, while leading competitors consistently used dashboard-first layouts, persistent sidebar navigation, and visible payment data. The core conclusion was that the existing portal was not only visually outdated, but structurally behind market standards.

Design Thinking Process

The project followed five sequential phases. Research began with client interviews, rejected concepts, and complaint-ticket analysis to identify root problems. Findings were narrowed into three priorities: clearer subscription details, easier payment tracking, and a more trustworthy interface. Cross-functional ideation with stakeholders and engineering shaped the solution direction. Prototypes were then built around a dashboard-first experience with simplified navigation and visible payment data. Finally, user testing validated the redesign and informed refinements before development started.

Design Concept

The redesign was guided by empathy for users, not by a style preference. Every design decision traced back to a specific complaint theme or research finding, which kept the critique loops focused on whether the solution was working rather than whether the visual direction felt right.

Dashboard Overview
The new landing surface consolidates active subscriptions, payment schedules, overdue amounts, and transaction history onto a single screen. Users get the full state of their account before making a single navigation decision, directly answering the transparency problem.

Sidebar Navigation
Tabs were replaced with a persistent left sidebar covering Summary, Subscriptions, Payment Schedule, and Payments. Users always know where they are and can jump between sections in one tap, eliminating the horizontal context-switching that had driven much of the original friction.

Improved Subscription Details
Clear labels for subscription names, statuses, and payment schedules replaced the expandable-row pattern. Critical payment data is visible in the flow, not hidden behind interaction.

Post-Launch Testing & Success Measurement

Post-launch validation combined A/B testing, user feedback, behavior analytics, and support-ticket monitoring to measure real impact. The redesign improved navigation speed by 80%, reduced subscription and payment-related support tickets by 40%, achieved 92% positive user satisfaction, and reached 95% adoption within the first month. Improved transparency and usability also contributed to a 40% increase in subscription renewals.

Challenges & Conclusion

Not every trade-off was clean. Two areas asked harder questions than the pre-launch brief anticipated.

Balancing density against clarity
The dashboard-first approach required careful calibration. Too much information on the landing view would recreate the original clutter problem under a new visual system. The solution was strict hierarchy, primary metrics as large summary tiles, secondary information in scannable tables, tertiary actions tucked into the sidebar, but the calibration took iteration, and the first prototype was too dense. The second version pulled back.

Migrating existing users without disruption
95% adoption was the headline, but the 5% who hesitated surfaced a real signal: long-time users had built muscle memory around the tab navigation, and even a demonstrably better system creates short-term friction for the users who were most fluent in the old one. The lesson carried forward: migration communication and opt-in onboarding need to be designed with the same care as the product itself.

The Subsbase customer portal redesign validated the core bet: that clarity, hierarchy, and navigation convention, applied thoughtfully, resolve trust issues that surface as visual complaints. Every top-line metric moved positively, support load dropped, and subscription renewals, the metric that actually pays the bills, increased 40%. The work reframed the portal from a liability merchants apologized for into a surface they were willing to put in front of their own customers.