IMtech

Service

Platforms for restaurants and hotels

We build operations systems for venues: who came in for a shift and whether they're cleared for it, what was done during the shift, what broke and who's fixing it, what was taken from stock. Our basis is the system for restaurants and hotels (a prototype) and the café's shift and stock tracking (live).

Animation: on a venue floor plan, staff come in for their shift and take their places, ticks appear on the checklist, a repair ticket lights up by a table, and a maintenance worker walks over to it.

When you need it

Situations that bring people to us for this service.

  • The venue runs on unconnected tools

    The rota in a messenger, training in files, a breakdown reported by phoning someone.

  • Unclear whether someone may take a shift

    The manager can't quickly check whether a staff member has completed the required training.

  • Shifts are closed on a word

    What was done at opening and closing nobody sees — they only hear about it.

  • Stock without records

    Products are taken without a record, and shortages can't be explained.

What's included

  1. Venue operations analysis

    Roles, shifts, checkpoints and what gets lost between tools today.

  2. Rota and check-ins

    Publishing the rota, swaps, shift confirmation, check-ins in an app or bot, reminders.

  3. Training and clearance

    Versioned courses; a passed test clears staff for the shift.

  4. Checklists

    Opening, service, closing — with photo confirmation and incident recording.

  5. Maintenance tickets

    Priority, a response clock, a log and closure confirmed by the reporter.

  6. Stock

    Stock issues with a catalogue, quantity, unit and photo.

  7. Manager's back office

    Who's on shift, who hasn't checked in, what needs a decision today; a role builder.

What you get

  • A description of the venue's roles, shifts and rules
  • A prototype of the end-to-end shift scenario
  • Apps for staff and the maintenance team
  • A manager's back office
  • Code and documentation that are open to you

The project path

From the first conversation to daily use

Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.

  1. 01

    Getting to know the task

    You describe the process and what gets in the way. We reply by email with questions and arrange a call.

  2. 02

    Discovery

    We study the process with the people who work in it and write down what the system must change and how we will check it.

  3. 03

    Prototype

    We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.

  4. 04

    Pilot

    We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.

  5. 05

    Launch and growth

    We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.

Systems where we have already done this kind of work.

Technology in these case studies

  • Expo
  • React Native
  • Next.js
  • Telegram Bot
  • Telegram Mini App
  • PDF

Questions about this service

Does this suit a chain of venues?

The system for restaurants and hotels was designed for café and restaurant chains, hotels and catering. How to split venues and roles in your case we decide during discovery.

Can we start with one module — shifts, say?

Yes. The café started with shift check-ins in a Telegram bot and stock issues.

What stage are these systems at?

The café's shift and stock tracking is live with the client. The system for restaurants and hotels is a prototype: the apps and back office run on demo data.

Have a project with no ready-made solution?

Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.

Get in touch