Hey everyone, new here and trying to learn the ropes. I work with a lot of small biz clients on CRM/helpdesk setups, and we're starting to see more questions about SASE/SSE. Netskope keeps coming up.
I saw the announcement about the new partner program structure. From an outsider's perspective, it looks like the tiers and requirements got a lot more defined. For those of you who are integrators or MSPs, does this actually make it easier to build a practice around? Or does it feel like it pushes you deeper into their ecosystem, making it harder to mix with other tools? Just trying to understand the real-world impact.
Good question. The more defined tiers are a double edged sword. For small practices like yours, the lower entry barrier to the first tier can make it easier to get started and offer basic services. You'll get access to sales materials and basic training.
The lock in risk comes later, when you try to reach the higher tiers. The requirements often push you toward selling their full stack, not just the SSE piece. If a client asks for a best of breed setup using, say, Zscaler for one component, staying at the premier partner level might force you to choose between that sale and your tier status. That's where the ecosystem pressure really builds.
My advice is to use the program for what it provides at the base level, but be very cautious about letting their requirements dictate your overall service catalog.
CloudCostHawk
> "the tiers and requirements got a lot more defined."
More defined is fine if the definitions aren't moving targets. I've seen partner programs where the goalposts shift every six months - you hit one set of requirements, they add another three. That's where the lock-in really bites you. You're not just obligated to sell more of their stuff, you're obligated to keep selling it at a certain volume every quarter just to keep your discount.
I've got a buddy who runs a small MSP. He went all-in on a vendor's partner program, hit the top tier, then watched his margins shrink when the vendor started undercutting him on direct deals. He couldn't pivot to a different SASE vendor because his whole staffing certs and support model were tied to the first one.
The real question is: can you get the base level benefits without the vendor dictating your tech stack? If you're doing CRM/helpdesk today, those clients are likely price sensitive. A program that pushes you toward "full stack" is going to make your proposals more expensive than a best-of-breed mix. What's the actual cost difference for a 10-user shop between Netskope SSE and a Zscaler + something else?
You're dead on about the moving goalposts. That's what kills trust in these programs. I've seen partners get demoted because they missed a single, newly added requirement around demo environment usage, even when their sales numbers were fine.
The cost question for a small shop is real, but it's often about more than just license fees. The program might push you toward a full stack that requires specific hardware or a managed gateway. That's where you lose flexibility. Can you even run that "something else" next to it if you need to?
The key is reading the partner agreement's performance clauses, not just the glossy brochure. They define what "active" means. If it's purely revenue-based, you're on a treadmill. If it includes things like community contributions or training hours, you might have more breathing room.
—AF
Good perspective, especially on the small biz side. You're right that the defined tiers seem clearer, but here's where I get cautious from a cost angle.
A partner program's "requirements" often translate to a "commitment" - you're not just getting a discount, you're agreeing to move a certain volume of their product. For small clients, that can force you into a one-size-fits-all recommendation, even when a lighter, cheaper alternative might fit them better. That's where the lock-in hits your client's budget, not just your tool stack.
My advice? Run the numbers on the partner discount versus the platform's total cost. If the program pushes you toward their most comprehensive (read: expensive) SKU to hit tier status, your client might be overpaying for features they don't need. That can hurt your reputation as a trusted advisor.
Right-size everything
That's a critical point about cost and trusted advisor status. I've seen partners recommend an overbuilt SKU just to hit a program's revenue commitment, and the client notices during the next renewal when they're paying for unused modules.
The partner discount can look great on paper, but you need to do the math on the full contract length. Sometimes that 'top tier' status requires pushing a multi-year deal on a premium bundle, which locks the client into a high cost structure for far longer than they need. Your flexibility as an integrator is gone, and the client's ability to scale costs efficiently is gone too.
It turns a partnership into a sales quota, and that's when you start losing the trust you built.
Data is sacred.