[ 01 ]
Public
- Courses & fees
- Find Your Course
- Fleet
- Instructors
- Locations
- RTSA & licensing
- FAQs
- Contact / WhatsApp
Roadstar Driving School · Driving school · Emmasdale and Thornpark, Lusaka
From Facebook interest to one enrolment front door.
Driving school digital platform · Strategy · UX · Full-stack development
Project at a glance
Who it is for
- Client
- Roadstar Driving School
- Sector
- Driving school · Emmasdale and Thornpark, Lusaka
- Delivered
- Public website, Staff CMS and Platform foundation
Public
Public
- Courses & fees
- Find Your Course
- Fleet
Staff
Staff
- Courses
- Fleet
- Instructors
Ready later
Ready later
- Students
- Payments & credits
- Lesson scheduling
Measured
SAVT 4.5 / 12 before the front door
Diagnostic
The challenge
What was getting in the way
01
- Enrolment
Find Your Course
Before
Every beginner chat restarted the same diagnosis: which class, which package, which branch.
Now
Hotter enquiries, and a clearer brief for reception.
02
- Pricing
School fees vs RTSA
Before
People asked for a total cost and mixed Roadstar tuition with RTSA and medical fees.
Now
An honest tuition-plus-statutory story, without a fake all-in price.
03
- Trust
One number, two branches
Before
Several phone numbers were in circulation, and Thornpark was known by area more than by a pin.
Now
A contact block that can be trusted when the production domain goes live.
04
- Staff CMS
Prices the owner can change
Before
Changing a fee meant editing Facebook posts, correcting chats, and hoping memory matched.
Now
One link can answer how much and which package, once the owner confirms the ladder.
The solution
One platform. Two experiences live. More built underneath.
[ 02 ]
Staff
- Courses
- Fleet
- Instructors
- Branches
- RTSA content
- FAQs
- Publish / approve
[ 03 ]
Ready later
- Students
- Payments & credits
- Lesson scheduling
- Practice papers
“Roadstar did not only need a nicer website. They needed one place that answers the enrolment questions Facebook never could — and a system that can grow into payments, lessons, and learning.”
Method
How we approached the project
The interesting part wasn't building pages — it was figuring out that Roadstar needed a phased platform, not a static brochure.
[ 01 ]
Investigate
Stakeholders · Facebook · competitors · RTSA · journeys
[ 02 ]
Diagnose
Seven revenue leaks · SAVT · where commitment breaks
[ 03 ]
Architect
Public front door first · backend owns publish, payment, and schedule truth
[ 04 ]
Build
Next.js site and CMS · Django domain APIs
[ 05 ]
Ship
Live demo at roadstar.jabulani.digital
Behind the build
Research, structure, and build notes
Open a section for the investigation, the structure, or the build notes.
Discovery and research
02
How we investigated
Sources: owner conversation, Facebook and competitor audit, RTSA fee-pathway research, and journey mapping. There was no owned website, so competitors could publish prices Roadstar could only explain in chat. Seven revenue leaks sat on that gap: no dated price matrix, no package-fit guidance, demand landing on Facebook, fragmented contact, unorganised trust proof, unstructured enquiries, and an unclear professional offer. Staff time went to repeating basics. The owner already needed payments, credits, scheduling, and learning, so Phase 1 had to be the front door of a platform, not a dead-end brochure. The course ladder was seeded as a draft. Specific fees stay out of this case study until the owner confirms them.
Architecture and design decisions
Capability
Technology & role
Strategy · UX · Full-stack development
- Next.js
- TypeScript
- Tailwind
- Django
- Postgres
- Docker
Implementation
Scope & limits
Implemented: public site, Find Your Course, structured leads and enquire, staff CMS, JWT roles, and platform APIs for students, commerce, scheduling, and learning. Not in this phase: online checkout, student portal screens, finance and scheduler calendars, learning screens, WhatsApp broadcast, or a native app. Installment policy is still owner-confirmed. Thornpark’s pin is still soft.
Have a similar problem in your organisation?
Whether you need a better public website, clearer communication, or a digital system that supports how the organisation works, let's discuss what is not working and what a practical solution could look like.