Custom Software

Off-the-shelf programs assume a way of working and try to fit the business to it. We do the opposite: first we map out your flow, then we build the system that runs it.

What it solves

Most businesses running on a packaged product end up in the same place: the work the program cannot handle moves into Excel, and before long those spreadsheets become the real system. What is lost is not the price of the program but a scattered single record.

• Is a step that is routine in your business treated as an exception by the package
• Who signs off, and does the system know it or does it run over the phone
• How many separate places hold the same information, and which one counts as correct

We put the scope in writing from the start: what is in this release is as clear as what is not.

How we build it

First we map out how the work actually runs — where each piece of information comes from, who approves what, where it stalls. The screens are built on top of that map; the person using them is not learning a new order of things, they see the work they already know on the screen. A first working version is in your hands before long, and it moves forward on your feedback.

Scope

• Internal systems shaped by your workflow — Quoting, approval, production or service tracking; whichever flow you have.
• Field, warehouse and dealer apps — Screens that work on phone and tablet for the team that is not at a desk.
• Renewing existing software — Moving to a new system with the data carried over from the one used for years.
• Go-live and what follows — Training, the switch to daily use and the development afterwards continue with the same team.