Start from the problem, not the technology

Most people arrive knowing what is going wrong rather than what they need built. Here is the shape of what we usually hear, and what answers it.

“Everything runs on spreadsheets”

Stock lives in one file, sales in another and neither agrees with the invoices. We replace the sprawl with one system that the whole team works from.

“Customers ask the same questions all day”

The answers are written down somewhere, and somebody still has to type them out forty times a day. We put an assistant in front of the repetitive ones and a person in front of the rest.

“We can't see what's happening in the field”

Machines, vehicles and sites that only report a problem when somebody phones in. We build the sensors, the firmware and the link back to a dashboard.

“It works fine until it gets busy”

The system was built for last year's volume. We rework the architecture so growth is a configuration change rather than a rewrite.

“We don't know what to build”

Everyone agrees something needs to change, nobody agrees what. We work out what the problem actually is and what solving it would take, before anyone commits to building.

“Nobody is looking after it”

The person who built it has moved on. We take responsibility for keeping it running, patched and moving forward.

Have something that needs building?