partner enablement that ends in a registered deal

Partner enablement has one job: getting a partner’s people from “we signed” to “we closed one without you”. Programmes tend to teach the product, because product courses are easy to build. Partners lose deals earlier, in the first conversation with a customer and in a POC without criteria. Build enablement around the steps of a deal, track certified people by name, and judge it by registered opportunities. Course completions tell you little.

where partners actually get stuck

A deal goes through the same steps whether a partner or your own team runs it. Each step needs a different capability, and each has a typical gap.

Step in the deal	Who at the partner	What they need	Typical gap
Spotting the opportunity	Account manager	Which customers have the problem, which triggers create urgency	Sells only when a customer asks by name
First conversation	Account manager	Explain the problem and outcome in the customer’s words	Talks features, cannot answer “we already have X”
Discovery and design	Presales engineer	Scope, sizing, integrations	Depends on your engineer for every deal
Demo and POC	Presales engineer	A demo, a POC with success criteria	No demo environment, POCs without criteria
Proposal	Account manager	Quote correctly, position services	Quotes the licence only, discounts early
Deployment	Delivery engineer	Install, configure, hand over	Learns on the customer’s site
Support and renewal	Support, account manager	First-line support, renewal conversation	Renewals lost or left to someone else

The first conversation and the demo or POC tend to be where revenue is blocked, and they are also where product training is weakest, because product courses describe the product and the customer’s problem gets little room.

build a path for each role

A seller, a presales engineer and a delivery engineer need different things. A workable structure is a path per role with three levels: foundation, practitioner and expert, each mapped to a requirement in your partner tiers.

What the vendor’s own training usually lacks, and a channel team in a country should add:

• Positioning in the local context. Local competitors, local pricing, the national regulation and the use cases it creates.
• Hands-on practice in the local language. A workshop where the partner’s engineer configures the product, instead of watching a recording.
• Solution plays. How your product combines with what the partner already sells, for a problem the customer recognises.
• Coaching on real deals. Joint calls and a debrief afterwards. Nothing else teaches discovery as fast.
• Business skills. How to price services around your product, how to package it for a managed service, how to prepare a tender.

demos are part of enablement

A partner without a working demo environment does not demo, and a partner that does not demo does not sell. Not-for-resale licences and a shared, always-on demo lab are part of enablement. If your product is hard to stand up, run the lab yourself and give partners access, so every demo starts in minutes instead of days.

certifications walk out of the door

Certifications expire and leave with people. A partner whose only certified engineer moves to a competitor loses its ability to deliver, and often its tier, overnight.

Track certification by named person, per partner and per product, in your CRM. Alert the partner manager 90 days before a certification expires. When a certified person leaves, agree a replacement plan within 30 days. Microsoft’s partner capability score, which counts certifications held by individuals associated with the partner, is a public example of why this matters: the skill belongs to the person.

from shadow to independent

The goal of your engineers’ time is a partner that no longer needs it. A simple four-stage model makes progress visible.

1. stage 1shadowThe partner's engineer attends while yours leads, then you explain your reasoning. Exit: certified at the first level.
2. stage 2co-deliverThe partner delivers parts of the demo and runs POC tasks. Exit: two POCs completed together.
3. stage 3partner leadsThe partner leads demo and POC; you review the plan and stay on call. Exit: two successful POCs led by the partner.
4. stage 4independentThe partner handles standard deals alone. You join only for exceptions and complex deals.

measure it from the result backwards

The Kirkpatrick model, the standard reference for evaluating training, has four levels: reaction, learning, behaviour and results. It is tempting to measure only the first two, satisfaction scores and passed exams, because they are easy. Start from the fourth.

The practical test: compare partners that went through the training with similar-sized partners that did not, over six to twelve months, on registered opportunities, win rate and deal size. If the trained group does not register more or win more, the training taught something other than selling.

Budget enablement in engineer hours. The constraint is how many hours your engineers can spend in partners’ deals and workshops, and that number decides how many partners you can bring to stage four in a year.

the question for your channel team

How many partners closed a deal last quarter without one of your engineers in the room?