For years, the typical GTM technology journey has been straightforward: start on HubSpot, grow the business, and eventually move to Salesforce.
But what if enterprise readiness isn't about graduating from one CRM to another?
That question was the starting point for a recent RevOps Co-op webinar on HubSpot enterprise readiness, and the conversation offered a more useful way to think about the decision: choose the platform that fits the complexity of your business, then build the data and processes around it that allow it to scale.
The conversation featured:
- Ed King, founder and CPO at Openprise
- Georgina Tsioutsiouli, group manager of sales operations at Foxit
- Amani Phipps, revenue architect at Bonusly
- Matthew Volm, founder of RevOps Co-op, moderating
The panel covered everything from how "enterprise" actually gets defined, to a live Salesforce-to-HubSpot transformation in progress, to what a data orchestration layer can add when a CRM needs to support a more complex GTM environment.
Here are five takeaways GTM teams can pull from the discussion.
HubSpot enterprise readiness comes down to whether your data, processes, and team capacity can support the business at its current complexity—not whether you've crossed a specific headcount or revenue line.
1. HubSpot enterprise readiness is a complexity question, not a headcount number
A live poll asked the audience how they define "enterprise." Most attendees pointed to headcount.
The panelists offered a different perspective. Tsioutsiouli put it plainly:
"Revenue and headcount are mostly marketing indicators. They're not RevOps or SalesOps indicators of what's enterprise ready." – Georgina Tsioutsiouli
A construction company with 1,000 employees might only need 50 people logged into the CRM. A 50-person company running a genuinely unusual process might need enterprise-grade infrastructure from day one.
King pointed to another useful signal: systems of record, or the number of distinct platforms a business runs on. As companies grow, they tend to add systems, data sources, and GTM motions. The ability to connect those systems and keep data consistent becomes increasingly important.
Phipps framed enterprise readiness around the GTM motion itself. At Bonusly, that means coordinating users across 15 countries, managing deal splits, and keeping account executives and customer success tightly aligned.
The better question isn't "How many employees do we have?"
It's "Can our current platform, data, and processes support the complexity of how we go to market?"
That gives GTM teams a much more useful framework for evaluating whether HubSpot is still the right fit.
2. The right CRM decision starts with the business, not the conventional growth path
King shared a story that illustrates what can happen when teams step back and evaluate the actual business need.
A returning Openprise customer accepted a new role and, three months before his start date, told King that his first nine months would involve a Marketo migration.
He'd never even logged into the company's HubSpot instance.
Six months into the job, he came back with a different plan. He'd talked to internal users and mapped where the real friction lived.
His marketing and sales teams actually preferred HubSpot's interface and campaign tools. The opportunity was to strengthen the backend and automation capabilities around the platform they already liked using.
The HubSpot instance stayed. The teams avoided a disruptive migration and focused instead on the capabilities they actually needed.
That experience reflects an important shift in how GTM teams can evaluate their technology stack. When a business starts experiencing scale-related friction, the answer may be to strengthen the infrastructure around the CRM rather than replace the CRM itself.
Phipps described several areas where HubSpot has evolved significantly over the last few years:
- Deduplication at scale. Large databases require more sophisticated ways to identify and manage duplicate records.
- Audit logging and property history. More visibility into record changes gives teams greater control over their data.
- Workflow complexity. More capable automation reduces the need to patch together additional tools for increasingly sophisticated processes.
That calculus has shifted for Phipps:
"I would do worse if I went to Salesforce today compared to if I did two years ago. HubSpot does most of what we need at this point, which is great." – Amani Phipps
Custom objects, deeper API access, predictive lead scoring, and HubSpot's own CPQ tooling have expanded what's possible on the platform.
As Phipps put it:
"Eventually, once their story was written, it just stayed on the shelf. It continued to become the book that we refer everybody to go and read, as opposed to seeing that the world is changing." – Amani Phipps
The takeaway for GTM teams is simple: evaluate today's platform against today's business requirements.
3. A CRM transformation is an opportunity to improve the data and processes around it
Tsioutsiouli is living the reverse of the traditional path. Foxit, a global PDF and eSignature company with roughly 1,000 employees, is moving from a 15-year-old Salesforce instance to HubSpot.
She's careful about the framing:
"This is not a migration. It's more of a transformation project, and how we build our GTM tech stack for the years to come." – Georgina Tsioutsiouli
That distinction matters.
Foxit built the effort around one question for every process, rule, and workflow: would this problem disappear if you changed the CRM?
In many cases, the answer was no.
The Salesforce instance holds roughly 5.5 million records, with duplicates and inconsistencies accumulated over years of use.
Moving that data into HubSpot without addressing its underlying quality wouldn't create a better foundation. The transformation gave Foxit an opportunity to address the data itself and rethink the processes built around it.
As Tsioutsiouli explained:
"If the data is bad, changing CRM won't fix it. If the process has too many steps, changing CRM won't fix that either." – Georgina Tsioutsiouli
That meant evaluating every validation rule, workflow, and approval:
Why does this exist? Who uses it? Would we build it the same way today?
Those questions turn a CRM project into something much more valuable: an opportunity to simplify the GTM operating model and create a stronger foundation for growth.
4. A data orchestration layer can extend what your CRM can support
If HubSpot provides the core CRM experience your GTM team wants, the next question becomes: how do you give the platform the data, automation, and connectivity needed to support a more sophisticated GTM motion?
That's where King sees a role for a data orchestration layer.
He broke the approach into four parts:
- A shared data layer. Connect the systems in the stack and build a unified view of the data. Matching records across systems so the same company is recognized consistently in the CRM, intent data, and engagement history is a particularly valuable part of that foundation.
- Cleaning, deduplication, and data firewalls. Automated processes keep data clean and prevent issues from continuously re-entering the system.
- Workflow and automation. Multi-vendor enrichment, segmentation, scoring, and centralized monitoring can be handled through a purpose-built layer rather than a growing collection of point solutions.
- Enablement. Self-service tools let end users build and load their own lists without an ops ticket, while API, webhook, and MCP connectivity can extend automation across the broader GTM stack.
Together, these capabilities create a layer around the CRM that helps GTM teams manage increasing data and process complexity without automatically adding more systems or manual work.
King summed up the value of consolidation:
"Instead of bolting on 20 different pieces of technology, having one single platform is very beneficial." – Ed King
He also noted that Forrester is preparing a landscape report on the data orchestration category, reflecting the growing attention around the role of data infrastructure in modern GTM.
The bigger opportunity is to make the technology you already have more capable, more connected, and easier to operate at scale.
5. Treating RevOps like a product team creates room for strategic growth
Phipps closed the session with a reframe worth considering: the way a team thinks about its role can influence how effectively it scales.
"RevOps is a product team. Every user at this organization is a customer. Every department shares a new ICP, and they need a different thing, but I need to have the time and space to think about what I'm doing and building." – Amani Phipps
That framing puts the focus on building systems that serve the broader GTM organization.
It means creating a roadmap, prioritizing the work that has the greatest business impact, and giving the team enough capacity to improve the systems that support revenue.
At Bonusly, that showed up in several technology decisions, including consolidating from a more complex customer success platform to a simpler one and using HubSpot's DataHub connector to bring Snowflake data directly into the CRM at a predictable per-record cost.
The common thread is intentionality: choose the technology and processes that help the GTM team move faster and support the business more effectively.
HubSpot enterprise readiness starts with the foundation around your CRM
The webinar offered a more useful way to think about HubSpot enterprise readiness.
It's not simply a question of company size or whether you've reached an arbitrary point on the path from one CRM to another.
It's a question of whether your data, processes, integrations, and team capacity can support the way your business operates today—and how you expect it to operate tomorrow.
For some companies, that may mean moving to a different CRM. For others, it may mean getting more from the platform they already have.
A data orchestration layer can play an important role in the latter by connecting systems across the GTM stack, keeping data consistent, and automating the workflows that become increasingly important as the business grows.
That's where Openprise fits: connecting the systems in your stack, matching and cleaning the data that flows between them, and automating the workflows that help GTM teams execute and scale.
The goal isn't to graduate from HubSpot. It's to build a GTM foundation that keeps pace with your business.
Want the full conversation, including the audience poll results and Q&A? Watch the full replay to hear Ed King, Georgina Tsioutsiouli, and Amani Phipps walk through it in their own words.
See how Openprise can help you build the data orchestration layer your HubSpot instance needs to scale.
