Remittance app retention: diagnose churn, prioritize fixes, and design validation tests

You are the product manager for a remittances product, a service people use to send money to someone in another country, most often family. You are asked how you would get more users to keep using it, and how you would validate those ideas and the assumptions behind them. ### Clarifying Questions - Is this a consumer app that individuals use directly, or a service that businesses build into their own products to pay people abroad? - Who are the main senders and which corridors matter most: workers sending part of each paycheck home, or occasional senders covering one-off expenses? - How is retention measured today: another transfer within some number of days, or monthly active senders, and how often does a typical sender need to send? - Do we know where users drop off: before the first transfer completes, right after it, or after months of regular use? ### Part 1 — Improve retention Explain why senders stop coming back and propose prioritized changes that would keep more of them. ```hint Where did they go? Most people who remit keep needing to send money, so a user who stops using the product is often still sending through someone else. Ask what made that alternative win at the moment of sending. ``` #### What This Part Should Cover - A churn diagnosis split by lifecycle stage and segment, separating users whose need ended from users who switched. - Ideas tied to the specific reasons people leave a money transfer service, such as total cost, speed, reliability, trust and the recipient's experience. - A prioritization with a stated rationale, and a primary retention metric that matches how often people send. ### Part 2 — Validate ideas and assumptions For your top ideas, show how you would test the assumptions they depend on, and how you would prove the ideas worked once built. ```hint Mind the cadence If people send roughly once a month, an experiment that waits for retention to show up will be slow. Look for earlier behavior that predicts a repeat send. ``` #### What This Part Should Cover - The assumption behind each idea, ranked by how risky it is. - Cheap research and data checks before building, then controlled experiments with holdouts. - Experiment design suited to money transfers: leading indicators, duration across sending cycles, and guardrails on fraud, revenue and compliance. ### What a Strong Answer Covers - A clear definition of retention for a behavior that recurs but is infrequent. - Attention to both ends of a transfer: the sender who pays and the recipient who receives. - The tension between retention bought with lower prices and revenue per transfer. - Trust and regulatory constraints that come with moving money across borders. - A sequenced plan from diagnosis to experiment to rollout. ### Follow-up Questions - A competitor launches a zero-fee promotion in your largest corridor. How do you respond without starting a price war? - Your experiment lifts second transfers, but fraud losses rise in the treatment group. How do you decide whether to ship? - How would your approach change if the product were an API that businesses use to pay workers abroad?