Overview
Zayid Persada rents cars and motorcycles in Jember. Before this project, they managed everything through WhatsApp messages and Excel files. Bookings, payments, vehicle availability — all tracked manually. It worked until it didn't.
They needed two things: a public website where customers could browse vehicles and contact them, and a backoffice system to manage inventory, bookings, and transactions. Not a full booking engine with online payments — they wanted to keep the personal touch. Just a way to organize the chaos.
I built both as a single Laravel application. The frontend is a simple company profile with a vehicle catalog. The backoffice is where the real work happens — tracking which vehicles are available, who's renting what, when they're due back, payment status. Basic CRUD operations, but it replaced hours of manual work.
Client
Zayid Persada is a small rental business in East Java. Family-run, maybe a dozen vehicles total. They're not trying to compete with the big apps. They serve locals who prefer dealing with people they know.
The owner was skeptical about software at first. He'd seen other businesses spend money on systems that never got used. I had to prove it would actually make his life easier, not add complexity.
Features
Public website shows available vehicles with photos, specs, and daily rates. Contact form and WhatsApp integration for inquiries. Nothing fancy — just enough to look professional and give customers the info they need.
Backoffice has vehicle management (add, edit, archive), booking tracking (who, what, when, status), and transaction records (payments, deposits, penalties). Simple dashboard shows what's rented, what's available, what's overdue.
User roles for staff — admin can do everything, operators can manage bookings but not edit pricing or delete records. Activity logs track who changed what, because trust but verify.
Tech Stack
Laravel for the backend and admin panel. Blade templates for the frontend because it's simple and doesn't need a separate build process. MySQL for data storage. Bootstrap for the UI — not pretty, but functional and familiar to the client.
Laravel's built-in auth for user management. Intervention Image for handling vehicle photos. No fancy deployment — just a shared hosting setup with cPanel. They didn't need more.
My Role
Full-stack developer. I designed the database schema, built the backend logic, created the admin interface, and put together the public website. The client provided vehicle photos and pricing — I handled everything else.
The hardest part was explaining how the system worked without overwhelming them. I built a simple workflow: add vehicle → create booking → mark as returned → record payment. Trained the staff in person, wrote a short manual, and made myself available for questions.
They've been using it for over a year now. The owner told me it cut his admin time in half. That's the metric that matters.