Studio concept buildCustom business software
Quarry
An operations portal: live orders, exceptions and workload on one screen, with role-based access.
Client engagements are private under NDA. These systems are our own builds, shown to demonstrate the standard we deliver.
The problem it addresses
Past a certain size, the operation lives in spreadsheets and one coordinator’s head. Status is whatever was last pasted into the chat, exceptions surface only when a customer calls, and the weekly numbers take an afternoon to assemble by hand.
What the system does
- 01One board of live work: orders with status, owner, age and next action, filterable by branch and stage.
- 02Exceptions first: late, blocked and unassigned work sits on top, not buried in a report.
- 03Role-based access: managers see workload and totals; operators see their own queue and nothing else.
- 04The weekly numbers without the spreadsheet: throughput, cycle time and backlog, computed from the same records.
- 05An audit trail on every change, so “who moved this” always has an answer.
Stack
- TypeScript
- Next.js
- React
- PostgreSQL
- Supabase
- GitHub Actions
Architecture
Next.js on PostgreSQL with row-level security: server-rendered views over one relational schema, with an event table driving both the audit trail and the numbers.
How we build this for you