Skip to content
Senior web & app development · 20 capabilities
oakstone.digital
Case study / Kindred Stays

Hospitality with a human signal.

A rebuilt booking journey and payment integration helped an independent stay win direct reservations.

Industry
Hospitality
Duration
7 weeks
Division
Websites & Commerce
Year
2026
Kindred Stays — hospitality web development project by Oakstone
Websites & Commerce / delivered
27%
of bookings now direct
11s → 2.8s
mobile time to interactive
6 → 3
steps in the booking journey
The challenge

Kindred operated four properties and paid platform commission on almost every booking. Their own site had a six-step booking flow, a calendar that could show unavailable dates as available, and a mobile experience that took eleven seconds to become usable.

Guests who tried to book direct frequently gave up and returned to the aggregator.

The move

We integrated availability directly from the property management system with a short freshness window, so the calendar stopped lying, and reduced the booking journey from six steps to three.

Payments moved to hosted fields with wallet support, deposits and cancellation terms stated plainly. Imagery was rebuilt through a media pipeline with reserved space and modern formats.

The result

Mobile time-to-interactive fell from over eleven seconds to under three, and the share of bookings taken directly rose to 27% within two seasons.

The commission saved in the first year exceeded the cost of the project.

Stack
AstroStripeCloudflare ImagesPMS REST APIPlausible
Team

One designer, two engineers

Constraints
  • Property management system API rate-limited availability lookups
  • Rate parity agreements limited what could be offered direct
  • Launch needed to precede the booking season by six weeks
What we would do differently

Caching availability with a short freshness window and showing the constraint honestly performed better than trying to look real-time. Guests forgive a "checked two minutes ago" label; they do not forgive a false vacancy.

We rebuilt the image pipeline twice because the first approach kept the original aspect ratios. Standardising crops earlier would have saved a week.

A better brief starts here

Your next proof point is waiting.

Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.

Start a conversation