Your Oakland dispatcher runs the whole yard from a spreadsheet and three carrier portals, and Airtable can't see any of it
A custom internal tool for an Oakland importer or manufacturer runs $40k to $110k over 2 to 5 months. Retool, Airtable, and spreadsheets get you surprisingly far until the tool has to read from the legacy AS/400, homegrown database, or carrier portal your operation actually runs on. Custom is worth it when the data your dispatcher or floor lead needs lives in systems the no-code tools can't reach, and the spreadsheet they rebuild every morning is itself a daily risk.
Retool, Airtable, and a stack of spreadsheets are the right first answer for most internal tooling, and plenty of Oakland operations should stay there. The wall appears when the data isn't in a clean database the no-code tool can connect to. Your dispatcher's real source of truth is a legacy AS/400 screen, a homegrown order system, and three separate carrier portals for reefer cutoffs and chassis status, none of which Retool can authenticate into or read cleanly.
So the dispatcher builds a spreadsheet by hand each morning, copying numbers off green screens and portals, and the whole yard runs on that one fragile file. When that person is out, the operation slows to a crawl because nobody else can reconstruct it. The cost isn't the license, it's the single point of failure sitting in one employee's head and one tab nobody backs up. That's the moment a custom tool that reads directly from those messy sources stops being a luxury.
Where the off-the-shelf tools fall short
- Retool and Airtable can't authenticate into your carrier portals or read your AS/400, so the data they show is always a stale manual copy
- The whole yard runs on one dispatcher's hand-built spreadsheet, and when they're out the operation stalls because nobody can rebuild it
- Reefer cutoffs, chassis availability, and container status live in three portals nobody has tied together into one screen
- Every no-code workaround adds another sync step, and by now the team trusts the spreadsheet more than any of the tools it was meant to replace
Custom internal tools: what Oakland teams actually get
You build custom when the value is in reading the unreadable. A custom internal tool can authenticate into carrier portals, pull from the AS/400 by file export or screen access, and merge it all into one live operations screen for the dispatcher. That removes the single point of failure (the human-built spreadsheet) and gives the floor a tool that reflects reality instead of last hour's manual snapshot. It pays off precisely where Retool's connectors stop.
- The data your team needs lives in legacy systems or portals that Retool and Airtable can't connect to
- A single hand-built spreadsheet is the real operating system of your yard or floor
- One person's absence noticeably slows the whole operation because the workflow lives in their head
- You're checking three or more separate portals by hand to assemble one daily picture
- Your data already lives in a database or app Retool can connect to natively
- The workflow is simple enough that an Airtable base and a few automations cover it
- You don't have a clearly painful, repeated workflow worth the cost of a custom build
- The team is small and the spreadsheet, while imperfect, isn't actually a single point of failure
- One live operations screen that merges legacy inventory, order status, and carrier portal data the no-code tools can't reach
- The dispatcher's fragile hand-built spreadsheet stops being a single point of failure when someone's out
- Reefer cutoffs, chassis status, and container milestones land in one view instead of three portals checked by hand
- The floor works from real-time data, so scheduling and yard moves stop running on an hour-old manual copy
- Cheaper and faster than a full ERP project, while solving the specific daily pain that's actually slowing you down
- A custom tool is something you own and maintain, unlike Retool where the vendor handles upgrades and uptime
- Reading from carrier portals and legacy screens is brittle by nature, so you're signing up for ongoing fixes when those sources change
- It solves one workflow well, so if your needs sprawl you can end up with several custom tools where one platform might have done
- If your data already lives somewhere Retool can connect to, building custom is spending money to solve a problem the no-code tool would handle
Feature priorities for Oakland teams
What we build under internal tools in Oakland
Digital Heroes builds the full internal tools stack for Oakland teams. Typical engagements span:
The honest cost picture for Oakland
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single-workflow internal tool reading from one legacy source | $30k to $55k | 2 to 3 months |
| Operations dashboard merging legacy data and carrier portals | $55k to $90k | 3 to 4 months |
| Multi-team internal platform with audit, roles, and accounting handoff | $85k to $140k | 4 to 6 months |
Timeline: what happens, and when
Exactly what you get
You get the one screen your dispatcher has been faking in a spreadsheet, built for real. It authenticates into your carrier portals, reads inventory and orders from your legacy system by file or screen access, and merges everything into a live operations view with roles, audit, and a clean handoff to your accounting software. The fragile morning spreadsheet retires, the single point of failure in one person's head goes away, and the floor near the Port of Oakland works from data that's actually current instead of an hour old.
How to choose a developer in Oakland
Hire a team that treats the integration as the hard part, because it is. Anyone can build a clean table view; the value is in reaching the AS/400 and the carrier portals that Retool can't. Ask to see an internal tool they built against a brittle legacy or portal source. Ask how they'd handle a carrier changing its login. Ask them to scope the single most painful workflow first rather than proposing a platform. A developer who has worked with Oakland operations answers in specifics about feeds and failure handling. One who hasn't shows you a dashboard with sample data.
- !They assume your data is in a clean database, ask how they'd read from an AS/400 and a carrier portal with no API
- !They've only built Retool front-ends, ask for a reference where they integrated a brittle legacy or portal source
- !They underprice the integration and overprice the UI, ask what share of the build is connecting to your real sources
- !They have no plan for when a portal changes its login flow, ask how they handle source feeds that break
- !They want to build five tools when you described one painful workflow, ask them to scope the single highest-pain piece first
Most Oakland teams pricing internal tools end up comparing notes on custom software, wordpress, accounting too; the systems share one data spine.
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
When should we move off Retool or Airtable to a custom internal tool?
When the data you need lives in systems Retool and Airtable can't reach, like a carrier portal or a legacy AS/400, and your team is filling that gap with a hand-built spreadsheet. For Oakland operations, that's usually the point where one person's spreadsheet has quietly become the system the whole yard runs on.
What does a custom internal tool cost in Oakland?
A single-workflow tool reading from one legacy source runs $30k to $55k. An operations dashboard merging legacy data and carrier portals runs $55k to $90k. A multi-team platform with audit, roles, and accounting handoff reaches $85k to $140k. Timelines run 2 to 6 months.
Can it read data from systems with no API?
Yes, that's often the whole point. A custom tool can pull from an AS/400 or homegrown database via scheduled file exports or screen-level access, and authenticate into carrier portals to scrape the data they don't expose cleanly. That's exactly the territory where no-code connectors give up.
Isn't a spreadsheet good enough?
Until it's the single point of failure for your operation. The moment the yard slows down because the one person who maintains the spreadsheet is out, you're paying for the fragility every day. A custom tool turns that tribal knowledge into a system anyone on the floor can use.