Decide what the portal is for.
Architecture, audits and the operating model underneath them — so the configuration follows a decision rather than an accumulation of requests.
Architecture before configuration.
A HubSpot consulting engagement starts by writing down what the portal is supposed to do: which object is the system of record, what a lifecycle stage means, who is allowed to change a definition, and which reports the business actually runs on.
From there the audit is straightforward. Everything in the portal either supports that model or contradicts it, and the contradictions are the work.
We stay through the rebuild rather than handing over a document. The people who wrote the architecture are the people who implement it.
Six deliverables, not a document.
Portal audit
Objects, properties, workflows, integrations and permissions, inventoried and reconciled against how the business actually operates.
Data model
One definition of a company, a contact, a deal and a customer, with the associations that hold them together.
Lifecycle design
Stages with entry and exit criteria that two different operators apply the same way.
Reporting model
The dashboards the operating cadence runs on, built from properties the portal is guaranteed to hold.
Governance
Naming, ownership and change control, so the portal does not drift back within a quarter.
Roadmap
What to fix now, what to fix next, and what to stop paying for.
The rest of the HubSpot practice.
Start with the portal you have.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.