HubSpot is a powerful CRM. It can organize your pipeline, automate follow-up, give leadership better visibility, connect marketing and sales, and make a complicated sales process easier to manage.
It can also make a mess of things.
Usually, that isn't because HubSpot itself is the problem. The trouble starts when a business begins configuring the software before it has taken the time to understand how its sales process actually works.
Default properties get adopted because they're already there. Deal stages get created because someone thinks they sound right. Workflows automate steps nobody has really agreed on. Reports are built on data the sales team doesn't consistently enter.
A few months later, everyone technically has a CRM, but salespeople are still keeping notes somewhere else, managers don't trust the pipeline, and leadership is asking why HubSpot isn't delivering the visibility they expected.
The CRM has become another layer of work instead of making the work easier.
A good HubSpot implementation should do the opposite. It should take the way your business sells and make that process easier to follow, manage, measure, and improve.
Here are some of the most common ways that goes wrong.
1. Your Deal Stages Don't Match the Way Customers Actually Buy
One of the first things most companies build in HubSpot is a deal pipeline.
It also happens to be one of the easiest things to get wrong.
A pipeline might start with stages like:
- New Opportunity
- Discovery
- Presentation
- Proposal
- Negotiation
- Closed Won
That looks reasonable. The problem is that the stages may describe what your salesperson is doing rather than what has actually happened with the buyer.
For example, "Proposal Sent" tells us that sales completed an activity. It doesn't necessarily tell us anything about the customer's commitment to the process. Maybe the buyer asked for the proposal. Maybe the salesperson sent one because the conversation was going nowhere and they hoped a proposal would revive it.
Those are very different opportunities.
Your deal stages should represent meaningful changes in the sales process, with clear criteria for entering and leaving each stage. Salespeople shouldn't have to guess whether a deal belongs somewhere, and managers shouldn't have to interpret the pipeline differently depending on who owns the opportunity.
Before configuring the pipeline in HubSpot, map the real sales process. Look at what actually happens from the first qualified conversation through a buying decision. Then build the CRM around those milestones.
2. You Automate a Process Nobody Has Agreed On
HubSpot makes automation very tempting.
A deal moves stages, so create a task. A property changes, so send an email. A lead becomes qualified, so assign it to someone. A form comes in, so update five records and enroll the contact in a workflow.
Automation can save an enormous amount of time when the underlying process makes sense.
It can also scale confusion remarkably efficiently.
If sales and marketing haven't agreed on what qualifies a lead, automating the handoff doesn't solve the disagreement. If nobody knows when an opportunity should move into a particular stage, automatically triggering tasks from that stage simply adds more activity around an unclear process.
We've seen companies start with the question, "What can HubSpot automate?"
A better starting point is, "What should happen consistently?"
Document that process first. Run it. See where people get stuck. Understand which steps require human judgment and which are predictable enough to automate.
Then use HubSpot to remove repetitive work from a process you already understand.
3. Your CRM Asks Salespeople to Enter Data Nobody Uses
Every CRM implementation eventually runs into the same temptation: collect everything.
Industry. Revenue. Number of employees. Lead source. Product interest. Competitor. Buying timeframe. Budget. Pain points. Decision process. Next step. Last contact. Ten different qualification fields.
All of that information could theoretically be useful.
The sales rep who's trying to update six opportunities at the end of the day may feel differently.
Every required field creates work. If salespeople don't understand why a field matters, they'll find the fastest way through it. Sometimes that means guessing. Sometimes it means selecting the same value every time. Sometimes they stop updating the CRM altogether.
Then reporting becomes unreliable, which causes leadership to ask for even more data.
Before adding a property, ask what decision it supports.
If knowing the buyer's industry changes how you sell, capture it. If a specific qualification field helps determine whether an opportunity should move forward, make it part of the process. If management uses a field to forecast revenue or identify where deals are getting stuck, there is a reason to maintain it.
If nobody does anything differently based on the information, you may not need to ask sales to enter it.
Good CRM data comes from creating a system people understand and use consistently, not from collecting the maximum amount of information possible.
4. Marketing and Sales Have Different Definitions of the Same Customer
This problem often existed long before HubSpot arrived.
Marketing says it generated 100 leads.
Sales says it received 12.
Marketing says an opportunity is qualified because the person requested a consultation. Sales says half of those people were never real opportunities.
Someone asks how many qualified leads turned into customers, and suddenly everyone is debating what "qualified" means.
A CRM won't resolve those disagreements automatically. In some cases, it simply makes them easier to see.
Before configuring lifecycle stages, lead statuses, qualification fields, routing rules, or reporting, marketing and sales need shared definitions.
What makes someone a lead?
When is someone ready for sales?
What makes an opportunity qualified?
When does an opportunity belong in the pipeline?
What happens when someone isn't ready yet?
What information needs to move from marketing into sales?
Those decisions should come before the workflow.
Once the definitions are clear, HubSpot can help enforce them consistently and show you where the customer journey is breaking down.
Without that alignment, the CRM ends up maintaining two versions of reality inside the same database.
5. Your Dashboards Look Precise, but the Data Underneath Them Isn't
One of the great things about HubSpot is the visibility it can provide.
One of the dangerous things about any CRM is that a polished dashboard can make bad data look authoritative.
A report says you have $800,000 in pipeline. Great.
How much of that pipeline is real?
Are deals being moved through stages consistently? Are close dates updated? Do salespeople leave dead opportunities open because nobody defined when they should be closed? Does one salesperson qualify opportunities much more aggressively than another?
The dashboard can only report what the system contains.
This is why reporting design should begin with the business questions leadership actually needs answered.
You might want to know:
- Where qualified opportunities are coming from
- How opportunities progress through the pipeline
- Where deals tend to stall
- How long the sales cycle takes
- Which opportunities are most likely to close
- Why deals are being lost
- Whether marketing is creating opportunities that sales can actually convert
Once you know the questions, you can work backward and determine which processes and data points need to be reliable enough to answer them.
Building reports first and hoping the data eventually catches up usually creates a lot of dashboards nobody fully trusts.
6. The Implementation Is Technically Correct, but Nobody Wants to Use It
A HubSpot implementation can be perfectly logical on paper and still fail.
The workflows work.
The properties exist.
The pipelines are configured.
The dashboards are beautiful.
The sales team hates it.
This is where CRM projects often get reduced to technical configuration when the real issue is adoption.
Salespeople need to understand how HubSpot helps them do their jobs. If every interaction with the CRM feels like administration for management's benefit, adoption will always be a fight.
That doesn't mean salespeople should get to ignore process or refuse to enter important information. It does mean the implementation should remove unnecessary friction wherever possible.
Can information be captured automatically?
Can the number of required fields be reduced?
Can views be organized around what a salesperson actually needs to see?
Can tasks and reminders replace things people currently keep in their heads?
Can automation eliminate repetitive updates?
Can the system make the next action obvious?
The closer HubSpot gets to the actual work of selling, the easier it becomes for people to use it consistently.
Training also matters, but training shouldn't be a tour of every HubSpot feature. People need to understand the parts of the system that apply to their role, the reason the process is structured that way, and what good usage looks like day to day.
Start With the Sales Process, Then Build HubSpot
A lot of CRM problems are diagnosed as configuration problems.
Sometimes they are.
More often, configuration exposes process problems that were already there.
The team never agreed on qualification. Deal stages were loosely defined. Sales and marketing had different expectations. Managers forecasted differently. Important follow-up depended on individual memory. Nobody had really decided what information needed to be captured or why.
HubSpot gives you an opportunity to fix those things, but only if you resist the urge to start with the software.
We prefer to understand the operating process first.
How does a new opportunity enter the system? What happens next? Who owns it? What information matters? What decisions need to be made? Where do handoffs happen? What does management need to know? Where does the current process break down?
Once those answers are clear, HubSpot becomes much easier to design.
The CRM becomes the system supporting your process instead of the place where your process gets invented by accident.
Your HubSpot Portal Should Reflect the Way Your Business Works
Two companies can both use Sales Hub and need completely different implementations.
A staffing firm may need to manage relationships between companies, contacts, job opportunities, and recruiting activity.
A manufacturer may have long sales cycles, multiple stakeholders, complex quoting, and account-based relationships.
A SaaS company may care heavily about lifecycle transitions, recurring revenue, expansion, and customer success.
Trying to force all of those businesses into the same generic HubSpot setup would miss the point.
HubSpot gives you building blocks. The value comes from configuring those building blocks around the way your team actually sells, serves customers, and makes decisions.
That is also why copying somebody else's pipeline or downloading a generic "perfect CRM setup" rarely solves the real problem. You may get useful ideas from it, but your system still has to reflect your business.
A Good HubSpot Implementation Should Make the Sales Process Easier to See
You should be able to look at HubSpot and understand what is happening without conducting an investigation.
Salespeople should know what deserves their attention.
Managers should understand where opportunities are moving and where they're getting stuck.
Marketing should be able to see whether the leads it generates become real sales opportunities.
Leadership should be able to trust the reports well enough to make decisions.
And new employees should have a system that helps them understand how the business sells rather than relying entirely on tribal knowledge.
That's the standard.
HubSpot can absolutely help you get there. The implementation just has to begin with the business instead of the software.
Build HubSpot Around the Way You Actually Sell
Orange Pegs helps businesses implement and optimize HubSpot around their real sales processes, customer journeys, handoffs, and reporting needs.
If your CRM feels disconnected from the way your team actually works—or you're preparing for a new HubSpot implementation—we'll start by understanding the process before deciding how the platform should be configured.
