How to Build a Partner Training Program: Onboarding Steps, Tiers, Certification and How to Measure It
A partner training programme is the shortest path from a signed agreement to a partner running your demo without you. Build it around the tasks each partner role performs, certify by having partners perform them, and measure it by time to first partner-led demo, not by course completions.
To build a partner training program, list the tasks each partner role must perform on your product, give each task a short video and written steps, and certify partners by having them perform those tasks in a demo environment. Organise it in three tiers (sales, pre-sales or technical, and support) and measure it by how quickly a new partner runs their first demo without you in the room. Everything else is detail around that spine.
This page covers the programme in the order a partner meets it. Our view of the videos themselves is on partner enablement.
Partner onboarding steps, from signed agreement to first partner-led demo
A partner becomes useful the first time they show your product to a prospect and the demo works. Every step should move them towards that moment.
| Step | What the partner does | What you provide | Done when |
|---|---|---|---|
| 1. Kick-off | Names who will sell, demo and support | A named contact and the training plan | Each partner role has a named person |
| 2. Access | Logs in to the portal and the demo environment | Accounts, a seeded demo environment, the docs | The partner reaches the starting screen of the main task |
| 3. Positioning | Learns who buys, why, and the common objections | A short positioning brief and objection answers | The sales person can name the buyer and the first question to ask |
| 4. Task training | Works through the task videos for their tier | One video and one set of written steps per task | The partner has run each core task once on their own |
| 5. Certification | Performs the core tasks while someone watches or checks the result | A task list and a pass rule for each task | The product shows the result the task promised |
| 6. Shadowed demo | Runs a demo with you present | Notes on what went wrong and the fix | The demo finishes without you taking over |
| 7. First partner-led demo | Demos to a prospect alone | Support on call, nothing more | The partner reports it and logs the opportunity |
Three tiers: sales, pre-sales and support
Partner staff do different jobs, so split the programme by role. In a small partner, one person may take two tiers.
Sales
Sales people need to know who buys, which problem they bring, the common objections and when to call in a technical colleague. They should run a short demo of the workflows prospects ask to see first. They do not need the installation.
Pre-sales and technical
This tier carries the real demo and the proof of concept: first-run setup at a new customer, every workflow a prospect may ask to see end to end, the integrations, and the step that usually goes wrong. Most of the training effort belongs here.
Support
Support staff need the upgrade path, the common failures, how to diagnose them and when to escalate. They learn best from troubleshooting material: what the error looked like, its cause and the fix.
Partner certification: test a task performed, not a quiz on features
A multiple-choice quiz tests whether someone remembers the feature list. A partner can pass it and still fail the first demo. Certify on tasks instead: a clean demo environment, a task with a finish line, and a check that the product shows the result. A backup either restores or it does not.
Sales certification can be a recorded short demo against a prospect scenario. Technical certification is the setup and core workflows, performed. Support certification is a broken environment to diagnose. Marking costs more than a quiz, because someone has to check each result; that is the tradeoff. After a major release, re-certify only on the tasks that changed.
What content each tier needs
- Short task videos, one task each, recorded on a stated version.
- Written steps beside each video, with commands and settings a partner can copy. How to write step-by-step instructions covers the format.
- A demo environment with realistic data, the same one partners certify on.
- Objection handling, shown on the product where possible rather than argued on a slide.
- Troubleshooting notes for each task, because partners search for the failure when a demo goes wrong.
Keep the long kick-off recording for context. Nobody watches it twice.
How long should partner training videos be?
As long as the task takes, and one task per video. We have no data that proves an ideal length, and would distrust anyone quoting one. A video covering one task with a clear finish line is easy to find, easy to replace when the task changes and easy to certify against. If a task is long, keep it in one video with chapters. Instructional video production for software covers the planning.
Where to host partner training
Host it where partners already look when a prospect asks a question, which for most vendors is the partner portal, beside the price list and deal registration. An LMS earns its place when you need enrolment, tracked completions and certification records; the cost is another login partners forget. A workable split is the LMS for certification and the portal for the task videos.
For the files, YouTube's unlisted setting is a cheap option. Per YouTube's help page on privacy settings (checked 15 October 2026), unlisted videos can be watched by anyone with the link and do not appear in YouTube search unless someone adds them to a public playlist. Material under NDA belongs behind a login instead.
Partners in other markets need their own language
Partners demo to their own customers and cannot ask a colleague what a step means, so training needs their language. One recording can serve every market: translate captions and narration, and keep product names, menu labels and commands exactly as on screen. Re-record only where partners use a localised interface. Product demo video in multiple languages covers that choice, and One product demo. Five markets. shows it in thirty seconds.
Keeping partner training current after every release
A partner demonstrating a version from two releases ago shows the prospect a dated product or a button that has moved. Tag every task video and certification task with its version. On release day, list the tasks the release touched and re-run those. The failure mode is a library nobody owns, accurate for one release and then drifting. Give it an owner and put the re-run in the release checklist. Onboarding videos face the same problem.
How to measure partner training effectiveness
Course completions measure attendance. Measure what the programme is for.
- Time to first partner-led demo, counted from the signed agreement. It tells you whether onboarding works.
- Certification completion by tier, and the tasks partners fail most. A failed task usually points to a missing video or a confusing step.
- Partner-sourced pipeline from certified against uncertified partners, read with care, because the keenest partners certify first.
- Support tickets from partner customers about tasks the partner was trained on. A rise after a release means the training did not move with the product.
These numbers already sit in the CRM, the LMS and the support desk. Record the starting values before you change the programme, or you will have nothing to compare against.
What should a partner training program cover?
The tasks each partner role performs: the demo workflows and objections for sales, setup and proof of concept for technical staff, and the upgrade path and common failures for support. Start from what partners do in front of a prospect, not from the feature list.
Partners are not watching the training videos. What should I change?
Usually they are too long, cover too much, or sit where partners do not look. Cut them to one task each, title them with the task, and put them in the portal.
Should partner certification be a quiz?
Not on its own. A quiz checks recall. A partner who performs the task in a demo environment and gets the result the product promised has shown the skill the prospect will see.
Send one task your partners keep getting wrong. We run it on your product and deliver the video, the written steps and the troubleshooting notes, in the languages your partners need. The first sample is free.
$ get-sample →