Gradwayte

Inspiration

Gradwayte was born from a painfully real problem. Applying to universities means juggling 5 to 15 portals, different emails and passwords, scattered deadlines, scholarship forms, and cost calculations across countries. There is no single system that helps students see the full picture.

As international applicants, we experienced the chaos firsthand. Spreadsheets became messy. Funding comparisons were unclear. CGPA conversions were confusing. We realized students were making life-changing decisions based on fragmented information.

Gradwayte exists to replace stress with structure and guesswork with data.

What it does

Gradwayte is a centralized university application command center.

It allows students to:

Track multiple university applications in one dashboard
Manage per-school checklists and deadlines
Log scholarships and funding details
Calculate tuition and total program costs
Convert CGPA across grading scales
Compare universities side by side

The core innovation is the ROI Score, a weighted decision model:

[ ROI = (0.35F) + (0.30R) + (0.20C) + (0.15P) ]

Where:

(F) = Funding Score
(R) = Ranking Score
(C) = Cost Efficiency
(P) = Program Fit

Instead of asking “Which school feels better?”, students can now ask, “Which school makes more sense?”

How we built it

Gradwayte was built using:

Next.js + TypeScript for a scalable full-stack foundation
Tailwind CSS + shadcn/ui for a clean, accessible UI
PostgreSQL + Prisma for structured relational data
Secure credential encryption (AES-256) for portal storage
Multi-currency logic + CGPA conversion engine for global applicants

We structured the system around modular components: Applications, Checklists, Scholarships, Cost Tracking, and the Comparison Dashboard.

Challenges we ran into

Designing a fair ROI scoring model without oversimplifying decision-making
Handling multi-currency cost normalization
Securely storing sensitive portal credentials
Avoiding feature overload while maintaining MVP clarity
Creating a comparison system that feels helpful, not robotic

Balancing simplicity with depth was the hardest part.

Accomplishments that we're proud of

Turning a chaotic application process into a structured workflow
Building a comparison engine that produces real, actionable insights
Designing for international students from day one
Creating a scalable architecture that can support 100K+ users
Transforming spreadsheets into a product with real decision intelligence

What we learned

Students do not just need organization. They need clarity.
Financial transparency changes decision confidence dramatically.
Simplicity is harder to design than complexity.
Data-backed recommendations increase trust.
Building for global users requires flexibility in grading systems, currency, and funding structures.