Case study/SaaS
WaiverKing: Software Development for Waiver Form Creator
WaiverKing is a document management business serving primarily the health and fitness industries. The platform is partnered with MindBody Online, one of the largest business-systems providers for gyms and yoga studios.
unicrew took over development of WaiverKing, a live waiver and document management platform for the health and fitness industries, and refactored its barely documented legacy codebase onto the Yii 2.0 framework, under a standing condition that hundreds of active customers should feel no major impact while it happened. Updates that once took weeks to reach live now go out in a couple of hours, and the team stayed on to build what came after.

- Client
- WaiverKing
- Focus
- SaaS
- Market
United States
- Engagement
- Legacy takeover and modernization
- Stack
Yii2
PHP
JavaScript
MySQL
Outcome at a glance
What this project delivered, in numbers.
- Weeks to hoursTime for an update to reach liveafter the refactor and release automation
- Around 2,000Companies on the platformup from a couple hundred, in the CEO's words
Project Overview
WaiverKing is an online service that helps businesses around the world manage waivers, and the document management hassle that comes with them, in a simple and integrated way. The application is designed to streamline the completion, storage, submission, and integration of waivers with third-party services, securely and efficiently.
WaiverKing pairs sophisticated digital signature capabilities with MindBody Online integration. That lets WaiverKing customers fill out and sign legal documents in a matter of minutes and have them transferred immediately to their MindBody Online profiles, which update in real time. The service delivers a simple, user-friendly experience on both web and mobile.
Challenge
Our team took over a live project that was already in use. The main challenge was to proceed with a legacy codebase that was barely documented and had been built around its original scalability and data-privacy requirements. On top of that, the system carried an excessive number of dependencies that made it hard to modify and improve based on feedback from WaiverKing’s new customers. Because of that, deadlines and delivery of additional features were always at risk. It was clear the codebase had to be refactored to support the growing success of the business.
Another challenge was that the system was in use by hundreds of active clients, so all refactoring work had to happen without a major impact on their experience.
Solution
Given all these challenges, and to remove roadblocks in the future, we decided to refactor the codebase and adopt the Yii 2.0 framework. This makes sure the software is ready for further growth in a structured and secure way.
We moved the codebase to Git for version control and, together with deployment automation, eliminated human mistakes during release activities. With these efforts it is now possible to deliver new features to end users in hours or days instead of weeks. The overall reliability of the software under a constantly growing load improved noticeably, and the service reappeared as a fast, easy-to-manage, and highly customizable platform.
Once the refactoring phase was complete, our team continued on the project and delivered a set of new features, including:
- Secure 2-factor authentication
- Customizable permissions management
- Sales management and reporting systems
- A fully automated billing system using Authorize.net
- A fully reinvented user experience based on mobile-first principles
- Dozens of other customization options
The next step in WaiverKing’s development was the rental management system, which used IoT technologies to track rental status in real time and was released successfully within the following four months.
Result
Since we took over the project, WaiverKing has shown year-to-year revenue growth along with a significantly improved end-user experience. The overall time required to release updates to live dropped from weeks to a couple of hours, thanks to a set of automated tests and a scalable software architecture. The engagement has run since January 2014, with unicrew providing development, QA and project management throughout.
Inheriting a codebase you did not choose, on a product customers are already using, is a different job from building one. More of what clients say about long engagements is on our client reviews page.
What the client says
They’ve been helping us grow our platform together since the beginning, from a couple hundred companies to around 2,000. Artelogic has been front and center in this process.
06/Quick answers
The questions behind the project
What did unicrew do for WaiverKing?
unicrew took over development of the WaiverKing platform, a live waiver and document management service for the health and fitness industries, and refactored its legacy codebase onto the Yii 2.0 framework. After the refactor the team stayed on and built new features: two-factor authentication, customizable permissions management, sales management and reporting, a fully automated billing system using Authorize.net, a mobile-first rework of the user experience, and later a rental management system using IoT to track rental status in real time.
Why refactor onto Yii 2.0 rather than patch the old code?
Because the old codebase was the bottleneck. It was barely documented, built around the original scalability and data-privacy requirements, and carried an excessive number of dependencies that made it hard to modify on customer feedback, so deadlines and new features were always at risk. Moving to Yii 2.0 put the software on a structured, secure base for further growth. unicrew also moved the codebase to Git and automated deployment, which took human error out of releases.
How do you refactor a live platform with hundreds of active clients?
Carefully, and without a major impact on their experience, which was a condition of this project: WaiverKing was already live with hundreds of active clients when the work started. Version control in Git plus deployment automation removed the manual mistakes that come with release activities, and a set of automated tests went in behind a scalable architecture. Reliability under a constantly growing load improved noticeably.
What changed after the refactor?
The time needed to get an update live dropped from weeks to a couple of hours, on the back of automated tests and a scalable architecture, and the end-user experience improved significantly. Over the engagement the platform's client base grew from a couple hundred companies to around 2,000, which is the CEO's own figure in his verified Clutch review. For similar work, see our SaaS modernization for a paddle-sports center.
