New research from SBI and Polaris I/O tracked 58,000 business evolution signals across 46 enterprise accounts. The findings make a strong case for rethinking how account expansion gets done.
Enterprise accounts represent 60% or more of B2B revenue for most companies. Demand is forming inside those accounts right now, driven by real changes in the customer’s business. Most go-to-market teams have no system to detect it.
That is the central finding in new research from SBI and Polaris I/O, and it points to something more significant than a process gap. It points to a structural shift in how GTM teams need to operate.
The Confidence Gap Showing Up in CEO Surveys
SBI surveyed 118 CEOs on their top growth priorities. Of those surveyed, 71% rated account expansion as critical to hitting their targets. Only 49% said they trust their teams to execute it.
That 22-point gap is not a coaching problem or a headcount problem. It is wider than the confidence gap on GTM efficiency (19 points) and nearly three times wider than the gap on customer retention (7 points).
Most of these companies have already invested in account management, customer success teams, and intent data platforms. The gap persists anyway.
The reason is that demand is forming inside accounts before anyone starts researching vendors, before anyone fills out a form, before any intent platform registers a signal. Most teams have no way to see it at that stage.
What Intent Data Misses
Intent data was a genuine step forward. It gave teams a signal that demand existed somewhere in the market.
The problem is that intent data is late by design. By the time a buyer is actively searching for solutions, they have typically already defined their requirements, shortlisted vendors, and aligned on budget. At that point, you are not shaping the deal. You are auditioning for it.
What intent data cannot show is the event that created the demand in the first place.
A customer does not start searching for an enterprise data migration platform for no reason. Something changed in their business. A new CTO arrived with a modernization mandate. A regulatory shift forced a re-evaluation of existing infrastructure. An acquisition created integration requirements that did not exist six months ago. The business evolution came first, and the intent signal followed. Companies that only monitor intent are seeing the second half of a buying journey that started without them.
What the Research Found
SBI and Polaris I/O tracked over 58,000 business evolution signals across 46 enterprise accounts over 12 months. The same accounts, the same period, with two parallel discovery methods running side by side. The gap between them was significant.
Signal-driven teams generated 4x more qualified opportunities (4,270 vs. 1,007 through traditional account management).
Conversion rates were 71% compared to 20% for traditional approaches.
Average deal sizes were 7.4x larger ($2.6M signal-driven vs. $350K traditional).
Deals closed 128 days faster (144 days vs. 272 days).
The accounts were the same. So were the reps and the products. What changed was when teams recognized that demand was forming and how they responded to it.
The full research, methodology, and 90-day implementation playbook are available here: Pipeline in Plain Sight: Predictable Account Expansion in Unpredictable Times
Where to Focus: Three Signal Types Drive 82% of Closed Deals
Not every business change creates a buying opportunity. The research identified three categories that drove 82% of all closed expansion deals:
Strategic Transformation (31%): Digital transformation programs, platform migrations, and modernization efforts. These come with executive sponsorship, dedicated budgets, and real urgency.
Growth and Restructuring (28%): New business units, geographic expansion, and acquisitions. These create infrastructure demand with committed capital behind them.
Environmental Disruption (23%): Regulatory shifts, organizational change, and external forces that force re-evaluation of existing vendors and open buying windows that would not otherwise exist.
These are not obscure signals. They are public and observable. The issue has never been that they did not exist. It is that no one has built a system to connect them to revenue at scale.
When You Engage Determines the Role You Play
When a business evolution event happens inside a customer organization, requirements begin to form, budgets shift, and the window for influence starts to close. The role the buyer assigns you depends on when you show up.
Days 0 to 30: Evolution Partner. No requirements exist yet. The supplier who engages during this window gets invited in as a thinking partner, helping shape priorities, budget, and evaluation criteria. You know you are in this role when the buyer is asking what they should prioritize, not whether you can meet their requirements.
Days 30 to 90: Preferred Contender. Requirements are forming and suppliers are being compared. You can still influence evaluation criteria, but the conversation has shifted from “help us think through this” to “prove you can deliver.”
Days 90 and beyond: Commodity Bidder. Requirements are locked and the RFP is out. Everyone answers the same questions on the same timeline and competes on price, risk, or familiarity.
The research makes the timing stakes clear. Early engagement is not just about relationships. It is about the role you get to play in the deal.
Why This Moment Matters for GTM Leaders
For most of the last decade, data-driven GTM meant intent data. That era is not ending, but intent data alone is no longer sufficient.
AI-powered monitoring has made it economically and operationally viable to track business evolution signals across every buying center in every strategic account, continuously and at scale. Signal-driven expansion in the SBI/Polaris I/O study penetrated an average of 8 buying centers per account. Traditional account management reached 3. That difference is not a function of effort or skill. It is a function of what humans can observe manually versus what a platform purpose-built for this can surface automatically.
Account planning that does not include pre-intent signal monitoring is working with incomplete information. A plan built on renewal dates, relationship history, and intent platform alerts is organized around demand that has already surfaced. The buyers who drive the most expansion revenue are reshaping budgets around strategic changes that are happening right now, and most teams are not aware of them until they receive an RFP.
What Getting Started Looks Like
This shift does not require replacing GTM infrastructure. It requires adding a layer of visibility that most teams do not currently have, then building the discipline to act on what it surfaces.
SBI’s research outlines a 90-day buildout:
Weeks 1 to 3: Map the last eight quarters of closed expansion deals back to the business event that created the need. The patterns will concentrate around a small number of signal types. That analysis becomes your signal investment thesis and determines where monitoring resources go.
Weeks 3 to 10: Deploy signal monitoring across your top 20 accounts. Run it for 90 days and compare what the system finds to what your account teams already knew. The size of that gap is a direct measure of how much pipeline is currently invisible.
Weeks 4 to 12: Build a composite account view that combines signals, CRM data, call themes, and relationship maps. The goal is surfacing prioritized actions so reps spend time executing rather than analyzing.
Weeks 6 to 12: Replace part of the pipeline review with a forward-looking signal review. The frontline manager runs it as part of the existing cadence, not as an additional meeting. Without this step, signals accumulate in a dashboard without changing how the team operates.
The Pipeline Is Already There
Of the expansion deals your team closed last year, how many did they find because they saw a need forming early, and how many came through an inbound request or an RFP?
If most came to you, the pipeline was already visible. The opportunity now is building a system to see it earlier.
Related Posts
Nothing found.

