Should You Build a Direct Booking Site? Pass the Gate First

The case for a direct booking site is usually made with a cost comparison, and the comparison is real. What it leaves out is the word that carries the whole argument: the lower cost applies once a working site and booking engine already exist.

Getting there is the project. This page is a gate on whether you can run that project and then operate what it produces, because a half built direct channel is more expensive than no direct channel at all.

TL;DR

• The reported direct cost of 4% to 5% assumes a working site and engine already exist.
• Reported commission on other channels runs 15% to 30% of booking value.
• A site does not create demand. It changes who you pay when demand arrives.
• Score payments, agreements, insurance, support, compliance and demand source first.
• Choose build, close prerequisites, or defer, and put a date on the choice.

Key facts this decision rests on

Read the Cost Comparison with Its Condition Attached

Hospitality Net reports that direct bookings cost around 4% to 5% once a functioning website and booking engine are in place, against 15% to 30% of booking value for bookings through online travel agencies.

Once in place. That is the whole gate.

The same reporting notes that processing fees and currency conversion charges can add one to three percent on top of a base commission, so neither side of the comparison is a single clean number.

A Site does not Create Demand

The most expensive misreading of the cost comparison is that a cheaper channel is a fuller one. It is not. A direct site changes who you pay when a booking arrives, not whether it arrives.

Cheaper per booking. Not more bookings.

Where direct demand actually comes from

Direct bookings come from guests who already know you exist. Repeat guests, referrals, and people who found you somewhere and chose to book straight through instead.

If none of those describes your current guests, a site will sit there. That is not a failure of the site. It is a demand source you did not have before you built it and still do not have after.

A booking engine converts demand. It does not manufacture it.

The Six Prerequisites

Readiness is not a feeling about whether you are technical enough. It is six concrete questions, each of which has an answer today.

Six answers. All available today.

The one that fails most often

Demand source. It is the only prerequisite that cannot be bought, configured or subscribed to, and it is the one hosts skip because the other five feel more like real work.

Insurance is the Quiet One

Payments and agreements get attention because they are visible in the booking flow. Insurance does not appear anywhere in the flow and is the one most likely to be discovered after an incident.

Ask your insurer before you take a direct booking.

A booking taken outside a platform may sit under different terms from one taken on it. Whether it does is a question for your insurer about your policy, and it is a short conversation to have in advance.

Three Outcomes, Each with a Date

The gate resolves to one of three, and each carries a date. A decision without a date is a preference.

Build

You build when all six prerequisites are ready and you can name the demand source. Set the date you will look at whether direct bookings actually arrived.

Close prerequisites first

You close first when the demand source is real but one or more of the other five is not. Name each gap, name who closes it and name when. Then revisit.

Defer

You defer when the demand source is not there yet. That is the honest answer far more often than hosts expect, and deferring costs nothing beyond a note in the calendar.

Defer is cheap. A dead site is not.

Four Ways a Direct Site Becomes an Expense

Direct booking projects rarely fail loudly. They fail by sitting there, and there are four common routes to that outcome.

Building before naming a demand source

The site goes live, the payment flow works, the design is fine and nobody comes. Every part of the project succeeded except the one that was never specified.

A working site with no visitors is still a cost.

Treating it as a one time build

A site needs updating, its engine needs maintaining and its terms need reviewing. The reported low cost per booking assumes a working site, and working is a state you maintain rather than reach once.

Built once. Maintained always.

Running it alongside platforms without syncing

A direct booking and a platform booking can take the same night. If the calendars do not talk to each other, the first serious week of direct demand produces a double booking.

Two channels. One calendar. Always.

Skipping the insurance question

It costs one phone call in advance and it is the item most likely to matter exactly once, at the worst possible moment.

One call now. Or one problem later.

What This Gate Cannot Tell you

The limits matter here because direct booking attracts confident claims, and nothing on this page supports any of them.

• It cannot tell you a direct site will bring bookings.
• It cannot tell you what your own cost per booking would be.
• It cannot compare platforms, which was not measured.
• It cannot tell you what other hosts achieved, which is not evidence about you.
• It cannot tell you whether building is worth it, only whether you are ready.

Readiness is the question here. Nothing else.

Cancellation behaviour is sometimes offered as a further argument. Hospitality Net reports that cancellations through online travel agencies can approach 50% in some markets, against around 18 to 20% for direct bookings. That is a reported pattern for hotels, not a prediction for your property.

Where This Sits Among your Other Decisions

A direct site is often considered for a reason that has nothing to do with distribution, and the gate works better when the real reason is on the table.

If the reason is a quiet calendar, run the booking layer audit first, because building a site is a slow answer to a problem that may be a setting. If the reason is that another platform looks attractive, the channel readiness score is the closer comparison. And if the reason is that your economics changed, the fee calculator models both sides of that directly.

Name the real reason before you build anything.

A note on being found

A direct site has to be discoverable to be useful, and that is its own project. Airbnb, for instance, has a setting that controls whether search engines display your listing pages, which is a reminder that discoverability is always a setting somewhere.

Your own site has no such switch to flip. Being found is work you take on when you build, and it belongs in the demand source prerequisite rather than being assumed to follow.

Pass the gate. Then decide. Then build.

In that order.

Not before.

And not on a hope.

A site is easy to start and slow to stop.

So start it with a reason you can name.

Then the rest is just work.

Work you chose, with a date on it.

That is what ready looks like.

Anything else is a project you drift into.

And drifting is what makes it expensive.

So run the gate first. It takes an hour.

An hour now. Or a year of a site nobody visits.

Take the hour.

What to look at six months after you build

If you do build, the review is short and it has one question. Did the demand source you named actually send bookings to the site? Not whether bookings exist, which they may for other reasons, but whether the specific source you predicted delivered.

You named a source. Check that source.

A yes means the model works and you can invest further with a reason. A no means the site is running on demand you did not plan for, which is worth understanding before you assume it continues.

Either answer is useful. What is not useful is looking at total direct bookings and calling it a result, because that number moves for reasons that have nothing to do with the decision you made when you built.

Check the prediction. Not the total.

If you defer instead

Deferring is not doing nothing. Put a date on it and name the one condition that would change the answer, which is almost always the demand source. Then work on that condition rather than on the site.

Repeat guests, a referral habit and a reason for people to look you up are all things you can build without a website. If they arrive, the gate passes on its own and the build becomes obvious rather than debatable.

Build the demand. The site follows.

That order is slower to start and much harder to regret. A site built for demand that already exists starts working immediately. A site built to create demand starts a second project you had not planned for.

Demand first. Infrastructure second.

Questions Hosts Ask About This Decision

Operator Notes

Three notes below are reserved for Sean and are deliberately unfilled. Nothing has been written into them on his behalf, and no view below is attributed to him.

• The prerequisites Sean requires before building direct: ______________________________.
• How Sean describes a real demand source: ______________________________.
• When Sean defers a direct site rather than closing gaps: ______________________________.