Understand
Learn the people, pressures, decisions, tools, exceptions, and daily reality of the business.
Bespoke operational software
The operation comes first. The software follows.
Salem Experience Design studies how your business runs, then builds a bespoke working environment around it. Salem OS is the name for that software.
From Salem Experience Design · Four fictional references
Why bespoke
Too complex for spreadsheets. Too individual for generic software.
For growing service and experience businesses whose operation has become more complex than the tools holding it together.
When essential work is spread across messages, spreadsheets and specialist tools, the team ends up carrying the connections. Salem Experience Design maps those handovers and designs the working environment around the operation.
01Spreadsheets
02Email
03WhatsApp
04Generic software
05Manual handoffs
06Disconnected systems
The result is a clearer day: the right context, the next action and the person responsible, visible together.
The principle
Your business. Your workflows. Your operating system.
One business may begin with a single critical workflow. Another may need the whole operation connected. The scope follows the work.
How Salem works
Design the operation before designing the software.
Understand the people and handovers first. Decide what the software should do only after the operation is clear.
Understand Map Simplify Build Integrate Refine
Map
Trace how information, responsibility, customer needs, and work move through the operation.
Simplify
Remove duplication, unclear handoffs, and processes that no longer serve the business.
Build
Create the operational software around the improved way the business should work.
Integrate
Connect the specialist systems that already do their job well.
Refine
Learn from real use and keep improving clarity, flow, responsibility, and control.
A hotel, seen in full
One booking changes the whole hotel day.
At fictional Kydonia House, a guest's choice moves into room preparation, team work and a useful day for the manager. The public experience and the hotel operation belong to the same story.
Kydonia House / fictional boutique hotel
One business. One operation. One Salem OS.
In this implementation, reservations, guests, arrivals, housekeeping, requests, payments, and staff operations can be understood as one connected working environment.
Kydonia House is a fictional boutique hotel and one bespoke Salem OS reference implementation.
Follow the hotel walkthrough
One stay, across the hotel
The guest sees a considered stay. The team sees the work needed to deliver it.
- Reservations
- Guests
- Arrivals
- Housekeeping
- Requests
- Payments
- Staff operations
Four working references
Different operations need different systems.
Each fictional business has its own public experience, walkthrough and working environment. Explore the one closest to the work you want to understand.
02 / Property & stay operation
Thalassa Private Collection
Twenty-four villas across three islands. Every stay carries property readiness, owner context and the work of the local team.
Follow the walkthrough
03 / Journey & supplier coordination
Asteria Destination Management
One itinerary across Greece. Travellers, services, suppliers and live changes move with the same journey.
Follow the walkthrough
04 / Mobility & dispatch
Helios Executive Mobility
Journeys, drivers and vehicles in motion. Dispatch sees assignments, exceptions and a simulated fleet map as the day unfolds.
Follow the walkthrough
Integration philosophy
Keep what works. Custom-build what the business actually needs.
Salem Experience Design keeps useful specialist systems in place and connects them to the wider operation where it helps the team.
The purpose is not to replace everything. It is to make the whole operation work together.
Where the business has a genuine gap, Salem Experience Design can build what is missing. A proven specialist tool can remain and connect to the work around it.
Booking engines
Payment providers
Channel managers
POS systems
Accounting software
Who it is for
Growing service and experience businesses with operational complexity.
Particularly businesses where important work moves between people and systems without one clear operational view.
A good fit when
- Spreadsheets are carrying decisions they were never designed to hold.
- Email and WhatsApp have become part of the operating process.
- Manual handoffs create uncertainty, repetition, or missed detail.
- Several useful systems exist, but the operation between them is disconnected.
- Generic software would force the business to lose the way it creates value.
How the work begins
- Study the work as it happens today.
- Find the handovers that need clarity.
- Keep useful specialist tools in place.
- Define the smallest valuable scope.
- Build and refine with the team that will use it.
From Salem Experience Design
The experience outside. The operation inside.
Salem can design both the experience customers interact with and the operational systems the team works with. The same thinking about clarity, atmosphere, trust, and use continues from the public experience into the working environment behind it.
Visit Salem Experience Design
Customer-facing
The experience people see, feel, and use.
Operational
The systems the team relies on to deliver it.
Operational discovery
Tell me how your business works.
The conversation begins with your operation: where work moves, what already works, where it fragments, and how the business should work before any software is proposed.