Detailed case study · Operations · Event rentals

Bibow Playground booking platform

I built the booking website and admin panel for Bibow Playground Rentals, a mobile playground rental business in Valenzuela, Metro Manila, and Bulacan. Customers book from their phone; the team verifies payment and confirms the date from one place.

Role
Full-stack web developer
Period
September–November 2026
Status
Live
Bibow admin overview showing new requests, confirmed bookings, and recent bookings
Bibow admin overview showing new requests, confirmed bookings, and recent bookings

01 / The problem

Bookings lived in chat threads

Requests arrived through Messenger. Dates, venue details, and payment screenshots were scattered across conversations, and customers could not see which days were open.

The business also had no website that Google knew about. Searches for the brand found its Facebook and Instagram pages but not a place to book.

02 / The approach

Design for a phone, manual payments, and a non-technical team

Most customers book from a phone, often inside Messenger. I kept the form to five short steps, let customers pay now or later through a private booking link, and shrank photos on the device before upload.

Payments are GCash and BDO transfers, so the flow centers on a receipt screenshot that staff review before confirming. Each change shipped with a short illustrated guide for the team.

03 / The solution

A booking form, a payment-proof flow, and an admin panel

Customers choose a package, an open date and time, their contact details, and an inflatable, then optionally attach up to five venue photos. They get a booking reference, a private link, and a booking image to keep. Quotes include promos automatically and flag transport and stair fees as quoted separately.

Staff see requests on a dashboard and in calendar, table, and Kanban views. They open a booking, review the venue photos and payment proof, verify or reject the payment, and move the booking to Confirmed. Inventory photos, promotions, turnaround time, and payment details are managed in the same panel.

It runs as one Cloudflare deployment: a Svelte 5 app and a Hono API, with D1 for data and R2 for images. A daily job expires unpaid requests, venue photos are deleted 30 days after the event, and booking links use hashed tokens.

04 / What changed

One booking record, live on its own domain

The site is live at bibow-playground.com. Each booking now holds the request, venue photos, and payment proof in one place, and customers see their status on the same link they booked with.

After the owner tested the page, I added an elevator handling fee, a selectable end time, a clearer availability calendar, and a fix for the verification step that had blocked bookings on the new domain. I also wrote an owner checklist for Google Search Console and Business Profile. I have not included booking-volume or revenue figures because I do not have verified numbers.

Selected evidence

Booking and admin screens

Screenshots are from a test booking with sample photos. Customer screens are shown as they appear on a phone.

A useful place to start

What is slowing your
business down?

Tell me about the workflow, the friction, and what a better version would look like.

Schedule a call