Winning a new customer is difficult. Earning enough trust to become part of that customer’s technology conversations can be even harder.
Once that relationship exists, however, the next opportunity doesn’t always have to come from finding another customer.
It may come from understanding more of what the customer is trying to accomplish.
For Technology Advisors, MSPs and other channel partners, enterprise technology needs rarely fit neatly into a single category. A conversation that begins with connectivity may eventually involve security, cloud infrastructure, managed services, voice, mobility or technology lifecycle requirements.
The opportunity isn’t to sell everything.
It’s to recognize when one business need connects to another—and be prepared to help the customer navigate what comes next.
Customers Don’t Experience Technology in Silos
Technology services may be organized into categories, but business problems usually aren’t.
A company opening new locations might initially need connectivity. But those locations can also create questions about network management, security, voice, mobility and ongoing support.
A cloud initiative can raise questions about network performance, security, data movement and infrastructure management.
An acquisition may introduce overlapping carriers, contracts, invoices, technologies and service providers.
From the customer’s perspective, these aren’t necessarily separate projects. They’re interconnected pieces of a larger business requirement.
Technology Partners who understand those connections can have broader conversations without trying to force every customer into the same solution.
Listen for the Need Behind the Request
Customers often begin a conversation by describing the immediate requirement.
“We need internet at 20 new locations.”
“We’re evaluating a new cloud environment.”
“Our network costs keep increasing.”
“We need better visibility across our locations.”
Solving that immediate problem matters. But so does understanding what’s driving it.
What Changed?
A new location, acquisition, contract renewal, technology refresh, cloud migration or business expansion can create requirements beyond the initial request.
Understanding the change helps uncover the larger picture.
What Else Does This Affect?
A connectivity change could affect security or network management. A cloud decision could change network requirements. An acquisition could expose duplicate services or fragmented billing.
The goal isn’t to manufacture another opportunity. It’s to understand the dependencies surrounding the customer’s decision.
Who Else Is Involved?
Technology decisions increasingly cross organizational boundaries.
IT may own the technical requirement while Finance is concerned about cost, Operations is focused on continuity and business leaders are concerned about growth or customer experience.
Understanding who is affected can help a Technology Partner frame the conversation around the business requirement rather than an individual product.
How Is AI Changing the Requirement?
AI can introduce requirements that weren’t part of the customer’s technology environment even a short time ago.
If the organization is experimenting with or deploying AI, ask how those workloads are being used today and what happens if they move from pilot to production.
Where does the workload need to run? What are the requirements for compute, storage, connectivity, security and data movement? Does the existing environment still make sense for the workload as its requirements change?
The objective isn’t to assume AI requires a particular infrastructure model. It’s to make workload placement part of the conversation.
That can open a broader discussion about whether a workload belongs on-premises, in public cloud, private cloud or across a hybrid environment—and what the customer needs from each.
More Conversations Don’t Require More Products
Expanding a customer relationship doesn’t mean introducing another product every time you speak with them.
Sometimes the most valuable next conversation is about:
- what is changing in the customer’s business
- where technology has become difficult to manage
- where responsibilities are fragmented
- which contracts or technologies are approaching a decision point
- where the customer lacks visibility
- what the organization expects to accomplish next
Those conversations can uncover requirements that aren’t visible when the discussion begins and ends with a quote.
They can also help move the relationship from responding to individual requests toward helping the customer think through a broader technology environment.
Know Where Your Capabilities End
No Technology Partner needs to build every capability internally.
In fact, knowing where your organization’s expertise ends can be just as important as knowing where it begins.
A customer may trust you for one area of its technology environment and then ask for help with something outside your core offering.
That creates a choice: step away from the opportunity, try to develop a capability you don’t have, or bring in complementary expertise while remaining involved in the customer relationship.
The right supporting relationship can make the third option possible.
It allows the customer to continue working with someone they already trust while giving the Partner access to additional capabilities when the situation requires them.
Look Across the Customer’s Technology Environment
For complex, multi-location organizations, there are often natural connections among technology requirements.
Connectivity can lead to conversations about managed network services.
Network changes can raise questions about SASE and security.
Cloud, AI and infrastructure decisions can raise questions about workload placement, connectivity, performance, data movement and where infrastructure should run.
Growth and acquisitions can create new requirements across voice, mobility, services, vendors and locations.
And fragmented technology environments can create a need for greater visibility and lifecycle management.
The value isn’t in turning each category into a separate sales pitch.
It’s in recognizing how those requirements intersect and helping the customer connect the pieces.
Protect the Relationship You’ve Already Earned
For many Technology Partners, one concern about bringing another provider into an opportunity is straightforward:
What happens to my customer relationship?
That makes the structure of supporting partnerships important.
You own the customer relationship. EnTelegent optimizes, delivers and supports the technology.
That gives Technology Partners a way to address requirements beyond their core capabilities without having to build every capability internally. As customer needs expand across network, managed services, security, cloud infrastructure, voice or lifecycle management, the Partner can remain at the center of the relationship while bringing additional expertise into the conversation.
The objective isn’t to replace the relationship.
It’s to help you do more with the relationship you’ve already earned.
One Relationship Can Create More Opportunity
New-logo acquisition will always matter.
But growth doesn’t have to depend exclusively on finding more companies to call.
There may already be opportunities inside the customer relationships you’ve worked hard to build.
Start by asking:
What is changing in the customer’s business?
What other technology requirements could that change affect?
Where could complementary expertise help?
And what conversation should happen next?
Because sometimes the next opportunity isn’t another customer.
It’s another conversation with the customer you already have.
EXPLORE REFERRAL OPPORTUNITIES
Your next opportunity may be one relationship away. Explore how the relationships already in your circle could create new paths to opportunity.
Explore Referral Opportunities →
PARTNER GROWTH SERIES
Continue the Partner Growth Series
01 — EXPAND YOUR CIRCLE
Your Next Opportunity May Be One Relationship Away
Trusted relationships may provide a more direct path to the customers you want to reach.
Read Article →
02 — YOU’RE READING THIS ARTICLE
One Customer Relationship. More Technology Conversations.
Look beyond the initial request to uncover more of your customer’s technology needs.
03 — BUILD YOUR CHANNEL
Build Your Own Channel: Look Beyond the CIO
Fractional CIOs, associations and private equity relationships can create new paths to opportunity.
Read Article →
04 — CREATE OPPORTUNITY
From Introduction to Opportunity: Two Ways to Build Your Channel
See how trusted relationships can create introductions—and how those introductions can develop into new opportunities.
Read Article →
