Your Retool dashboard is gorgeous until it has to read a tag off the stamping line
Custom internal tools for an Oshawa manufacturer cost $30k to $90k over 6 to 14 weeks. Retool and Airtable are excellent for office workflows that sit on top of a clean database. They fall apart the moment you need a tool to read a live tag off a stamping press PLC, drive a shop-floor terminal a maintenance tech uses with gloves on, or run on the plant network behind a firewall.
Your operations team in Oshawa wired together a few Retool apps and a stack of Airtable bases to track tooling changeovers, scrap, and shift handoffs. It worked beautifully in the office. Then the floor needed it. Retool wants an HTTP API and a friendly auth flow; your Allen-Bradley PLC speaks EtherNet/IP and lives on an isolated network with no internet route. Airtable hits a row limit and chokes when a line scans thousands of parts a shift.
So the floor tools stay on paper or in a brittle Excel macro, and the office tools never quite connect to what's actually happening on the line. The gap between the no-code layer and the OT (operational technology) network is exactly where most Oshawa manufacturers' internal tools die.
- A tool needs to read or write a live PLC tag and Retool simply can't reach it
- Airtable is hitting row or rate limits under your line's scan volume
- The tool must run on a firewalled OT network with no cloud route
- Operators need a gloved-hand interface no-code builders can't deliver
- The workflow is office CRUD on a clean database with no OT touch
- Ops needs to iterate the tool themselves without waiting on a developer
- Volume is low and Airtable's limits are comfortably out of reach
- It's a short-lived experiment not worth a custom build
- Direct PLC/SCADA connectivity (OPC-UA, EtherNet/IP) the no-code tools can't provide
- Runs on the air-gapped plant network without depending on a cloud round-trip
- Operator UIs built for gloves, glare, and speed, not a desktop mouse
- Handles per-part scan volume without the row limits that kill Airtable
- Tools talk to your ERP and MES so floor actions update the system of record
- You give up the drag-and-drop speed that makes Retool changes a five-minute job
- Custom tools need a developer for every change, where ops could self-serve in Airtable
- On-prem deployment on the OT network adds IT and security overhead
- Easy to over-build; some workflows genuinely belong in Retool and shouldn't be custom
Internal Tools pricing in Oshawa: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single floor tool with PLC connectivity | $30k to $55k | 6 to 9 weeks |
| Suite of floor + office tools with ERP/MES integration | $60k to $90k | 10 to 14 weeks |
| Office-only tool no-code can't quite do | $18k to $35k | 4 to 6 weeks |
The features that matter for Oshawa
What we build under internal tools in Oshawa
The engagements Oshawa teams bring us most often:
Exactly what you get
Tools that finally cross the office-to-floor line. The ones that touch the PLC are custom, run on the plant network, and are built for the way operators actually work. The ones that don't stay in Retool or Airtable where they belong. You get a clear boundary instead of a no-code tool quietly failing on the floor. These often feed a warehouse management system, an inventory management layer, and business intelligence dashboards built from real floor data.
How to choose a developer in Oshawa
The deciding question is OT experience. A web developer who has only built SaaS will treat your PLC as a REST API and discover the truth the hard way. Look for someone who has read a tag over OPC-UA, knows why the OT network is air-gapped, and respects it. They should also tell you honestly which of your tools should stay in no-code; a partner that wants to custom-build everything is padding the invoice.
From kickoff to launch: the schedule
- !They've never deployed to an OT network. Ask how they'd reach a PLC with no internet route.
- !They say 'we'll just use the Airtable API'. Ask what happens at your real scan volume.
- !No experience with EtherNet/IP or OPC-UA. Ask which industrial protocols they've actually read.
- !They ignore operator ergonomics. Ask how the UI works for a tech wearing gloves.
- !They want to custom-build your office CRUD too. Ask why that shouldn't stay in Retool.
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
Can Retool connect to our PLC with a custom integration?
Only through a middleware layer that exposes the PLC over HTTP, and at that point you've built the hard part yourself. For a single tool the custom-built approach is usually cleaner and runs natively on the OT network instead of routing floor data out to the cloud and back.
Should we replace Airtable entirely?
No. Keep Airtable and Retool for office workflows on clean data; that's exactly what they're good at. Build custom only for the tools that touch the floor or exceed no-code limits. Replacing the no-code layer wholesale wastes money and slows down the people who self-serve in it today.
How do these tools stay secure on the OT network?
By design: role-based access, on-prem deployment, and a controlled bridge to the IT side rather than an open internet route. Manufacturing OT security is its own discipline; a developer who has worked on a plant floor will architect for segmentation from day one rather than bolting it on.
What's the smallest useful first build?
One painful floor tool, often shift handoff or scrap capture, with a single PLC connection. That's $30k to $55k and six to nine weeks, and it proves the office-to-floor bridge before you commit to a suite.