ScholarSync

Inspiration

Honestly, ScholarSync started with a problem we faced ourselves.

Whenever we looked for scholarships, finding the right website was already a struggle. And even after finding one, the application process could be so long and tiring that we sometimes just gave up halfway.

To see if it was only us, we asked "21 of our friends" about their experience. "15 of them said they had faced similar difficulties."

That frustrated us even more was spending around "10 minutes filling out an application", only to find out at the very end that we weren't eligible because of something like our income, location, or another requirement.

That made us think: Why can't students know these things before they spend their time applying?

That simple question became the reason we started "ScholarSync."

We wanted to make the scholarship journey less confusing and help students understand what they are eligible for, what they need, and what they should do next.

What it does

ScholarSync is designed to make the scholarship journey "simpler from the very beginning".

Instead of making students search through different websites, fill out long forms, and only discover problems at the end, ScholarSync brings the important information together in one place.

It helps students "discover relevant scholarships, understand why they are eligible or not, see the requirements and documents they need, get guidance on missing documents, and make the application process easier"

Our idea is simple: "Don't just show students a scholarship. Show them what they need to do to reach it."

How we built it

We started with the problem before thinking about the technology.

First, we spoke to our friends and tried to understand where students actually struggle. From those conversations, we broke the scholarship journey into different problems - finding opportunities, checking eligibility, understanding missing requirements, and applying.

We then turned those problems into the core features of ScholarSync.

Our planned prototype brings these features together through a "student profile, scholarship database, eligibility matching system, document guidance, and a simpler application flow."

For us, the most important part wasn't just building something that looks good. We wanted every feature to have a reason behind it - "something that solves a frustration we actually experienced."

Challenges we ran into

One of our biggest challenges was actually "figuring out what the real problem was".

At first, we thought students simply needed a website where they could find scholarships. But after talking to people and thinking about our own experiences, we realised the problem was much bigger.

Students struggle with eligibility, documents, complicated applications, and sometimes don't even know what to do after finding a scholarship.

Another challenge was deciding "what we should solve first". There are so many things we could add, but with limited time, we had to focus on the problems that mattered most.

And honestly, trying to turn a real-life frustration into something that can actually be built was a challenge on its own.

But that process helped us understand our idea much better.

Accomplishments that we're proud of

What we're most proud of isn't just having an idea - it's that we started with a problem we personally experienced and actually took the time to understand it.

We spoke to "21 students", found that "15 of them faced similar difficulties", identified the major gaps in the scholarship journey, and turned those problems into a clear solution.

We also managed to bring our ideas together as a team and shape them into "ScholarSync".

For us, seeing a simple frustration turn into an actual project idea is something we're genuinely proud of.

We know there is still a lot more to build, but "this is where our journey begins."

What we learned

This project taught us that sometimes a problem looks small when you experience it alone, but it can actually affect many more people.

We started by thinking,"Finding scholarships is difficult"

But as we explored the problem, we realised that finding one is only the beginning. "Eligibility, documents, guidance, and the application process can all become barriers."

We also learned that building a solution isn't just about adding as many features as possible. Every feature should have a purpose and should solve a real problem.

Most importantly, we learned how to take something that frustrated us personally and turn it into an idea that could potentially help other students too.