Hotel groups and management companies
Several properties on a cloud PMS, with guest, rate and operations data spread across 15 to 20 other tools.
Hospitality
Hotel PMS and restaurant POS systems that talk to each other
We connect PMS, POS and operations tools for hotel groups, restaurant groups and the software companies that sell to them. We also own two hospitality products, a housekeeping app for hotels and a back-office service for restaurants, so we know the work on the floor as well as the data behind it.
PMSMews, Apaleo, OPERA Cloud, Cloudbeds
POSToast, Lightspeed, Square
Our own productsHousekeeping app, Kitchen Back Office
Who we work for
Groups and software companies, not single venues
A single hotel or restaurant is usually better served by an app from its PMS or POS marketplace. We work on what those apps don't cover: several sites, several systems, and the software companies building for them.
Restaurant groups
Twenty or more sites on one POS, where stock, payroll and head-office reports don't agree with the tills.
Hospitality software companies
A product that needs a reliable connector to Mews, Apaleo, OPERA Cloud or Toast, ready for the platform's marketplace review and kept working as the APIs change.
What we build
Integrations and tools we build
PMS integration
Two-way integrations with Mews, Apaleo, Oracle OPERA Cloud and Cloudbeds for hotel groups and software vendors, with sync you can trust on a full night.
POS integration
Toast, Lightspeed and Square integrations for multi-site restaurant groups: orders, menus, stock and sales flowing into the tools your teams already use.
Operations software
Custom back-office tools for kitchens, housekeeping and operations when off-the-shelf apps no longer fit, built by a team that owns two hospitality products.
Integration audit
A fixed-price audit of how your PMS, POS, channel manager and ops tools exchange data: where sync breaks, what it costs you, and a priced plan to fix it.
Proof
Our own hospitality products
We built both and sell them ourselves, so the housekeeper's phone, the stock count and the month-end report are problems we have had to solve as owners, not only as contractors.
Kitchen Back Office
Our own back-office service for restaurants: the kitchen sends photos and voice notes, we close the stock counts and report P&L and food cost on our Kitchen app.
Housekeeping app
Our own app for hotel housekeeping: daily room tasks on staff phones, live room status for supervisors and reception, supplies tracked per room.
Why a small team abroad is a safe choice
What goes wrong with agencies, and what our contract says instead
The people you meet are the people who build
Your proposal names the engineers who will do the work, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.
Your repository and accounts from the first commit
Code, cloud, app-store and domain accounts are in your name, and we work inside them from day one. The contract assigns the IP to you in the present tense ("hereby assigns"), so there is no later transfer to wait for. Portuguese law (Decree-Law 252/94) also treats commissioned software as the client's by default. lawyer to confirm DL 252/94
Nothing depends on us staying
You pay per milestone, for work you have seen running. Everything lives in your accounts, and every milestone ends with a written handover: architecture notes and runbooks your next engineer can follow without us.
Reviewed work, under a 90-day warranty
A second engineer reviews every change before it merges, and code written with AI tools is read line by line (our AI-use policy). Paths that touch money and data have automated tests. A written 90-day warranty covers defects in our work.
Questions
Hospitality questions
Are you a Mews or Apaleo partner?
No, not today, and we don't claim to be. We build against each platform's published API, using your company's developer or partner account, so the integration and any listing belong to you. If a platform requires a certified partner for your case, we tell you before you sign.
Can you list our integration in a PMS marketplace?
Yes. We prepare what the marketplace asks for: its review or certification steps, test scenarios, documentation and support details. The steps and waiting times differ by platform, so we plan the build around them from the first week. The listing is in your company's name.
Who owns the code and the IP?
You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.
Who will actually work on our project?
The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.
How do time zones work for a UK or US team?
We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.
What contracts do you sign?
A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.
How do we pay?
The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.
Free 30-minute call
Tell us what has to work, and by when
You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.