LeadrPro’s original swipe-based design resembled a dating app more than a business tool.
Executives struggled to find relevant vendors quickly, resulting in just 10% user engagement.
Demo bookings, the platform’s main revenue stream, were being missed.
After analyzing the issues with the swipe-based design, I met with LeadrPro’s CEO and CTO to propose a hub-based system. The reasoning for this shift was clear:
We agreed that this shift would streamline the platform and boost engagement.
After analyzing the issues with the swipe-based design, I met with LeadrPro’s CEO and CTO to propose a hub-based system. The reasoning for this shift was clear:
The Vendor Hub was redesigned to help executives quickly identify relevant vendors and take immediate action, reducing friction in their decision-making process.
The demo scheduling process was reimagined to eliminate friction and enhance user efficiency and team collaboration. This redesign directly supports LeadrPro’s core objectives:
Increasing demo bookings
Streamlining user interactions
42% ↓
User Drop Off Rate
27% ↑
Profile Completeness
34% ↑
Time Spent on Profiles
🚨🚨 One Challenge: Event Misses Due to Lack of Cross-Hub Alerts!
While navigating between different hubs—such as the Software or Vendor Hub—users occasionally missed their scheduled events. This happened because there were no cross-hub notifications reminding them of upcoming events while they were focused on other tasks in different hubs.
To resolve this, we introduced cross-hub integration, ensuring that users are notified about their events, regardless of which hub they are currently using. This way, they can stay informed without missing any important engagements.
The features were carefully chosen to maximize user engagement and drive key business outcomes. Each tab focuses on reducing friction and ensuring users can quickly access actions that matter most, like demo bookings and vendor interactions.
