How Altvia Cut off Clutter and Enhanced Employee Performance with SweetProcess

Introduction

Ben Hendershot is the Chief Operating Officer at Altvia. Working in an organization that helps private equity firms and other private market participants operationalize their software, he was no stranger to streamlining business processes. He was keen on improving his company’s business operations, but finding the right system was a bottleneck. Ben understood that his team would be more efficient if they had all the tools that they needed in one place, instead of toggling between different systems. He found the missing plug after trying out SweetProcess. He tells us about how SweetProcess fine-tuned their operations. First, let us know more about the company for a better understanding.

Ben Hendershot Chief Operating Officer at Altvia

About Altvia

Altvia is a software-driven company that assists private equity firms to strengthen their relationships with clients using data intelligence. The company leverages the best technology and processes to create a free flow of communication between limited partners (LPs), general partners (GPs), and portfolio organizations. 

A premier entity for private equity created on salesforce, the Broomfield-based organization offers various expert services including investor relations, business intelligence, capital raise and deployment, and compliance.

Established in 2006, Altvia has a clientele of top firms across the world.

Listen to the audio interview:

Listen to more customer stories and interviews like this:

Their Biggest Pain Point: Too Many Processes

Many organizations suffer from the lack of documented business processes in their workflow. However, this was not the case with Altvia. They created too many processes that impeded their workflow. 

“We had lots of different processes and procedures and documentation spread across various systems. We had an internal wiki of sorts that had a whole bunch of instructions in it,” Ben says.  

Creating tons of processes was meant to enhance their efficiency, but it turned out to be counterproductive. With as many as ten different processes for one task, team members were overwhelmed. They struggled to sieve the useful information from the fluff. Sometimes they mistakenly picked the wrong document from the pile. They also had many questions about what to do and how to do it. It became apparent to Ben that something was off, and all fingers pointed at the gaps in their processes.

Finding a Great Product at an Irresistible Price

Ben’s decision to adopt SweetProcess was born out of a need to resolve an operational problem. He wanted to be able to create a single version of every procedure to avoid things getting mixed up. 

“When I heard of SweetProcess and when we implemented it, it was great because you can only have one version that’s active of a particular procedure or process. Therefore, you minimize the likelihood that somebody is going to look out fo...