HubSpot is a reasonable choice for most B2B businesses at the growth stage. It’s flexible, it has a usable free tier, and it integrates with most of the other tools in a typical stack. The problem is that most businesses that use it don’t configure it properly, and then they end up with a database that stores data without producing insight, and a pipeline that the founder doesn’t trust.
The issue usually isn’t the tool. It’s that nobody spent the time to set it up for how the business actually sells.
This post is about what actually needs to be done. Not every feature. Not an exhaustive setup guide. The specific things that determine whether your HubSpot instance becomes useful or becomes another system people avoid.
The context for this is the broader RevOps picture: What RevOps Actually Means covers how CRM architecture fits into a functioning revenue infrastructure. And if you want to understand how pipeline stages work, Pipeline Stage Definitions with Exit Criteria has the template.
The mistake to avoid first
Most founders either set HubSpot up themselves in an afternoon, or they let a junior hire do it, or they use a template an agency gave them.
The result is a CRM that reflects how someone imagined the business might work, not how it actually works. Deal stages that don’t map to the real sales cycle. Properties that nobody fills in. Contact records that have the email address and not much else. A pipeline that exists but doesn’t tell you anything.
Before you configure anything, spend a day writing down your actual sales process. How do deals come in? What happens in discovery? What has to be true before you’d send a proposal? What does closing actually look like in your business? The CRM should reflect that process. If you configure the tool first and try to fit the process to it later, you’ll get something that’s wrong in ways that are hard to unpick.
The five things that actually matter
1. Deal pipeline stages with exit criteria
This is the most important configuration decision you’ll make. The pipeline stages in HubSpot define how you see your revenue: what’s early, what’s late, what’s close to closing. If they’re vague, everything downstream is unreliable.
Each stage needs a name and an exit criterion: the specific condition that must be true before a deal moves forward. Not “we had a good call” but “budget confirmed and decision-maker engaged.” Not “proposal sent” but “proposal presented and next meeting booked.”
The stages themselves should reflect your actual sales cycle. A business that sells to enterprise procurement teams with six-month cycles needs different stages than a business that sells to individual founders who can commit on a call. Don’t use HubSpot’s defaults without thinking about whether they match.
2. Contact and company properties that get filled in
HubSpot has hundreds of properties out of the box. Almost none of them matter for a B2B business at growth stage.
The properties that matter are: company size and sector (does this fit our ICP?), lead source (where did this come from?), deal value and expected close date (for forecasting), and whatever fields your qualification process depends on. If you’re qualifying on headcount, configure a headcount property and make it required to advance past a certain stage.
Everything else is noise. A CRM that asks people to fill in twenty fields per deal is a CRM that gets abandoned. Keep the required fields to the ones that actually inform decisions.
3. A sales sequence or email tracking setup
Even if you’re not using HubSpot’s sequences feature in full, the email integration matters. Having outbound emails logged automatically, and being able to see whether a prospect has opened your proposal or clicked a link, changes how you follow up.
The basic setup: connect your Gmail or Outlook, install the HubSpot sales extension, and make sure outbound emails from reps are being logged against the contact and deal records. This takes an hour and is one of the highest-return configurations you can do.
4. Reporting that covers the metrics you actually care about
HubSpot has a dashboard builder. Most people don’t use it, or they use it for vanity metrics that don’t inform decisions.
The reports worth building first: deals created by source (is your lead generation working?), conversion rate by stage (where are deals falling out of the pipeline?), average deal cycle (how long does it actually take?), and deals created vs deals closed by month (are you building or running down the pipeline?).
These four reports will tell you most of what you need to know about whether your revenue function is working. You can build them in about two hours and they’ll pay for themselves the first time you use them in a pipeline review.
5. Deal owner accountability
Every deal should have a single owner. Not a shared inbox, not “the team.” One person whose job it is to move that deal forward.
This sounds obvious but HubSpot makes it easy for this to go wrong: deals without owners, deals assigned to people who’ve left, deals where the owner has changed three times without the record being updated. A monthly CRM audit to clean up ownership is worth building into the rhythm.
What you can ignore for now
HubSpot has a lot of features that are genuinely useful, but not yet. Marketing Hub automation, predictive lead scoring, revenue attribution, custom objects. None of these matter until the foundation is right.
The sequence is: configure the pipeline stages, get the right properties filled in consistently, build the basic reports, establish the review cadence. Do that for six months. Then look at what else would be useful based on what questions you can’t yet answer.
Adding complexity before the foundation is solid produces a system that’s impressive-looking and practically useless.
How to know if your HubSpot is working
Three tests worth running regularly.
First: could a new person join your sales team and understand the state of every live deal from the CRM alone, without asking anyone? If not, the records aren’t good enough.
Second: can you produce a 90-day revenue forecast from the pipeline data right now, without having to cross-reference a spreadsheet? If not, either the data quality or the stage definitions (or both) need work.
Third: do the reps actually use it without being chased? If pipeline reviews are still being run from memory or from spreadsheets the reps maintain separately, the CRM hasn’t been adopted. That’s a process and management problem, not a technology problem.
If you want to understand what a properly configured revenue infrastructure looks like beyond just the CRM, What RevOps Actually Means covers the full picture: reporting, process architecture, and tech stack management. And if you’re building this from scratch rather than fixing an existing setup, How to Build a Sales Process From Scratch is the place to start.