Customer and partner portals: giving every audience a front door

The problem

In a multi-brand portfolio, the people you serve fall into distinct audiences with distinct needs. Customers want their own information and resources, in the context of the brand they bought from. Partners want the materials and clarity to sell with you. When neither has a proper front door, every request becomes an email, every email becomes someone's task, and the team spends its time as a human lookup service. It doesn't scale, and it isn't a good experience for anyone involved.

What I built

Two builds with one philosophy. First, a customer portal spanning the brand portfolio: a logged-in place where customers reach what is theirs, presented in the right brand context, without a support ticket in between. Second, the Paragon partner portal: a dedicated home for partners, putting the materials and information they need to sell in one organised place rather than scattered across email threads and shared drives.

The architecture, described generically: a gated layer over the existing marketing and CRM infrastructure, so the portals show people what is relevant to them specifically, and the content behind them is maintained once rather than duplicated per audience.

The outcome

Self-service where there used to be inbox traffic. Customers and partners get answers at the moment they want them, and the team gets its time back for work that actually needs a human. The partner portal in particular changed the relationship dynamic: partners equipped with current, organised materials sell with more confidence than partners working from whatever attachment they were last sent.

As with everything in this portfolio, the build is the proof. I'll show the working thing rather than narrate numbers around it.

The stack

• HubSpot CRM as the data backbone
• Gated, membership-based portal pages
• The custom module and template system handling multi-brand presentation
• Custom front-end work, CSS and JavaScript