KSAFE SDN BHD

Run on Google Forms and a lot of copy and paste

KSAFE runs safety training courses. Before we built anything, the whole operation lived in Google Forms and Excel. Someone collected bookings through a form, copied the responses into a spreadsheet by hand, checked payments against bank transfers one at a time, then sent out confirmations and certificates manually. It worked, in the way manual things work right up until they do not. The founder was spending around three hours a day just moving information from one place to another, and double bookings were a constant risk because nothing checked availability in real time.

No system to replace, which is its own kind of hard

Anatta and Hopedwell had a broken system to rebuild. KSAFE had no system at all, just habits. That sounds easier, but it is not, because every unwritten rule living in someone head has to be turned into something the software can enforce. How seats are counted. What happens when a company sponsors a group. How an HRDC government-funded booking differs from someone paying for themselves. All of that had to be pinned down before a single screen made sense.

What we built

A custom Laravel and React platform that took the entire booking and admin process off spreadsheets:

• • A public booking flow that walks a customer from programme to course to location to the exact session, checking seat availability as they go so two people cannot take the last place
• • Three kinds of booking handled properly: individuals paying for themselves, companies sponsoring staff, and HRDC government-funded training
• • Online payment through ToyyibPay with FPX and card, replacing the manual checking of bank transfers
• • An HRDC workflow with its own approval, rejection, cancellation and refund steps, because government-funded bookings follow different rules
• • Digital certificates with a public verification page, so a certificate can be checked by IC number, including by tapping an NFC tag
• • A registration back office with search and filters across participants, companies and courses, with receipts and confirmation emails sent automatically
• • A sales dashboard showing revenue by course, by date range and by sponsorship type, and an audit log of every change

The quiet automation

Most of what made the daily three hours disappear is work the client never sees. Confirmation emails, admin alerts, HRDC status updates and payment links all go out as background jobs that retry themselves if something hiccups. Payments reconcile against ToyyibPay instead of a person reading a bank statement. The booking page counts seats for itself. The founder went from data entry clerk back to running the business.

Where it stands now

KSAFE books courses, takes payment, issues certificates and reports on its own sales from one system instead of a stack of forms and spreadsheets. The daily admin that used to eat three hours now takes a fraction of that, double bookings are gone because the software will not allow them, and a certificate can be verified by anyone in seconds. The business finally runs on software built for it, rather than on borrowed tools bent to fit.

More case studies