Case study: a booking system for 40 freight depotsWe are hiring a senior backend engineer in Manchester
Start a project

One team from the first workshop to the night shift.

We take on a small number of systems and stay with them. The engineers who build your software are the ones who answer when it needs attention.

How a project runs

A typical first release takes three to five months.

  1. 01Weeks 1โ€“4

    Discovery

    We sit with the people who do the work, map the process and write down what the first release must do.

  2. 02Weeks 5โ€“8

    Prototype

    A clickable prototype tested with five to ten users, and a fixed price for the first release.

  3. 03Months 3โ€“5

    First release

    Built in two-week cycles, used by a pilot team from the first cycle, then rolled out site by site.

  4. 04After launch

    Run and improve

    Hosting, on-call and a monthly release of improvements, on a yearly contract you can end with three months' notice.

Where we fit

The kinds of systems we know well.

Bookings and scheduling

Slots, capacity, reminders and the rules that make them hard.

Logistics and stock

Depots, routes, scanning and the paperwork around them.

Internal tools

Replacing the spreadsheet that five departments edit at once.

Tell us what the process looks like today.

A short call is enough to tell whether we are the right studio for it. We reply within two working days.

Start a project
Edit this page