Systems / Specifications
Systems we build
Five families of internal system. Choose a tab to read its specification.

Operations systems
A database-backed application tracking jobs, orders, stock or assets through defined states. Screens for each role, search, filters, audit history and exports. Typical replacements: the master spreadsheet, the whiteboard and the job book.
- Defined states and transitions
- Role-based screens
- Audit history on every record
- Import from existing spreadsheets
- CSV and PDF exports
Workflow automation
Scheduled or event-triggered jobs that move and transform data between your existing tools: accounting, CRM, email, storage and e-commerce back offices. Every run is logged; failures alert a named person.
- Documented API connections
- Retry and failure alerts
- Run log you can read
- Configuration not hard-coding
- Manual override path
Approvals and requests
Forms that route requests to approvers based on your rules, such as amount, department or type, with reminders, delegation for absence and a permanent record of decisions.
- Rule-based routing
- Delegation and reminders
- Decision log
- Email notifications with direct links
- Monthly summaries
Scheduling tools
Allocation of people, vehicles, rooms or equipment with conflict detection, availability, and a shared calendar view. Exports to staff calendars where useful.
- Conflict detection
- Availability rules
- Shared views by resource
- Calendar export
- Change history
Reporting pipelines
Automated collection of figures from several systems into a consistent dataset and a scheduled report, replacing the Monday morning copy-and-paste.
- Source-by-source extraction
- Validation checks
- Scheduled delivery
- Clear definitions of each figure
- Archive of past reports
Common to every system
Accessible interfaces usable by keyboard and screen reader. Sign-in through your existing accounts where possible. Backups and a tested restore. A plain-English operator manual and technical documentation. Hosting in your own cloud account.
Inputs we need
Real examples, including the awkward ones; access to test versions of the tools we connect to; a process owner with authority to decide; and a few hours of staff time each fortnight to try releases.