Stores, dining, and on-site services
Consumer-facing systems have to follow what actually happens in the store: who rings up the sale, who works the kitchen, who redeems the voucher. When the flow is wrong, staff go around the system and keep paper records.
A retail system has to hold up at the counter: fast scanning, permissioned price overrides, members recognised in one step. Shared stock and membership across online and in-store is the precondition for private-domain retail.
A catering system is judged during the two-hour rush: ordering has to be fast, dishes have to be right, and late tickets need an owner. Details like kitchen printing and dietary notes decide whether staff use it at all.
On-site services sell time and technicians, so booking, rostering, and redemption have to line up. Get package balances or commission wrong once and neither the front desk nor the technicians trust the system again.
Start from how the work happens today, what must change, and what stays—written as a checkable scope list.
Fix data definitions, interfaces, and the permission model, and confirm how we connect to existing ERP, finance, and hardware.
Ship module by module, integrate key flows against real data, with acceptance criteria written before work starts.
Roll out in phases, train the frontline, hand over deployment and runbooks, and keep iterating afterwards.
Tell us how the work happens today, where it breaks, and when you need it live. We will come back with a scope you can check and a phasing plan.