Emerging Categories and AI

Building a GSI-Led AI Buying Motion

Creating a buying motion for an emerging AI category through the GSIs who owned the customer relationship.

The Situation

The AI opportunity was real, but the buying motion was not yet clear.

Cloud had become the default path for enterprise AI because it was mature, familiar, and easy to buy. Edge AI was different. The demand was forming in places where data, latency, cost, privacy, or operational constraints made local processing valuable — but customers did not yet have a clear way to evaluate when edge made sense, what it was worth, or how to compare it with cloud.

The capability existed before the category was easy to buy.

What Had Changed

The issue was not simply more selling.

Customers needed help deciding which AI workloads belonged in the cloud, which belonged at the edge, and how to think about value across both. The GSIs who owned the customer relationship were best placed to shape that conversation.

But their economics and operating habits were anchored in cloud. They did not lack awareness of the edge opportunity; they lacked a strong reason to lead it.

The block was not attitude. It was position and economics.

The Redesign

The motion had to give GSIs a reason to lead.

The shift was to position cloud-plus-edge as a broader AI architecture conversation, not as another product sale. That gave GSIs a stronger role with the customer: helping decide where AI should run, what business problem it solved, and how the architecture should evolve.

The buying motion was built around that role. GSIs could lead the customer conversation, while the underlying structure helped classify workloads, frame value, and identify where edge had a clear advantage. Vertical use cases gave the motion a concrete starting point rather than leaving it as a general technology discussion.

Internally, the motion also needed protection from the short-term sales engine. Emerging-category work requires different expectations, because the market is still learning how to buy.

What Mattered

What mattered was recognizing that GSIs do not lead an emerging category because the vendor wants them to.

They lead when the category gives them a stronger position with the customer. In this case, the opportunity was not to out-incent cloud, but to create a cloud-plus-edge role that GSIs could own.

Outcome

The motion was built, tested with GSIs and customers, and gave the category a clearer path to adoption. It turned an emerging technical capability into a GSI-led commercial motion the market could begin to repeat.

Note

This case note is intentionally brief. If it is relevant to a challenge you are facing, I would be glad to discuss the fuller context, decisions, and trade-offs.

Start a conversation →