Patterns
Reusable designs for a HubSpot portal.
Each pattern is a decision you can hand to the next admin. A demo that only works on ten records is not a pattern.
Data model
Property, object, or a labeled association. The report you want decides which one.
Pipelines and lifecycle
One set of stages the room can say. Marketing and sales share the words before anyone automates them.
Teams and permissions
Who sees which records. A 200-user portal needs partitions, not a shared password.
More than one business
A label, a business unit, or a separate portal. The choice follows who must not see whom.
Reporting
If the model cannot hold the question, the dashboard will lie. Grain and association come first.
What to leave out
One pipeline per rep, a property for every idea, a shared super admin. They feel tidy, then they break.
A pattern has a name a new admin can find.If it only lives in someone’s head, it is a habit.
The portal after year two is the design.The demo on day one is not.