What to Put in a Customer Portal (And What to Leave Out)

Here's a question most customer success and operations leaders can't answer cleanly: what does your customer actually see when they log in to your portal?

Not what you intended them to see. Not what was scoped in the original project. What they actually experience when they arrive, try to find something, and either succeed or give up.

For a lot of teams, the honest answer is uncomfortable. The portal is overcrowded with content nobody asked for, underbuilt in the areas that matter most, and completely disconnected from the rich customer data sitting inside their CRM.

That last part is the real missed opportunity. Because if your CRM is HubSpot and your website is built on HubSpot, you already have everything you need to power a login experience that feels genuinely personal and genuinely useful. The data is there. The relationships are there. The portal is just the experience layer that finally puts it in front of the right people.

Getting that experience layer right is the challenge. This post is about how to do it.

the data you have and the experience you're delivering are not the same thing

Think about what lives in your HubSpot CRM right now.

You know which customers are in active onboarding and which are three years into their contract. You know their renewal dates, their product tier, their support history, their assigned CSM, which features they've adopted and which they haven't touched. You know which contacts are decision-makers and which are day-to-day users. You know who's healthy and who's a retention risk.

None of that reaches your customers through a generic web experience.

When they log in today, they likely see the same thing everyone else sees: a static, one-size-fits-all portal that knows nothing about them as an individual. So they email your team for status updates on things you already track. They ask for documents that already exist in your system. They have no visibility into their own relationship with you.

That's the gap a well-built HubSpot portal closes. Not by adding features for the sake of features, but by taking the data you're already maintaining and making it visible, useful, and personal for each customer based on exactly who they are.

what belongs: let your CRM data decide

The most reliable way to figure out what should be in your portal is to look at what your CRM already knows about your customers and ask: if they could see this, would it make their life easier?

Start there, and the content decisions become a lot clearer.

account status and relationship context

Your customers want to know where things stand. What's active, what's pending, what's upcoming. And because HubSpot already tracks this, you don't have to build a separate system to surface it. You just have to expose it.

Renewal dates, contract details, current project status, their assigned team members and how to reach them. This is the content that answers "where do I stand with you?" without requiring an email. When customers can see this at a glance, it removes the ambiguity that erodes trust in long-term relationships.

support and ticket history

If your customers ever submit requests or issues to your team, they want full visibility: every ticket, every status, every update, in one place. Not just the latest reply. The whole thread.

A portal that shows partial history, or that requires a phone call to get a status update, isn't serving your customers. It's just shifting the frustration upstream. The support experience in your portal should be as transparent as a conversation, because that's what customers expect.

documents and deliverables

Contracts, proposals, reports, invoices, project outputs. Whatever your team regularly resends when someone asks is exactly what belongs in the portal.

A simple test: look at your support or email inbox and count how often you receive "can you resend..." requests. Every one of those is a portal content decision waiting to be made. If it's being requested more than twice, it belongs in the portal.

personalized resources based on where they are in the relationship

Here's where the HubSpot CRM integration earns its keep in ways a standalone portal tool simply can't match.

A customer in month two of onboarding should see different resources than a customer who's been with you for three years. A power user should see different content than someone who's barely logged into your product. An enterprise contact with a dedicated team should see a different experience than a self-serve customer.

All of that personalization is driven by data you already have in HubSpot. Contact properties, list membership, lifecycle stage, deal tier, product usage, custom fields. The portal reads that data and renders the right experience for each person. No manual curation. No sending separate emails to different segments. The portal knows who's logged in and responds accordingly.

This is the part most portal builds underutilize, and it's the biggest differentiator between a portal that feels generic and one that makes customers feel genuinely understood.

what doesn't belong

Every portal has content that shouldn't be there. Knowing what to cut is just as important as knowing what to include.

marketing content

Your portal is not a marketing channel. Customers who are already in a relationship with you don't need to be sold to every time they log in to check a status or pull a document.

Case studies, promotional banners, "have you seen our new product" callouts. These belong on your marketing site. Inside the portal, they read as noise at best and as a sign that you don't understand the difference between acquiring a customer and serving one at worst.

The exception: content that helps customers get more value from what they've already bought. Onboarding tips, adoption guides, feature walkthroughs. That's useful. Anything that feels like a sales pitch isn't.

your CRM data without translation

This one is subtle but important. Just because data exists in HubSpot doesn't mean it's ready to be shown to a customer.

Internal status labels that mean nothing to an outside person. Pipeline stages built for your sales process, not for customer comprehension. Fields that made sense to your ops team when they were set up but would confuse anyone without context.

When you surface CRM data in a portal, it needs to be translated into a language your customers understand. "Stage: Closed Won" is not a customer-facing status. "Your contract is active through December 2026" is.

everything, just in case

The instinct to add more is almost always wrong when it comes to portals. More content means more navigation, more cognitive load, and more chances for the customer to fail to find the one thing they came for.

A portal that does three things beautifully will be used more than a portal that does fifteen things adequately. Start with the jobs customers come to do most often. Earn the right to add more by watching how they actually use what you've built.

content with no owner

A resource library that hasn't been updated in a year. A knowledge base article referencing a product that no longer exists. FAQs from the original launch that nobody has reviewed since.

Nothing erodes portal credibility faster than stale content. If you can't commit to keeping a section current before launch, leave it out. You can add it later. Recovering from a customer who was misled by outdated information is much harder.

the question that cuts through most portal debates

When your team is arguing about whether a piece of content should be in the portal, one question usually settles it:

Did a customer ask for this, or did we decide they should have it?

Customer-requested content almost always belongs. "We thought it would be helpful" content almost always needs more scrutiny. Your customers are telling you what they need every time they email your team, every time they submit a support ticket, every time they ask a question on a call. That behavior is your content roadmap.

Build the portal around that, and you won't have an overcrowding problem.

what this looks like when it's working

When a customer portal is built with intention in HubSpot, and connected properly to the CRM data behind it, the experience stops feeling like a portal and starts feeling like a relationship.

The customer logs in and sees their world: their account, their history, their next steps, their team. Everything reflects who they actually are and where they actually are in the relationship. Not a generic experience with their name dropped in at the top.

Your team, meanwhile, sees every interaction in HubSpot. Every login, every document view, every ticket update, every resource accessed. That activity enriches the CRM automatically. Over time, the portal becomes a source of customer intelligence, not just a UX improvement.

That's the compound value of building on HubSpot. Your CRM data and your customer experience aren't two separate systems trying to stay in sync. They're the same system, finally working together.

most portals fail before the first line of code is written

The content decisions that determine whether a portal succeeds or fails happen in planning, not in development. What to include, what to leave out, how to segment the experience, what data to surface and how to translate it, who owns keeping it current.

Get those decisions right and the build is relatively straightforward. Get them wrong and no amount of good development work will fix it.

This is why Media Junction's portal work starts with discovery. We map what your customers actually come to do, what your CRM already knows about them, and where the gaps are. The content strategy comes first. Everything else follows.

not sure what should be in yours?

If you're planning a customer portal, or if you have one that's not performing the way you expected, a conversation is the right starting point.

We'll look at your HubSpot setup, talk through what your customers are actually asking for, and give you an honest picture of what a portal built on your existing data could do.

Request a consultation with Media Junction and let's figure it out.

You can also read the previous post in this series on why companies are building custom portals in HubSpot, or explore our full HubSpot services to see where portal development fits in a broader strategy.