04Web · Foreign consultancy platform

Admivo

Study-abroad consultancy product — destination discovery, application workflows, and admin surfaces ops can run without engineering help.

Open admivo.in All case studies

Admivo was designed and engineered by Yuvraj Singh, Forward Deployed Engineer.

Admivo product — study destination quiz hero and university destination cards — Product interface · Admivo

Role: Full-stack engineer — document and application workflows, REST APIs, and the admin surfaces operations staff run
Timeline: Live at admivo.in. No engagement dates are published for this build, so none are stated here.
Stack: React.jsNext.jsNode.jsExpress.jsPostgreSQL

01Context

The problem

Admivo is a foreign-education consultancy platform. A student picks a destination, gets onboarded, and then moves through an application that is mostly documents — collected, checked, and chased until the file is complete. The people running that day to day are counsellors and operations staff rather than engineers, so the admin side is the product as much as the student-facing side is.

Constraints(04)

An application is a long-lived record whose student, destination, stage, and documents have to stay consistent.
Documents arrive out of order and get corrected, so the record has to tolerate being edited for months.
Operations staff must be able to move an application forward themselves, without engineering help.
The first thing a prospective student does is explore destinations, before anyone is ready to take an enquiry.

02Scope

What was built

01
Guided destination quiz and student onboarding
02
Document pipelines for application status
03
Admin surfaces designed for operations staff

03Architecture

The system

React.js and Next.js modules over Node.js and Express.js REST APIs, with PostgreSQL holding the application records. Students, destinations, applications, and documents are related rows rather than nested blobs, because every one of them is read from more than one direction. The guided destination quiz is the front door: it captures what a student is looking for as structured answers that seed the application record. Admin surfaces read and write those same records, so operations staff change the thing itself rather than asking for it to be changed.

PostgreSQL-backed application records
Scalable REST APIs for document workflows
React/Next modules composed for ops dashboards

04Decisions

What was chosen, and what it beat

A decision with no rejected option is a feature list. Each one below carries the alternative that was actually on the table and the reason it lost.

Decision 01 / 03Admivo
Keep students, destinations, applications, and documents in PostgreSQL as related records.
Rejected
A schemaless document store holding each application as one nested blob.
Why this won
An application is read from several directions — by student, by destination, by stage, by which document is still missing — and those reads are the admin dashboard. Relational rows keep them cheap and stop a document from hanging off an application that no longer exists. The flexible-shape argument for a document store applies to changing content, not to case records operations query all day.
Decision 02 / 03Admivo
Put a guided destination quiz at the front door, ahead of any enquiry.
Rejected
A generic contact form that hands every visitor to a counsellor to qualify by hand.
Why this won
Most first visits are exploration rather than intent, and counsellor time is the scarce resource. Structured quiz answers let a student self-serve destination discovery and arrive as a record with a stated preference, which then starts the application instead of sitting in an inbox waiting to be re-typed.
Decision 03 / 03Admivo
Ship admin surfaces operations staff run themselves.
Rejected
Leaving application and document state to be corrected by an engineer on request.
Why this won
Document workflows generate a constant stream of small corrections: a file re-uploaded, a stage moved back, a detail fixed. Routing those through engineering makes throughput a function of developer availability, and it puts the people who understand the process furthest from the record. The dashboards exist so the process owner owns the data too.

05Status

Where it stands

Live at admivo.in.
Students self-serve destination discovery through the guided quiz and onboarding flow.
Applications and document pipelines are tracked on PostgreSQL-backed records behind REST APIs.
Operations staff run application and document workflows without engineering help.
Related but separate from the platform work: 1st place at HackMivo, the hackathon conducted by Admivo.

See it running at admivo.in

06Questions

Admivo, answered

What is Admivo?

Admivo is a foreign-education consultancy platform. Students find a destination through a guided quiz, get onboarded, and move through an application made largely of documents, while counsellors and operations staff track and progress each case from admin dashboards. It is live at admivo.in.

Who developed Admivo?

Yuvraj Singh developed Admivo. He built the student onboarding and document workflows, the PostgreSQL-backed application records, the REST APIs over them, the admin dashboards operations staff run without engineering help, and the responsive React.js and Next.js frontend modules. He separately won 1st place at HackMivo, the hackathon conducted by Admivo.

What technologies does Admivo use?

Admivo is built with React.js and Next.js on the front end, Node.js and Express.js REST APIs, and PostgreSQL for application and document records. The relational store is deliberate: an application is long-lived, and its student, destination, documents, and stage have to stay consistent while it is edited over months. No AI systems are claimed for Admivo — the AI work in this portfolio is on Potato Bazaar.

What problem does Admivo solve?

A study-abroad application is a slow, document-heavy case that several people touch: the student uploading files, the counsellor advising, and the operations staff checking what is still missing. Admivo turns destination discovery into a guided quiz a student can self-serve, keeps each application as a record the whole team reads from one place, and gives operations the admin surfaces to move it forward themselves.

Related work