LukeStays Case Study: Building a Modern Direct Booking Platform

A growing short-term rental business does not always realise that it has outgrown its website.

The first signs often appear behind the scenes. Prices displayed to guests are no longer reliable. Bookings require additional manual checks. Integrations fail at inconvenient moments, and the website becomes increasingly difficult to adapt as the property portfolio and business model develop.

This was the situation facing LukeStays, an established vacation rental brand operating in the UK and UAE.

The company’s existing WordPress website was no longer capable of supporting the growing business reliably. Incorrect and outdated pricing created a risk of lost revenue, booking information was not always dependable, and the overall website experience did not reflect the image of a modern accommodation provider.

LukeStays needed more than a visual redesign.

The project required a connected booking platform that could present accommodation professionally, provide accurate information, process secure payments, communicate with third-party services and continue performing as the business grew.

This direct booking website case study explains how CODATIVITY approached that challenge and built a platform connecting the guest experience with the operational systems behind it.

A strong direct booking website is not simply an alternative place to display properties. It must function as a reliable part of the business.

1. The Business Challenge: More Control Without More Administration

Online travel agencies provide valuable visibility for short-term rental companies. They introduce properties to large audiences and remain an important source of new guests.

However, relying heavily on third-party platforms also limits control.

The operator pays commissions, competes inside a standardised marketplace and has fewer opportunities to build a direct relationship with the guest. The risks become greater when the company’s own website cannot provide an equally convenient booking experience.

LukeStays already had a website, but the technology behind it was struggling to serve the growing operation.

One of the most serious problems involved pricing. Incorrect or outdated prices could appear on property listings, creating the possibility of lost revenue and an inconsistent experience for guests. Booking and integration issues added further uncertainty, while the outdated website affected how visitors perceived the company.

These were not isolated website problems. They affected marketing, booking management, revenue and brand reputation at the same time.

The new platform therefore needed to achieve two goals.

It had to create a modern and convincing guest experience, while also improving the flow of information between the website and the third-party systems used by the business.

Increasing direct bookings could not come at the cost of additional manual work. If every reservation required staff to verify availability, correct pricing or update several systems, the direct channel would simply introduce another operational burden.

The new solution needed to provide:

• accurate and current property pricing,
• dependable booking information,
• secure online payments,
• reliable third-party integrations,
• a professional guest-facing experience,
• and an architecture capable of supporting future growth.

This balance is central to the wider discussion around OTA versus direct bookings. The objective was not to remove LukeStays from every marketplace. It was to give the business a stronger channel that it could control and develop over time.

2. Designing a Booking Journey Around the Guest

Technology alone does not persuade a guest to book.

A direct booking website must first create confidence.

Visitors need to understand the accommodation, find suitable dates, see accurate prices and move through the booking process without unnecessary interruptions. If the journey feels confusing or unreliable, returning to a familiar OTA platform becomes the easier choice.

CODATIVITY began by analysing the existing solution and the capabilities of the third-party services already used by LukeStays. This helped identify which systems could continue providing value, where integration problems existed and which parts of the guest journey required a new approach.

A bespoke website design and user experience were then prepared around lead generation and conversion.

The aim was to make the journey from property discovery to booking feel like one connected experience. The website needed to present the LukeStays brand consistently while giving guests the practical information required to make a decision.

This meant treating property presentation, availability, pricing and payment as parts of the same journey rather than separate website features.

A guest should not feel that they are moving between unrelated systems. They should be able to explore accommodation, confirm that it meets their needs and proceed towards a reservation with confidence.

This is one of the principles behind a high-converting short-term rental website. Good design is important, but its purpose is to make decisions easier and remove uncertainty.

The platform also created space for LukeStays to communicate its own value as a hospitality brand.

Unlike an OTA listing, an independent website can explain why guests should book directly, demonstrate the company’s standards and present its services to different audiences. LukeStays could support leisure guests and contractor accommodation while also generating enquiries for its property management and franchise activities.

The result was not an attempt to reproduce an OTA under another name. It was a booking journey designed around the business, its guests and its wider commercial goals.

3. Connecting Availability, Pricing and Payments

The technical centre of the project was the integration layer behind the website.

A booking platform can only be trusted when the information shown to guests is accurate. A modern interface does not solve the problem if pricing is outdated, availability is incorrect or a reservation fails to reach the systems used by the operational team.

CODATIVITY developed the new website and booking module using GatsbyJS. The guest-facing application was supported by .NET microservices hosted on Microsoft Azure.

These microservices handled communication between the website and the relevant third-party services. Instead of placing every responsibility inside one large application, the platform separated different integration and business functions into focused services.

This approach created a more dependable foundation for booking logic.

When a guest searched for accommodation or progressed towards a reservation, the website could obtain current information through the integration layer. Pricing and availability could be validated before the booking moved forward, reducing the problems caused by stale data and helping prevent conflicting or incorrect reservations.

Stripe was integrated to provide secure online payment functionality.

The payment experience therefore became part of the booking journey rather than an improvised final step. Guests could move from discovering a property to confirming and paying for their stay through a professional process supported by a recognised payment provider.

The architecture also made individual integrations easier to manage. If a third-party service changed or required maintenance, its connection could be addressed without rebuilding the entire website.

This is particularly important in short-term rental technology, where a website may depend on booking systems, pricing tools, payment providers and other external services.

The exact systems differ between companies. Some operators may use a channel manager and property management platform such as Uplisting, while others require a more bespoke integration model. The underlying principle remains the same: the website must exchange information with operational systems reliably.

Our guide to Uplisting integration explains this wider concept. The LukeStays implementation used its own combination of third-party services and a custom Azure integration layer, but the business objective was similar—keeping the guest-facing website and operational booking data connected.

A booking website is only valuable when guests and operators can trust the information it provides.

4. Building for Performance, SEO and Future Growth

The previous WordPress website had become a limitation as LukeStays expanded.

The replacement platform was designed as a long-term business system rather than a temporary marketing page.

GatsbyJS provided the foundation for a fast guest-facing website, while cloud and CDN hosting helped deliver content efficiently. This was particularly valuable for accommodation pages, where large property images and mobile browsing can easily affect loading speed.

Guests rarely describe a website in technical terms. They simply notice whether pages load quickly, navigation responds smoothly and the booking process feels dependable.

A faster website supports conversion because it reduces friction. It also creates a stronger technical foundation for search visibility.

The structure of the new platform could support property information, destination content and future landing pages without depending on a growing collection of WordPress plugins. This gave LukeStays more flexibility to develop its organic visibility and use the website as an active marketing channel.

Our guide to SEO for short-term rental companies explains why this foundation matters. SEO requires useful content, clear website structure and strong performance to work together. A technically weak website makes each of these activities more difficult.

Scalability was equally important.

The cloud-hosted architecture allowed the website and its supporting services to develop as traffic, bookings and integration requirements increased. New functionality could be introduced without forcing the business to replace the entire platform.

CODATIVITY also made practical use of the third-party services LukeStays had already configured. Reusing suitable services avoided the cost and disruption of rebuilding functionality that was already available.

Custom development does not mean building every component from the beginning. It means selecting the right combination of existing services and bespoke functionality for the business.

This approach created a platform that could evolve together with LukeStays rather than forcing the company to adapt its processes to the restrictions of a template.

5. The Result: A Stronger Foundation for Direct Bookings

The most important result was not simply a more modern-looking website.

LukeStays gained a direct booking platform that connected its guest experience, pricing, payments and third-party services more effectively.

The improved experience helped the company increase the number of direct bookings completed through its website. Accurate and current pricing also gave the business a better foundation for protecting revenue and adjusting rates in response to reservation volume.

The platform supported lead generation beyond guest bookings. LukeStays could present its property management and franchise services more professionally, improving opportunities to attract partners and grow other parts of the business.

Operational reliability was another important benefit.

A better integration layer reduced the risk created by disconnected systems and unreliable information. Staff could have greater confidence in the data supporting website bookings, while guests received a smoother and more dependable experience.

The project delivered several connected outcomes:

• a significant increase in direct website bookings,
• more accurate and current property pricing,
• a modern booking and payment experience,
• improved lead generation for other business services,
• stronger guest trust and brand reputation,
• and a scalable platform capable of supporting continued growth.

No invented percentage has been attached to these results. The strongest evidence is the operational change: LukeStays moved from an outdated website with unreliable pricing and booking integrations to a cloud-hosted platform designed around accurate information, secure payments and direct conversion.

This distinction matters.

A successful direct booking project should not be judged only by its visual design. Its real value comes from improving how the business attracts guests, processes reservations and manages the systems behind the experience.

A Direct Booking Website Must Connect Marketing and Operations

The LukeStays project demonstrates why a direct booking website cannot be treated as an isolated marketing asset.

The guest-facing experience and the operational platform must work together.

Professional design builds trust. Fast performance keeps visitors engaged. Accurate pricing and availability support confident decisions. Secure payments allow guests to complete the journey. Reliable integrations ensure the booking reaches the systems used by the business.

When these elements work together, the website becomes an active sales and operational channel.

The objective was not to replace every OTA reservation overnight. It was to give LukeStays greater control, reduce operational risks and build a direct channel that could become more valuable as the business developed.

For STR operators facing similar problems, the lesson is practical.

A new website will not solve disconnected booking processes by itself. The project must begin with an understanding of how guests book, how information moves between systems and where unreliable data creates risk.

The right solution connects all three.

You can also read the original LukeStays project overview for a concise summary of the technology and project outcomes.

If inaccurate availability, disconnected systems or an outdated booking experience are limiting your business, contact CODATIVITY to discuss how a custom direct booking platform could support your operation.

Frequently Asked Questions

What problem did the LukeStays website solve?

The project replaced an outdated WordPress website that was struggling to support the growing business. The previous setup had problems with incorrect pricing, missed or incorrect bookings, unreliable integrations and an outdated guest experience.

How can a direct booking website help prevent double bookings?

The website must validate availability through the systems where reservations are managed. In the LukeStays platform, an Azure-based integration layer connected the website with third-party services so current booking information could be checked before a reservation progressed.

Can a custom STR website integrate with an existing booking system?

Yes. A custom website can integrate with property management systems, channel managers, pricing services, payment providers and other third-party platforms. The exact architecture should be designed around the systems already used by the business.

Why were GatsbyJS and Azure microservices used?

GatsbyJS provided a fast and modern guest-facing website. The .NET microservices running on Microsoft Azure handled booking logic and third-party integrations separately, creating a more scalable and maintainable platform.

Does a direct booking website replace Airbnb and Booking.com?

Not necessarily. OTAs can remain useful discovery and sales channels. A direct booking website gives the operator an additional channel with greater control over the guest experience, pricing, branding and long-term customer relationship.

Is a custom booking platform suitable for a growing property portfolio?

Yes, provided it is designed for growth. A cloud-hosted platform with well-structured integrations can support more properties, visitors and booking activity without requiring the business to rebuild the entire website.

What makes a vacation rental website scalable?

Scalability comes from more than hosting capacity. The website should use a flexible architecture, dependable integrations, optimised media delivery and components that can be extended as the portfolio and operational requirements grow.