Independent software studio · Taking on new work

Software that
actually holds up

Most of what a company runs on is unglamorous: admin panels, dispatch boards, reconciliation screens. We build those properly — fast to use, hard to break, and still maintainable two years in.

01 — What we build

Four kinds of work, one team

01

Internal tools

The admin panels, dispatch boards and review queues the business runs on every day. Designed for someone using them eight hours straight, not for a screenshot.

  • Admin interfaces
  • Workflow design
  • Permissions
  • Bulk operations
02

Data & integrations

Connecting systems that were never meant to talk to each other. Imports, syncs, reconciliation, and the audit trail that makes them trustworthy.

  • ETL
  • API integration
  • Reconciliation
  • Audit trails
03

Front-end engineering

The layer people actually touch. Performance budgets, state that doesn't drift, and a component layer that survives the fifth feature request.

  • TypeScript
  • Performance
  • Design systems
  • Accessibility
04

Long-term maintenance

Software rots quietly. Monitoring, dependency upkeep and small steady iterations keep it from becoming something nobody dares touch.

  • Monitoring
  • Upgrades
  • Iteration
  • Handover
02 — Capability

Where the time goes

Internal tools
94%

The screens people live in all day deserve the most care.

Data & integrations
89%

Most “UI bugs” turn out to be data problems.

Front-end
92%

Performance is a feature, not a cleanup task.

Maintenance
88%

Software you'd still take over is software that holds.

03 — Selected work

Some things we've built

Case 01 / 2026

Logistics dispatch console

Dispatchers were running the day off a whiteboard and three spreadsheets. We built a live console with route state, driver availability and exception flags on one screen — the whiteboard came down within a month.

Realtime UIState modellingTypeScript
Case 02 / 2026

Insurance claims workflow

A claim moved between six people and four inboxes, and nobody could say where a file was. We made every claim a single object with a visible stage, a named owner and its full history.

Workflow designPermissionsAudit trail
Case 03 / 2025

Retail store audit app

A field team of ninety was photographing shelf conditions and emailing them in. We shipped an offline-first app that works in a basement with no signal and syncs the moment it finds one.

Offline-firstMobile webSync
04 — Start a project

Got a system
nobody wants to touch?

Tell us what it does today, who depends on it, and what breaks. No proposal needed first. We reply within two working days and say straight whether it's worth rebuilding or repairing.