Decided once, and every product is held to it.
A five-product register is only credible if the fifth product does not have to re-learn offline sync, signatures, data residency and exports. These are the decisions Logic makes once — before a product is specified, never per feature.
All of it is in production in Logic SAT today. Products marked In development or Planned inherit these standards as requirements.
The field is the hard case, so we design for it first.
Hospitality software fails in the same three places: a basement with no signal, a phone nobody wants to install anything on, and a document somebody later disputes. Everything else is easier than those.
- Offline is the normal case
- Field apps hold their work locally and reconcile when the connection comes back. A job started in a cold room finishes in a cold room — no spinner, no lost hour, no "try again upstairs". Sync is a background detail, never a step the user has to perform.
- Installs from a QR code
- Any Android or iPhone with a browser. Staff scan a code and the app is on the home screen the same afternoon: no store account, no device-management policy, and no fleet of company phones to buy before the software can be tried.
- Signed documents are closed
- The moment a customer signs on screen, that document stops being editable. A correction is a new version carrying its own signature, and the superseded one stays readable. An audit trail is only useful if nothing behind it can be edited afterwards.
- Records keep their history
- Rates, tariffs, settings and prices are versioned. Change a rate today and every document signed last year still says what it said last year —
Where the data lives, and who can see it.
The company is registered in Dubai. The data is not. Customer data for our products is stored in the European Union, because that is where our customers and their guests are.
- EU residency, GDPR rights in-product
- Access and erasure are functions inside the application. A customer can answer a subject request without opening a support ticket with us.
- Location is stamped twice
- Where a product records position, starting and finishing a job, it records exactly those two moments. Continuous tracking of staff is not a feature we build, and it is not one we will add on request.
- One screen per job
- Owner, office, field, client. Each role gets the screen for its job and nothing more, and every change is attributed to a person and a moment. The client role is deliberately narrow: your customer sees their own jobs, never your business.
- White label by default
- Documents, portals and notifications carry the customer's brand, not ours. If our name appears in front of your client, we have made a mistake somewhere.
We build the exit before we build the front door.
Every Logic product exports its data in full, in formats the rest of the building already reads. Month-end leaves as CSV for Holded, Sage or a3. Structured data is available over an API. Documents are PDFs you can keep.
This is not generosity, it is the only honest way to sell software to a small operator. A tool that is painful to leave will eventually be kept for the wrong reason, and we would rather be kept for the right one.
What leaves the building
- Monthly close as CSV, mapped to the accounting system in use
- Signed documents as PDF, with their signatures and photos intact
- Master data — clients, machines, rates — as structured files
- An API for the parts a customer wants in their own systems
Keeping it running.
A small house has to be honest about operations. Here is what we do, stated plainly, with no certification badges we have not earned.
Backups and recovery
Production data is backed up on a schedule and restores are practised. Recovery is a procedure somebody has actually run.
Versioned releases
Changes ship in versioned releases with a record of what changed. Nothing reaches production that has not run against real data in a staging environment first.
Monitoring and response
Availability and errors are monitored. When something breaks, customers hear it from us — we would rather send an awkward email than have an operator discover it mid-service.
Two languages, one product
Our products are built to work in Spanish and English rather than translated once and left. Dates, currencies and tax wording follow the operation.
Readable in bad light
Field apps are used in dim plant rooms and bright terraces by people who are not sitting down. Type stays large, targets stay big, and nothing important is signalled by colour alone.
Support from people who know the job
Questions are answered by the same small team that builds the product, and by an operations group that has stood where the question came from.
Want the technical detail?
Security questionnaires, data-processing agreements and integration questions go to the same address as everything else, and they are answered by someone who can actually answer them.