SpyderHill is a boutique forest retreat nestled in the Berembun Forest Reserve, Negeri Sembilan — about 90 minutes from Kuala Lumpur. With two beautifully appointed rooms overlooking pristine rainforest, it's the kind of property that guests rave about and return to.
For years, SpyderHill ran on WordPress with the HBook plugin for booking management. It worked — until it didn't. This is the story of why they switched to Tamu and what happened next.
The HBook Setup: What Worked
HBook is a popular WordPress booking plugin used by thousands of small accommodation providers. For SpyderHill, it handled the basics: availability calendar, booking form, email confirmations. The WordPress site looked good and ranked reasonably well in Google.
For a 2-room property, the basic features were sufficient. Guests could check dates, fill in a form, and receive a confirmation email.
Where HBook Fell Short
As SpyderHill grew from a side project to a serious hospitality business, the limitations became clear:
- No iCal Sync: HBook couldn't sync with Airbnb, Booking.com, or Agoda calendars. This meant manually blocking dates across platforms — a recipe for double bookings.
- No FPX Support: Malaysian guests expect to pay via FPX (instant bank transfer). HBook's payment options were limited to PayPal and basic Stripe — no local payment methods.
- WordPress Maintenance: Plugin updates, security patches, hosting costs, SSL certificates, backups. A WordPress site is a part-time job to maintain.
- No Mobile Dashboard: Checking bookings meant opening a laptop and logging into WordPress admin. No mobile app, no quick glance at today's arrivals.
- No Guest CRM: Guest data was scattered across emails and WordPress entries. No way to track repeat guests, send follow-ups, or manage guest preferences.
- No Revenue Analytics: Basic booking counts, but no revenue breakdown, occupancy trends, or OTA vs direct comparison.
The Migration to Tamu
Total migration time: 5 days, with the property accepting bookings throughout. No downtime, no lost reservations.
- Day 1: Property setup — rooms, photos, pricing, and availability imported from HBook data
- Day 2: Payment configuration — Stripe with FPX enabled, pricing set in RM
- Day 3: iCal feeds connected — Airbnb and Booking.com calendars synced bidirectionally
- Day 4: Testing — test bookings, payment processing, email confirmations verified
- Day 5: Go live — DNS pointed to Tamu, old WordPress site archived
What Changed After Switching
The differences were immediate and measurable:
| Metric | HBook (Before) | Tamu (After) |
|---|---|---|
| Double bookings per quarter | 2-3 | 0 |
| Payment methods | PayPal, Stripe (cards) | FPX, cards, Touch 'n Go |
| Calendar sync | Manual | Automatic (iCal) |
| Mobile dashboard | None | Full owner portal |
| Guest database | Scattered emails | Centralised CRM |
| Revenue analytics | Manual spreadsheet | Real-time dashboard |
| Monthly maintenance time | 4-6 hours | < 30 minutes |
| Platform cost | ~RM 150/month (hosting + plugins) | RM 99/month |
The Revenue Impact
The most significant change was in direct booking revenue. With HBook, SpyderHill relied heavily on Airbnb and Booking.com for bookings because the direct booking experience wasn't competitive. The WordPress site looked dated on mobile, the booking form was clunky, and there was no review display.
After switching to Tamu, SpyderHill's direct booking page became as polished as an OTA listing — professional photos, real-time calendar, guest reviews, secure payments. Guests who found SpyderHill on Google or Instagram could book directly with confidence.
Within 6 months, SpyderHill's direct booking share grew from approximately 15% to over 40%. On RM 80,000+ annual revenue, the commission savings from shifting those bookings off OTAs were substantial.
What Nikt (SpyderHill's Owner) Says
"The biggest change is peace of mind. Before, I was always worried about double bookings because Airbnb and HBook didn't talk to each other. Now everything syncs automatically. I check my phone in the morning, see today's arrivals, and that's it."
"The FPX option was huge. Most of my Malaysian guests prefer bank transfer. With HBook, I had to handle bank transfers manually — check my account, confirm to the guest, update the booking. Now it's all automatic."
"I don't miss WordPress maintenance at all. No more plugin updates breaking things, no more hosting renewals, no more worrying about security patches. Tamu just works."
Should You Switch from HBook?
If you're a Malaysian property owner using HBook (or any WordPress booking plugin), consider switching if any of these apply:
- You've had double bookings due to lack of OTA calendar sync
- You want to accept FPX or local payment methods
- You spend more than 2 hours per month on WordPress maintenance
- You want a mobile-friendly owner dashboard
- You want to reduce OTA commission by growing direct bookings
- You want guest CRM, analytics, and automated follow-ups
Migration Is Easier Than You Think
Switching from HBook to Tamu doesn't mean starting from scratch. Your property photos, descriptions, and pricing transfer easily. Your OTA listings stay active during migration — no booking gap. And Tamu's setup wizard walks you through the entire process.
SpyderHill did it in 5 days with zero downtime. Most properties complete the switch in 3-7 days.
Ready to explore? Visit tamuhq.com/case-studies/spyderhill for the full SpyderHill case study, or start your free trial at tamuhq.com.
More from the Tamu Blog
How to Sync Your Airbnb Calendar with a Direct Booking Engine (Step-by-Step)
Double bookings are the number one fear of every property owner using multiple booking platforms. iCal sync solves this. Here's exactly how to set it up in 10 minutes.
How to Get Direct Bookings for Your Malaysian Homestay
OTAs bring visibility, but direct bookings bring profit. Here are 10 proven strategies Malaysian homestay owners use to drive direct bookings and reduce OTA dependency.