Services Custom Web Applications

When the spreadsheet stops coping, we build the thing that replaces it.

Every operator has one process that no product covers properly. It lives in a shared spreadsheet, three people edit it at once, and once a month it costs someone a day of their life. That is what this is for.

Fixed quote before any work starts
You own the code and the data
Built on the platform you already run

What we build

The usual suspects

These come up again and again. If yours is not here, it is probably still something we have built a version of before.

Central kitchen and commissary

One kitchen producing for six branches, each ordering daily, each with different quantities. Orders in, production sheets out, delivery notes at the end.

  • Branch ordering with cut-off times
  • Production sheets by item
  • Transfer notes and costing

Catering and event quoting

A quote builder that prices a hundred-head event correctly, sends a proper PDF, takes a deposit and puts the date in the calendar.

  • Per-head and per-item pricing
  • Deposits through KNET
  • Quote to invoice in one flow

Staff scheduling and shifts

Who is on, who swapped, who is over their hours. Published to phones rather than pinned to a wall in the back corridor.

  • Rota published to staff phones
  • Swap requests with approval
  • Hours totalled per period

Stock and supplier ordering

What is in each branch, what is running low, what to order from whom. With costs attached so you can see where the margin went.

  • Stock levels per branch
  • Purchase orders to suppliers
  • Recipe costing against sales

Reporting across branches

One screen showing all six branches side by side, in the shape your accountant actually asked for, sent automatically every Sunday.

  • Consolidated multi-branch view
  • Scheduled email reports
  • Export to Excel or your accounts system

Connecting what you already run

Your accounting package, your POS, your payroll. Most have an interface; we make them talk to each other so nobody retypes anything.

  • POS and accounting integrations
  • Data imported on a schedule

How it goes

From spreadsheet to something that holds

A real example

A group with five branches ran their central kitchen on one shared spreadsheet. Branches sent orders on WhatsApp at midnight, one person typed them in at six, and roughly once a week a branch got the wrong quantity of something. Now branches order on a phone before the cut-off, the kitchen prints one production sheet, and the typing at six in the morning does not happen.

  • Four weeks from first conversation to live
  • One screen replaced eleven spreadsheet tabs
  • Ordering errors down to almost none
  • Two hours a day of retyping gone
WAS Orders by WhatsApp nightly
WAS Manual retyping 2 hrs/day
NOW Branch ordering self-serve
NOW Production sheet automatic

It sits on top of what you already have

Because your menu, guests and orders are already in Zideira, a custom build starts from real data instead of an empty database. A catering quote can price from the menu you already maintain, and an event booking can land on the same floor plan as everything else.

  • Reads the menu you already keep
  • Shares one guest list with the rest
  • Same login and permissions for staff
  • No second system to keep in step
MENU Shared with QR menu yes
GUEST Shared guest list yes
LOGIN One staff account yes
SYNC Duplicate data entry none

How it works

The arrangement

We start by watching

Before anything is quoted we sit with whoever does the job now and watch them do it. Half the time the answer turns out to be simpler and cheaper than what was originally asked for.

  • A conversation, not a form
  • Honest advice about whether to build at all

A fixed price before we start

You get a written scope and a fixed quote. If the scope grows we quote the change separately — the number does not quietly drift.

  • Written scope and fixed quote
  • Changes priced separately
  • Payment against milestones

You own what we build

The code and the data are yours. If you stop working with us you keep both, and anyone competent can pick it up.

  • Source code handed over
  • Data exportable at any time
  • No lock-in clause

Arabic and English, as standard

Anything your staff or your guests touch works in both languages, with proper right-to-left layout. Not an afterthought at the end of the project.

  • Bilingual from the first screen
  • Kuwaiti dinar to three decimals

Questions

About custom work

It depends entirely on the scope, so any number quoted before we have understood the job would be dishonest. Small tools that replace a single spreadsheet are usually a few hundred dinar; a full central kitchen system is considerably more. You get a fixed quote before committing to anything.

Small tools, two to three weeks. Something the size of a central kitchen system, six to ten. We would rather give you a slower date we can hold than a fast one we cannot.

No, though it is usually cheaper if you do, because the menu, guests and staff accounts already exist. We do build standalone applications for businesses that run their menu elsewhere.

You can take it and maintain it yourself, or keep us on a support arrangement. Either way the code is handed over — that is not conditional on continuing to pay us.

Yes. If an existing product does the job for thirty dinar a month, we will say so rather than quote you three thousand to rebuild it. That happens more often than you would expect.

Tell us about the spreadsheet.

Describe the process that is currently held together by one file and one person who understands it. We will tell you what it would take to fix, or whether it is worth fixing at all.

Request a quote