Designed for the portal. Not the demo.
How HubSpot portals are actually built: data model, pipelines, permissions, and the patterns that keep a 200-user account readable.
Data model
LifecycleA portal is a design, not a pile of properties.
One object map
Company, contact, and deal, plus the association a report can actually use.
Permission after the object
Who may see the record is decided once the object exists, not before.
A report with one name
Sales and marketing share the definition, or the chart is two stories.
A portal copied from a demo is a pile of properties.Data model
One pipeline per rep is not a design. It is a private language.Pipelines
NEXT
Permission, the report, the second team.
Permissions
Who may see the record, edit the property, and export the list. Decided after the object exists.
Reporting
One definition of a stage. If sales and marketing disagree, the chart is two stories.
More than one team
A portal that several brands or regions share, without a private pipeline for each.
Retire the field
A property nobody can explain gets an owner or it gets removed. It does not stay because a demo had it.
Say the stage out loud
If two reps describe the same deal with different stage names, the pipeline is not finished.
Read the break
Anti-patterns are the builds that look busy and cannot be reported.
Start here
The object, then the owner, then the stage a person can say out loud.
- Named associations
- One lifecycle
- A property with an owner
Leave this out
The demo portal, the unused app, and the field nobody can explain.
- A pipeline per rep
- Two names for one stage
- Reports that disagree