top of page
Construction Site View

CASE STUDY: Driving Product-Led Revenue

Automating Sales Conversion via Self-Service UX

The Challenge: STACK relied heavily on a high-touch sales model, creating a bottleneck for smaller accounts and increasing the cost of acquisition (CAC).

 

The Solution: I led a targeted UI/UX initiative to introduce a self-service conversion flow, allowing users to bypass the sales pipeline for standardized tiers.

 

The Impact: In the first year, this flow generated 3% of total company revenue with zero additional sales or support headcount, significantly improving the company’s profit margins on mid-market accounts.

Modern Architecture

Team

Design Manager

2 Engineers

My Role

Qualitative Research

Quantitative Research

Design

Usability Testing

Dev Handoff

Timeline

6 Weeks

Construction Worker Planning

01

Identifying the "Sales Gap"

Through an audit of our sales pipeline and user behavior, I noticed a segment of "ready-to-buy" users who were stalling. Our existing model required every user to "Talk to Sales," which led to:

  • High Friction: Small-to-medium users didn't want a 30-minute demo; they wanted to start working.

  • Sales Burnout: Account Executives were spending valuable time on low-contract-value leads instead of enterprise whales.

  • Training Overhead: Each new user required manual onboarding assistance from support staff.

02

The Pointed Intervention

Rather than a total platform overhaul, I focused on high-leverage UI "pivots" to guide users toward autonomy.

1. The "Just-in-Time" Conversion Trigger I identified key "Value Moments" within the app—specific actions that indicated a user was hitting a paywall or a limit. I designed contextual prompts that appeared exactly when the user’s intent was highest.

2. Reducing Cognitive Load in the Checkout Construction-tech billing can be complex (per-user, per-project, or flat-fee). I simplified the pricing display into a Three-Tiered model that allowed for one-click selection, removing the need for a sales rep to explain the contract.

3. Automated Onboarding (The "Zero-Training" Goal) To ensure these self-converted users didn't immediately flood the support queue, I introduced:

  • Progressive Disclosure: Surfacing advanced features only after basic tasks were completed.

  • Interactive Tooltips: Replacing manual training sessions with automated, task-based walkthroughs.

Screenshot 2026-04-01 17.22_edited.png
Screenshot 2026-04-01 17.22_edited.jpg
Screenshot 2026-04-01 17.25.15.png

03

Overcoming Internal Friction

One of the biggest challenges in introducing PLG to a sales-led company is "Channel Conflict." I worked closely with the VP of Sales to ensure:

  • Lead Routing: Only accounts under $5M in revenue were pushed to self-service, protecting the sales team's high-value targets.

  • Incentive Alignment: We ensured the system helped sales by "warming up" leads that might later upgrade to enterprise tiers.

04

The Results (By the Numbers)

  • Revenue Growth: Accounted for 3% of total annual revenue in the first year.

  • Sales Efficiency: Reduced the sales team’s involvement in small-tier accounts by 41%, allowing them to focus on larger deal sizes.

  • Operational Cost: $0 increase in support or sales staffing costs to manage this new revenue stream.

  • Time-to-Value: Users were able to go from "Account Created" to "Fully Onboarded" in 10 minutes, compared to the previous 4-day sales cycle.

Screenshot 2026-04-01 17.25_edited.jpg
Wireframe Design Sketch

05

Reflection

This project proved that UX isn't just about "look and feel"—it’s a mechanical lever for business growth. By identifying a friction point in the business model and solving it through interface design, we unlocked a scalable revenue stream that continues to grow without increasing overhead.

bottom of page