The spreadsheet macro running your Wrexham despatch desk is one broken formula from a bad day
A custom internal tool for a Wrexham operation runs £20,000 to £70,000 over 6 to 16 weeks, depending on how many real-world things it has to touch. Retool, Airtable, and a clever spreadsheet get you surprisingly far, right up until the tool needs to read a weighbridge, drive a label printer, write back to your ERP, or send an EDI despatch advice. On the Wrexham estate that's most useful tools. The honest answer is to start with Retool or Airtable and only commission a custom build for the workflows that touch machines, traceability, or customer integrations, which is where the no-code ceiling is real.
Your despatch desk, your goods-in booking, and your quality sign-off probably run on spreadsheets with a macro someone wrote three years ago who's since left. It works until it doesn't: a formula breaks, two people edit at once, or the macro can't talk to the new label printer. You've tried Airtable, and for a simple list it's great, but the moment the tool has to print a SSCC label or write a batch back to the ERP, you hit the wall.
Retool gets you further because it connects to a database, but you still need someone who can wire it to your line hardware and your customer EDI, and at that point you're building software, just inside a tool that charges per seat for the privilege. For the workflows that genuinely run your North Wales operation, the goods-in, the despatch, the traceability capture, you eventually want code you own, not a no-code app you rent and can't extend the day it needs to read a scale.
Where the off-the-shelf tools fall short
- Critical desks run on a spreadsheet macro written by someone who's left, and nobody fully understands it anymore
- Airtable and Retool can't drive label printers, weighbridges, or barcode scanners, so the physical line stays manual
- No-code tools can't write traceability data back to the ERP, so the same batch gets keyed twice
- Per-seat no-code pricing climbs fast once every line operator and despatcher needs access
Custom internal tools: what Wrexham teams actually get
You go custom for the handful of internal tools that touch hardware, traceability, or customer systems, where no-code genuinely can't follow. A build for a Wrexham operation might be a despatch app that books a load, prints the SSCC label, writes the batch to traceability, and fires the EDI despatch advice in one screen. That's not an Airtable base, it's an application, and owning the code means it can read your scale and survive the day your label format changes. The custom case is targeted, not a blanket rebuild of every internal list you keep.
- The tool has to drive a label printer, scale, or scanner that no-code can't reach
- A critical desk depends on a spreadsheet macro nobody alive fully understands
- The same batch or stock figure is keyed into two systems because no-code can't write back
- Per-seat no-code costs are climbing as every operator needs access
- The workflow is a simple list, form, or approval Airtable or Retool handles in an afternoon
- Nothing in it touches line hardware, traceability, or customer EDI
- You need it live this week and can live with no-code limits
- Only a handful of office staff use it, so per-seat pricing stays cheap
- Tools that actually drive line hardware: label printers, weighbridges, and barcode scanners, not just hold data
- One screen that books a despatch, prints the SSCC label, writes the batch, and sends the EDI advice with no rekeying
- Code you own and can extend, instead of a no-code app that stalls the day it needs to read a scale
- Flat cost regardless of how many line operators use it, ending per-seat no-code price creep
- Traceability captured once at the point of action, removing the double-keying between spreadsheet and ERP
- A custom tool needs hosting, monitoring, and someone to fix it; Airtable handles all that for you
- Small tools can sprawl into an unowned mini-app graveyard if you build without a plan or naming discipline
- Lead time is weeks, not the afternoon an Airtable base takes, so it's overkill for genuinely simple lists
- You'll still want Retool or Airtable for the simple internal stuff; custom only earns its place at the hardware and integration edge
Feature priorities for Wrexham teams
Wrexham internal tools: the full scope
The engagements Wrexham teams bring us most often:
The honest cost picture for Wrexham
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single workflow tool with hardware integration | £20k to £35k | 6 to 9 weeks |
| Despatch or goods-in app with EDI and traceability write-back | £35k to £55k | 9 to 13 weeks |
| Suite of connected line tools replacing the spreadsheet stack | £50k to £70k | 12 to 16 weeks |
Timeline: what happens, and when
Exactly what you get
A small number of tools that do the jobs no-code can't: drive line hardware, write batches back to the ERP, and fire EDI to customers, all in one screen instead of a spreadsheet and three manual steps. Concretely, a despatch app, a goods-in booking tool, or a quality-capture screen wired to your printers, scales, and scanners, with the source code in your hands. For the simple lists, you keep Airtable or Retool; this is only for the hardware and integration edge. These tools usually sit on top of your inventory management software and feed your warehouse management system and ERP, with business intelligence dashboards reading the data they capture.
How to choose a developer in Wrexham
Find a team that asks which hardware the tool has to touch before they quote. If they're confident it's all an Airtable base, they haven't built for a real line, where the value is in the label printer and the scale, not the form. Ask which scanners, printers, and EDI formats they've integrated, and ask them to be honest about which of your tools should stay in no-code. A good partner narrows the custom build to the workflows that genuinely need it and points the rest at Retool, the same restraint a strong custom software development or warehouse management system team shows.
- !They say they'll do it all in Airtable; ask how Airtable drives your label printer
- !No question about your line hardware; ask which scanners and printers they've integrated before
- !They ignore EDI; ask how the despatch advice reaches the customer without rekeying
- !They build with no naming or ownership plan; ask how you avoid an unmaintained tool sprawl
- !They price by seat like no-code; ask for a flat build cost you own outright
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
Should we just use Retool or Airtable instead of building?
For simple lists, forms, and approvals, yes, and a good partner will tell you so. The line where custom earns its place is hardware and integration: the moment a tool has to drive a label printer, read a weighbridge, write a batch back to your ERP, or send EDI to a customer, no-code either can't do it or needs so much glue you're building software anyway. On the Wrexham estate, most genuinely useful tools cross that line.
Can a custom tool print SSCC labels and read our weighbridge?
Yes, that's exactly the kind of job that justifies custom over Airtable. A build can talk to label printers over standard protocols, read a weighbridge or floor scale, and capture barcode scans from handheld terminals, then tie all of it to the batch in one action. That hardware integration is the wall no-code hits, and it's where owning the code matters most.
How do we avoid building a graveyard of half-maintained tools?
Discipline: a naming convention, a clear owner for each tool, and a shared data model so tools talk to the ERP rather than to each other ad hoc. The risk with internal tools is sprawl, so a good build starts with which handful genuinely need custom and leaves the rest in Retool. Treat the custom tools as real software with monitoring, not throwaway scripts.
What's the smallest sensible custom internal tool?
Usually a single workflow that touches hardware, like a despatch screen that prints the label and sends the EDI advice, at £20k to £35k over 6 to 9 weeks. Below that, you're better off in Airtable or Retool. The hardware and EDI integration is what justifies stepping up to a custom build rather than a no-code base.
Will the tool keep working if our warehouse wifi drops?
It can, if it's built for it. Parts of an industrial estate have patchy warehouse coverage, so a well-built capture tool queues scans and despatch actions locally and syncs when the connection returns. That offline tolerance is something you design in deliberately; it's another reason these line tools often need real code rather than a browser-only no-code app.