Stock, contracts and orders — prototyped in two days.
Silbury Marketing moves £100m of food ingredients a year on Sage 200 and a shared Excel control sheet. They sent us a scoping document; we sent back a clickable prototype of the database that replaces it — designed in Figma with AI, delivered alongside the quote.
Built straight from their own scoping document.
A £100m business,
run on a shared spreadsheet.
Silbury Marketing supplies industrial tomato, pizza sauce, vegetable oils, boxed fats and cooked protein to more than 450 customers across the UK and Europe — around £100m of turnover, 40 suppliers, three third-party warehouses and a 41-person team in Banbury.
Sage 200 handles the accounting, but it cannot manage contracts, has no materials planning and no workflow. So stock records, contract drawdown and delivery tracking all live in Excel. A single control sheet — open to several people at once — holds every order placed, and gets archived and rebuilt every few months once it grows too large to stay stable. There is no validation, so formats drift and columns get mixed.
With a move to SAP4HANA still eighteen months out, Silbury needed a dependable interim home for its most business-critical data. Their scoping document set out the requirement in detail. We prototyped it.
Four decisions behind the prototype.
The scoping document described three spreadsheets. The prototype models them as one system — with the phase-two reporting and the eventual ERP migration already accounted for.
One record, not three sheets
The control sheet, contract progress records and stock sheets were modelled as a single relational structure, so an order entered once flows through to stock balance, contract drawdown and delivery tracking.
Contracts that track themselves
Every contract gets a live progress record — quantity, drawdown, current balance and a full delivery log — replacing the per-contract spreadsheets finance was reconciling by hand.
Stock across three 3PLs
Warehouse views show value, tonnage and utilisation per site, with batch numbers and best-before dates surfaced so expiry is visible long before it becomes a quarantine problem.
Built for Power BI, and for SAP
Structured for phase-two reporting from the start, with Excel, CSV and Power BI exports — and a data shape designed to migrate cleanly into SAP4HANA later.
What the screens show.
Something to react to,
not just read.
Instead of a written proposal, Silbury got a working interface built from their own scoping document — their product names, their contract references, their warehouse structure. The kind of thing a team can point at and say “that column should sit there instead”.
Two days from brief to clickable prototype, delivered alongside the quote.
Operations dashboard with live stock, contract and order status
Batch expiry and late-delivery alerts surfaced on landing
Order register filtered by type, customer, status and contract
Contract progress records with automatic balance calculation
Warehouse views across all three 3PL sites, with utilisation
Quarantine tracking for batches held back from sale
Report library with Excel, CSV and Power BI export
Global search across contracts, orders and customers
Two days, brief to prototype.
Scoping document in
Day 0
Structure & screens
Day 1
Clickable prototype delivered
Day 2
What the prototype was built with.
Designed in Figma, with AI doing the heavy lifting on structure and screen generation.
FigmaGot a spreadsheet you are trying to replace?
Send us the scoping document, or just the problem. We will turn it into a clickable prototype you can put in front of your team — normally within a few days.
Questions, answered straight.
Have an outcome in mind?
We'll help you
ship it.
- You're building a data product and need a team that can deliver.
- You want to get AI-ready — pragmatically, not theoretically.
- Your reporting is a mess and you need a real platform underneath it.