Building Edu4u Agents — a custom affiliate CRM replacing WhatsApp chaos

A custom-built affiliate CRM for a UK student recruitment agency — three role surfaces (agent mobile, consultant desktop, admin), MLM referral tree, and a commission engine that replaces spreadsheets and WhatsApp groups with a single source of truth.

The Challenge

Edu4u recruits students for UK universities through a field network of agents. Before this build, the agent operation ran on the combination that kills most scale-up attempts: spreadsheets and WhatsApp groups.

• Commissions were calculated manually in Excel. No audit trail, no version history — just whatever was in the sheet that month.
• Sales materials, PDFs, graphics and links were all pushed through WhatsApp. Links expired, files got buried in chat, agents asked the same questions repeatedly.
• No structured way to inform agents when a commission was paid out. Every payout triggered a round of individual WhatsApp messages.
• Zero visibility for agents into their own pipeline — no view of earnings, no rank, no sense of how close they were to the next tier.
• The result: agents lost motivation, recruiting slowed, and the network stopped growing.

Why off-the-shelf wouldn't work

Edu4u had already looked at the usual suspects — HubSpot, Pipedrive, generic affiliate platforms. None of them fit. The business logic was too specific:

• MLM-style referral tree. Agents earn commission not only on their own students, but also on students brought in by agents they invited. Off-the-shelf CRMs don't model multi-level referrals.
• Tier engine. Commission rates depend on an agent's current tier, which changes with performance. Tiers must affect future earnings without rewriting past ones.
• 2-tranche payouts. Commissions are paid in two stages, tied to the student's lifecycle milestones. No affiliate SaaS models this out of the box.
• Commission snapshotting. Once a commission is locked in, later rule changes must not retroactively rewrite what agents are owed. Every payout needs an immutable record.
• Three role surfaces with real separation. Agents need a mobile app for the field. Consultants need a desktop dashboard for their region. Admins need full control. Each role sees a different product.

Stitching this together in Zapier would have been fragile to run and impossible to audit. We built it from scratch.

What we built

The app ships three distinct UIs from the same backend: a mobile-first agent app, a desktop dashboard for consultants, and a full admin panel. Across them, ~25 routes cover every flow from student intake to commission payout.

Motivation built in: quests, leaderboard, resource hub

Agents need three things to keep recruiting: a clear goal, visibility of where they stand among others, and frictionless access to the materials they need to close. The app delivers all three as a single experience:

• Quests — time-boxed goals tied to concrete outcomes ("recruit 3 students this week"). No more vague pep talks.
• Live leaderboard — visible rank among peers. Social pressure replaces the silent spreadsheet.
• Resource hub — central store of PDFs, graphics, sales scripts and onboarding materials. Replaces the WhatsApp chaos where links died in chat.

Commission engine with snapshotting

Every commission is calculated against the tier rules in force at the moment it's earned. If Edu4u later changes the rate structure, historical commissions stay locked to the rules that applied when they were generated. This protects both sides: agents know exactly what they were promised, Edu4u can evolve the rules without rewriting history. Payouts happen in two tranches tied to the student's lifecycle milestones.

MLM referral tree

The network expands virally: every agent can invite others, and earns a slice of commission from every student those agents bring in. The app visualises the whole tree — useful for agents (to see their downline) and for admins (to spot where the network is thriving and where it's stuck). Every personalised invite link carries attribution straight into the tree.

Admin panel

One operational surface replaces the spreadsheet-and-WhatsApp mess: network metrics, per-agent performance, commission approvals, quest configuration, payout history, and audit logs. Admins see the whole system; consultants see their region; agents see themselves. Clean role boundaries, no cross-leakage.

Under the hood

For the technical readers: Next.js 15 + React 19, Supabase as the full-stack data and auth layer with row-level security tuned per role, a typed database layer, migrations under version control, rate limiting and CSP on the perimeter, containerised and running on a Hetzner host. Three role surfaces share one model; commission logic lives behind a pure, tested tier engine with immutable payout snapshots. End-to-end build: 3 weeks. Rollout: 1 week.

Status