All work

Custom business software · 2026

Combined Management System

Restaurant operations and workforce management, connected in one platform.

RoleDesign & build
ScopeTwo platforms combined — operations, workforce, money and stock
ScreensEight owner and manager screens shown
Year2026
Scroll to see the full screen
OWNER DASHBOARD

Context

Most small businesses run on four or five separate things at once: a billing screen, a stock book, an attendance register, a payroll sheet and a notebook for the day’s money. They do not talk to each other, so the same numbers get written down three times and nobody trusts any of them.

This platform was built around the way the business actually works, not around the way software usually gets sold. The strongest workflows from two existing systems — restaurant operations and workforce management — were combined into one connected platform, with separate owner and staff experiences on top of the same data.

Band A — the combination

Two systems, combined into one.

The strongest workflows and features from two existing systems, brought together into one connected platform and tailored to the business. Restaurant operations on one side, workforce and business operations on the other.

Scroll to see the full screen
RESTAURANT OPERATIONS — MANAGER DASHBOARD
Scroll to see the full screen
WORKFORCE & BUSINESS OPS — OWNER DASHBOARD

= One customised management platform

Band B · Platform 1 — restaurant operations

Everything needed to run the floor, sales and stock.

Dashboard, POS and billing, KOT, menu, inventory, staff and reports, and settings — the seven things a manager touches during service, behind one login.

  • Today’s sales, orders today, open orders and low stock items at a glance
  • Payment split across cash, UPI and card
  • Top five items today, and a low stock panel that names what is running out
Scroll to see the full screen
MANAGER DASHBOARD

Band B · sales, menu and stock

Order taking, pricing and ingredient stock in the same system.

Billing draws down the ingredients the menu item is made of, so the stock figures are a by-product of the service rather than a separate evening job.

  • POS: searchable menu (press “/”), New Order (F2), category filters, tap-to-add cards priced in ₹
  • Menu: item, category, price, GST, recipe, availability, edit and delete
  • Inventory: stock, low threshold, cost, ingredient and package views, history
Scroll to see the full screen
POS / BILLING

Band B · screens

Menu and stock, managed in place.

Band C · Platform 2 — workforce and business operations

People, attendance, shifts, payroll and the day’s money.

Overview, attendance, income and expense, shifts, payroll, inventory and staff. The owner opens one screen in the morning and can see the whole day.

  • Income today, expense today, net for the day, staff on floor
  • Income versus expense over the last 14 days
  • Low stock listed with quantity against threshold
  • Today’s roll call with a status against each person, and net for the month
Scroll to see the full screen
OWNER DASHBOARD

Band C · attendance, shifts and payroll

From the daily register to the weekly rota to what each person is paid.

The register feeds the rota and the rota feeds payroll, so absences are already counted by the time the month closes.

  • Attendance: present, late, absent and weekly off, with mark-all-present and per-person marking
  • Shifts: a weekly rota across morning, evening and night with staff assigned per day
  • Payroll: gross pay, advance deductions, net payable per employee and a mark-paid action
Scroll to see the full screen
ATTENDANCE

Band C · screens

The rota, and what it pays out.

Band D · business income, expense & inventory

The money side and the people side, in the same place as the operations side.

Daily income and expense entries with a running net, employee presence, and stock tracked against reorder thresholds. This is part of this system’s scope — not a separate product — which is exactly the point: the numbers come from the work rather than from a second app someone has to remember to update.

  • Daily income and expense entries, with net for the day and net for the month
  • Employee presence carried through from the same register that drives payroll
  • Stock held against a low threshold, so reordering is a list rather than a guess
Scroll to see the full screen
INCOME, EXPENSE & NET FOR THE DAY

Band D · screens

Stock, tracked against what it should be.

Band E — owner and employee experiences

Two sides of the same system.

The owner sees the whole business. Each employee sees only their own day — what shift they are on, whether they have been marked in, what still has to be done and what they are being paid.

  • HomeThe employee’s own starting screen for the day.
  • AttendanceTheir own attendance record, as marked on the register.
  • ScheduleThe shifts they are assigned to in the weekly rota.
  • ChecklistThe tasks attached to their shift.
  • PayslipTheir own pay for the cycle, from the payroll run.

Described as scope rather than shown: there are no screenshots of the employee side in the source material, and a portfolio is not the place to invent one.

Band F — why it matters

Billing, stock, staff and money in one place.

One shared computer at the counter. Separate logins for the owner and for staff, so the person taking an order does not see the payroll. Data stored locally on the machine that runs it.

It was built to be used during service — while orders are coming in and the floor is busy — not filled in after hours. That is why billing, the stock that billing draws down, the register that decides payroll and the day’s money all sit behind the same login instead of in four different books.

What was delivered

  • Product design
  • UI/UX design
  • Front-end build
  • Responsive layout
  • POS & billing
  • Inventory
  • Attendance & shifts
  • Payroll
  • Income & expense
  • Owner and employee experiences
  • Reporting

Technology note

Front end

A responsive, component-driven interface built and handed over end to end. The same table, card and filter components are reused across every module, which is why nine screens look like one system.

Access

Separate owner and staff logins over the same data, so the person taking an order does not see payroll.

Data

Data is stored locally on the machine that runs it, at the counter.

Not claimed

No usage figures, employee counts or results are given anywhere on this page, because none were measured. What is shown is the scope of the system and the screens that exist.

Next project

TMR Expense Tracker

View case study

Start a project

Tell me what you're trying to build.

Send a message with what your business does and what you need. I'll reply with what it would take, how long, and what it costs.

WhatsApp Enquire