I think every vendor with a partner channel should hand partners the same accreditations its own sellers hold, and put them behind a self-serve door.
What Elastic did
Seismic published an interview with Hailey Gibbons, Senior Manager for External Partner Enablement at Elastic, on October 27. Gibbons describes a plain sequence. Elastic took enablement content it already had for its own sellers, made partner versions, and put everything in one self-service center organised by partner type and sales stage. Partners receive the same accreditations and certifications Elastic’s sellers receive, plus overviews, technical material, news and events. The post says partner-sourced deals grew 50% year over year.
Gibbons said of the starting problem, “It wasn’t a content issue. It was an ease-of-access issue.” Her rule for what partners get was equally direct: “if it’s good enough for our Elastic sellers, it’s good enough for our external partners”. Of the result, she said partners “can show up with authority and the same knowledge our sellers have”.
Advertisement
Why I would copy it
A new partner program can start by commissioning partner decks. Elastic started by asking what its own sellers already had. That is cheaper, because the content exists, and it keeps partner messaging from drifting away from the direct team’s. A partner who pitches from a stale deck can cost the vendor a deal in a room the vendor never sees.
The certification point carries more weight than the content point. Accreditation is the one thing a partner’s buyer can verify. When a reseller’s rep holds the same credential as the vendor’s rep, the customer has a reason to take the partner’s recommendation at face value, and the partner has a reason to invest rep time in earning it. A badge that only the vendor’s staff can hold sends the opposite message.
Self-service matters because a partner seller who wants to learn a product should be able to do it without filing a ticket. Gibbons describes a portal where “any partner can go and find enablement content tailored to their partner type”. Segmenting by partner type and sales stage means a reseller in discovery and an integrator in delivery do not search the same pile. Our recent coverage of enablement hours returned to sellers and of adoption moving out of the training room argues the same direction for direct teams: the best enablement is the kind a seller can reach without asking.
The counter-argument
The strongest objection is control. Internal content carries pricing logic, competitive positioning and roadmap hints, and a vendor that opens the whole library to partners may hand a competitor’s reseller the same material. A second objection is attribution. The Seismic post gives the 50% figure beside the portal and does not separate the portal’s effect from everything else that changed for Elastic in a year, so a reader should not treat the growth as proof that the portal caused it.
Both objections are fair, and neither changes my view. Control is a matter of partner-specific versions, which is the second step in Elastic’s own sequence: the post describes creating partner-specific versions of the internal content, so the sensitive material never has to leave. On attribution, I do not need the 50% to be causal to make the argument. The case for matching credentials rests on what a customer can verify and what a partner rep will spend time earning, and Elastic’s quotes support that reasoning on their own.
What to do on Monday
A partner manager can test this in a week. List every certification your direct sellers must hold. Mark the ones a partner could earn today and the ones the program blocks. For each block, write down the reason, and challenge any reason that amounts to habit. Then look at where partners go to find the material: if the answer is an email thread, the access problem Gibbons describes is yours too.
I would also ask partners directly which deal stage they feel least equipped for, and build the next partner version of an internal asset for that stage first. Elastic’s sequence suggests the content already exists. The work is converting it, publishing it in one place and letting partners in with the same credentials.
Source: Seismic Blog, how Elastic built its partner enablement framework
