As a sales-led company, our Sales team needs to always stay on top of product updates. Sales enablement is a big part of what PMs do — especially when it comes to more technical features, like building our API.

There are a couple of ways this is made possible: 

Depending on the feature's importance/technical complexity, we sometimes create sales enablement documents for Sales to refer to later on (like this one). 

Product conducts training sessions for the Sales team for all the major product releases. 

Our design team creates prototypes of the upcoming features so that they can be used during the sales process. 

We have a public roadmap which Sales uses during demos and webinars.

It's essential they know how to explain and sell this to prospects because it's often one of the main selling points for large enterprise customers.

Often products/features are sold before they are built, so it’s important Sales know what the product strategy and roadmap looks like (at least on a high level). We start involving Sales more when we have defined the scope of the feature and know what the MVP will look like. 

In this case, this is a living document. We update it quite frequently whenever there’s a new question that comes up often or if there are any updates to how the API works.

RAMS and Training Register are B2B SaaS products. It was a strategic decision for us to build APIs for both of them, instead of native integrations with other software. 

We knew that one of the most common use cases for customers was using our product alongside HR software. However, when we started interviewing our customers, we realised that most of them were using very different HR systems, and there wasn’t a single leader on the market. So we decided to build our own API to give as much flexibility to our customers as we could.

The best way for us to understand if the sales enablement document is working is by gauging how often Product needs to be involved in the sales process when a prospect wants to use the feature. The more times Sales can successfully handle it themselves, the better!

This is a living document owned by Product, which means we keep it up to date and communicate any changes to relevant teams, such as CS/Sales.

Iryna Struk

We are a sales-led company so sales enablement is a big part of what PMs do — especially when it comes to more technical features, like building our API. It's essential they know how to explain and sell this to prospects.

Our customers use a lot of other software for their day-to-day activities and in order to make their job a bit easier and less manual, they might want to connect HandsHQ to something like Microsoft Sharepoint. For this, they will have to use an API (in order to get these two applications to talk to each other and transfer information).

 now, so both of our products can be integrated with other software.

How to set up an API integration with HandsHQ

The easiest way to set up the integration is using 

 which is a user-friendly no-code way for users to set up integrations between their software (they support more than 5000 apps and HHQ is one of them: 

). Zapier is a freemium product so anyone can use it for free.
In order for our customers to use HandsHQ through Zapier, please share this link with them - this will allow them to add HandsHQ app to their Zapier account [link]

Another way to set up the integration is via 

https://powerautomate.microsoft.com/en-gb/

 but this will require more advanced technical knowledge. To integrate HandsHQ with Microsoft products, they’ll need to use this method. Here is a short guide on how to help customers set it up [link]

Finally, the most advanced way to set up the integration is using our 

 (for this our customers will need to have their own developer/dev team or hire a consultant). They will need to refer to our technical documentation: [link]

The best way for us to understand if the sales enablement document is working is by gauging how often Product needs to be involved in the sales process when a prospect wants to use the feature

View a project PDF or collection of projects [link to docs]

Create/update/duplicate projects [link to docs]

Send the most recent RAMS PDF to other software

Add, update, show & remove personnel from an existing project (NEW)

Get signature status details of a project or particular personnel (NEW)

Send a link to a project that needs to be signed (NEW)

Sync personnel records in other systems with TR when updating/archiving/deleting them and vice versa

Sync training status of personnel from TR to other systems every time it changes (training status from the main TR dashboard)

Sales Enablement Document for APIs at HandsHQ

Sales enablement document at HandsHQ

HandsHQ API explained

What’s an API?

How to set up an API integration with HandsHQ

Sign up to see more