maavdnbo.com

The HubSpot Setup for Early-Stage SaaS

4 systems. Not 47 workflows. A framework for building HubSpot setups that your team actually uses.

System Architecture
System 1
Pipeline & Lifecycle
Lifecycle stages · Deal creation · Lead Object · Assignment
System 2
Sales Handoff & Signals
Qualification · Signal management · Ownership rules
System 3
Process Automation & Custom UI
Shadowing-driven automations · Custom views · Team-specific workflows
System 4 — Foundation
Data Richness & Cleanliness
Deduplication · Attribution · Property hygiene · Enrichment · GDPR
Everything above breaks if the data layer below it is unreliable.

Pipeline & Lifecycle Architecture

How business moves through your organisation, from first form fill to closed-won and beyond.

Lifecycle stages
What are the meaningful transitions?
Define the points where responsibility shifts or action is required. The specific labels don't matter. What matters is everyone agrees on the definition behind each stage.
Contact vs Company lifecycle
Do they move in sync?
Sometimes syncing makes sense (small deals, single-threaded). For multi-stakeholder or ABM, the company often needs its own criteria.
Deal creation
When does a lead become a Deal?
At qualification? Demo booked? When the rep decides? Too early = noisy pipeline. Too late = lost visibility. Also determines forecasting.
The Lead Object
Use it or stick with lifecycle stages?
Useful for tracking multiple lead events for the same contact. Adds complexity. If the team is small and the cycle is simple, lifecycle stages are usually enough.
Assignment
Who picks this up?
Always a balance between fair distribution and right person on right deal. Complexity varies wildly. No point overengineering for a three-person team.

Sales Handoff & Engagement Signals

When and how business gets to sales. Where marketing-sales alignment works or breaks.

Hand-raisers
Clear path: qualify and route
Demo requests, high-intent forms. The decisions are about what "qualified" means and how fast the handoff happens.
Vague signals
Who reaches out? Marketing? Sales?
Pricing page visits, resurfacing leads, usage milestones. Without clear rules, the most common outcome is nobody reaching out at all.
Which signals to surface
How do we keep it useful?
Not every pageview deserves a notification. The system needs to be selective enough that sales actually pays attention.
What happens after
Clear owner? Defined action? Automated?
Every signal needs a defined response: who owns it, what's the expected action, or does automation handle the first touch.
The 33/33/33 rule

Of non-handraising signals: as long as ⅓ trigger direct outreach, ⅓ are "hmm, interesting" without action needed, then ⅓ noise is fine. When it shifts toward noise, sales stops checking.

Process Automation & Custom UI

The small, specific things that save your team time every day. Discovered by shadowing, not guessing.

Examples
What does "custom" look like?
Exclude companies from LinkedIn ads post-outbound. Sales views hiding zombie deals. Properties capturing informal influence in deals.
Discovery method
How do you find what to build?
Shadow sales reps. Watch their actual workflow. The automation ideas come from the work, not from a blueprint.
🔄
Tab switching. Rep jumps between HubSpot and another tool → property or integration gap.
📋
Copy-paste patterns. Data manually moved between fields → automation candidate.
🧠
Mental checklists. "I first check X, then Y, then Z" → pre-compute and surface.

Data Richness & Cleanliness

The plumbing. None of the other three systems work if the data is unreliable.

Deduplication
Matching rules & merge strategy
Duplicates are inevitable. Define matching rules, decide which record wins, and build prevention + cleanup.
Country normalization
One standard, enforced everywhere
"Belgium," "BE," "BEL," "België" — pick one, build normalization workflows, enforce across every entry point.
Property movement
Copy, sync, or derive?
One-time copy = snapshot. Live sync = current but limited. Rule-based derivation = flexible but needs maintenance.
Marketing contacts
Who gets billed?
HubSpot bills for marketing contacts. Competitors, employees, churned contacts from 2 years ago should not count. GDPR from day one.
Attribution

At 15–30 deals per quarter, multi-touch attribution is statistically meaningless. Instead: collect raw data cleanly, build one simple attribution field (technical + self-reported), and ask better questions than "which channel gets credit."

Listen first, build second

The shadowing surfaces raw material. The framework turns it into systems. The experience decides what to build, what to skip, and what to build differently than what was asked for.

1
Shadow
Sit with sales reps. Do UX interviews. Understand how the team actually works vs. how they think they work.
2
Structure
Map what you heard to the 4 systems. Identify the key decisions for each one. Fill in the framework.
3
Build (and push back)
Apply SaaS unit economics, sales efficiency, and GTM knowledge. Build systems that solve the real problems, not just faster versions of what existed.
"If I had asked people what they wanted, they would have said faster horses."
— Henry Ford

Full article: The HubSpot Setup I Actually Build for Early-Stage SaaS

maavdnbo.com — SaaS Growth Marketing