Fixed price
Agreed before anything starts. You know the number on day one, and it doesn't move because the work turned out to be harder than we thought. That's our risk, not yours.
Leeds, UK · Warehouse & SAP tooling
Most warehouse and production teams run something critical on a shared spreadsheet, a WhatsApp group, and somebody's memory. We build the missing piece — properly, once.
FIG. 01 Racking bay — 3 × 4 × 2 slots
01 — The problem
The stock file has a version number in the name, and the live one lives on someone's desktop.
Every number is typed twice — once in the sheet, once in SAP. Friday afternoon is copy-paste afternoon.
Nobody fully trusts it, so everyone keeps their own version. Now there are four versions of the truth.
The moment two people need the same answer at the same time, the spreadsheet has stopped being a tool and started being a liability.
02 — What we build
SAP knows the bill of materials. It does not know that Andy is half way through building kit 4471, that it's short two copper busbars, and that his shift ends in twenty minutes.
We track the kit as a physical thing: who is building it, how far they have got, what is missing, and who picks it up at handover. Two orders from the same sales order can be kitted together as one physical kit with one label and one shortage note. When a kit is delivered to the line, the line confirms it.
Log a line-stop in thirty seconds. One live record everyone can see, instead of four people hunting the same pallet without knowing the other three are looking.
Daily counts on a phone. Variances flagged the same day, while the cause can still be found — not discovered at year end when the trail has gone cold.
Delivery slots and GRN status in one place. No surprise wagons at the gate at four o'clock on a Friday, and no stock sitting unreceipted where the system can't see it.
Find the broken records — missing units of measure, duplicate materials, orphaned batches — before they break your go-live rather than after.
Not on the list? It's usually still the same job: a process that lives in somebody's head needs to live somewhere the whole team can see it.
03 — How we work
Agreed before anything starts. You know the number on day one, and it doesn't move because the work turned out to be harder than we thought. That's our risk, not yours.
Small tools, shipped. You'll have something your team can actually open and use while a traditional project would still be in requirements-gathering.
We fit the way your team already works rather than asking twelve people to change their habits for a piece of software. The tool adapts. Not the warehouse.
No per-user licence, no annual contract, no vendor lock-in. You own the tool and the data it holds, and you can hand it to anyone to maintain.
04 — Evidence
None of this is a concept. The kitting and shortage system runs at a manufacturing site where a missing part stops the line, and where the first fifteen minutes of every shortage were being lost to walking the floor and messaging people who didn't have the answer.
Type a production order and it fills itself in from the SAP export — sales order, line, product type, quantity. The kitter works the kit, adds shortages as they hit them, and hands over mid-build if the shift ends first. The line confirms the kit when it arrives.
05 — Get in touch
No pitch deck and no discovery phase. Describe the job that keeps landing in a spreadsheet, and we'll tell you honestly whether it's worth building — and what it would cost.
rodrigo@burlesystems.co.ukBased in Leeds. Working with small and mid-sized businesses across the UK.