HubSpot Data Model Design
A document with objects, properties, associations and pipelines, ready before anyone starts the setup.
- phaseSolution Design
- engagementProject
The problem this solves
Two years in, a portal set up without a plan has properties with near-identical names, deals used for things that need their own object, and lifecycle stages each department reads differently. Fixing that now means a migration. In a document before setup, it means changing a few lines.
How I work
I start with the hard cases: multi-year contracts, renewals, subsidiaries and sales through distributors. We agree what a company, a contact and a deal mean in your business, what needs its own object and which associations must exist for your reports to work.
Then I write the design: a diagram of objects and associations, a property dictionary with type, options and owner, pipelines with entry and exit criteria for every stage, lifecycle stages and naming rules. I record the reasoning behind every decision. I change nothing in the portal. I can set up the portal from the document, or your team can.
What you get
- A diagram of objects and associations
- A property dictionary with type, options and owner
- Pipelines with entry and exit criteria for every stage
- Lifecycle stages agreed by sales and marketing
- Custom object recommendations with reasoning
- Naming rules for properties, lists and workflows
What usually goes with this service 1
Let’s check whether this service fits your situation
After you submit the form, you pick a time in my calendar. I prepare the scope and a quote after the call.