RDS CRM

Raja Driving School runs driving lessons and handles the RTO paperwork around them: learner's licences, driving licences, renewals and commercial badges. That paperwork lived in registers and spreadsheets, with no single view of who owed what or which application was stuck. The school needed one system for intake, applications, payments, invoicing and reporting.

The business is five workflows running in parallel, each with its own status lifecycle: learner's licences, driving licences, renewals, badge applications and training. One customer can be in several at once. Payments can apply to any of them, so balances and invoices had to reconcile across every service, not a single order table.

One Next.js app: server-rendered dashboard pages and an API talking to a single MySQL database, with no separate backend service. Two independent login systems run side by side, one for staff with role and per-module permissions and one for the customer portal, so a problem in one cannot reach the other.

Beyond the core CRM (customers, applications, renewals, training, payments, invoices, expenses and reports), a full learning platform. Staff author courses as a sequence of videos and quiz checkpoints. Uploaded video is transcoded on the server to encrypted streaming and served through short-lived signed links, never a direct file URL. A server-side unlock engine decides what a learner can see next, so there is no client-side rule to bypass. Finishing a course issues a certificate PDF with a QR code that opens a public page where anyone can confirm it is genuine.

Live at crm.rajadrivingschool.com, with the learning module running and its first course published.