Search around the learner's actual subject, grade and support need.
Helping you find your way.
South African tutoring, matched.
BUZA is being developed to make it easier for learners and families to find the right academic support, compare tutoring options, book around real schedules and move through a clear learning journey.
- 01DiscoverSearch by subject, grade, tutor or location.●
- 02ChooseCompare profiles and session formats.●
- 03ScheduleCheck availability and avoid timetable clashes.●
- 04LearnMove into the booked lesson journey.◌
- 05Close outFeedback completes the prototype session cycle.●
UI direction shown here is based on the current BUZA application prototype, not a promise of public availability.
Finding support should not create another admin problem.
The prototype is built around a practical idea: tutoring is easier when discovery, availability, bookings and the lesson timetable are part of the same journey.
Rather than treating a tutor listing as the end product, BUZA is exploring how the pieces around a lesson can fit together for both the learner and the tutor.
Availability and existing commitments matter before a booking is made.
A lesson is a journey from request to confirmation, timetable, session and feedback.
There is already a product skeleton behind the idea.
These are prototype workflows currently represented in the BUZA demo. They are not yet production services.
Find tutors
Search and filter around tutor name, subject, grade and location.
Compare session options
Tutor profiles can present different lesson formats, durations and session types.
Clash-aware booking
The demo checks tutor availability and existing learner or tutor timetable commitments.
One-to-one + group learning
The prototype supports individual booking flows alongside tutor-created group classes.
Personal timetables
Learners and tutors see different calendar views built around their own bookings and teaching commitments.
Notifications + lesson lifecycle
Requests, responses, timetable links, a session shell and feedback are already modelled in the demo.
Learner journey. Tutor workflow.
The current prototype does not treat tutors as static listings. Both roles have actions, schedules and responsibilities.
Find support and keep track of it.
- Discover tutors by learning need
- Compare tutoring and session options
- Request one-to-one bookings
- Join available group sessions
- See booked learning in a personal timetable
- Receive updates and submit lesson feedback
Manage teaching as a real schedule.
- Set available teaching windows
- Block unavailable time
- Create advertised group classes
- Accept or decline booking requests
- See teaching commitments in a timetable
- Move a demo lesson through start, end and feedback
From “I need help” to “lesson completed.”
- 01Find
Start with the learner's subject, grade or academic need.
- 02Choose
Understand the tutor and the kind of session being offered.
- 03Book
Select a time that works without creating a timetable clash.
- 04Learn
Use the booked session as the centre of the learning interaction.
- 05Close out
Record feedback and complete the lesson cycle cleanly.
A working prototype is not yet a public tutoring service.
BUZA still needs production infrastructure, operational rules and safeguarding before learners, families or tutors should rely on it as a live marketplace.
The current demo stores its working state locally in the browser and uses mock users, tutors, bookings and lesson data. The public Veni Publishing site will not present those demo profiles, ratings or prices as real.
Before BUZA can launch, the real service still needs:
- 01Production accounts + authenticationReal learner, parent and tutor identity flows.
- 02Tutor verificationCredential, identity and suitability processes that are more than a demo badge.
- 03Persistent backend infrastructureA real database and cross-device state rather than browser-local demo storage.
- 04Payments, payouts + disputesProduction financial workflows and clear rules for cancellations, refunds and resolution.
- 05Real lesson technologyVideo/audio, chat, screen sharing and resource tools still require live integration.
- 06Safeguarding + privacyChild-safe operational, data and communication policies must be locked before public use.