Most businesses don’t have a HubSpot problem. They have a people problem that looks like a CRM problem. The HubSpot best practices that fix it are simple to state: start with how your people work, put structure in place before automation, automate the repetitive work, build dashboards that lead to decisions, keep removing friction, and review the setup regularly. Follow them and HubSpot stops being admin software and starts helping you grow.
The symptoms are familiar. Sales logs in because they have to, not because it helps them sell. Marketing generates leads nobody follows up. Operations cleans data nobody uses. The system runs, but nobody trusts it: dashboards are glanced at rather than acted on, and automations fire that nobody remembers setting up. The good news is that this is fixable.
| Best practice | The question it answers |
|---|---|
| Start with people and the customer journey | How do we actually work, and where does information get lost? |
| Put structure before automation | Do our stages, properties and owners reflect reality? |
| Automate the boring stuff | Which tasks do we repeat every week? |
| Build dashboards that drive decisions | What decision could we make from this data? |
| Keep removing friction | Where is HubSpot harder than it should be? |
| Review every quarter | What should we prune, replace or change? |
Why should you start with people, not pipelines?
HubSpot rarely fails because it is too complex. It fails because it was set up before anyone asked how the business actually works. Before you launch a single automation, bring marketing, sales and service together and find out what slows them down, where information gets lost and what they don’t trust in the system today. Then map the customer journey and build HubSpot around it.
Ask the team:
- What slows you down every day?
- Where does information fall through the cracks?
- What do you not trust in the system right now?
Then sketch the customer journey on one sheet and ask:
- What happens when someone fills in a form?
- Who owns each follow-up?
- Where does data move automatically, and where does it stop?
A gap here is often an ownership problem. If leads wait days after a form fill because nobody owns the next step, fixing that one gap shortens the sales cycle. If your sales team sees HubSpot as admin rather than an advantage, redesign it so that updating a deal actually helps them close. For the bigger picture of getting started, see how to use HubSpot.
What structure does HubSpot need before you automate?
Too many teams sprint into automation with a messy house. Before you scale, define lifecycle stages around your own customer journey rather than HubSpot’s defaults, standardise naming, clean up ownership and set permissions based on how your team works. If nobody can explain why a property exists, it is clutter, and clutter kills adoption.
- Define lifecycle stages based on your customer journey, not HubSpot defaults.
- Standardise naming conventions for properties, pipelines and deal stages.
- Clean up ownership and make sure every contact links to a company.
- Set permission roles based on how your team actually works.
- Agree a shared definition for every lifecycle stage and property.
Then run a monthly data health check for duplicates, missing stages, contacts with no owner and dead deals left open. Without shared definitions, one rep logs a booked demo as “Opportunity” while another uses it for any email reply, and every report built on that data is fiction. Our guide to fixing duplicate data covers the clean-up in more detail.
What should you automate in HubSpot?
Automate the boring stuff, not the human stuff. Automation isn’t about removing people; it is about removing friction. Write down every task your team repeats twice a week or more, pick three and automate them. Lead assignment, follow-up nudges and meeting scheduling are good places to start. That doesn’t just save time; it protects revenue.
A simple example of a lead-handling chain:
- A prospect fills in a form.
- HubSpot assigns a rep.
- It sends an introductory email.
- It creates a follow-up task.
- It alerts a manager if the lead is untouched after 48 hours.
Leads no longer sit in a queue waiting for someone to notice them.
How do you build HubSpot dashboards that drive action?
A dashboard nobody uses is decoration. Every dashboard, workflow or report should start with a business question, such as where leads are dropping off, what is clogging the pipeline, or which marketing activity leads to deals. If you look at a dashboard and can’t name a decision you could make from it today, rebuild it.
- Define KPIs that reflect real revenue progress.
- Agree definitions across departments before you build anything.
- Design dashboards around today’s priorities, not yesterday’s templates.
- Tie campaigns, forms and emails back to revenue using Campaigns, deal attribution and lifecycle stages.
- Report on revenue influenced, not just opens and clicks, and align sales and marketing around pipeline rather than content output.
Cutting reports back to a few that matter, such as pipeline by source, revenue by campaign and cost per acquisition, gives marketing a seat at the revenue table. If teams are debating whose numbers are right, fix the definitions first, then the dashboards. For the how-to, see creating effective HubSpot dashboards.
How do you keep removing friction and driving adoption?
Once HubSpot is live, your job shifts from building to listening. Every frustration is a clue: a rep skipping unclear fields, a marketer exporting reports to Excel every week, lifecycle stages left un-updated. Interview users regularly, track what is ignored or bypassed, and roll out changes the way you would launch a product, so people actually adopt them.
Listen and fix:
- Interview users monthly and ask, “Where is this harder than it should be?”
- Track tool usage: what is ignored, skipped or bypassed?
- Run monthly user clinics where teams show you what’s confusing, then fix it quickly.
- Turn the feedback into a prioritised improvement plan.
Treat adoption like a product launch. A single onboarding video won’t do it. Instead:
- send internal emails explaining what HubSpot means for each team;
- run short, role-specific micro-training sessions of around 15 minutes;
- make adoption visible and rewarding, for example with team contests or quarterly adoption awards.
For more on this, read why HubSpot adoption fails.
Why review HubSpot every quarter?
HubSpot isn’t a set-and-forget tool. A setup left untouched for long enough ends with nobody trusting the data and usage falling away. Every 90 days, prune the workflows nobody uses, replace remaining spreadsheets with automation, review the reports that didn’t lead to decisions, and track who is using the system and why others aren’t.
Each quarter, ask:
- What needs pruning?
- Where are we still patching gaps with spreadsheets?
- Which reports led to action, and which didn’t?
- Who is using HubSpot, who isn’t, and why?
Treat HubSpot like a product: assign an owner, track changes, test small improvements and celebrate the wins. This isn’t about using more features. It is about tightening the loop between insight and action.
When people, processes and systems are aligned, which is what The APPS Principle™ (Alignment of People, Processes and Systems) assesses, marketing knows what converts, sales knows what to prioritise and leadership sees one version of the truth. The Cogent Blueprint™ is how Cogent puts that into practice: Diagnose, Confirm, Deploy, Adopt and Level Up, with each engagement moving you up one Level. If your setup feels off, you don’t need to start again. Our audit and scoping service is a sensible first step, or book a call to talk it through.
Questions people also ask
Do we need to rebuild HubSpot from scratch if usage is low?
Usually not. If usage is low, reporting is unclear or you're not sure what's working, you need a smarter path forward rather than a rebuild. Find out what slows people down and what they don't trust, clean up the structure, fix the definitions behind your reports, then keep reviewing. Start small and build from there.
How do we stop sales and marketing arguing about lead numbers?
Fix your definitions first, then your dashboards. When marketing says leads are qualified and sales disagrees, it is a reporting definition problem rather than a people problem. Agree what each lifecycle stage means across departments, define KPIs that reflect real revenue progress, and build dashboards on those shared definitions.
What should a monthly HubSpot data health check cover?
Look for duplicates, missing lifecycle stages, contacts with no owner and dead deals left open. Make sure every lifecycle stage and property has a shared definition, so different reps don't update records in different ways. Good data leads to good decisions; bad data leads to budgets based on wishful thinking.
Who should own HubSpot inside the business?
Treat HubSpot like a product and assign it an owner. That person tracks changes, reviews automation and property usage, keeps dashboards in line with current goals and monitors who is and isn't using the system. Without an owner, setups drift, trust in the data falls and usage drops off.