���ϳԹ���

“It’s fair to say that without a tool like ���ϳԹ��� our agency’s ability to continue to carry out our mission would be hampered by confusion and obsolete guidance which ���ϳԹ��� helps us avoid.” – Dustin Bystrom, Minnesota Associate Council for Veterans

Documentation and hand-off at the end of any implementation can be more challenging than the project itself. Passing off all training and answering the many questions that pop up after can take massive amounts of time and potentially extend the project.

We know that the overall cost of implementation is one of the most important metrics clients want and need to control. For that reason, if there are any specific pieces that threaten or put pressure on the timeline and/or budget, you run the risk of an unhappy client, a freeze on resources or even a failed project.

With time, scope and budget being so finite, anything that can help mitigate unforeseen challenges can be the difference between a satisfied client and an unhappy one. This is particularly important when it comes to maintaining a client for life relationship.

So, what’s the solution? How can you eliminate these seemingly inevitable hurdles and problems that come with wrapping up a project? Let’s break down how ���ϳԹ��� can help you create the perfect Salesforce roll out and win over your clients again and again.

Why ���ϳԹ���?

���ϳԹ��� is an in-app learning and digital companion that helps employees learn their tools and navigate process changes by accessing answers and enablement resources in real-time, everywhere they work.

Built by sales ops professionals for growing and remote teams, ���ϳԹ��� blends the sophistication of a modern digital adoption platform with the simplicity of a contextual knowledge base for a lightweight yet powerful solution to continuous employee training.

So, how can it help you during and after implementation?

Documentation, documentation, documentation

Let’s start with the big one, documentation. What systems and tools are you currently using to execute your project documentation? Powerpoint? Word? Excel? Email? Maybe even your clients internal system(s)?

There’s nothing specifically wrong with any of these tools on their own, but what happens when there are changes to the scope of the project? What if your client makes frequent updates or consistently alters the scope of the project? How easy is it to edit and complete the new documentation? Losing project time to documentation has traditionally felt like par for the course, especially when it comes to communicating with your clients.

It also affects your clients post-implementation. Long term, what happens when changes are made in their Salesforce instance? Is your client prepared to manually update those changes in the provided documentation? Do they have a plan for documenting and communicating?

���ϳԹ��� helps you overcome these seemingly unsolvable problems. Let’s take a look at an example…Let’s say you’re implementing a CPQ solution for a new client.With ���ϳԹ���:

• You create the documentation once and add it in the ���ϳԹ��� wiki (for example, if you’re implementing NPSP, all your basic NPSP content is added into ���ϳԹ���).
• That content can quickly be customized to meet your client’s needs (for example, add the Client’s name, any unique terms or definitions they need).
• Voila! You can hand off this project to your client as a customized documentation solution that they can access from directly within Salesforce or across any app via our Chrome Extension.
• Starting a new project with a new client? Easy! Just clone your existing documentation, customize to the new client’s needs and publish!

Getting started in ���ϳԹ��� is easy and doesn’t require heavy lifting to get up and running. In a few steps you’ll be ready to start your documentation and provide real-time updates for your client.

This once tedious task is now easy and efficient to replicate across clients. Now, let’s look at how you can hand this off after implementation.

Enabling a smooth handoff and future-proofing your project

Now, you’ve gone through the process of creating documentation and you’re ready for the handoff. The project is wrapping and you need to provide your client with the specifics about why you did what you did, how you did what you did, the nuances behind the solution you built for them and the details behind everything in their org from custom objects to individual fields.

Using ���ϳԹ��� to help roll out your implementation and complete detailed documentation throughout the project means you’re already one step ahead. This training isn’t new to the client. Likely, they’ve been involved to a degree in your process so far. They’ve had access to the shared training in ���ϳԹ��� and you’ve assigned “Experts” to manage content after you’ve left.

Through the dynamic content created during documentation, you’ve already provided training materials they can immediately get started with. With knowledge and videos embedded with the ���ϳԹ��� content, they can immediately use to get up to speed on the amazing solution you built for them.

This is crucial because now they’re able to turn around and customize any additional training for their team so they can get up and running right out of the gate. This means sooner recognition of ROI on a tool they’ve invested a lot of time and money into.

They’re also able to collect data from their employees in real-time to find out if everything is working the way it should be. This could be a potential source of