.png)
What HubSpot does, and doesn't do, out of the box
HubSpot can support your business from the moment you switch it on. It can capture enquiries, store customer records, log activity, trigger follow-up, and give your team a working CRM.
What it does not do out of the box is model how your business actually runs.
That is the gap most teams run into. The platform is live, contacts are coming in, and the dashboards are filling up. But the system still does not reflect how you win work, how revenue is really made, or where it leaks away. Buying the licence gets you the platform. It does not get you the design.
Jump to your sector:
- Software and SaaS
- Consumer and field services
- Agencies and marketing services
- Financial services and capital markets
- Industrial, energy and production
What HubSpot gives you on day one
HubSpot starts with standard records for contacts, companies, deals and tickets. It can capture form submissions, track original source, log emails and meetings, and deduplicate contacts by email address. If someone enquires through your website, the CRM registers the lead and shows where it came from.
It also comes with a default deal pipeline, standard lifecycle stages, and the tools that feed the database: forms, landing pages, tracking code and marketing assets. On the right subscription you also get workflows, sequences, lead scoring and reporting dashboards.
That gives you a working starting point. It is still a generic one. No business runs on generic stages and generic definitions.
What still needs to be designed
Six things decide whether HubSpot reflects your business or just stores records about it.
Qualification. Which contacts are worth pursuing, which are out of scope, and which need action today.
Routing. Who picks up a new enquiry or account, and on what basis: territory, product, size, urgency or existing relationship.
Pipeline design. The stages your revenue actually moves through. If those stages are not visible, you lose sight of where demand turns into revenue and where it drops away.
The data model. Which fields matter, which records they belong on, and whether the standard objects are enough or you need custom ones.
Integration. Which other systems hold commercially important data, how it reaches HubSpot, which platform owns each field, and what happens when two sources disagree.
Reporting. What counts as a lead, an opportunity and a win, and which timestamps leadership should trust.
HubSpot will run workflows on top of unclear rules without resistance. It will automate whatever process you give it, whether that process is sound or not.
What those six look like depends on your sector. Go to yours below.
Software and SaaS
In a SaaS business, most of the revenue that matters happens after the first deal closes. Renewals, expansion and churn decide the year. Out of the box, HubSpot is set up to track the first sale.
A SaaS example
Take a UK B2B software company selling annual subscriptions, with free trials feeding a sales team.
HubSpot can capture the trial sign-up, create the contact and company, record the original source and open a deal. Marketing can see which campaign drove the demo request.
What HubSpot does not know by default is whether that trial user ever activated, which product workspace belongs to which company record, what the account pays according to your billing system, when the contract renews, or whether usage dropped three months before the renewal conversation. That data lives in the product and the billing platform, and it never reaches the CRM unless someone designs the route.
What gets designed in practice
- Product usage is mapped to company records, not just to individual users, so account health is visible where the account owner works.
- Billing data such as plan, contract value and renewal date syncs into HubSpot, with one system named as the owner of each field.
- New business, renewal and expansion run as separate pipelines, because they are different motions with different owners and forecasts.
- Renewal dates trigger workflows a set period ahead, so the conversation starts before the notice window rather than after it.
- Churn reasons are captured as structured fields, not free text, so they can be reported on.
Once that is in place, you can forecast renewals from the CRM, see churn risk while there is still time to act, and tie expansion revenue back to where the account came from.
Indeemo's enterprise accounts span multiple regions and billing entities. Before anything was built, the contact and lead model had to be designed around that structure. Six platforms, including Close CRM, Freshdesk and SendGrid, now run as one HubSpot environment.
Consumer and field services
A consumer field services business does not operate through generic sales stages. It operates through lead response time, booking windows, postcode coverage, quote turnaround and engineer capacity.
A field services example
Take a residential heating and plumbing company generating enquiries for boiler replacements, repairs and annual servicing.
Out of the box, HubSpot can capture a website form, create the contact, record the original source, and open a deal or ticket. The team can see that an enquiry arrived. Marketing can see whether it came from paid search, organic traffic or a social campaign.
What HubSpot does not know by default is whether the lead is inside your service area, whether the customer wants an emergency repair or a planned installation, whether a survey is needed before quoting, whether somebody called back within target time, or whether the job was worth pursuing once travel time, parts and labour were counted.
The real pipeline is rarely a neat sales sequence either. It is closer to: enquiry received, callback attempted, survey booked, quote sent, follow-up complete, job won or job lost. Those rules are operational. They need to be designed.
What gets designed in practice
- Enquiry forms capture the details that matter early: postcode, service needed, urgency, property type and preferred contact method.
- Workflows route new enquiries to the right person based on area, trade or urgency.
- Lead response time is measured from real timestamps, so management can see whether the team is actually calling back quickly enough.
- The pipeline reflects the journey from first enquiry to booked job, so quote-to-job conversion is visible stage by stage.
- Quote follow-up is structured, so the team can separate lost jobs, delayed decisions and quotes that were never chased.
- Booking and job-management data syncs back into HubSpot, so marketing source, quote activity, engineer scheduling and won revenue sit together instead of across disconnected tools.
Once that is in place, you can see which channels bring in the right enquiries, how long it takes to get from first contact to quote, which services convert best, and where jobs are being lost.
Agencies and marketing services
An agency's margin is made or lost in the mix between retainers and projects, and in how closely the hours delivered track the hours sold. Out of the box, HubSpot sees neither.
An agency example
Take a mid-sized UK agency with a mix of monthly retainers and one-off projects, running new business through HubSpot.
HubSpot can track the pitch as a deal, store the client's contacts, log the proposal emails and report on new business won by source.
What HubSpot does not know by default is whether a win is a retainer or a project, when each retainer is up for renewal, how many hours the team is delivering against what the client pays for, which clients are profitable once time is counted, or what the client is expecting to see in their monthly report. Time tracking and resourcing usually sit in another tool, and client reporting often lives in a spreadsheet someone rebuilds every month.
What gets designed in practice
- Deals and line items distinguish retainer from project revenue, so the retainer share of the book is always visible.
- Retainer start and end dates drive renewal workflows, with the account lead notified well before the review.
- Time tracking or resourcing data syncs into HubSpot against the client record, with a clear owner for each field, so utilisation sits next to revenue.
- Upsell and scope changes run through their own pipeline, so growth within existing clients is tracked separately from new logos.
- Client reporting is built as dashboards that can be handed to the client, rather than rebuilt by hand each month.
Once that is in place, you can see which retainers are at risk, which clients are over-serviced, and how new business and account growth each contribute to the year.
Financial services and capital markets
In financial services, the CRM has two jobs: showing the pipeline, and keeping a clear record of what happened and when. Out of the box, HubSpot logs activity and changes, but it doesn't know which of them matter to your business or how they should be reviewed.
A financial services example
Take a UK investment or wealth firm where advisers track their pipeline in a spreadsheet that runs alongside the CRM.
HubSpot can store contacts and companies, log emails and meetings, and move deals through a default pipeline. Leadership can see some activity.
What HubSpot doesn't know by default is how your relationships are structured, meaning the individuals, households and entities, and the funds or mandates they sit in. It doesn't know which adviser owns each relationship or the assets under management each one represents. It doesn't know where a prospect is in onboarding and checks, or which record changes your team actually needs to be able to show later. Assets data usually sits in a portfolio or platform system. The spreadsheet exists because the CRM was never designed to hold what advisers actually need.
What gets designed in practice
- The data model reflects how relationships are really structured, using associations and, where needed, custom objects for entities or mandates.
- Adviser ownership and team permissions are set deliberately, so each adviser sees their own book and access to sensitive information is limited to the people who need it.
- Pipeline stages map to your onboarding steps, with the checks at each stage held as required properties so nobody has to remember them.
- Assets under management and mandate data sync from the system that owns them, so pipeline value in HubSpot reflects real figures.
- Communication logging and stage-change history are defined up front, so the sales and onboarding history sits in the CRM, alongside your firm's own record-keeping rather than instead of it.
Once that is in place, leadership sees adviser pipeline without asking for the spreadsheet, and the history of each relationship is in one place instead of scattered across inboxes.
Industrial, energy and production
Across manufacturing, energy and production, the price you agree is rarely the price you end up earning. Margin moves between the quote and the invoice. The data that shows where sits in the ERP, the order system or the job sheet. Out of the box, HubSpot sees none of them.
Where the leak happens depends on how you sell. If you install, it leaks between quote and completion, through install costs that overrun the quote and jobs that slip between order and handover. If you make or distribute, it leaks between the price list and the invoice, through trade terms agreed account by account, rebates tracked outside the CRM, and orders that ship short because stock went elsewhere.
An industrial example
Take a UK manufacturer that prices and quotes from its ERP, installs through its own teams or subcontractors, and runs sales activity in HubSpot.
HubSpot can capture the enquiry, track the opportunity as a deal, log calls and site visits, and report on pipeline by rep.
What HubSpot doesn't know by default is current stock or lead times, the prices and terms the ERP holds, or whether the quoted price survived to the invoice. It doesn't know what the install actually cost against the quote, or which product lines an existing customer has never bought from you. Reps end up quoting from one system and selling from another, and nobody sees the margin until month end.
What gets designed in practice
- The product catalogue syncs from the ERP, with the ERP owning price, stock and account-level terms, so reps work from current figures.
- Deals in HubSpot carry the ERP quote or order reference, so each one can be traced to what was invoiced.
- Margin is captured at quote and again at invoice, so the gap is visible deal by deal.
- Install or fulfilment runs as its own set of stages after the win, so slippage shows up before it becomes a write-off.
- Order history and reorder frequency sit on the company record, with a white-space view of the product lines each account doesn't yet buy.
Once that is in place, you can see where margin leaks, which accounts have room to grow, and which reps are winning profitable work rather than just volume.
What the result looks like
Across every sector the pattern is the same. The default setup captures that something happened. The design work decides whether the CRM can tell you why revenue moved, where it is leaking, and what to fix first.
HubSpot provides the structure. The commercial clarity comes from the rules, routing, data and reporting designed on top of it. That design is the part the licence does not include.