Let me guess: you chose HubSpot at least partly because you heard it was more customizable than other CRMs. And now you're staring at a portal that technically works, but doesn't quite match how your team actually operates, and you're not sure where to start.
That gap is common, and it's usually not a HubSpot problem. It's a sequence problem. Most CRM implementations run into trouble because configuration happened before the business process was clearly defined. HubSpot ended up reflecting what someone thought the process was or wanted it to be, not what actually happens day to day.
This post walks through how to close that gap practically, without starting over.
Before touching any settings, the most useful thing you can do is document what actually happens in your business: from the moment someone first hears about you to the moment they become a customer and (ideally) beyond.
This doesn't need to be formal. A whiteboard photo or a simple flowchart is enough. The goal is to get the steps out of people's heads and onto something you can all look at together.
A few things worth capturing:
One thing this exercise consistently reveals: the process isn't as consistent as most teams assume. That's not a failure on your part, but rather, the whole point. You can't build reliable automation around a process nobody has agreed on yet.
Once you have the process mapped, HubSpot's configuration starts to make a lot more sense. Each step maps to an object, a pipeline stage, or a lifecycle stage. Each decision point maps to a workflow branch or a required field. Each handoff maps to a task, a notification, or a stage change.
HubSpot's CRM is built around a set of standard objects — Contacts, Companies, Deals, and Tickets — each with their own default properties. Every business has unique data needs that don't always fit neatly into those defaults, which is why custom properties and custom objects exist.
Custom properties let you capture data points specific to your business — things like customer tier, territory, product line, or qualification criteria. These properties can be used to segment contacts, trigger workflows, and personalize outreach. You can create custom properties on any standard object.
Custom objects go further. If your business tracks something that doesn't fit neatly into Contacts, Companies, Deals, or Tickets — a property listing, a project, a piece of equipment, a membership — a custom object lets you build that into your CRM with its own properties, pipelines, and associations. Custom objects are available on Enterprise subscriptions.
The property list you build here should come directly from your process map. Every data point you need to capture at a step in your process should become a property somewhere in HubSpot.
Pipelines in HubSpot help visualize processes through stages: steps that signal where a record is in a process. Deal pipelines track that deal's progress towards real revenue. Ticket pipelines track service issues. And you can create pipelines for other objects too, including custom objects.
The most common mistake when setting up pipelines is using stages that describe activities rather than states. A stage like "Proposal Sent" tells you what you did. A stage like "Proposal Under Review" tells you where the deal is. The difference matters because pipeline stages should reflect something objective and verifiable. Something a workflow could evaluate without ambiguity.
If your business has two genuinely different sales processes with different stages, create separate pipelines. If your teams follow the same process but just need visibility separation, permissions and views handle that without the overhead of multiple pipelines.
Once your process is mapped and your data structure is in place, workflows let you automate the repeatable parts. HubSpot workflows are triggered by filter criteria, and then execute a series of actions. This filter criteria can be made up of things like property values, form submissions, lifecycle stage changes, a deal entering a stage, etc.
The key word there is criteria. Automation in HubSpot requires binary, objective truth. A workflow can evaluate whether a deal stage is equal to "Proposal Sent." It cannot evaluate whether a sales rep feels good about a deal. The cleaner your process definition, and the more you've specified what "done" looks like at each step, the more reliably your automation will work.
A few practical places where workflow automation adds the most value in a typical B2B setup:
If you find yourself trying to automate something and can't figure out the right enrollment trigger, that's often a sign the underlying process hasn't been defined clearly enough yet. The automation question becomes easier once the process question is answered.
One of the more underutilized customization options in HubSpot is the record layout, which determines what properties appear on a contact, company, or deal record, and in what order.
By default, HubSpot shows a standard set of properties. But you can customize which properties appear in the left sidebar and in the main body of the record, and you can set different layouts for different teams or pipeline stages. This means a sales rep opening a deal record can see exactly the qualification information they need, without scrolling past irrelevant fields.
This is a small thing that makes a real difference in day-to-day usability, and usability is the difference between a CRM that gets used and one that doesn't.
CRM customization tends to work best when it's iterative. Map the process, configure HubSpot to match, use it for a few months, and then revisit. Your process will evolve, and your HubSpot setup should evolve with it.
It also helps to involve both the people who design your process and the people who actually execute it. They often have different answers to "how does this work right now"... and both answers are useful.
Finally: you don't have to use every feature. HubSpot has a lot of tools, and the temptation to configure everything at once is real. Starting with the pieces that address your biggest points of confusion or drop-off will get you further faster than trying to build everything at once.
Yes. HubSpot workflows can update properties automatically based on criteria you define, such as a form submission, a deal stage change, or a lifecycle stage update. Some properties are also filled in natively by HubSpot, like timestamps for lifecycle stage transitions ("Became MQL Date," "Became Customer Date"). For everything else, workflows handle it.
The key is that the criteria triggering the update need to be clear and objective. Automation can act on a property value, but it can't make judgment calls.
Lifecycle Stage options are the same across Contacts and Companies. You can't have one Lifecycle Stage that is available only on Contacts and not on Companies.
Contacts and Companies can use different values from that set at any time, though. If one of your companies has a Lifecycle Stage of "Customer", the contacts at that company don't necessarily have to also be "Customer". This is especially important when you're dealing with companies with several divisions, where your sales team may be working on several deals that involve people at a large company who have never met before.
You can choose whether you'd like HubSpot to try to keep these in sync for Contacts at Companies in your Lifecycle Stage settings.
HubSpot has conditional property logic that lets you show or hide properties on a record based on the values of other properties. So if a property is only relevant when a deal is in a certain stage, or when a contact meets certain criteria, you can set it up to only appear when it's actually needed. This keeps records cleaner and reduces noise for your team.
To some extent, yes. HubSpot's user permissions let you control what different users and teams can access at a fairly broad level. For more granular control over specific properties (who can edit what), that typically involves a combination of permission sets, required fields, record views and workflow logic rather than property-level access restrictions. It's worth thinking through what you actually need to protect and why before building a lot of structure around it.
You can embed external content like Google Sheets or Excel Sheets directly onto a HubSpot dashboard using the external content embed feature. You don't have to choose between the two during a transition period.
That said, HubSpot's index view (the table view of any object) is closer to a spreadsheet than most people expect. It's filterable, sortable, and editable inline. Worth trying before assuming a spreadsheet is still the easier option.
It depends on what "this" means for your specific process. For automations like workflows, lifecycle stage updates, and email notifications, HubSpot runs in the background regardless of whether anyone is logged in. HubSpot will also track your outgoing emails and email replies via the Outlook or Gmail extension, so that part is automated too.
For data entry, manual activity logging, and task completion, yes, that generally requires your team to be in the tool. (Note: HubSpot is regularly making more updates to their email extensions and mobile app, which is making it easier to do some of these things straight from your email inbox or from your phone.)
The more you automate the data capture side, the less manual daily interaction is required. But HubSpot works best when it's part of how your team already works, not an additional system they check separately.