Skip to main content

Keys to Building a Partner Ecosystem That Scales

Barb Huelskamp
SolarWinds

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field.

Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast.

The reality is that vendor offerings don't address modern complexity on their own, and enablement resources that don't map to real selling situations aren't resources at all. In a landscape that is evolving faster than most organizations can keep up with, surface-level channel programs will always fall short.

What the channel actually needs and what customers ultimately depend on is a partner ecosystem built to scale alongside that complexity. One that gives partners predictable frameworks, genuine specialization, and the kind of support that makes them more capable, not just more certified. Because when we get that right, partners don't just sell better. They deliver better outcomes for the customers who need them most.

Complexity Is Now the Persistent Reality

Current IT environments are completely different than they were just five years ago. Many IT teams must now manage hybrid architectures, multi-cloud developments, and edge infrastructure all at the same time. When you layer in a growing number of workloads that include AI, complexity becomes the baseline for modern IT architecture.

Ideally, partners should be absorbing this complexity for their clients. They should be helping them make sense of this new normal of distributed, hybrid environments, while limiting the noise that comes from monitoring, observability, and security platforms. But if partners are going to succeed, vendors need to look at things from a partner-first perspective and ask whether their program is removing complexity, or just adding to it.

Providing a Clear View of the Program

Providing enterprises with a single pane of glass has become a best practice for observability platforms, and modern partner programs can learn a lot from this. Partners need a clear view of where they stand: their tier, what they're earning, and where their growth opportunities are. Without that transparency, you get blind spots that slow deal-making and, ultimately, hurt customers.

Historically, this is an area where we, like many vendors, haven't always gotten it right. But it's something we're actively building toward. Our recent updates around structured, tier-based discounting are a step in that direction, giving partners a more consistent pricing framework they can count on when forecasting margins and co-selling, and we're expanding certifications and specialization tracks so partners have a concrete path to becoming genuine subject matter experts. 

We're working to make the everyday partner experience more seamless and role-based, and our goal is clear: partners should never have to guess how they can help customers achieve the outcomes they're looking for.

Enablement That Aligns with Partner Workflow

The best enablement programs provide more than deep learning opportunities because they match actual partner habits and workflows. Enablement is only as good as a partner's ability to access and leverage it in real time.

Flexibility and supporting different learning styles should always be top of mind. Instead of providing a certification and calling it a day, look at partners as an extension of the organization. When rolling out a new internal battle card, build a version for our partners online. In our case, we have introduced monthly webinars and newsletters to touch partners in different ways every month, as a means of giving them a differentiated story to take to market.

What I love about this approach is surrounding partners with whatever resources they need, whether that means looping in our sales, engineering, product, or marketing teams. When enablement is a true priority, it allows partners to build an expertise that sits right at the intersection of their customers' problems and the technical solutions needed to solve them.

Keeping the Customer at the Center

The North Star of any partner program must be customer success. We cannot run parallel paths or treat the partner like a barrier between us and the end user. It’s essential to get on a call with the partner and the customer together to deliver the right outcome.

When partners have clearer incentives, less friction, and attainable enablement opportunities, they can integrate technologies and deliver real customer outcomes. That is how you create a framework where every single part of the ecosystem wins together.

Barb Huelskamp is VP of Global Channel and Alliances at SolarWinds

Hot Topics

The Latest

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...

Keys to Building a Partner Ecosystem That Scales

Barb Huelskamp
SolarWinds

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field.

Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast.

The reality is that vendor offerings don't address modern complexity on their own, and enablement resources that don't map to real selling situations aren't resources at all. In a landscape that is evolving faster than most organizations can keep up with, surface-level channel programs will always fall short.

What the channel actually needs and what customers ultimately depend on is a partner ecosystem built to scale alongside that complexity. One that gives partners predictable frameworks, genuine specialization, and the kind of support that makes them more capable, not just more certified. Because when we get that right, partners don't just sell better. They deliver better outcomes for the customers who need them most.

Complexity Is Now the Persistent Reality

Current IT environments are completely different than they were just five years ago. Many IT teams must now manage hybrid architectures, multi-cloud developments, and edge infrastructure all at the same time. When you layer in a growing number of workloads that include AI, complexity becomes the baseline for modern IT architecture.

Ideally, partners should be absorbing this complexity for their clients. They should be helping them make sense of this new normal of distributed, hybrid environments, while limiting the noise that comes from monitoring, observability, and security platforms. But if partners are going to succeed, vendors need to look at things from a partner-first perspective and ask whether their program is removing complexity, or just adding to it.

Providing a Clear View of the Program

Providing enterprises with a single pane of glass has become a best practice for observability platforms, and modern partner programs can learn a lot from this. Partners need a clear view of where they stand: their tier, what they're earning, and where their growth opportunities are. Without that transparency, you get blind spots that slow deal-making and, ultimately, hurt customers.

Historically, this is an area where we, like many vendors, haven't always gotten it right. But it's something we're actively building toward. Our recent updates around structured, tier-based discounting are a step in that direction, giving partners a more consistent pricing framework they can count on when forecasting margins and co-selling, and we're expanding certifications and specialization tracks so partners have a concrete path to becoming genuine subject matter experts. 

We're working to make the everyday partner experience more seamless and role-based, and our goal is clear: partners should never have to guess how they can help customers achieve the outcomes they're looking for.

Enablement That Aligns with Partner Workflow

The best enablement programs provide more than deep learning opportunities because they match actual partner habits and workflows. Enablement is only as good as a partner's ability to access and leverage it in real time.

Flexibility and supporting different learning styles should always be top of mind. Instead of providing a certification and calling it a day, look at partners as an extension of the organization. When rolling out a new internal battle card, build a version for our partners online. In our case, we have introduced monthly webinars and newsletters to touch partners in different ways every month, as a means of giving them a differentiated story to take to market.

What I love about this approach is surrounding partners with whatever resources they need, whether that means looping in our sales, engineering, product, or marketing teams. When enablement is a true priority, it allows partners to build an expertise that sits right at the intersection of their customers' problems and the technical solutions needed to solve them.

Keeping the Customer at the Center

The North Star of any partner program must be customer success. We cannot run parallel paths or treat the partner like a barrier between us and the end user. It’s essential to get on a call with the partner and the customer together to deliver the right outcome.

When partners have clearer incentives, less friction, and attainable enablement opportunities, they can integrate technologies and deliver real customer outcomes. That is how you create a framework where every single part of the ecosystem wins together.

Barb Huelskamp is VP of Global Channel and Alliances at SolarWinds

Hot Topics

The Latest

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Enterprise IT environments have never been more observable ... Yet many organizations still grapple with outages, lengthy incident resolution cycles, and increasing complexity. Most teams do not suffer from a shortage of data. They struggle to determine what deserves attention and what action to take next ... Enterprise IT operations must move beyond monitoring and visibility. The next stage of maturity is decision operations, an approach that helps teams make faster, better-informed decisions ...