Work / 07 Education finance company
An education finance company helped students fund study abroad through paperwork and phone calls. We built a product website, a student application, and an admin dashboard so applications move from first question to decision in one flow.
- Client
- Education finance company
- Engagement
- 6 months
- Delivered
- 2024
ServicesApplied AI Applications
- Time to complete an application45 to 22 min
- Time from submission to decision5 to 3 days
- Applications completed once started58% to 81%
The brief
What they came to us with.
Students applying for finance had to gather documents, call for updates and bring a co-signer into the process by hand. Many gave up before finishing.
The company wanted a clear public website, an application students could finish on their own, and a dashboard where its team could see every application and move it forward.
Constraints
- Sign-in by phone number and one-time code
- A co-signer added during the application
- Every status change visible to the student
- The team sees volumes and queues each day
Before and after
What actually changed.
The same finance product, with the paperwork moved online.
What we did
How an application moves.
- 01
Make the application something students finish
Students sign in with their phone number and a one-time code, then complete the application in short steps. A co-signer is invited from inside the flow, and progress is saved so nobody starts again.
Fig. 1 The student’s journey, step by stepDiagram - 02
Give the team one place to work
The admin dashboard shows the last 24 hours at a glance, then lists every application. Staff change a status, leave a comment, and the student sees the update.
Fig. 2 The admin dashboard, simplifiedDiagram - 03
Three surfaces, one platform
The website, the student application and the dashboard share one backend, so a change made by the team appears for the student straight away. New products and countries are added as data.
Fig. 3 How the three parts fit togetherDiagram
How it ran
How the work was paced.
The application came first, because it decided whether anyone finished.
Journey design
Map the student and team journeys, design the screens.
Application and sign-in
Phone sign-in, application steps, co-signer.
Website and dashboard
Product website and admin dashboard.
Testing and launch
Test with real applicants, document, train the team.
Outcome
What it changed.
Measured on applications before and after launch.
Time to complete an application
45 to 22 min
Before45 minAfter22 min
How measured: Median time from starting an application to submitting it.
Time from submission to decision
5 to 3 days
Before5 daysAfter3 days
How measured: Median working days from a complete submission to a decision.
Applications completed once started
58% to 81%
Before58%After81%
How measured: Share of started applications that were submitted.
Built with
ReactWeb interfaces
Node.jsServices and APIs
What we would tell the next team
- Saving progress at every step did more for completion than any redesign of the form.
- Showing students the status removed most of the calls we had expected to handle.
- A shared backend meant the team’s comments reached students without extra work.
More work
Contact
Book a free 15-minute call to talk through what you are working on.
How we connect
- 01Book a short call
Choose a time that works for you on our calendar.
- 02Discovery call
A short call to understand the problem, the people and the constraints.
- 03Final scope and kickoff
We send a clear scope and cost. Once you agree, we start.
Office
393, WeWork Vijohn Tower, 3rd FloorUdhyog Vihar Phase-4, GurugramHaryana 122016
Follow