Founder POV: Most hospitality tech is built from a single lens for a single vertical.

This article is adapted from a LinkedIn post by Robbie Francis, Founder of Hops.

Most hospitality tech is built from a single lens for a single vertical.

I knew when we started building Hops® that we HAD to break this mold, having seen so many customers struggle with SaaS solution not maluable enough to fit their operation.

I've seen this occur when you get a founder from vertically specific backgrounds (QSR's for example), they're always going to be great at building systems that work for other QSRs…… It makes sense, as this is the prime lens through which they see hospitality.

But the architectural decisions they make early on in there products development, often don't translate across to other verticals.

Before we wrote a single line of code for Hops, we’d already supported 100s of different operators, across almost EVERY vertical through Eposability, our founding company.

Michelin-starred restaurants, bustling food halls, quick-service chains, boutique hotels. You name it, we've been in the trenches with them.

We saw what broke, what scaled and ultimately what was missing.

So we built our app with a completely different philosophy in mind: it must match the reality of every operator. Which is to say:

🔧 Configurable enough to match how every operator runs 🔧 Works across verticals, not just in one niche 🔧 Solves real-world problems with real-world constraints

Because whilst it’s one thing to build pretty dashboards…

It’s another to build something that actually works, inside the messy, chaotic, glorious reality of hospitality.

---

About Robbie Francis
Robbie Francis is the Founder of Hops. He has spent years building and implementing hospitality technology with operators, focused on simplifying back-of-house operations across inventory and finance.

Follow Robbie on LinkedIn: linkedin.com/in/robbiefrancis

View the original LinkedIn post: Most hospitality tech is built from a single lens for a single vertical.