HubSpot is one of the most capable CRMs a small business can adopt. It is also one of the easiest to over-build.
The free tier alone gives you contacts, deals, pipelines, tasks, email tracking, meeting links, and reporting. The paid tiers add automation, sequences, custom properties, and enough configuration options to keep an operations team busy for months. Every feature has a use. Almost none of them are needed on day one.
Most small businesses that adopt HubSpot make the same mistake. They configure everything, build elaborate pipelines and automations before the team has logged a single deal, and end up with a system so heavy that the sales team quietly keeps tracking deals in a spreadsheet. The CRM becomes a place data goes to be entered, not a place work gets done.
This is the setup we use with small businesses. It is deliberately minimal. It is designed to be in real use within two weeks, not rolled out over six months.
Before You Touch HubSpot
Three decisions to make before you configure anything.
Decide what HubSpot is for in your business. HubSpot can be a CRM, a marketing platform, a help desk, and a content management system. Pick one job to start. For most small businesses that job is sales: tracking leads, deals, and the activity that moves them. Marketing automation and service tools can come later, once the sales core is in genuine use. Trying to switch on everything at once is the fastest way to use none of it well.
Decide who owns the configuration. CRMs get messy when several people add properties and pipeline stages ad hoc. Name one person, usually the operations lead or the founder, who approves structural changes. Anyone can suggest changes. One person decides.
Map your real sales process on paper first. Before you build a pipeline, write down how a lead actually becomes a customer in your business today. The stages a deal genuinely passes through. Not the stages a textbook says it should. Your HubSpot pipeline should mirror your real process, not impose a generic one.
Build the Pipeline Around Your Real Process
The pipeline is the spine of the CRM. Get this right and the rest follows. Over-build it and the team will resent every deal they have to drag through it.
Keep the stages few and meaningful. Most small businesses need between four and six deal stages. Each stage should represent a real, observable change in the deal, not an internal feeling. A good stage is one you can answer yes or no to from the outside.
A typical small-business pipeline looks like this. New lead, for an enquiry that has arrived but not been qualified. Qualified, for a lead that fits and has a real need. Meeting booked or proposal sent, depending on how you sell. Negotiation, for a deal where terms are being agreed. Closed won and closed lost as the end states.
The mistake to avoid is inventing stages for internal admin steps. "Awaiting internal review" or "follow-up needed" are not stages. They are tasks. Stages track the deal's progress towards a sale. Everything else is activity logged against the deal.
Define what moves a deal from one stage to the next, and write it down. If nobody agrees on what "qualified" means, the pipeline data is meaningless within a month.
Set Up Only the Properties You Will Use
HubSpot lets you create custom properties for contacts, companies, and deals. This is powerful and dangerous. Every property you add is a field someone has to fill in, and a field nobody fills in is worse than no field at all, because it makes the record look complete when it is not.
Start with the default properties and add custom ones only when you have a specific report or workflow that needs them. For most small businesses the essential custom properties are few. Deal source, so you know where business comes from. Deal value, which exists by default. Maybe one or two fields specific to your business, such as service type or region.
Resist the urge to capture everything. A CRM with twelve required fields per contact is a CRM the sales team will fight. Capture the minimum that drives a decision or a report, and nothing more. You can always add a field later when a real need appears. Removing fields after the team has half-filled them for six months is much harder.
Get the Team Logging Activity, Not Just Data
A CRM earns its place when it reflects what is actually happening with customers. That means logged activity: calls, emails, meetings, notes. This is where most CRM rollouts succeed or fail.
Connect email and calendars so that activity logs itself. HubSpot can track emails sent to contacts and log meetings booked through its scheduling links. The less manual logging the team has to do, the more reliable the data. Manual data entry is the first thing a busy salesperson drops.
Use tasks for follow-ups. Every deal that is active should have a next step with a date. The team's daily view should be their task list, not the pipeline. A CRM where the team starts their day looking at "what do I need to do today" is a CRM in use. One where the pipeline is only updated before a sales meeting is a reporting exercise, not a working tool.
Set one rule and enforce it gently. If it is not in HubSpot, it did not happen. Deals discussed in meetings but not in the CRM create a parallel reality that undermines the whole system. The discipline matters more than the configuration.
Skip These Features at the Start
Knowing what to leave out is as important as knowing what to switch on. For a small business getting started, skip the following until the core is in genuine use.
Complex automation. Workflows that move deals, assign owners, and fire emails automatically are useful later, but they encode your process. If your process is still settling, automation just makes the mess move faster. Build automations once the manual process is stable and proven.
Sequences and heavy marketing tooling. Email sequences, lead scoring, and marketing campaigns are a separate discipline. Adding them before the sales core works splits the team's attention and overwhelms the rollout.
Elaborate custom reporting. The default deal and pipeline reports tell you almost everything a small business needs early on. Build custom dashboards once you know which numbers actually drive your decisions, not before.
Multiple pipelines. One pipeline is enough until you genuinely sell two different things in two different ways. Most small businesses do not, and a second pipeline added too early just fragments the data.
Make the Rollout Stick
A CRM only works if the team uses it. The configuration is the easy part. Adoption is the real work.
Train the team on the workflow, not the software. Nobody needs a tour of every HubSpot feature. They need to know how to add a deal, move it through the stages, log activity, and set their next task. Teach the daily loop and nothing else at first.
Lead by using it. If the founder or sales lead checks the pipeline in every sales meeting and asks questions only the CRM can answer, the team learns fast that the CRM is where the real conversation happens. If leadership ignores it, so will everyone else.
Review and prune after a month. Once the team has used HubSpot for a few weeks, look at what is actually being filled in and what is being ignored. Remove the fields and stages nobody uses. A CRM that gets lighter as it beds in is a CRM the team trusts.
What to Do Next
Map your real sales process on paper. Build a pipeline with four to six honest stages that mirror it. Add only the handful of custom properties you will genuinely use. Connect email and calendars so activity logs itself. Then get the team logging real activity for two weeks before you add a single automation. The businesses that get value from HubSpot are not the ones that configured the most. They are the ones whose teams actually use the little they set up.
Related Reading
- ·How to Audit Your Business Tool Stack - work out whether you need a new CRM before you implement one
- ·How to Set Up ClickUp for a 20-Person Team - the same minimal-configuration discipline applied to project management
- ·Systems and Tools - how we design and implement business tool stacks around your real workflows