CUSTOM SOFTWARE — BUSINESS APPS
The spreadsheet that runs the business no longer keeps up.
The spreadsheet worked at four people. At fifteen it is a liability: one person owns it, nobody trusts the version they have open, and the business is making decisions from a file that was accurate on Tuesday. This is a system built around how the work actually moves — jobs, people, assets, customers, money.
Free · 20 minutes · no commitment
WHO THIS IS FOR
Operations that outgrew the spreadsheet two years ago and have been patching around it since.
THE PROBLEM
It degrades in a particular direction: the spreadsheet grows to fit, so the pain never spikes hard enough to force a decision. Businesses run on them years past the point of sense. The real cost is the questions nobody bothers asking any more, because getting an answer takes an afternoon.
WHAT IT LOOKS LIKE
Plant system
Go-live check · Monday, 6:00 am start
SPREADSHEET FROZEN FRIDAY 5:00 PM · COUNTS CHECKED SATURDAY 10:20 AM
Moved from the spreadsheet
Products and recipes
- Spreadsheet
- 64
- New system
- 64
- Difference
- None
Customer accounts
- Spreadsheet
- 212
- New system
- 209
- Difference
- 3 duplicates, Anita to confirm
Open orders
- Spreadsheet
- 47
- New system
- 47
- Difference
- None
Supplier certificates
- Spreadsheet
- 118
- New system
- 118
- Difference
- None · 5 expired, flagged to QA
Lot records, last two years
- Spreadsheet
- 3,906
- New system
- 3,906
- Difference
- None
| Records | Spreadsheet | New system | Difference |
|---|---|---|---|
| Products and recipes | 64 | 64 | None |
| Customer accounts | 212 | 209 | 3 duplicates, Anita to confirm |
| Open orders | 47 | 47 | None |
| Supplier certificates | 118 | 118 | None · 5 expired, flagged to QA |
| Lot records, last two years | 3,906 | 3,906 | None |
Who sees what
Anita · operations manager
Everything · owns the system on your side
TrainedLine leads · 4
Their own line’s batches and allergen changeovers · cannot change a recipe
TrainedQA · 2
Release or hold any batch · supplier certificates
TrainedOffice · 3
Orders, customers and invoices · no recipe access
TrainedShipping · 2
Today’s orders and the lot codes to pick
Trained
12 PEOPLE · 5 ROLES, SET UP THE WAY THE PLANT RUNS
Before Monday
Done: Every count matches, or the difference has a reason
One difference: 3 duplicate customers
Done: Each role trained on its own screens
12 people, Tuesday to Friday
Done: Spreadsheet set to read-only and kept
Not done: Anita confirms the duplicates and signs off
Before Monday, 6:00 am
The code, the documentation and the hosting account are in your name. A support window starts at go-live.
What you get.
- A system modelled on your operation, not a template with your logo on it.
- Roles and permissions matching how the business is really organised.
- Migration of the data you already hold, reconciled before go-live, not after.
- Source code and documentation handed over. You own what we build.
- A support window after launch, because the first month of real use is when the gaps appear.
How it works.
Priced against the scope, after a Diagnostic that is small on purpose. The shape of the work we can tell you now.
- THE SHAPE
- A build with a defined handover. Support afterwards is optional and quoted separately.
- WHAT WE NEED FROM YOU
- An internal owner with authority to decide, available throughout, not only at the end.
- WHAT YOU KEEP
- The code, the documentation and the infrastructure, all in your own accounts.
What this does not include.
Published because you should know before the call, not after the invoice.
- Rebuilding what an existing product already does well. We will tell you to buy instead.
- A build with no internal owner. Somebody on your side has to hold it.
- A system nobody was trained on. Handover includes the training or it is not handover.
QUESTIONS
Why build when you could buy?
Usually you should buy, and we will say so. Building is right when the way you work is a real advantage worth protecting, or when every product on the market forces a change you cannot make.
What if we stop working with you?
You keep the code, the documentation and the infrastructure, because they were in your accounts the whole time. Another team can pick it up, and we will talk to them.
MORE UNDER CUSTOM SOFTWARE
Bring us one bad week.
Book a pilot call. Tell us where the week goes wrong, and we’ll tell you what an Operations Diagnostic would map and measure.
The first paid step has a clear scope and an end date, and the pilot after it is one workflow — not a platform, and not an open-ended retainer.
Free · 20 minutes · no commitment