Three Norwich teams, three spreadsheets, and the Retool dashboard that still can't see the field
Custom internal tools for a Norwich agritech, food, or insurance operation usually run £25,000 to £80,000 over 6 to 16 weeks. Retool and Airtable are excellent until your tool needs to reconcile field data, harvest yields, and supplier orders that live in three different spreadsheets, enforce who-can-see-what, and run reliably during the August spike. Past that point, the no-code ceiling becomes a daily tax.
You wired up an Airtable base and a couple of Retool screens, and for a while it felt like magic. Then the agritech reality crept in: field data in one spreadsheet, harvest yields in another, supplier orders in a third, and a Retool dashboard that can only read whatever a person remembered to paste in. The tool is only as fresh as the last manual copy-paste, which means it's wrong by mid-afternoon.
The other wall is permissions and load. Airtable doesn't cleanly separate what a grower sees from what finance sees, and Retool's pricing and performance bite once real volume hits during harvest. So you keep the spreadsheets as the real source and treat the no-code layer as a pretty front that nobody fully trusts. That's the moment a purpose-built internal tool earns its keep.
- Your Retool or Airtable tool is always stale because data lives in three places
- You need real permissions that no-code can't enforce
- The tool buckles under harvest-season load when you most need it
- The tool is simple, internal, and low-volume, where Retool or Airtable shines
- Requirements change weekly and you value drag-and-drop speed over robustness
- You don't yet have the data volume or permission complexity to justify code
- Live data straight from source, so the tool is never one paste behind reality
- Proper role-based access, so growers, pack-house staff, and finance each see the right slice
- Built to hold steady under the August spike instead of degrading when you depend on it
- Reconciliation logic moved out of fragile spreadsheet formulas into tested, documented code
- Free to integrate with your ERP, accounting, and supplier portals without per-row no-code limits
- Slower to change than dragging a field in Airtable; small tweaks need a developer
- You're now maintaining real software, with hosting and updates, not a no-code subscription
- Over-building is a risk: some tools genuinely should stay in Retool
- Upfront cost is higher than a no-code seat, even if it pays back fast
Internal Tools pricing in Norwich: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single reconciliation tool replacing a spreadsheet | £25k to £45k | 6 to 10 weeks |
| Multi-role operations dashboard (field to finance) | £45k to £80k | 10 to 16 weeks |
| Connectors and permissions layer over existing tools | £18k to £35k | 5 to 8 weeks |
The features that matter for Norwich
Norwich internal tools: the full scope
Everything a internal tools build here can cover:
Exactly what you get
A tool that reads live from your real data, reconciles it automatically, and shows each person only what they should see. No more dashboards that are stale by lunchtime. It holds up under harvest load, logs every change for supermarket compliance, and connects to your ERP software, accounting software, and supplier portals so the numbers are real. Where Retool or Airtable still does the job, a good developer leaves it there rather than rebuilding for ego. Think of it as the connective tissue between your inventory management software, your BI dashboards, and the field.
How to choose a developer in Norwich
Hire someone who tells you honestly which parts to keep in Retool and which to build, rather than quoting a full custom rebuild for everything. Norwich's agritech and food firms run lean, so a developer who respects that, and ships a small, high-value tool first, is worth more than one selling a platform. Ask to see a previous internal tool that connected to live data with real permissions, and ask how it behaved under peak load. The test is whether they understand that your tool's whole value is being trusted, which means never stale and never showing the wrong person the wrong data.
From kickoff to launch: the schedule
- !They propose rebuilding everything custom when Retool would do half of it. Ask which parts genuinely need code and which don't.
- !No mention of role-based access. Ask how a grower is prevented from seeing finance data.
- !They ignore the seasonal spike. Ask how the tool performs under August load, with numbers.
- !They won't document the reconciliation logic they're encoding. Ask for the rules in writing before they build.
- !They've never connected to a supplier portal or ERP. Ask to see a prior live-data integration.
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
Is Retool ever good enough for us?
Often, yes, for simple low-volume internal screens. The line is crossed when your tool must merge three live data sources, enforce real role separation, and survive the August spike. Below that line, Retool saves you money; above it, it quietly costs you trust.
Why does the seasonal spike matter so much?
Because a tool that degrades during harvest is failing at the one moment everyone depends on it. A custom tool is load-tested for that peak, so it stays responsive when field, pack-house, and finance are all hammering it at once.
How do permissions work in a custom tool?
Each role, grower, pack-house, finance, management, gets its own view, and the system enforces it server-side. Unlike a shared Airtable base, a grower can't accidentally or deliberately see finance data.
Can it pull from our existing spreadsheets during transition?
Yes, as a bridge. A good build can read existing spreadsheets while you migrate the real source of truth into the tool, so you're not forced into a risky big-bang cutover mid-season.