FXpress · AI Co-Pilot for Cross-Border Remittance · Synthesis Debrief
| Property | Value |
|---|---|
| 🏷️ Status | Complete |
| 🧩 Source | 4 surveys + 4 interviews — Jenni · Kang · Perry · Sadie |
| 🔬 Method | Affinity clustering → insight extraction → design-implication mapping |
| ➡️ Feeds Into | Personas · POVs & HMWs · IA · Interaction Design |
Following affinity clustering across all survey and interview data, seven recurring themes emerged. Each theme was translated into a direct design implication. This document is the primary evidence that FXpress is research-derived — every major architectural and interaction decision traces to at least one insight documented here.
Evidence: Three of four participants have delayed a send waiting for a better rate. Kang has calculated exact losses from sending on the wrong day. Sadie monitors rates actively but misses optimal moments. Jenni Googles but can't evaluate what she sees. Perry doesn't have time to check but would want guidance if it required zero effort.
What this is not: A lack of motivation. Every participant wants to optimize. The barrier is capability and cognitive load, not interest.
Design implication: FX timing assistance is not a supplementary feature — it is the primary product value. Fexi must proactively surface a read of the current rate and where it sits across a window of recent market data. The read belongs on the canvas as a persistent element, not hidden behind a menu.
Evidence: All four participants described conditions under which crypto would be acceptable — but every condition involved crypto being invisible to them or their recipient. No participant described a scenario where they wanted to see the word "USDC" or configure a wallet. Perry: "if it's just something in the background, fine." Jenni: "if I didn't have to deal with crypto myself." Kang: "my mom doesn't need to know what USDC is." Sadie: "abstracted when necessary for non-crypto users."
What this means: The product can use stablecoin rails to achieve speed and cost efficiency without ever surfacing this in the standard flow. Crypto visibility is a power-user option — not a default.
Design implication: All crypto terminology is removed from the default Send and FX Convert flows. "USDC," "wallet," "gas fees," "off-ramp," and "stablecoin" do not appear in any screen Perry or Jenni will encounter. Routing details are available in an expandable section for Kang and Sadie.
Evidence: Every participant's response to "what would make you feel confident?" converged on the same four elements: exact fee, exchange rate, recipient amount in local currency, and delivery time — all before the send button is tapped. Jenni: "the total fee, and knowing it's guaranteed to work." Perry: "exact fees, where the money is going, how fast it will get there." Kang: "no surprises." Sadie: "recipient payout time."