Digging in
Before anyone writes code, we look at how the work actually runs today. Not at a meeting table, but where it happens: at the planning desk, in the warehouse, behind the counter or in the van.
What comes out of that is almost never what the brief said. Usually half the problem turns out to sit somewhere else, and two things turn up that you can fix without software at all.
What we do
One to three weeks, depending on how many systems are involved.
- Spend a day or two alongside the people doing the work.
- Go through the systems already in place: what can go, what stays.
- For existing software, a code scan: what state is it in and what would taking it over cost.
- Map the exceptions, because that is where the complexity lives.
- Set an order: what delivers the most, first.
What you get
- A written account of how the process runs today, in plain language.
- A list of what we would build, ordered by what it returns.
- A price indication per item, saying where the uncertainty sits.
- An honest recommendation if an existing package would do the job.
What we need from you
- A day of access to the floor and the people who work there.
- Read access to the systems involved.
- Someone who can decide on the order.