Your Derby shop floor runs on eleven spreadsheets and a Retool app nobody documented
Custom internal tools for a Derby engineering business replace the brittle web of shop-floor spreadsheets and half-built Retool screens that hold your scheduling, inspection logging and traceability. Expect $35k to $95k and 2 to 5 months per cluster of tools. The win is moving the work that keeps the factory running off fragile spreadsheets and onto tools with validation, audit trails and roles, before a broken formula or a deleted tab takes a production cell down for a shift.
You run a precision-engineering operation in Derby, and the real operating system of your shop floor is a stack of spreadsheets: the day's job sequence, the inspection log, the gauge calibration tracker, the rework list. Retool, Airtable and the spreadsheets got you here, but they were built by whoever had time, with no validation, no permissions and no record of who changed what, and now the business depends on tools nobody owns.
The day it bites is predictable: someone sorts a column wrong and breaks the link between a serial and its inspection result, or a shared workbook locks during a shift change, and a quality engineer cannot prove which gauge measured which feature. In a city where aerospace and rail customers expect exacting records, a spreadsheet that silently loses traceability is not a convenience, it is an audit risk waiting to surface.
Why the usual tools struggle in Derby
- Critical scheduling and inspection logic lives in spreadsheets with no validation, so one mis-sort corrupts traceability
- Retool and Airtable apps were built ad hoc, with no permissions, so anyone can overwrite shop-floor data
- No audit trail of who changed a record, which fails the evidence standard aerospace and rail customers expect
- When the spreadsheet owner is on holiday, nobody else can safely change the tool that runs the cell
What a custom internal tools build changes
Custom internal tools earn their keep here because the spreadsheets already encode your real shop-floor process, they just do it dangerously. Rebuild the highest-risk ones as proper tools with field validation, role-based access and a full change log, and you keep the workflow your team knows while removing the silent failure modes that threaten traceability and stall a cell when a formula breaks.
- A spreadsheet failure or a wrong sort can corrupt traceability or stall a production cell
- Shop-floor tools have no permissions and anyone can overwrite critical records
- You cannot show an auditor who changed a record and when
- Key tools only work when one person is in, creating a single point of failure
- The tool is low-risk and a spreadsheet or Airtable base is genuinely good enough
- Your team is comfortable in Retool and the app needs no audit trail
- The process changes constantly and is not ready to be fixed in code
- You need it this week and accept the fragility for now
- Validation that stops a serial being unlinked from its inspection result by a careless sort or paste
- Role-based access so operators log and supervisors approve, with no accidental overwrites of shop-floor data
- A full audit trail of every change, giving you the evidence standard aerospace and rail customers demand
- Tools that survive the owner being away because access and logic no longer live in one person's workbook
- Built around your existing Derby shop-floor process, so adoption is fast and disruption is low
- Custom tools cost more upfront than another spreadsheet or a Retool screen someone throws together in an afternoon
- You take on maintenance for tools that used to be free, so small changes now go through a developer or a config screen
- Rebuilding too many spreadsheets at once is a trap; the value is in the few that carry real risk
- If a tool genuinely changes weekly, a flexible no-code base may still beat a hardcoded build
The features that matter for Derby
What we build under internal tools in Derby
The engagements Derby teams bring us most often:
Internal Tools pricing in Derby: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single high-risk tool rebuilt with validation and audit | $35k to $55k | 2 to 3 months |
| Cluster of connected shop-floor tools | $55k to $95k | 4 to 5 months |
| Annual support and enhancements | $8k to $20k | ongoing |
From kickoff to launch: the schedule
Exactly what you get
You get the few shop-floor spreadsheets that actually carry risk rebuilt as proper tools, with validation that protects traceability, permissions that stop accidental overwrites, and a change log an auditor can read. The rest stay as spreadsheets, because not everything needs a build. Feed the rebuilt tools into your ERP or traceability spine, lean on a business intelligence dashboard for first-pass yield, and consider a field service management tool if your team also works at customer sites.
How to choose a developer in Derby
Pick a team that asks to see your riskiest spreadsheet first and tells you which ones do not need rebuilding, because a developer who wants to replace all eleven is selling hours, not value. Insist on validation, audit logging and a clean ERP export. Avoid anyone who treats internal tools as throwaway screens with no record of who changed what on a shop floor that owes its customers exacting traceability.
- !They want to rebuild every spreadsheet at once; ask them to rank by traceability risk first
- !No audit trail in their design; ask how an auditor sees who changed a record
- !They skip permissions; ask how an operator is stopped from overwriting an approved inspection
- !No ERP export; ask how the tool feeds your system of record
- !They cannot explain genealogy across a rework; ask to see a part-split scenario before you sign
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
Which shop-floor spreadsheets should we rebuild first?
Start with the ones where a failure corrupts traceability or stalls a cell: the inspection log, the serial-to-result link, the calibration tracker. Leave low-risk lists as spreadsheets. The point is to remove silent failure modes, not to convert every workbook into software for its own sake.
Is Retool not good enough for internal tools?
Retool is fine for low-risk dashboards and quick admin screens. It becomes a liability when an ad-hoc app holds traceability with no permissions and no audit trail, which is exactly the evidence a Derby aerospace or rail customer expects you to produce on demand.
How fast can we replace one risky tool?
A single high-risk tool rebuilt with validation and an audit trail takes 2 to 3 months. A connected cluster of shop-floor tools runs 4 to 5 months. The pace depends mostly on how tangled the source spreadsheets are and how clean the data is when you migrate it.
Will operators actually use a custom tool?
They will when it mirrors the workflow they already know and removes the friction of a fragile spreadsheet. Adoption fails when a developer imposes a new process; it succeeds when the tool captures the existing one with validation and speed the team can feel.