The house01
We are a software engineering company. The work that shaped us is hospitality: hotels, destinations, and the desks that have to convert an inquiry into an occupied room before the guest opens a second tab.
Tourism companies live on occupancy, reputation, and a short clock. A missed inquiry is an empty night. A slow check-in is a review. That is the constraint we design for — and it is why we did not start with a generic “digital transformation” brochure.
Remote-first. Europe and beyond. The same people who consult, build, and operate also run the product that hotels already use.
The product02
iSales is our only product — the tourism app that powers hotels around the world. It is not a side project. It is the center of the company: sales, guest operations, and occupancy in one rhythm, shaped by real front-desk work.
ProductiSales
Our only product
iSales
Hotels need occupancy, guest communication, and sales in one place — not a CRM skin and a spreadsheet named Season_final. iSales is built for that desk: inquiries, stays, and follow-up that staff can actually run on a peak night.
We do not only sell it. We operate it. The same team you brief for a website or a consultation is the team that maintains the platform live properties already depend on.
See iSales
The stay03
The way we offer our work is simple. If you are a tourism company, iSales is the starting conversation. It is the product we already run — occupancy, sales, and guest service without inventing a new stack for every property.
When a hotel, group, or destination needs something iSales does not cover — a public site, a brand system, a custom workflow, a consultation on what to buy and what to leave — we sell that as services. The product stays the spine. The services do not compete with it.
That is the honest offer: one hospitality platform, and a delivery team that can sit at the desk, map the leak, and ship the rest without pretending every brief needs a new product.
The offer04
Web development, web applications, graphic design, consultations, and digital services are how we extend iSales, or how we help when the brief is not hospitality. They share the same method. They do not replace the platform.
The public face of the stay — sites that convert without fighting the brand or the inventory.
Custom tools when the desk needs a workflow iSales should not be bent to cover.
A visual language that holds on the site, in the product, and in the campaign.
What belongs in iSales, what is custom, what the OTA already owns — decided in the open.
The weekly rhythm around the stay: content, reporting, and support after go-live.
The method05
The method is the same whether you adopt iSales or ask us to build beside it. We start at the desk. We write the decision down. We ship something staff can run. We stay for the season.
Stand at reception at turnover. Map the guest path including the workarounds. If iSales already covers it, we say so.
Product first. Then what to configure, what to build as a service, what to leave. Ownership after launch is written down.
iSales when hospitality is the whole product. Sites, apps, and brand when the stay needs a public face or a custom tool.
We run iSales in live properties. Client work follows the same rule: the week after launch should get quieter, not louder.
The briefing06
Send a request. We will tell you honestly whether iSales is the right first step, or whether the brief is a service around it — and what the first slice of work should be.