01Work02Services03About04Writing05Contact

amansonwani43@gmail.com

← All work

Resource Management System

A system that gives skilled but under-utilised students real project work — matching people to resources the way a good manager would.

Role

Full-stack developer & researcher — end-to-end: UX, schema, APIs, frontend, and co-author of the published paper.

Timeline

3 months · Solo build

Stack
  • Next.js
  • Strapi
  • PostgreSQL
  • TailwindCSS
  • REST APIs
Year

2024

The problem

Institutions sit on two wasted assets: idle resources (labs, equipment, project slots) and skilled students who aren't currently engaged with them. Nobody had visibility of either side, so allocation happened through personal contacts.

The result was predictable — the same small group got every opportunity while capable students stayed invisible, and expensive resources sat unused between semesters.

My approach

(01)

Treat it as a matching problem

Framed the system around skills and availability as first-class data — every student profile and every resource carries structured, filterable attributes.

(02)

Strapi for speed, Postgres for truth

Used Strapi as the admin layer so non-technical staff could manage resources without a developer, backed by PostgreSQL for relational integrity.

(03)

Design for the coordinator

The key screen isn't the student's — it's the coordinator's allocation view: see demand, see idle capacity, resolve them in one interface.

The solution

A platform where students maintain living skill profiles, coordinators publish resources and project openings, and the system surfaces matches both ways — students discover opportunities, coordinators discover people.

Utilisation reporting made the invisible visible: which resources idle, which skills go unused, and where engagement actually happens.

The outcome

1

Research paper published

2-way

Skill ↔ resource matching

100%

Allocation moved off spreadsheets

Revedor SaaS Products