Strategy & planning
Every Microsoft partner we work with reaches the same fork in the road at some point along their growth path. Things are going well, and they begin to build some momentum, but they can’t see the end goal as clearly as they should.
This is a question that is older than any of these partners, and perhaps older than the concept of marketing as we understand it today. It's the same question asked in The Epic of Gilgamesh, The Odyssey, and many other stories that speak of a hero’s journey. Homer's Odysseus asks himself this question off the coast of Troy, staring at a horizon that suddenly looks a lot longer than expected. He'd won the war, but the hard part, it turns out, hadn't started yet.
The hero's journey, the narrative pattern Joseph Campbell mapped across mythology, follows a shape that shows up in countless enduring stories: the protagonist leaves the world they know, faces a series of trials that test who they are, and comes back transformed, carrying something worth sharing. In fact, it was a part of the inspiration behind the Enki name.
I doubt Campbell or any of these authors were thinking about channel partners or Marketplace listings when conceiving their stories. But when strip away the sea monsters and the epithets, and the shape of Odysseus's ten-year detour maps onto the arc of a Microsoft partner’s growth path. From the first certification through the messy middle years to the eventual return to a business that finally works the way it was supposed to.
The Cyclops's Cave: Overcommitting to One Big Account
When Odysseus and his crew wander into Polyphemus's cave, they don't leave when they have the chance. They stay, sample the cheese, and wait around longer than they should. It costs several of them their lives. A lot of partners do something similar with their first win: they build the roadmap, the staffing plan, even the culture, around one account that feels too good to walk away from. The problem is that it works, but only until the account renews on worse terms, or doesn't renew at all, and the business built entirely around it has nowhere else to stand.
Circe's Island: The Profitable Distraction
Circe turns Odysseus's men into pigs, and Odysseus himself stays on her island for a year before his crew reminds him of his goal. Plenty of ISVs have their own Circe: a lucrative custom project, or a one-off integration that pays the bills so well that nobody wants to ask whether it's pulling time away from the core product. A year is a long time in our ecosystem. It's important to consider the opportunity cost of where you are today and whether focusing on other areas is more valuable.
The Sirens: The Pull of Whatever's Loud Right Now
The Sirens' song promises knowledge no mortal has ever held. Right now, in the Microsoft ecosystem, that song sounds a lot like – say it with me now – agentic AI. If we’re being honest, most of the ISVs chasing an AI feature roadmap this year haven't finished the product-market fit work on what they already shipped. Odysseus survives the Sirens because he plans for the moment before he's in it: wax in the crew's ears, himself tied to the mast. He gets close enough to hear the song but doesn’t steer the ship into the rocks. Deciding in advance what you will and won't chase is critically important. You can always correct course and adjust if needed, but overinvesting in one area because it is popular today can ruin a business’ future.
Scylla and Charybdis: The False Binary
Forced to choose between a six-headed monster and a ship-swallowing whirlpool, Odysseus picks the option that costs him six sailors instead of the whole crew. It's not a good choice, but it's the lesser evil, and he makes it deliberately. Partners face this constantly: build proprietary IP versus stay a pure implementation shop, go deep on one Microsoft product versus spread across the platform, chase Marketplace transactability versus stick with the relationship-driven sales motion that's worked so far. A question that is harder than any of these is whether you’re making decisions based on a strategic outlook or a unique level of aptitude or are just drifting toward whichever monster looked smaller from where you were standing. Following a cadence of SWOT analysis meetings to assess upcoming threats, how to tackle them, and which to prioritize is one of the most basic, yet often ignored, practices that partners should adopt.
The Cattle of the Sun: The Shortcut That Costs More Than It Saves
Starving and marooned, Odysseus's crew slaughters cattle sacred to Helios against direct orders, and every one of them pays for it. There's a version of this in partner-land too: a demo that overpromises what the product does, a claim that stretches past what's been proven, or a case study that leaves out the part where the implementation took months longer than planned. They may bring back a quick win or two, but they also erode the trust and are deeply damaging in the long run.
What This Means for You
Of course, none of this is really about Homer’s epic or any piece of literature. It's about the fact that the Microsoft partner ecosystem in 2026 rewards the return trip more than the departure. Recent benchmarking across the partner ecosystem points the same direction: access to designations, programs, and Marketplace listings has become table stakes, and the partners gaining ground are the ones building strong foundations and internal processes to maximize impact, not just going through the motions.
Microsoft's own guidance leans the same way, pointing toward stacking several deliberate moves rather than betting on one: form strategic partnerships that reach new customer segments and build alliances with other partners tackling the same problems. Going back to the analogy, it’s the equivalent of Odysseus finally accepting help from the Phaeacians instead of trying to sail the last leg home alone out of pride. The partners who get home fastest tend to be the ones willing to take a ride when one's offered, whether that's a co-sell introduction, a joint community event, or an outside set of eyes on the plan.
The partner version of the "returning with the elixir" part of the hero’s journey looks like this: a repeatable sales motion that doesn't depend on your founder's relationships, a product roadmap that isn't hostage to whichever custom request came in most recently, and an impactful story you can tell a prospect, a partner, or Microsoft. This kind of experiential wisdom, as costly as it may have be, is what Odysseus brings back to Ithaca.