Three people editing the firing spreadsheet at once is not a kiln scheduling system
A custom internal tool for a Stoke-on-Trent operation runs $25k to $80k over 2 to 5 months. You build it when the spreadsheet or Airtable base that runs your firing schedule, dispatch list or seconds log has become load-bearing, gets edited by three people at once, and breaks the day someone deletes a column.
Retool and Airtable get a Potteries firm a long way. The kiln schedule starts as a Google Sheet, the dispatch list as another, the seconds log as a third. It works until it doesn't: two supervisors edit the firing rota simultaneously, a formula gets pasted over, and suddenly a load is booked into a kiln that's already full. The tool that was supposed to save time now needs a person to babysit it.
The deeper problem is that these tools don't talk to anything. Your firing spreadsheet doesn't know what the store sold, your dispatch sheet doesn't know what was graded as seconds, and your seconds log doesn't feed your accounts. Each is a silo with a single point of failure, and that failure is usually the one colleague who understands the macros and is on holiday the week you need them.
Why the usual tools struggle in Stoke-on-Trent
- The firing-schedule spreadsheet has no record locking, so simultaneous edits overwrite each other
- Dispatch, seconds and scheduling tools are separate sheets that never reconcile
- One colleague owns the macros and the whole operation stalls when they're away
- No audit trail, so when a load goes to the wrong kiln nobody can see who changed what
What a custom internal tools build changes
A custom internal tool replaces the fragile sheet with a proper application: record locking so two supervisors can't double-book a kiln, role-based access so the right people edit the right things, an audit trail so mistakes are traceable, and live links to your ERP (Enterprise Resource Planning) and inventory so the firing schedule reads from real stock. It's the difference between a tool that needs constant nursing and one that quietly runs the floor.
- A spreadsheet has become critical and breaks under concurrent edits
- The same tool runs scheduling, grading and dispatch but none of them reconcile
- Only one person understands the macros and that's now a business risk
- You need an audit trail because mistakes are expensive and untraceable
- The workflow is genuinely simple and Airtable's locking is enough
- Only one or two people ever touch the tool and conflicts don't arise
- You can live within Retool's limits without custom logic
- There's no need to integrate with production or finance systems
- Concurrent editing without overwrites, so multiple supervisors can schedule firings safely
- Role-based access that stops the wrong person changing a booked kiln load
- A full audit trail of who scheduled, graded and dispatched what, and when
- Live connection to your ERP and inventory so the schedule reflects real stock
- No single colleague holding the operation hostage with undocumented macros
- A bespoke tool costs more upfront than a Retool app you can stand up in a day
- Simple tweaks that a spreadsheet-literate staffer could make now need a developer
- You take on hosting, backups and security that a SaaS would otherwise handle
- Over-building is a real risk if the workflow is genuinely simple enough for Airtable
The features that matter for Stoke-on-Trent
Internal Tools services we deliver in Stoke-on-Trent
Digital Heroes builds the full internal tools stack for Stoke-on-Trent teams. Typical engagements cover internal portal, business process automation, data-entry tools, admin panel development and internal dashboards.
Internal Tools pricing in Stoke-on-Trent: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single internal tool (kiln scheduler or dispatch board) | $25k to $45k | 2 to 3 months |
| Integrated tool suite linked to ERP and inventory | $45k to $80k | 3 to 5 months |
| Multi-site operations platform | $80k+ | 5 to 8 months |
From kickoff to launch: the schedule
Exactly what you get
You get the spreadsheet's job done properly: a kiln-scheduling and dispatch tool with record locking, role-based access and a full audit trail, wired to your ERP and inventory so it reads real stock instead of a stale copy. Shop-floor staff log firings from a tablet, supervisors can't double-book a kiln, and when something goes wrong you can see exactly who changed what. It typically sits alongside a custom ERP and an inventory management system, replacing the fragile sheets that bridge them today.
How to choose a developer in Stoke-on-Trent
Find a developer who'll resist the urge to over-build. The best ones look at your spreadsheet, work out which two or three workflows are genuinely load-bearing, and replace exactly those with something robust. Ask how they handle concurrent edits, what the audit trail captures, and how the tool stays in sync with your production and stock systems. A team that knows the six-towns pace of family firms will keep the interface plain enough that a supervisor who lived in Excel feels at home on day one.
- !They suggest a no-code tool for a workflow that already broke a no-code tool; ask why this time differs
- !No mention of concurrency or locking; ask how two supervisors editing at once is handled
- !No audit trail in the plan; ask how you'll trace a double-booked kiln
- !They skip integration; ask how the tool reads live stock from your ERP
- !No mobile consideration for shop-floor staff; ask how someone away from a desk records a firing
If internal tools is on the roadmap, custom software, wordpress, accounting usually follow within the year. Budget them as one conversation.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Isn't Retool or Airtable cheaper than a custom tool?
Upfront, yes. But you came to this page because a no-code tool already failed under real use: simultaneous edits, no locking, no audit trail. If the workflow is critical and breaks under load, the cheap option is costing you more in errors than a robust build would.
What makes a spreadsheet 'load-bearing'?
When the business stops if it breaks. A firing schedule that three supervisors depend on, that books kiln loads and feeds dispatch, is load-bearing. The day someone deletes a column or two people edit at once, you've lost production. That's the moment to replace it with a real tool.
Can the tool connect to our other systems?
It should. A custom internal tool's main advantage over Airtable is that it can read live stock from your ERP and inventory and write back grading and dispatch results, so everything reconciles. A standalone tool that doesn't integrate is just a sturdier silo.
Will shop-floor staff actually use it?
If it's built for them, yes. That means mobile-friendly entry so someone at the kiln can log a firing from a tablet, plain screens, and no fiddly logins. The fastest way to kill adoption is to build for the office and ignore the floor.