We’re Building the Booking System We Wish We’d Had Years Ago

For a long time, I’ve had the same thought every time I’ve used most accommodation booking systems:

How is this still the standard?

Not in an overdramatic way.

In a genuinely frustrated, sat-staring-at-the-screen, waiting-for-pages-to-load kind of way.

If you manage a holiday park, campsite, or other accommodation business, you probably know exactly what I mean.

The systems running so many businesses in this industry still feel like they belong to another era.

They’re slow.

They’re clunky.

They’re full of features nobody really uses.

Simple jobs take too many clicks.

And too often, you end up adapting your business around the software, instead of the software adapting to your business.

And sometimes it goes beyond frustration into something worse: embarrassment.

That moment when the system lets a double booking slip through, and someone on your team has to ring a guest and explain that the stay they thought was confirmed suddenly isn’t.

That’s not just a software problem. That’s a trust problem.

That frustration is a huge part of why we’re building Keydesk.

This didn’t start as “let’s launch a SaaS company”

It started more as:

Why does accommodation software still feel 15 years behind where it should be?

The more time I spent in the industry, the harder it became to ignore.

There are plenty of systems that can technically take a booking. That’s not really the issue.

The issue is that so many of them feel like they were built in the 1990s, then patched, expanded, and layered over the years until they became these bloated, awkward, half-modern systems that everyone tolerates because “that’s just what’s available.”

And that’s what makes it feel so strange.

In almost every other part of life and business, we use modern software without even thinking about it. Banking. Retail. Marketing. Customer support. Team communication. We’ve all become used to tools that are fast, intuitive, and constantly improving.

So why would accommodation be the exception?

Why should this industry be one of the few where clunky, outdated systems are still treated as normal?

And once you’ve worked with that kind of software for long enough, you start seeing the same pattern everywhere:

Teams wasting time on jobs that should be simple.

Operators stuck with rigid workflows.

Online booking journeys that should convert well, but don’t.

Integrations that feel like an afterthought.

And software that seems far more interested in helping you administer your business than helping you grow it.

That’s the bit that always felt wrong to me.

Because accommodation software shouldn’t just be a place where bookings go to live.

It should actively help you win more of them.

Most booking systems are built to manage bookings

We want Keydesk to help businesses sell more stays.

That’s a very different mindset.

Most systems in this space are sold as booking software. PMS software. Reservation software. Call it what you want.

But the core promise is basically the same:
here’s a system to run your accommodation business.

Useful, of course. Essential, even.

But also limited.

Because if your system only helps you manage operations, then it’s only solving half the problem.

The real challenge for most operators isn’t just “how do I store bookings?”

It’s:

• how do I convert more website visitors?
• how do I reduce manual admin?
• how do I market more effectively?
• how do I move faster?
• how do I make better decisions?
• how do I grow occupancy and revenue without growing complexity at the same rate?

That’s the opportunity I think this market has been missing.

And it’s why I don’t just see Keydesk as another booking system.

I see it as the beginnings of what I’d call an Accommodation Marketing System.

That means the booking engine is the foundation - but not the whole story.

The bigger goal is to build software that understands your accommodation business and helps automate the time-consuming, repetitive, commercially important work around it.

Not just managing bookings.

Helping create more of them.

So what are we actually building?

Right now, we’re building Keydesk as a modern, browser-based, cloud-hosted platform for holiday parks, campsites and other accommodation businesses.

Which already means one important thing:

No more feeling like your business is tied to legacy hosting, old-school desktop software, sluggish remote database setups, or systems that feel fragile the minute you want them to do something new.

That alone matters more than some software companies seem to realise.

People want modern tools now. Teams expect it. Guests expect it. Owners definitely expect it.

But beyond that, we’re trying to build Keydesk in a way that removes friction from the stuff operators deal with every day.

A few examples of where we’re focusing:

1. Easier setup and smarter bulk editing

One thing I’ve seen again and again is how painful configuration can be in legacy systems.

• Changing prices across date ranges.
• Applying restrictions.
• Updating availability rules.
• Managing unit types, grades, channels, mappings and booking logic.
• Making bulk changes without feeling like you’re one bad click away from a mess.

A lot of systems make this harder than it needs to be.

So one of the big things we’re working on is making setup and ongoing configuration feel much more intuitive, with smarter bulk editing and cleaner ways to manage configuration that fits around your business.

Less repetition.
Less hunting around.
Less “where on earth is that setting?”
Less admin for the sake of admin.

2. API-first from the beginning

This is one of those things that I think should be normal by now, but somehow still isn’t.

Modern accommodation businesses need their systems to connect properly with the rest of their systems.

• Websites.
• Payment platforms.
• Online travel agents (OTAs).
• Customer support.
• Marketing tools.
• Internal apps.
• Reporting layers.
• Future tools that don’t even exist yet.

Too many systems still feel closed, awkward, or heavily dependent on custom workarounds when you want them to play nicely with something else, or even worse - they charge you for adding these things.

We’re building Keydesk with an API-first approach from day one because I think integration should be a core feature, not an expensive afterthought.

That helps developers.
It helps agencies.
It helps operators with more complex needs.
And honestly, it helps future-proof the platform.

3. Built-in marketing automation

This is the part that excites me most.

Because I think it’s also the part where accommodation software has the most room to improve.

Most systems in this market are operational tools first and foremost. They help you manage inventory, reservations, pricing, availability and guest records.

That’s fine. That’s table stakes.

But what about the rest?

What about helping operators follow up better?
Market smarter?
Recover more lost demand?
Spot revenue opportunities?
Trigger the right messages at the right time?
Automate the jobs that currently live in spreadsheets, inboxes, staff memory, or “we should really do that more consistently”?

That’s where I think the category needs to go.

The long-term vision for Keydesk is not just “better PMS software.”

It’s software that becomes a more commercially useful part of the business.

Software that helps accommodation businesses grow.

4. A better online booking experience

A lot of accommodation websites do a decent job of getting people interested.

Then the actual booking journey lets them down.

That’s such a costly place to lose people.

If the booking process is slow, confusing, dated, or badly structured, all the work that went into getting a potential guest there in the first place starts leaking value.

So we’re putting a lot of thought into the booking experience too.

Not just “can someone technically complete a booking?”

But:

• Does it feel modern?
• Does it build confidence?
• Does it reduce friction?
• Does it boost conversion?
• Does it work the way real guests actually browse and book?

That part really matters.

We’re not trying to build the longest feature list

This is important.

I’m not interested in building one of those systems where the sales pitch is basically a 14-page feature matrix and the product itself feels like operating an aircraft cockpit.

A lot of software gets worse as it grows because it confuses more features with more value.

What I’d rather build is software that feels sharp, useful and commercially intelligent.

Yes, it needs depth.
Yes, it needs power.
Yes, it needs to handle real operational complexity.

But it also needs to feel clear.

It needs to be fast.
It needs to make sense.
And it needs to help accommodation businesses do better work, not just more work.

In early plans, part of the temptation was to imagine Keydesk as an all-in-one platform that did absolutely everything.

On paper, that sounds appealing. One system. One login. One place for it all.

But the more we thought about how accommodation businesses actually operate, the more we realised that forcing everything into one tool isn’t always the smartest answer.

Most operators already have parts of their stack they like. A website team they trust. A CRM they already use. Marketing tools they rely on. Reporting workflows they’ve built around.

So instead of trying to replace every tool around the business, we’ve become much more interested in building Keydesk to integrate cleanly with the rest of them.

That’s a big reason why API-first matters so much to us.

Not because “API-first” sounds good in software circles, but because flexibility matters in the real world.

Why I’m sharing this now

Because I want to build Keydesk in public.

Not in a performative “watch us hustle on the internet” way.

More in a practical sense.

I think there’s value in sharing what we’re building, talking openly about the problems we’re trying to solve, and getting feedback from the people who actually live with these systems every day.

There’s also something useful about being honest:

Keydesk is not finished.
This isn’t a polished, all-singing, all-dancing final product reveal.
We’re still building.
Still refining.
Still deciding what deserves to exist and what doesn’t.

But that’s exactly why this stage matters.

Because if we’re going to build something genuinely useful for holiday parks, campsites and accommodation operators, then it makes sense to bring the industry into that journey early.

One of the things we’re still working through is where the line should be between power and simplicity.

Accommodation software has to deal with real complexity. Pricing rules, availability logic, restrictions, channels, unit hierarchies, edge cases. That part is unavoidable.

But just because the logic underneath is complex doesn’t mean the product should feel complex to use.

We don’t have every answer to that yet. We’re still figuring out how to make something genuinely powerful without letting it become bloated in the same way so many systems already have.

And honestly, I think that’s one of the most important design challenges in the whole category.

The ambition is simple

We want to build the industry-leading software for holiday parks, campsites and accommodation businesses.

That’s the goal.

Not just software that’s newer.
Software that’s better.

Better designed.
Better connected.
More commercially useful.
More aligned with how modern accommodation businesses actually operate.

And over time, I want Keydesk to become more than a booking system.

I want it to become the system that helps operators run smarter, market better, and grow with less friction.

That’s a big ambition.

But I think this industry is ready for it.

Want early access?

We’re opening up early interest for Keydesk’s closed beta.

So if you run an accommodation business and you’re tired of outdated booking software - or just curious about what we’re building - you can register for early access.

Early adopters will get a chance to:

• see what we’re building,
• get access before public launch,
• help shape the direction of the platform,
• and influence the features that matter most.

If that sounds interesting, join the waitlist here:

Register for early access

And if nothing else, I’ll keep sharing what we’re learning as we build.

Because honestly, this industry has needed better software for a long time.

And we think it’s time this industry had it.