Freelance · 4.5 months · 2024 ·5 min read
Zyeero — Study Abroad
Journey Platform
Most platforms stop helping at admission.
Zyeero stays until students settle.
I designed the complete experience — from landing page to post-arrival dashboard.
Overview
What I was hired to do
Zyeero is an all-in-one platform helping Indian students plan, apply, finance, and settle abroad. The founders brought me in as the sole designer to design the complete platform from scratch — working directly with the founding team and a front-end engineer over 4.5 months.
My scope covered 6+ service landing pages (Universities, Loans, Visa, Insurance, Exam Prep, Moving Abroad), a post-arrival student dashboard, an events platform, and a full design system. Every screen in this case study was designed, iterated, and delivered by me.
"This project taught me that designing for students going abroad is less about interfaces and more about emotional safety. They don't want a tool. They want support, clarity, and someone who stays with them."
01 — Business context
Understanding how Zyeero makes money
Before designing anything, I needed to understand the business model — because design decisions that don't connect to revenue are decoration, not product work. Zyeero operates on a commission and partnership model across its core service verticals.
This understanding had a direct impact on prioritisation. The loan application flow wasn't just important for user experience — it was the primary revenue driver.
02 — Problem
The journey felt overwhelming, scattered, and alone
Studying abroad involves hundreds of decisions across a 12–18 month journey. At every stage, students feel like they are figuring it out alone. The emotional experience is consistently described in three words: overwhelmed, confused, and unsupported.
03 — Research
Structured research across the journey
Key findings — what students actually said
"Bhai honestly, itna confusion hai… har consultant kuch alag bolta hai. Kisko trust kare samajh hi nahi aata."
Finding → Trust deficit is the primary adoption blocker. Transparency and real references aren't nice-to-have features — they are the entire value proposition.
"Loan ke time pe sabse zyada dar lag raha tha… galat document upload kar diya toh reject ho jayega kya?"
Finding → The loan flow is the highest-anxiety moment. Document upload specifically caused the most hesitation — directly shaped the categorised checklist design.
"After landing, mujhe literally SIM card aur room ke liye YouTube dekhna pada."
Finding → Post-arrival is completely unserved. This single quote justified the entire "Setup Your Home" dashboard section — and became Zyeero’s primary competitive differentiator.
"Mujhe bas ek checklist chahiye thi… kya kab karna hai. Abhi sab random lagta hai."
Finding → Students need sequence and clarity, not more information. Shaped the guided task-by-task architecture over a feature-library approach.
Competitive landscape
| Platform | Strength | Critical gap |
|---|---|---|
| Leverage Edu | Strong mentor system, trusted brand | Consultant-led — student has no ownership of their own journey |
| IDP | Global recognition, structured process | Expensive, rigid, stops completely at admission |
| UniBuddy | Peer-to-peer student connections | Advice only — no execution support |
| AdmitKard | Application guidance | Drops off at admission, no post-arrival presence |
| Zyeero | OpportunityEnd-to-end + post-arrival | Building now |
04 — User personas
Two students, two stages, one platform
05 — The critical reframe
I was solving the wrong problem
Early in the project I was designing features — better university search, cleaner loan comparisons, smarter filters. The founders were satisfied with the direction. But something felt shallow.
The problem was my framing. I was asking the wrong question entirely — and no amount of good UI execution fixes a wrong problem statement.
This was also where the founder pushback happened. When I proposed investing design time in post-arrival features, the founders asked: "Do students really need a study-abroad platform after they've already landed?" I returned with the research data and student quotes.
06 — Design goals
Four principles that governed every decision
07 — Journey mapping
Mapping every moment of the student journey
Before designing any screen, I mapped the complete student journey from university exploration to settling in a new country.
The journey map directly shaped the dashboard architecture. Each node became a dashboard section. The map made the scope of the post-arrival problem undeniable.
08 — Lo-fi explorations
Structure before style
Before any high-fidelity work, I explored information architecture and layout hierarchy in lo-fi wireframes.
09 — Final screens
Key screens with decisions and trade-offs
I'm going deepest on the loan flow — the primary revenue driver — then covering the other key surfaces.
The loan flow is the most important surface on the platform — it directly drives Zyeero's primary revenue through referral commissions. It is also the highest-anxiety moment for students.
10 — Design trade-offs
What I chose not to build — and why
Good product design isn't about making everything perfect. It's about making deliberate trade-offs and being honest about what was sacrificed.
| Decision | Gained | Sacrificed | Mitigation |
|---|---|---|---|
| 3 loan offers instead of 12 | Reduced cognitive overload, higher completion likelihood, cleaner experience | Power users who want to compare all available options lose easy access | "View all options" CTA preserves full access without forcing complexity on everyone |
| Minimal dashboard information density | Reduced overwhelm on the most-visited screen, clear next actions | Users who want all data at a glance must click through to detail pages | Prominent "See Your Details" CTAs on every widget make depth accessible on demand |
| No loan comparison tool | Simpler experience, faster decision-making, less analysis paralysis | Students can't run side-by-side comparisons between loan products | Accepted trade-off in V1. Identified as a Phase 2 feature for returning users |
| Breadth of platform scope | Complete end-to-end journey — Zyeero's primary differentiator vs. competitors | Each individual section is less deep than a dedicated single-purpose tool | Focused depth on the loan flow (primary revenue) and dashboard (retention) |
| Light mode only (no dark mode) | Higher trust signals for financial workflows — research showed dark interfaces felt less trustworthy to the target demographic | Users who prefer dark mode have no alternative | Accepted trade-off in V1. Dark mode identified for future roadmap |
11 — Visual identity
A design system built on trust and aspiration
Every visual decision was grounded in the emotional context of the users — students making one of the biggest decisions of their lives.
Colour rationale — the exploration before the decision
Purple was chosen because it carries three emotional signals simultaneously: richness (aspiration), wealth (financial credibility), and trust.
Typography system
Display / Headings — geometric, modern letterforms signal clarity and precision.
Poppins / Epilogue — approachable, warm, legible at every size.
Body / UI text — rounded letterforms reduce the clinical feel common on financial platforms.
12 — Validation
What we learned from showing the designs to real students
After completing the initial high-fidelity screens, I ran informal walkthroughs with 5 students — sharing screen while walking them through the loan flow, dashboard, and university exploration.
A note on metrics: the founders ran cohort testing but I do not have access to the quantitative results. I am presenting the qualitative validation I personally conducted — which is what I can speak to with honesty and precision in any interview.
13 — What's next
Identified gaps and the Phase 2 roadmap
14 — Reflection
What I would do differently
Designing Zyeero was the first time I understood the difference between designing for tasks and designing for people. The task was "help students apply to universities." The reality was "help a 21-year-old from Pune feel less alone while making the biggest decision of their life."
If I were starting this project today, I would invest more in the loan flow's edge cases — specifically: what happens when a student's documents are rejected? The happy path is well-designed. The failure paths aren't.
I would also instrument the product from day one. In future projects, I want to define success metrics before the first wireframe.
Finally — my background in biotechnology at IIT KGP trains you to think in systems, identify second-order effects, and distinguish correlation from causation. The reframe moment was the same intellectual move as redefining a research hypothesis when early data doesn't explain the phenomenon you're observing.