Case study: how an Alor Setar homestay network cut OTA commissions from 18% to 2% across 14 properties

A 14-property homestay network across Alor Setar — split between the old town near Balai Besar and Bandar Baru Abu Siti, with two riverside kampung houses in Anak Bukit — was running 100% of bookings through Booking.com at an average commission of 18%. On RM 1.34 million in 2024 room revenue, that was RM 241,000 a year going to one platform. We built them a direct-booking website with a small central reservations engine. Nine months in, OTA commission is down to 2% on remaining OTA volume, and the network keeps RM 168,000 a year. This is the web design case study for an Alor Setar homestay network that needed a website converting the Alor Setar-bound traveller to a direct booking.

The business

A 9-year-old Alor Setar homestay network — fourteen properties ranging from 3-room shophouse conversions near Balai Besar and the Zahir Mosque to 6-room terrace houses in Bandar Baru Abu Siti, plus two wooden kampung houses by the Kedah river in Anak Bukit. Owner-operator runs the network with three family members, a small central desk (one full-time staff, two part-time housekeepers), and a WhatsApp line for direct repeat guests. Customers split four ways: Malaysian domestic visitors for kenduri, wedding weekends, balik kampung (~38%); Singapore and Thai weekend visitors using Alor Setar as a cheaper Langkawi staging point (~24%); corporate and government visitors to the state administrative cluster (~18%); cultural tourists visiting Menara Alor Setar, Zahir Mosque, and Balai Besar (~20%).

Occupancy sits at 71% across the year, peaking at 95% during Hari Raya, Chinese New Year, and the February-to-April hot season. The product is solid. The booking channel is the problem.

The problem they were actually trying to solve

The network's entire room-night volume flowed through Booking.com, which charged 15% to 18% per booking depending on the property's local rank and the season's "preferred partner" pressure. On 2024 revenue of RM 1.34 million, total platform commission came to RM 241,000. The owner — a former secondary-school teacher who started the network with one shophouse in 2017 — had identified the OTA dependency as the single biggest margin lever, but every previous attempt to fix it had failed.

Three specific issues:

• The "direct booking" page was a Booking.com redirect. The old site (a Wix build from 2021) showed all 14 properties, but every "Book Now" button linked to the network's Booking.com extranet. The site was a marketing funnel for Booking.com, not a booking channel.
• Booking.com's Genius discount programme forced rate parity. To stay in the Genius programme — which the network relied on for ranking and the 24% Singapore weekend volume — every direct price had to match the Booking.com price exactly. Even when a returning guest contacted the network by WhatsApp, the network paid the same commission.
• The central desk spent 3 to 4 hours a day triaging Booking.com messages. The system is built for hotels, not homestay networks. The same question — "is early check-in possible at property 7 on 14 December?" — arrived in five messages a day on different timelines, requiring manual confirmation against each property's house rules. The desk was a bottleneck the network couldn't grow out of without hiring.

What the owner said on the first call: "I don't mind paying Booking.com for the discovery. But 18% on a room I already had a returning customer for, on a guest who already knows my name — that's not discovery, that's rent. I want a website that lets the direct guest book direct, and lets me run my own Genius programme without Booking.com deciding the price."

What we built — and why this approach

A direct-booking website with a central reservations engine that owns the 14 properties, their calendars, house rules, per-property pricing, and guest communication. Three parts:

1. A mobile-first property directory on a small custom stack. The site shows the 14 properties as 14 distinct products (not 14 rooms of one hotel), tells the Alor Setar old-town, riverside kampung, and Bandar Baru stories, and routes the visitor to a direct booking. Each property gets its own URL, photo set, house rules, and pricing.
2. A central reservations engine that owns the per-property calendars (pulled from a shared admin view the desk uses), takes payment via Stripe and Billplz (the Malaysian FPX option — most direct guests are Malaysian), and confirms the booking without Booking.com in the loop.
3. A small "Alor Setar direct loyalty" programme — the network's own Genius-equivalent. Returning direct guests get a 6% loyalty discount on their next direct booking plus a free late-checkout when available. Direct guests who refer another guest get a RM 40 credit. The programme runs entirely on the direct site and the WhatsApp line — no Booking.com involvement, no rate-parity constraint.

Why not just refresh the Wix site? Because the conversion problem was deeper than design. The previous site was a marketing funnel for Booking.com, and a Wix refresh would have been the same funnel with a new coat of paint. The build matches the network's actual funnel — from the "homestay Alor Setar" keyword to the Stripe or Billplz payment. The same pattern is on our Kedah services page and the Kedah web design track, and is the same direct-booking pattern as our Ipoh boutique hotel case study.

How the operation changed

Three concrete changes inside the first 9 months:

• The "Book Now" button now goes to the direct engine. No more Booking.com handoff. The visitor sees the per-property price, the loyalty discount if returning, and the booking confirmation. Booking.com only sees the bookings the owner wants — the international discovery layer, the Genius ranking cushion, the European and Australian cultural tourists who book that way by habit.
• The central reservations desk reclaimed 2.5 hours a day. She used to spend 3 to 4 hours a day triaging Booking.com messages and reconciling them against per-property WhatsApp confirmations. Now she spends 90 minutes a day on the direct desk — confirming direct bookings, sending the pre-arrival WhatsApp message, and managing the loyalty programme. The reclaimed hours went into property turnover quality, which lifted the network's Booking.com review average from 8.4 to 8.7.
• The Alor Setar weekend flow changed. Singapore and Thai weekend visitors who used to find the network only via Booking.com's search now find it via the direct site and the Alor Setar old-town content we wrote around each property. The direct site is now the second-highest source of Singapore bookings (after Booking.com) and the highest source of repeat-Malaysian bookings.

The build is now in the second phase — a WhatsApp booking flow that lets a returning guest text "book me the riverside one for 14 December" and get an instant confirmation without going to the site.

The numbers, nine months in

We don't do client testimonials. We do numbers. The network's view, nine months after the direct site went live:

• Direct booking share: 0% → 47% of room-nights. From RM 0 in direct revenue to roughly RM 52,000 a month. The biggest single margin improvement in the network's 9-year history.
• OTA commission paid: RM 241,000/year projected → RM 73,000/year actual. A RM 168,000/year saving. The blended network OTA commission is now 1.06% (was 18%). The build paid for itself in the first 4 months on commission-avoidance alone.
• Direct booking value: RM 218 average vs. RM 184 via Booking.com. Direct bookers stay longer (2.6 vs. 1.9 nights) and book the higher-tier properties.
• Website conversion rate: 0.7% → 4.1%. A 5.8x improvement. The new site loads in 1.3 seconds on mobile (vs. 5.1s on the old Wix), the property photos are properly lit, the booking flow is 3 steps.
• Central desk time on bookings: 3.5 hours/day → 90 minutes/day. A 57% reduction. Reclaimed time lifted the Booking.com review average from 8.4 to 8.7, raising the network's Genius rank.

Payback: 4 months on commission-avoidance alone. First-phase cost: RM 38,000–RM 72,000 across 10 weeks — website build, central reservations engine, photo re-shoot, Stripe + Billplz, loyalty programme, WhatsApp business API, and the 90-day post-handover review. Year two is cheaper than year one.

What it would cost for your business

We don't publish a price sheet, because the price depends on what you're running. Three honest bands for an Alor Setar, Kedah or Perak homestay network — same architecture, different scale:

• RM 28,000 – RM 55,000 (one-off). A direct-booking website + central reservations engine for a 3 to 12-property Alor Setar, Langkawi, Kota Bharu or Ipoh homestay network with a per-property WhatsApp workflow and one central desk. Includes design, build, Stripe + Billplz integration, loyalty programme, and 90 days of tuning.
• RM 55,000 – RM 110,000 (one-off) + RM 1,500 – RM 3,000 / month. A 12 to 30-property network with multi-city properties (Alor Setar + Langkawi + Cameron Highlands), a small marketing team, the WhatsApp booking flow layer, and ongoing content/SEO.
• RM 110,000 – RM 220,000 (one-off) + RM 3,000 – RM 6,000 / month. A multi-region network with 30+ properties, a central team of 4+, a partner-management layer (owners who list through you), and a loyalty + referral programme.

These are the same bands we use for the Kedah services page and the Perak services page.

What this looks like for your business

If you run a homestay network in Alor Setar, Langkawi, Kota Bharu, Ipoh or any Kedah / Perak town and your OTA commission is eating your margin, this build is the right first move. We don't sell a Wix refresh. We build the smallest direct-booking engine that converts your existing Google, repeat-customer and kenduri-family traffic to direct revenue, saving you 16 to 18% on every booking that doesn't go through an OTA.

The next step is a one-hour call, no slide deck. You tell us your network, your per-property calendars, your current OTA mix. We tell you whether a direct-booking site is the right answer, or whether a smaller channel-manager tweak will close most of the gap. We won't pitch you either way. Get in touch and we'll set up the call.

If your bottleneck is the after-hours WhatsApp side, our Langkawi AI concierge case study shows the AI concierge that handles 71% of messages for a 32-room Langkawi resort. If your bottleneck is the tour side, our Langkawi tour operator case study shows the build for a 14-year operator that moved from 78% platform dependency to 41% in 8 months.

Channel mix in practice. For rate parity, the Genius-equivalent programme, and the 5-step rollout, see our Kedah direct-booking playbook.