Training the sales kit operations team: how extensive is it needed?
The question is not 'is training necessary' but 'how much training is enough for the team to truly utilize it'.
The mandatory minimum level includes three things: a session on how to use the repository, step-by-step editing documentation, and a Q&A channel during the initial running phase. More important than the training content is clearly separating the two roles: the administrator sets the rules and updates the repository, while the end user only creates within the locked boundaries. If no one on the team is ready to operate the tool, extensive training will still be wasted, so this investment is only worthwhile when users already have a foundation.
- The team is familiar with tools; they need a training session and documentation.
- A large team or many agencies need multiple workshops.
- Is there a new person who needs to review the recorded training session?
- No one on the team will use the tools after training.
- Not assigning management roles, so no one updates the repository.
Many businesses invest in creating sales kits and then hand them over to the team. A few months later, the sample materials are still there, but no one uses them, or they are used incorrectly to the point that the brand appears more chaotic than before. The reason is almost always the same: handover without training, or training without materials for newcomers to refer back to. The question is not whether there is training, but whether the training is on the right content, for the right people, at the right level.
Separate roles before training.
This is something Sinh Vũ often sees overlooked. In any template library system, there are two completely different roles that need to be clearly defined from the start.
- Brand asset manager: has access to the original files, sets rules for access, and updates brand assets as needed. Usually someone from the marketing team or the brand manager.
- The end user: only works within a copy, creating documents within pre-set boundaries, without touching the original file.
If these two roles blur into each other, the system breaks in one of two ways: the administrator gets pulled into handling every small request because no one else can, or the end user accidentally alters something they shouldn't because the boundaries are unclear. Separating roles is the first training step, even before turning on the machine.
The minimum training level and the sufficient level.
Good enough (large team, many newcomers, many agents): Multiple workshops by role groups, recorded training sessions for newcomers to onboard later, a manual in PDF or Notion format, extended Q&A channels, and a dedicated guidance flow for new sales.
The boundary between these two levels lies in two questions: does the team have new members continuously, and does the team operate across multiple branches or agents? If either is true, the minimum level will not be sufficient.
What should the guidelines document include?
A useful document is not one that explains what a warehouse is. Readers need to know specifically where to click, what to change, how to save, and who to send it to for approval before printing or sending to clients. A usable document typically includes:
- Guidelines for creating new documents from templates, step by step, according to the actual tool interface.
- List of what can be edited and what should not be touched.
- The way to export files in the correct format for each purpose: print, email, online posting.
- Who to contact when adjustments are needed outside of end-user permissions?
If the document only has one of those, the team will ask for the rest or guess in a way that could ruin the inventory.
Common errors after delivery
- Delivering a repository without training means the team is hesitant to use it for fear of making mistakes.
- One-time training, no recording, newcomers have nothing to review.
- Do not assign a specific administrator; no one updates the repository when the logo or brand colors change.
- Training for those unfamiliar with the tools, where most of the session is spent explaining the basic interface instead of diving into the content.
The success of a self-service system lies in the clear separation of roles, not just in the quality of the samples. A good tool is useless if no one knows what they are allowed to do.
Marq, Brand Templating Guide
The viewpoint of Sinh Vũ
In the P5 package, Sinh Vũ includes four layers of support: a workshop guiding the use of the entire kit, a recording of that session for newcomers to review, PDF guidelines for each part of the kit, and a Q&A channel after delivery. In the full package, the support channel lasts for 60 days, while the higher package extends to 90 days with onboarding for new sales and an operations manual for the team.
Sinh Vũ is upfront with clients before signing: if no one on the team regularly uses Canva or Figma, training will not be effective. It’s not due to poor materials, but because the learners lack the foundation to absorb the content. In that case, the right step is to provide basic tool training first or reassess whether the team truly needs to operate independently or still requires Sinh Vũ's production support.
Training is not an item to cut for budget relief. However, it should not be invested in when operational conditions are not ready. These two things need to go hand in hand.
Decision checklist
Topic: How much training and documentation is needed for the team to operate the sales kit independently? Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Marq, Brand Templating Guide. Gartner, What Is Sales Enablement and Marketing's Role in Buyer Enablement. Sinh Vũ, P5 service data (P5.json, p5-sales-toolkit.md).
Frequently asked questions
Is one training session enough?
Sufficient for a team that is familiar with the tools and has few members. But one session is not enough if the team is large, has many newcomers continuously, or if no one has ever used Canva or Figma. A practical solution is to record the session for newcomers to review, rather than having to organize it from scratch each time.
How detailed should the guidelines document be?
Sufficient for someone without direct training to still handle routine tasks. This means there must be step-by-step guidance using real tools, not just general documentation. If the documentation only explains 'what a warehouse is' without specifying 'where to click to create a new document', the team will either ask questions or overlook it.
Who is responsible for updating the library when the brand changes?
A specific administrator must be designated, not left vague. Without a responsible person, the repository will become outdated and the team will gradually lose trust in the assets within it. The administrator does not need to be a design expert, but must be granted access to the original files and understand the process for requesting edits from Sinh Vũ.