The Business
KJM Rental Bike is a bicycle and e-bike rental shop in Cebu City, Philippines. They serve a mix of local residents and tourists, with peak demand on weekends and during Cebu's festival seasons — Sinulog in January, Kadaugan sa Mactan, and the summer surge between April and June when the island's coastal roads fill with cycling tourists.
Kevin, the owner, built the business from nothing. He started with four bikes, a small lot near Mactan, and a Facebook page. By 2025 he had expanded to over 30 bikes and e-bikes, a loyal base of repeat customers, and a reputation built almost entirely on word of mouth. The business was real. The infrastructure holding it together was not.
The Before Picture
Before working with Skaly, KJM was a functioning business with a real customer base. The problem wasn't demand — it was everything that happened between a customer wanting to rent a bike and Kevin actually getting paid for it.
The owner started every morning the same way: open WhatsApp, read through the overnight messages, manually check a shared Google Sheet to see what was available, reply to each inquiry individually, send a GCash payment link, then update the spreadsheet once payment came through.
On a slow day, this took 90 minutes. On a busy weekend — say, a Saturday before a Cebu marathon or a long holiday weekend — it was the entire morning. Sometimes longer.
The specific problems:
- Double bookings — two customers booking the same bike for the same slot because the spreadsheet wasn't updated in real time
- No-shows — no reminders meant customers forgot, leaving bikes sitting idle
- Lost revenue — messages that came in at night or during busy periods sometimes weren't seen until it was too late
- No customer history — every repeat customer had to re-explain who they were and what they wanted
- No real numbers — Kevin had no reliable way to know his actual revenue by service, day, or bike type
- Payment friction — sending GCash links manually meant some customers dropped off before completing payment, especially first-timers
The spreadsheet problem was the most damaging. Without real-time inventory state, the only way to prevent double bookings was for Kevin to personally handle every single transaction — which meant the business could only grow as fast as he could personally respond to messages. He was the bottleneck.
Why Generic Tools Didn't Work
Kevin had tried solutions before reaching out to Skaly. He'd looked at Calendly, Booksy, and a few tourism-focused booking platforms. None of them fit.
The generic tools had two problems. First, none of them supported GCash or Maya natively — the two payment methods his customers actually used. International platforms pushed Stripe or PayPal, which many of his customers didn't have. Any checkout that required creating a PayPal account was a checkout that got abandoned.
Second, none of the generic platforms understood the inventory model of a rental business. Booking a bike isn't like booking an appointment — it has a start date, an end date, an asset (the specific bike), and a rate that may vary by duration. A calendar tool built for service bookings doesn't map cleanly onto physical inventory with multi-day rentals.
The right tool didn't exist. So we built it.
What We Built
In 72 hours, Skaly delivered a complete booking and operations platform tailored to how KJM actually works.
Customer-facing:
- Live availability calendar — bikes and e-bikes shown in real time with availability by date range
- Booking flow completable in under 3 minutes — select bike type, select dates, choose add-ons (helmet, lock, basket), pay via GCash or Maya
- Automatic SMS confirmation immediately after payment with a booking reference number
- Reminder SMS 24 hours before rental start, reducing the mental load that leads to no-shows
Admin panel:
- Dashboard showing today's bookings, active rentals, upcoming availability, and any bikes due back
- Revenue tracking by day, week, month, and broken down by bike type and rental duration
- Customer database — every client's booking history, total spend, contact details, and notes
- Inventory view — which bikes are out, expected return time, maintenance flags
Financials:
- GCash and Maya connected natively — payments flow directly to Kevin's account with no third-party holding funds
- Invoice generation for corporate clients and tour operators who book in bulk
- Monthly revenue summary exportable as PDF for accounting
SEO and discoverability:
- Structured data markup on every page so the booking system appears in Google search results
- Page copy optimized for Cebu-specific searches like "bike rental Cebu" and "e-bike rental Mactan"
- Google Business Profile integration with real-time availability shown in Maps results
The 72-Hour Build: How It Actually Happened
Day one was scoping and design. We spent two hours with Kevin mapping every step of his current process — not the process he wished he had, but exactly what happened from the moment a customer sent a WhatsApp message to the moment a bike left the rack. Every edge case, every exception, every workaround he'd invented to deal with the spreadsheet.
By end of day one we had a complete data model, a UI flow, and a payment integration plan confirmed with GCash's developer API.
Day two was build. The booking engine, the availability logic, the admin dashboard, the SMS integration. By midnight the system was running in staging with Kevin's actual bike inventory loaded in.
Day three was Kevin. We walked him through the admin panel, let him process five test bookings himself, watched where he hesitated, adjusted the UI. By late afternoon, KJM Rental Bike's new system was live and taking real bookings.
The first real booking came in at 11:34pm that night — while Kevin was asleep.
The Numbers After 3 Months
| Metric | Before | After |
|---|---|---|
| Morning admin time | 90–120 min/day | 20 min/day |
| Double bookings per month | 4–6 | 0 |
| No-show rate | ~22% | ~11% |
| Monthly bookings | baseline | +40% |
| Revenue visibility | none | real time |
| Late-night bookings captured | ~0% | included in +40% |
The 40% increase in bookings came from two things: online discoverability (the SEO-optimized site now ranks on the first page for "bike rental Cebu" and related terms) and the fact that customers could book at 11pm without waiting for a reply. A significant share of the new bookings were from tourists who discovered KJM through Google at night and converted immediately — customers Kevin would have lost entirely under the old system.
The Mechanics Behind Each Win
Admin time down 78%: The 90-minute morning routine existed because Kevin was manually coordinating state between WhatsApp, GCash, and a spreadsheet. When those three systems are replaced by one system that handles state automatically, the morning routine becomes reading a dashboard that already has all the answers.
Zero double bookings: The spreadsheet failed because it had no concurrency protection — two people could read the same "available" status and both proceed to pay before Kevin updated it. The new system uses database-level locking: the moment a booking is in progress, that slot is reserved. No manual step, no race condition.
No-show rate halved: The intervention is simple: an SMS reminder 24 hours before. Most no-shows aren't intentional — they're the result of a booking made two weeks ago that didn't make it onto anyone's calendar. One reminder message is enough to cut that rate in half.
+40% bookings: The combination of always-on availability (booking works at 2am), discoverability (SEO), and friction reduction (GCash checkout in 3 minutes versus waiting for a manual reply) compounds. Each factor alone would move the number. Together, they produced a 40% lift in three months.
Unexpected Benefits
Two things improved that weren't in the original brief.
First, corporate and tour operator bookings. With invoice generation now built in, Kevin started accepting bulk bookings from tour operators and Cebu-based companies doing team activities. This was a customer segment he'd turned away before because the manual invoicing process was too painful. It now accounts for roughly 15% of monthly revenue.
Second, maintenance visibility. The inventory view showed Kevin — for the first time — exactly how often each bike was being rented and flagged bikes that hadn't moved in a while. He discovered two bikes that were being consistently skipped by customers (both had subtle mechanical issues he wasn't aware of). Fixing them brought two previously idle assets back into active rotation.
What Kevin Said
"Before, I was basically the booking system. Every message, every confirmation, every payment — that was me. Now I open the dashboard in the morning, see everything I need, and get on with the actual work."
"The best part is the bookings that come in at night. I wake up and there are confirmed, paid bookings I didn't do anything to get. That's new."
The Cost
The full system — booking engine, payment integration, admin dashboard, SMS notifications, SEO setup — was delivered in 72 hours. Annual cost: ₱5,499/year on the Starter plan.
Kevin's previous cost was harder to calculate, but the components were: 90 minutes of manual admin every morning, revenue lost from missed late-night messages, revenue lost from no-shows, and the untapped demand that existed but couldn't reach him because he had no online booking presence.
Conservative estimate: the system paid for itself in the first week of operation from recovered no-show revenue alone. The 40% booking increase is on top of that.
Is Your Business in the Same Situation?
KJM's situation before Skaly is common. Not just in bike rentals — in tour operations, equipment hire, lesson bookings, activity centers, and any service business where physical assets and customer scheduling meet.
The pattern is always the same: WhatsApp for intake, spreadsheet for coordination, manual payment follow-up, admin that consumes the hours that should go toward the actual work. It works until it doesn't, and then it becomes the ceiling on how big the business can grow.
If your business runs on manual coordination and you're spending your mornings on admin that a system could handle, the situation is fixable — and faster than you think.
Start your project here. We scope in the first call and build in 72 hours.