NOTES — 2026-10-04
How much does a homestay website cost in Malaysia?
The honest answer is that price follows scope, not page count. A website that shows your homestay and sends guests to WhatsApp is a different job from a system your staff use to manage bookings. An illustrated map adds another kind of work. Calling all of them a “homestay website” does not make their quotes comparable.
There is no verified price data behind this article, so I am not publishing guessed ranges or a supposed Malaysian average. The same approach applies in my guide to website costs in Malaysia.
What you can compare is the work included, the responsibilities left with your team and the costs that continue after launch.
A simple presence site: explain the stay, invite an enquiry
A presence site helps guests understand the accommodation before contacting you. Its scope might include photographs, sleeping arrangements, facilities, location, house rules and a clear enquiry route.
The main work is gathering accurate information, organising it and making it easy to read on a phone. A guest should be able to work out whether the place suits their group and how to ask about dates.
This does not require instant booking. A WhatsApp link or enquiry form can be enough if your team will check availability and confirm the stay manually.
Ask what happens after the guest taps the button. Does it open a conversation? Does it submit a request? Neither should be described as a confirmed reservation unless that is actually what happens.
A booking-management layer: work for the team, not just guests
If the problem is following bookings across conversations, a public website alone may not address it. You may need an internal record as well.
This changes the scope. The developer needs to understand how staff record requests, confirm deposits, change dates and handle cancellations. Access permissions, record keeping and testing belong in the quote, not under a vague promise of “booking features”.
For Pulau Chekas, a homestay in Raub, Pahang, I built a guest website with Buku Lejar behind it for staff-managed bookings.
Buku Lejar brings website enquiries and manually entered WhatsApp or telephone bookings into one booking-management interface. It includes:
- Booking status and deposit tracking, with staff confirmation.
- Separate admin and operator access.
- A record of who changed what, and when.
These functions are different from publishing accommodation pages. They support the team's work after an enquiry arrives.
The documented workflow does not promise instant availability or automatic payment processing. Do not assume a booking ledger includes OTA imports or channel synchronisation either. Those capabilities need their own agreed scope and proof.
Interactive features: add them for a specific guest question
Pulau Chekas also has an illustrated 3D map connecting accommodation listings with the rivers, paths and facilities around them. Guests can explore the setting rather than only scroll through room names.
That is a separate deliverable from both the public information and the booking ledger. A similar feature needs its own illustration work, interaction design and testing. It also needs checking on phones, where the guest must still be able to find the accommodation information and enquiry route.
The Pulau Chekas map is illustrative, not a survey. It should not be treated as a promise of exact distances.
Not every homestay needs this feature. Ask which question it answers. If ordinary photographs and a clear layout explain your property well, start there. If the relationship between accommodation and the surrounding facilities matters to the choice, an interactive map may be worth discussing.
You can see how these parts fit together in the Pulau Chekas case study. It is an example of scope, not a published price benchmark.
Why page count is a weak way to compare quotes
A page of photographs and contact details does not involve the same work as a staff screen that changes booking records. Both can appear as a single page in a proposal.
Compare the actions instead. What can guests submit? What can staff change? What must be checked before a booking is accepted? What happens when someone enters the wrong details?
Content also changes the work. Supplying approved photographs and accommodation descriptions is different from asking a developer to sort old images and write everything from scratch. Say who will provide each item and who will check it before publication.
Your property information and booking rules should come from your business, not the developer's guesses.
Separate the build from the running costs
Ask for the initial project work and ongoing costs to be listed separately. Check domain renewal, hosting, maintenance, content updates and any subscription services included in the proposal.
For a staff tool, ask about backups, support and recovering records. Agree who can change accommodation details and who will manage staff access.
“Updates included” needs a boundary. Replacing a photograph is not the same as adding a new accommodation type with different booking rules. Ask how later changes will be quoted.
Ownership matters too. Who controls the domain? Can the site move to another host? Can booking records be exported? An owned asset should come with clear access and handover terms, not just your logo on the screen.
Compare an owned website with recurring OTA commission
OTA commission is a recurring cost on bookings subject to commission through that platform. Check your own agreement for the applicable charges rather than using a generic percentage.
A website with a direct enquiry route is an owned asset you can use to explain the property and receive interest outside an OTA listing. That does not make direct bookings cost-free. You still have running costs, promotion and staff time spent answering guests and confirming stays.
Nor does a website guarantee enquiries or occupancy. The Pulau Chekas case demonstrates a guest site and staff workflow; it does not establish commission savings or increased revenue.
Compare your actual channel costs with the full cost of operating the direct route. My homestay direct bookings vs OTAs article covers that decision in more detail.
Ask for a quote around your daily work
Give each supplier the same brief. Include your accommodation information, how enquiries arrive and who confirms the booking. Then ask them to separate:
- The guest-facing website and enquiry route.
- Any staff booking-management tool.
- Optional interactive features.
- Content preparation and your approval responsibilities.
- Testing, handover and ongoing support.
- Exclusions such as online payments or channel synchronisation.
Before accepting the work, follow an enquiry on a phone. If a ledger is included, ask staff to enter a telephone booking, update its status and correct a mistake. Check that the guest-facing wording matches the confirmation process.
Start with the smallest scope that addresses the real problem. A clear website may be enough when guests need better information. A booking layer deserves attention when the team needs better records. Neither should be bought simply because a package has more pages.