HubSpot as an operational backbone: What it can do, what it can't do, and what companies are building to make up the difference

HubSpot has more than 258,000 paying customers in more than 135 countries. [1] In the Spanish mid-market—especially in sectors such as hospitality, education, retail or professional services—it has become the central system for business data: the place where contacts, deals, interactions and campaigns live.

For many of these companies, HubSpot is no longer just a CRM.
It is, in practice, your “business ERP”.

This position has clear advantages. It's an easy-to-use tool, with more than 1,500 integrations in its marketplace, that unifies marketing, sales and customer service on a single platform and with a documented ROI of 505% over three years. [3]

But it also has limits.

And those limits don't usually appear at the time of purchase. They appear twelve to twenty-four months later, when the company grows and processes that are not strictly commercial begin to be left out of the system.

This item is not a Review from HubSpot.
It's an analysis of where their real capabilities end and what companies build to cover what's left out.

What HubSpot Does Right (and Why 38% of the Marketing Automation Market Is Yours)

HubSpot leads the market for marketing automation with a share of 38%. [3] This is no accident.

Its design focused on usability, its model Freemium and its training ecosystem and partners have created a base of adoption that no competitor matches in the mid-market segment.

In addition, its expansion within the customer is significant: 35% of its Pro+ customers use four or more hubs —Marketing, Sales, Service, CMS, Operations or Commerce—, which indicates that, in many cases, it has gone from being a CRM to becoming the central operating platform. [2]

The areas where HubSpot offers truly strong capability are clear:

• CRM: managing contacts, companies, deals and pipeline with a unified view of the customer
• Marketing Hub: email marketing, nurturing automation, landing pages, forms and campaign management
• Sales Hub: sequences, meeting schedule, opportunity tracking and sales forecasting
• Service Hub: tickets, knowledge base and chat with customers
• Operations Hub: data synchronization and data quality automation between systems

For a company with between 50 and 300 employees whose business depends on selling — services or products — with a structured business cycle, HubSpot covers between 80% and 90% of the needs.

Gartner's position as a Leader in B2B Marketing Automation supports this reality. [6]

Structural Limits: What HubSpot Can't Do by Design

But HubSpot doesn't try to cover everything.

It is a system of Front-office: It is designed to manage the customer relationship, the sales pipeline and marketing.

It is not a system of back office.

It does not manage inventory, production, logistics, accounting, human resources, or internal processes that do not have direct interaction with the customer.

And this is not a one-off limitation. It's a design decision.

Gartner does not position HubSpot in any quadrant of ERP, Supply Chain, or operating systems. [6] Its absence in these categories is neither temporary nor accidental: it responds to its strategic approach.

HubSpot is optimized to capture and manage demand.
Not to run the company's internal operation.

And it is precisely on that border where gaps begin to appear.

The CRM—ERP gap: the source of 70% of forecasting problems

The most documented gap in companies that use HubSpot as a central system is not within the CRM itself, but in what happens outside of it. The disconnect between business data and operational data is, in practice, one of the main points of friction in the organization's daily life.

Cherry Bekaert places this gap at the root of 70% of pipeline visibility and revenue forecasting problems in mid-market companies. [11] In parallel, 68% of organizations identify data silos as their main obstacle to digital transformation. [7]

The pattern is repeated quite consistently. The deal is closed in HubSpot, but from there the process continues in other systems: the order is generated in the ERP, the invoice is issued from the ERP and the payment is recorded in accounting. Each of these steps occurs correctly within your own system, but information doesn't automatically flow between them.

This creates a clear operational disconnect. The sales team considers the opportunity closed, but has no visibility as to whether the order has been processed or if it has been charged. The operations team manages the order without context about the customer's business origin. And management needs a consolidated vision that no system offers natively.

The result is a recurring process of manually reconstructing information. Data exists in each system, but it is not connected to a single operational narrative that allows for agile decision-making.

When this integration does exist, the impact is measurable. Companies that connect CRM and ERP reduce sales closing time by 14% and improve forecast accuracy by 32%. [11]

In this context, integration ceases to be a technical issue and becomes a structural element: it is what separates an organization that operates with full visibility from another that makes decisions with partial information.

What companies build to cover gaps

When HubSpot becomes the central front-office system, it doesn't take long for limits to appear. And the important thing is not that companies replace it, but how they complement it.

CRMs are, in fact, the second category of SaaS tools with the highest pressure to replace or expand using customized internal tools, depending on the Build vs. Buy Report of Retool 2026. [5] In the Spanish mid-market, this adaptation usually follows fairly clear patterns.

1. The HubSpot—ERP integration via iPaaS

The first step is usually to connect HubSpot to the ERP.

Tools such as Make, n8n or Zapier allow you to synchronize key data between both systems: deals, orders and invoices. HubSpot offers native connectors with some ERPs — such as NetSuite — and its Operations Hub includes synchronization features. However, in the Spanish context, where systems such as Sage 50, A3ERP or Navision are common, these integrations usually require additional configuration or specific development.

When this connection is well resolved, the impact is immediate.

The closing of a deal in HubSpot ceases to be the end of the business process and becomes the automatic start of the operation: the order is generated in the ERP with the data already synchronized, and any subsequent change—such as invoicing—is reflected back in the CRM.

This eliminates a significant part of the internal friction.

The sales team doesn't need to leave HubSpot to understand what's happening with their customers. The operations team works with consistent information from the source. And management stops relying on manual reconstructions for a reliable view of the business.

Rather than a technical improvement, it is a change in the way they operate: systems begin to behave as a single source of truth, rather than as isolated pieces that must be constantly reconciled.

2. The custom-built customer or supplier portal

Another common gap appears in the ongoing relationship with the customer.

HubSpot includes a CMS and basic functionality of membership, but it's not designed to build customer portals with specific business logic: access to orders, invoice history, project status, or customized documentation.

When a company needs to provide that visibility, the solution is rarely to force HubSpot. The usual thing is to build an external portal connected to both the CRM and the ERP.

This portal acts as an additional layer on top of existing systems.

In many cases, it is built with tools such as WeWeb on the frontend —capable of connecting directly to APIs—, with business logic orchestrated in n8n and with Supabase as an intermediate database. This layer makes it possible to unify the information that comes from HubSpot and the ERP without relying on rigid integrations between the two.

The result is a system that HubSpot, by design, doesn't intend to be.

A portal with a modern user experience, real-time access to relevant information and adapted to specific company processes. All this without the cost, time and rigidity of custom development from scratch.

At this point, the pattern repeats itself again: HubSpot is still the central customer relationship system, but it needs additional layers to cover processes that are beyond its reach.

3. The operational reporting dashboard

The third pattern appears in reporting.

HubSpot's native dashboards do their job well: they show pipeline, business activity, and marketing performance. But they are limited to data from the CRM itself. They do not include operational ERP information or financial accounting data.

For management, this creates an obvious problem: decisions are not made with business data alone. They need a vision that combines sales, operations and finance in one place.

Therefore, the usual solution is to build an external dashboard —in Power BI, Tableau or Looker Studio— that connects simultaneously to HubSpot via API and to the ERP through connectors or direct access to the database.

But here comes another level of complexity.

The value of the dashboard is not in the tool, but in the previous design. Deciding what HubSpot data is relevant, what ERP data should be incorporated, how it relates to each other, and how often it should be updated is what determines if the system will be useful or not.

When that design doesn't exist, the result is predictable: the dashboard is built, but not used. The numbers don't match, the definitions aren't clear, and each area interprets the data differently.

HubSpot is an excellent platform for what it was designed to do: managing business relationships with customers.

The most common mistake a midsize company makes is not choosing HubSpot.
It is to hope that it will also resolve the operational processes that are behind that relationship.

Understanding that limit is not a criticism of the system.
It is the first step in designing a coherent technological ecosystem, where each piece fulfills its function and critical processes do not depend on what a tool —by definition— does not intend to be.

References

[1] HubSpot. (2025). Q1 2025 Earnings Call. HubSpot Investor Relations. https://ir.hubspot.com

As of March 31, 2025, HubSpot had 258,258 paying customers (+19% YoY). Revenue for Q1 2025: $690M, with billings estimated at $766.8M (+20% YoY). Total revenue in 2024: $2,630M (+21% YoY). Presence in more than 135 countries.

[2] HubSpot. (2025). Q4 2024 Earnings Call. HubSpot Investor Relations. https://ir.hubspot.com

35% of Pro+ customers use four or more hubs, with 7% year-on-year growth. Enterprise contracts grew 21% YoY and net revenue retention (NRR) stood at 102% in Q1 2025.

[3] Hublead/multiple sources. (2026). Essential HubSpot Statistics 2026. https://www.hublead.io/blog/hubspot-statistics

HubSpot has a 38% share in marketing automation. Companies that use it report an ROI of 505% over three years and launch campaigns 68% faster. More than 200,000 professionals are certified in the HubSpot Academy.

[4] Resonate HQ. (2026). HubSpot Market Share in 2026: CRM Industry Analysis & Growth Trends. https://www.resonatehq.com/blog/hubspot-market-share

HubSpot surpassed 230,000 active customers in 2025, with international growth exceeding domestic growth. EMEA is the fastest-growing region. Compared to Salesforce, it stands out in usability and implementation time; compared to Salesforce and Microsoft, it loses in advanced customization and complex enterprise deployments.

[5] Retool. (2026). The Build vs. Buy Shift: How Vibe Coding and Shadow IT Have Reshaped Enterprise Software. BusinessWire. https://www.businesswire.com/news/home/20260217548274

CRMs are the second category of software with the highest pressure to replace or complement internal tools, only behind workflow automation tools.

[6] Gartner. (2024). Magic Quadrant for B2B Marketing Automation Platforms. Gartner Research.
HubSpot is positioned as a leader in B2B marketing automation. It does not appear in the ERP or Supply Chain quadrants, confirming its position as a front-office tool, not an operational management tool.

[7] MuleSoft (Salesforce). (2024). 2024 Connectivity Benchmark Report.
68% of organizations identify data silos as their main obstacle. The lack of integration between CRM and operating systems (ERP, logistics, production) is the most common gap in companies with 100 to 500 employees.

[8] Porters Five Force. (2025). Competitive Landscape of HubSpot. https://portersfiveforce.com/blogs/competitors/hubspot

HubSpot outperforms Salesforce and Microsoft in usability and speed of implementation in SMB and mid-market, while they surpass it in advanced customization, integration with legacy systems and global deployments.

[9] SaaStr. (2025). The Complete History of HubSpot's Net Revenue Retention. https://www.saastr.com

HubSpot's NRR has evolved from 88.6% in its IPO (2014) to 115% in 2021 and 102% in Q1 2025. 37% of Pro+ customers use four or more hubs, reflecting growing adoption as a complete platform.

[10] HubSpot. (2026). HubSpot Integrations Marketplace. https://ecosystem.hubspot.com/marketplace/apps

The HubSpot marketplace has more than 1,500 integrations. Integrations with industrial ERP systems (SAP, Oracle) are limited and in many cases developed by third parties.

[11] Cherry Bekaert. (2025). The Cost of Data Silos: Why CRM-ERP Integration Matters.
https://www.cbh.com/insights/articles/the-cost-of-data-silos-why-crm-erp-integration-matters/

The lack of integration between CRM and ERP explains 70% of visibility problems in pipeline and forecast. Companies that integrate both systems reduce the sales cycle by 14% and improve forecast accuracy by 32%.