Skip to content

Work

What we built, and what it changed.

Client names are withheld where agreements require it. The problems, the decisions and the outcomes are real.

LogisticsField service operator

An offline-first mobile app for crews with no signal

The problem

Technicians filled in paper job sheets that were re-typed into a spreadsheet two days later, so dispatch never knew what had actually been completed.

What we did

A React Native app with a local database and conflict-aware sync, plus a lightweight dispatch dashboard on the web.

Outcome

  • Job data available same-day instead of after 48h
  • Paper job sheets removed entirely
  • Shipped to both stores in 9 weeks
  • Mobile Engineering
  • Web Platforms
SoftwareB2B SaaS company

AI triage that reads the ticket before a human does

The problem

A two-person support team was spending most of its day categorising and routing tickets rather than answering the hard ones.

What we did

Retrieval over their help centre and past resolutions, a classifier for routing, and a drafted reply a human approves before it sends.

Outcome

  • First-response time cut by more than half
  • Draft replies accepted without edits on routine tickets
  • Evaluation suite run on every prompt change
  • AI & Automation
HealthcareIndependent clinic group

Replacing three tools with one booking platform

The problem

Scheduling, reminders and payments lived in three disconnected systems, and reconciling them was somebody's entire Friday.

What we did

A Next.js platform with role-based access, Stripe billing, automated reminders and an admin console for non-technical staff.

Outcome

  • No-shows reduced by automated reminders
  • One system instead of three subscriptions
  • Staff onboarding cut to a single session
  • Web Platforms

Next step

Your project could be the next one here.

Tell us what you are trying to build. If it is not a fit for us, we will say so early and point you somewhere better.