B2B PLATFORM · EDUCATION RECRUITMENT · 2025—26
URM ENROLL Agent Portal
One record, from first inquiry to commission paid.
01 / Context
The problem
Education recruitment is handled by agents, counselors, universities and a finance team who each see a different part of the same student. When those parts live in separate tools, nobody can say what a student is worth or what an agent is owed.
02 / Response
The product response
A multi-role operations portal on one record: agents source and nurture leads, counselors convert them through admissions, administrators run the catalog, contracts and finance. A public marketing site and agent application funnel feed the same pipeline.
03 / Contribution
My role
Technical Co-Founder & Full-Stack Developer at URM ENROLL LTD. Architecture and implementation of the agent portal, the commission engine and the operations surface. The repository is private.
04 / Architecture
How the pieces connect
- 01Express server-rendered portal
- 02Prisma domain model
- 03PostgreSQL operational data
- 04Stripe payments and payouts
05 / Execution
The engineering challenge
Four roles need four different views of one lifecycle without seeing each other’s data, and every commission has to stay explainable months later. Access control, audit trails and the commission rules are all part of the same design problem.
06 / Result
Outcomes & perspective
The portal is deployed and serves the agent partner programme. No independently verified adoption, revenue or performance figures are published here.
07 / Reflection
A lesson from the work
Money makes correctness visible. A commission that cannot be traced back through the record that earned it is a defect, however good the interface looks.
08 / Evidence
Evidence & scope
Source: private repository README and source tree, inspected September 2026. The repository stays private; no code, data or credentials are published here.