HubSpot architecture guide
Should you use the HubSpot customer portal or build your own?
Chris Bryant, Founder
Updated Nov 2026
Use HubSpot's built-in customer portal when its standard features cover the records and actions your customers need. Build a custom portal on HubSpot's CMS when members or partners need custom objects, custom access rules or their own workflows. Start by listing what each type of user must see and do, then test that list against the built-in portal.
Book a Call- HubSpot Diamond Partner
- 660+ client organizations
- 330+ five-star reviews
Your customers, members or partners want a login where they see their own records, and you need to decide where that login lives. The choice sits between the portal HubSpot provides and one we build for you on HubSpot’s CMS. In this guide, “HubSpot portal” refers to your HubSpot account, and “customer portal” refers to the login your users see.
Who faces the customer portal decision
The decision usually lands with the ops or RevOps lead who owns the HubSpot portal. Service owns the customer conversations, marketing owns the website, and the customer portal touches both. The request tends to arrive in one of these forms:
- A service team wants customers to check the status of their own requests.
- A membership organization wants members to see their status, renewals and benefits.
- A partner program wants resellers or referral partners to see the deals they registered.
- A company moving off another platform needs to replace the portal that platform ran.
The first request starts from records most service teams already keep. The other three depend on records shaped around one business, such as membership tiers, partner levels or referral payouts. That difference drives most of the decision.
A customer portal also shows your records to people outside the company. Duplicate contacts and stale fields that your sales team tolerates become visible to customers and partners. Data quality work often comes before either option for that reason.
The criteria in one table
Each criterion below names something your users need and compares how each option handles it. The built-in column points to HubSpot’s documentation wherever the answer depends on HubSpot’s current features.
| Criterion | Built-in customer portal | Custom portal on HubSpot’s CMS |
|---|---|---|
| Records users see | Set by HubSpot, confirm in its documentation | Any record in your data model |
| Custom objects | Confirm support in HubSpot’s documentation | Designed into the build |
| Access rules | Set by HubSpot | Written for each user type |
| Actions users take | Set by HubSpot | Scoped to your process |
| Look and layout | Confirm options in HubSpot’s documentation | Built to your design |
| Build effort | Configuration and a pilot | Custom builds typically run 8 to 16 weeks |
| Upkeep | HubSpot maintains the product | You own the code and its changes |
| Licenses | Bought directly from HubSpot | Bought directly from HubSpot, plus our build |
The first 3 rows decide most cases. When the records and access rules you need fall outside what the built-in portal supports, the remaining rows matter little.
The built-in customer portal against the criteria
The built-in portal is part of HubSpot’s product, so HubSpot decides what it shows, who can log in and when those features change. This guide does not list those features or their requirements. HubSpot’s knowledge base is the place to confirm both before you commit.
The trade is control for speed. Your team configures and tests a product that HubSpot maintains, so no custom code sits in your portal waiting for upkeep. Customers who need to see their service requests are the case to test first.
Run the fit check in this order:
- Write one brief per user type, covering the records they see and the actions they take.
- Mark each record as standard or custom in your current data model.
- Check each line of the brief against HubSpot’s current documentation for the portal.
- Set up the portal for a pilot group that works with real records.
- Record every gap the pilot finds, along with the user type it affects.
A gap list with a single item can still decide the question. One missing field that drives renewals or payouts outweighs a long list of features that work. Weigh each gap by the decision it blocks for the user.
A custom portal on HubSpot’s CMS against the criteria
We build membership portals and partner portals as custom development on HubSpot’s CMS. We do no design work, so your designer or your brand guidelines supply the look and we build to it. Most of the work behind the pages sits in the data model, which our HubSpot custom builds cover through these parts:
- Custom objects for records such as memberships or referrals.
- Associations that tie those records to contacts and companies.
- Property sets that hold the fields each user type sees.
- Pipelines and board views for the stages behind each record.
Custom objects carry most of the weight in a partner or membership portal. Our guide on when you need HubSpot custom objects walks through that choice.
How we build a custom portal
- Data model. We decide which records each page reads, and we add custom objects where a membership or partner record needs its own fields and history.
- Access rules. We write down which records each user type sees and edits, then build the portal to enforce those rules.
- Pages. We build the templates and modules to your design.
- Documentation. We record what we built and why, so your team can change it later.
The pages follow the same practices as any site build on HubSpot. Our guide to HubSpot website development covers that side of the work.
Cost and timeline for a custom portal
A custom portal is a defined scope, so it runs on our project rate. Every engagement starts with a written scope and transparent pricing.
| Item | What to expect |
|---|---|
| Project rate | $225 an hour |
| Minimum for new clients | 10 hours |
| Typical custom build | 8 to 16 weeks |
| HubSpot licenses | Bought directly from HubSpot |
The range in the table is typical for custom builds and makes no promise for your portal. The data model sets most of the timeline, because each custom object adds fields, associations and access rules to build and test.
What you take on with a custom portal
A custom portal is yours to maintain. A change to the data model requires a matching change to the pages and the access rules. Your team needs someone who owns those changes, either in-house or on a retainer. Our Growth Ops retainer runs $3,000 a month, based on 15 hours a month.
Conditions that tip the choice
Most teams can sort themselves with the lists below. Where a team matches items on both lists, the custom side usually wins, because one unmet need sends users back to email.
The built-in portal fits when
- Your users are customers who need to see their service requests.
- Every record they see already lives on a standard object.
- HubSpot’s documentation confirms each line of your user briefs.
- Your team has no developer to own custom code.
A custom portal fits when
- Your users are members or partners with records of their own.
- The portal reads custom objects, such as memberships, referrals or partner tiers.
- Each user type needs different access rules.
- The portal must follow your website’s design closely.
Suppose, as an imagined case, that your service team and your partner program both ask for a portal in the same quarter. The service request may pass the fit check on the built-in portal while the partner request fails it. Running both through the same user briefs keeps the decisions separate, and each group gets the option that fits it.
Teams moving off another CRM face the same test with one added input. The old portal’s pages show what users rely on today. We audit the current CRM before a migration, and the portal belongs in that audit.
Start with the user briefs from the fit check. Write one page per user type that lists the records they see, the fields they edit and the actions they take. That page settles the built-in test, and it becomes the scope for a custom build if the test fails.
Common questions
What is the HubSpot customer portal?
The HubSpot customer portal is the customer-facing portal HubSpot provides inside its own product, separate from any portal you build on its CMS. HubSpot sets its features, the records it shows and who can access it. Confirm those details in HubSpot's knowledge base before you plan around them.
Can you build a partner portal on HubSpot?
Yes, we build partner portals as custom development on HubSpot's CMS. The build sits on a data model designed for your partner program, with custom objects and associations for records such as referrals or partner tiers. Access rules decide which deals and accounts each partner sees.
Can you build a membership portal on HubSpot?
Yes, we build membership portals as custom development on HubSpot's CMS. The build starts with the data model, often with custom objects for memberships, renewals or benefits, associated to the contacts who hold them. Our custom builds typically run 8 to 16 weeks, and the data model drives most of that range.