Redesigning the purchase flow and e-invite experience to reduce drop-offs, improve trust, and strengthen post-purchase confirmation and transactional emails.
GoalReduce drop-off
RoleUX / Product (Web)
FocusConversion & Trust
ToolsFigma + HTML/CSS
AlsoTransactional Emails
Verified project record
Evidence, scope, and outcome.
Problem
Checkout friction, trust questions, and unclear post-purchase communication.
Contribution
UX and product decisions informed by frontend implementation constraints.
Delivery
Design artifacts and frontend-informed product work.
Evidence
Funnel observations, redesigned flows, final UI, and a defined A/B test plan.
Outcome
Success metrics are defined; no verified public conversion lift is claimed.
01 / Case study
Funnel + Drop-offs
The checkout funnel showed the biggest drop-offs around shipping and contact details, payment selection, and the e-invite setup step. The goal was to reduce friction and improve confidence at each step.
Key funnel: Product to Amount to Recipient to Payment to Confirmation
Hypothesis: unclear steps and trust questions cause abandonment
02 / Case study
Friction Points
Reviewing the flow and support patterns revealed three central problems.
Too much input
Too many fields appear before users understand code delivery, the recipient flow, or refund rules.
Trust questions
Users need reassurance about when the code arrives, whether the service is legitimate, and how gifting works.
Post-purchase gap
Confirmation and transactional emails must clearly explain order status, delivery, and who receives what.
03 / Case study
Redesigned Flow
The redesign simplifies steps, adds reassurance at key moments, and makes the e-invite feel intentional rather than like extra work.
Step clarity
A visible stepper and 'What happens next' microcopy.
Trust blocks
Code delivery, refund policy, and support information visible early.
E-invite defaults
Smart defaults with optional message, scheduling, and preview.
04 / Case study
A/B Test Plan
Primary metrics
Checkout completion rate
Payment-step completion
E-invite completion
Time to complete purchase
Secondary metrics
'Where is my code?' support tickets
Email open and click rate
Refund/dispute rate
Post-purchase feedback
05 / Case study
Final UI
High-fidelity screens showing the simplified checkout, e-invite setup, and clear confirmation states.
Checkout stepE-invite setupConfirmation
06 / Case study
Transaction Emails + Order Confirmation UX
To reduce 'Where is my code?' confusion, confirmation pages and emails were treated as part of the product, not an afterthought.
Order confirmation: clear status, expected delivery, and next actions
E-invite email: sender/recipient clarity and what happens when opened
Order updates: payment confirmed to code delivered to resend/support