Finding the real reason customers disappeared.

Customers had completed onboarding, verification, and underwriting. They received an approved offer—and then left without accepting it.

The natural explanation was friction in the final product experience. That explanation was specific enough to generate redesign ideas, but it had not been tested with the people who actually dropped.

• Converted a vague “why are users leaving?” question into a structured six-question interview instrument.
• Coordinated the target cohort and dialer workflow with customer-service operations.
• Defined response categories that could be compared while preserving room for the customer’s own explanation.
• Synthesized 88 completed conversations from 352 outreach attempts and documented the response-rate limitation.

The app was not the issue.

The largest drivers were mismatch between expectation and the final offer: approved amount and price. Seventy-seven percent said the final offer differed from what they expected. In contrast, 94% reported no technical problem and 96% reported no hesitation with digital acceptance.

The finding shifted the question from “How should we redesign the final screen?” to “How do we align expectations and offer policy earlier?”

A case study does not need to end with a feature to contain product impact. Here, the valuable decision was what not to build.

Redirecting the roadmap protected design and engineering time, challenged an internally comfortable story, and gave the risk and product teams evidence for a more consequential conversation about offer structure.

Qualitative evidence becomes more useful when the instrument makes it comparable, and quantitative evidence becomes more useful when people explain the behavior behind it. I also learned to state the limitation—the response rate was 25%—without treating it as a reason to ignore a strong directional result.