Inntelligent
A cloud platform for hospitality that started as a booking engine and a front desk, and now runs the hotel, the restaurant, the SPA, and the people and money behind all three.
- Client
- Inntelligent
- Industry
- Hospitality software
- Engagement
- Technical partner, day one to today
- Services
- Architecture, build, onboarding, support
- Live at
- inntelligent.co.uk
The brief
Inntelligent came to us with years of hospitality experience and an empty repository. The idea was a cloud platform an independent hotel, restaurant or SPA could run their entire day on - without the price tag, the consultants and the six-week training that the incumbent systems arrive with.
We joined on day one and laid the technical foundation: multi-tenant, multi-language, built to take on modules for years rather than to demo well in month three. Then we started small on purpose - a property management system for the front desk, and an embeddable booking widget operators could paste onto their own website to take direct reservations.
Everything after that was earned. Three years of expansion, driven half by Inntelligent's own roadmap and half by what real operators told us they were missing while we were sitting next to them during onboarding.
- 01One platform, wildly different businesses: a twelve-room B&B, a restaurant with a kitchen line, a SPA paying staff on commission.
- 02Every operator runs their business their own way and expects the software to agree with them.
- 03Multi-tenant and multi-language from the first commit, before there was a single paying customer.
- 04A feature set that grows every quarter without turning into a maze nobody can be trained on.
- +Modular, so each customer sees only the parts of the platform they actually use.
- +Configurable enough to feel custom-built, without a separate fork per client.
- +One data model under bookings, stock, staff and money, so the reports mean something.
- +A learning curve short enough for seasonal staff hired in May.
Every operator should feel the platform was built for their business. Nobody should be paying for a version that only exists for them.
What one platform covers
Six areas of a hospitality business, added one at a time over three years, all reading and writing the same data.
Property management
Calendar, rates and availability, dynamic pricing, guest profiles and a daily manager view - a receptionist's whole shift on one screen.
Booking engine
An embeddable widget that lives on the operator's own website. Direct reservations land in the same calendar as everything else, without a commission in between.
Restaurant & bar
POS, tables and areas, menus with modifiers and recipes, stock deducted as it's sold, kitchen view and end-of-day till reports.
SPA & services
Appointment calendars, prepaid packages and memberships, staff rota and commission tracking, multi-service invoices for a guest who did three things in one visit.
Guests & marketing
Guest history, feedback automation, vouchers, gift cards and loyalty - acquisition, retention and everything that has to happen between the two.
Money & people
Invoicing and financial control on one side, personnel, rota and payroll on the other, both fed by what actually happened at the desk and the till.
How we worked
Four stages, three of which are still running. This is not a project we handed over - it's one we're still building.
Foundation
Tenancy, localisation, deployment and access control decided first. Unglamorous choices made once, so three years of features never had to renegotiate them.
Core product
A PMS a receptionist can run a full shift on, and a booking engine that lives on the operator's own site so the direct reservation stays direct.
Expansion
F&B with POS and stock deduction, SPA and service scheduling, CRM, finance, personnel and payroll, marketing and retention - added module by module, each one wired into the same data.
In the room
We ran the first customer integrations ourselves, trained Inntelligent's support team, and still join pre-sales calls and go-lives for key accounts.
More than the code
Writing it was never the whole job. We spend nearly as much time in front of the customer as in the editor - which is where most of the roadmap comes from.
First integrations
We ran the earliest customer onboardings ourselves: real data migrated, the platform matched to how that business already worked, and whatever didn't fit fixed while we were still there.
Training the support team
Inntelligent's own staff answer the phone, not us. We trained them across every module so the platform doesn't depend on the people who wrote it.
Pre-sales & go-lives
We still join pre-sales calls and go-lives for key accounts. An objection heard from a hotelier in the room beats the same objection read in a ticket three weeks later.
Stack & infrastructure
Picked for a platform that has to be maintained for a decade and priced per tenant, not for whatever was trending the quarter we started. Self-hosted, so the cost of growth stays predictable - and bridged to the hardware sitting on the counter, because hospitality doesn't happen entirely in a browser.
Where it stands now
Inntelligent is live, selling, and onboarding new properties. We're still the development team behind it: shipping modules, sitting in on go-lives, and hearing what's missing from the operators themselves before it reaches a backlog.
You have a project. We have the time.
Tell us what you're planning and we'll tell you honestly whether we're the right team for it. No pitch deck, no sales call.