ApexRune
Back to Case Studies
CASE STUDY Medical Devices

From "Spaghetti Logic" to a Seamless Sales Wizard

MEDICAL DEVICE MANUFACTURER
Lightning Web ComponentsProgressive DisclosureCustom MetadataTerritory ManagementClient-Side Validation

The Client

A medical device manufacturer with a complex portfolio spanning multiple product categories, requiring sophisticated lead qualification and territory-based owner assignment across 50+ countries.

The Challenge

Visual tools are great—until they aren't. The client's "New Lead" process had grown into a massive, unmanageable Salesforce Flow with hundreds of decision nodes, undocumented loops, and legacy Aura components. What started as simple logic had mutated into a maintenance nightmare. The cost of this complexity was paralyzing the IT team: "What should take 2 hours was taking 2 days." User errors were rampant due to confusing single-screen forms.

Our Solution

We didn't just patch the Flow; we launched a complete modernization initiative. We replaced the monolithic backend process with a modular Lightning Web Component architecture featuring progressive disclosure, modern UI patterns, and intelligent territory-based owner suggestions.

  1. 1 3-Step Progressive Disclosure Wizard: Broke the process into intuitive stages (📋 Product Interest → 👤 Fulfillment & Ownership → ✅ Review & Confirm), reducing cognitive load and user errors by 60%
  2. 2 Modern UI Patterns: Replaced standard dropdowns with visual "Pill Selectors" and "Card Layouts" for faster data entry, plus country-based category/brand filtering via custom metadata
  3. 3 Territory-Based Owner Suggestions: Integrated Team Map Modal showing top 3 suggested owners based on account territory, category, and brand context
  4. 4 Client-Side Validation: Real-time validation prevents errors before server submission, with comprehensive field validation and country-specific dealer requirements

The Results

70% Maint. Time Cut
3x Faster Deployment
100% Better UX
Key Insight

"The "spaghetti Flow" wasn't just a technical problem—it was a user experience problem. By breaking it into intuitive steps with modern UI patterns and intelligent owner suggestions, we didn't just fix the code, we transformed how users interact with the system. Maintenance time dropped 70% because the code finally made sense."

Lessons Learned

  • Progressive disclosure (3-step wizard) reduced user errors by 60% compared to single-screen forms—cognitive load matters more than we thought
  • Territory-based owner suggestions eliminated the "who should own this?" question that was slowing down lead creation by 40%
  • Modular LWC architecture made future enhancements 3x faster—adding a new field to the wizard now takes minutes, not days