Your Miami operations run on a Retool dashboard and three spreadsheets that break the day a Brazilian shipment hits a customs hold
Custom internal tools for a Miami trade, real estate, or fintech operation run $40k to $110k and 2 to 4 months, depending on how many systems they stitch together. Retool, Airtable, and spreadsheets are the right first move and you should not rip them out early. You build custom when the glue itself becomes the risk, when an English-only Retool app and a shared spreadsheet are the only thing standing between a customs hold and a missed closing.
Your operations lead built a Retool dashboard that pulls from your ERP, your customs broker's portal, and a Google Sheet of currency rates, and for eighteen months it has quietly run the business. Then she goes on vacation, a Cartagena shipment hits a CBP hold, and nobody else can read the app well enough to fix it, partly because half the labels are in English and your floor works in Spanish. The tool that saved you is now a single point of failure.
Airtable and Retool are fast because they hide complexity, which is exactly the problem at scale. They do not enforce who can approve a wire, they do not version the currency-rate sheet, and they do not gate a sanctions check before an operator marks a counterparty cleared. For a Miami firm where a wrong FX rate or a skipped screening is a real-money or compliance event, the convenience layer quietly becomes the place where control disappears.
The problems nobody warns you about
- The Retool app that runs ops was built by one person and breaks the moment they are out
- A currency-rate Google Sheet feeds real money decisions with no version history or approval
- English-only internal labels slow a Spanish-speaking floor and invite errors on customs fields
- No role-based gates, so anyone with the link can mark a counterparty cleared or a wire approved
The case for owning your internal tools
Build custom internal tools when the spreadsheet-and-Retool layer is doing work that, if it failed, would cost real money or trip compliance. A custom tool can enforce approvals, version the FX feed, gate sanctions screening, and present a bilingual UI your whole floor can operate. The point is not to replace Retool everywhere; it is to harden the two or three workflows that have quietly become load-bearing for a gateway-to-Latin-America operation.
Budgeting a internal tools build in Miami
| Project scope | Typical cost | Timeline |
|---|---|---|
| Harden one or two load-bearing Retool workflows into a maintained tool | $40k to $70k | 2 to 3 months |
| Custom internal ops platform with approvals and bilingual UI | $70k to $95k | 3 to 4 months |
| Full internal suite with audit, exception dashboards, and integrations | $95k to $110k+ | 4 to 5 months |
What your build should include
Miami internal tools: the full scope
Digital Heroes builds the full internal tools stack for Miami teams. Typical engagements span:
Exactly what you get
You get the two or three workflows that quietly run your business turned into a real system: approvals enforced, FX feed versioned, sanctions screening gated, and every operator working in their own language. The fragile parts, the one-person Retool app and the currency spreadsheet, become maintained connections to your ERP, customs portal, and bank, with an exception dashboard that surfaces a Cartagena customs hold the moment it happens. It sits alongside your BI dashboards, inventory, and accounting so the same data is not re-keyed across four tools.
How to choose a developer in Miami
Hire the team that asks to shadow your operations lead before quoting, because the only way to find the load-bearing workflows is to watch the business run. Be wary of anyone who wants to replace Retool wholesale; the right move is to harden what is fragile and keep what is fluid. Look for a developer who builds approvals and audit in by default and who treats a bilingual floor as a day-one requirement. In Miami, the internal tool that matters is the one a Spanish-speaking operator can run when the person who built it is on a plane.
- !They want to rebuild everything from scratch; ask which two workflows are actually load-bearing and start there
- !They cannot connect to your customs-broker portal; ask how they will replace the scraped spreadsheet feed
- !They skip approvals and audit as out of scope; ask how a wrong wire gets traced and prevented
- !They treat the bilingual floor as a later phase; ask how operators in Spanish use the tool day one
- !They quote without watching your ops lead work; ask them to shadow the current Retool app first
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
When should we move off Retool to custom internal tools?
When a Retool or Airtable app has become load-bearing, meaning the business stops if it breaks, and when a single person is the only one who can fix it. Retool is excellent for fluid, low-stakes workflows. The moment money, compliance, or a customs deadline rides on it, the lack of approvals, audit, and version history becomes a risk that justifies a custom build of that specific workflow.
Do we have to rebuild everything at once?
No, and you should not. The right approach is to identify the two or three workflows that are actually load-bearing and harden those first, leaving the rest in Retool or Airtable where iteration speed is valuable. A developer pushing a full rebuild is usually selling a bigger project than your risk profile requires.
How do internal tools handle our bilingual floor?
By treating language as a day-one requirement, not a translation pass at the end. Operators in Doral working in Spanish should see Spanish labels and Spanish customs fields, while a Brickell analyst might prefer English. Building this in from the start prevents the errors that come from a Spanish-speaking operator guessing at English field names on a customs form.
What is the real cost of the spreadsheet we run on?
The cost shows up as key-person risk, untraced errors, and compliance exposure. A currency-rate sheet with no version history means a wrong FX number has no audit trail; a clearance toggle with no role gate means anyone can mark a counterparty cleared. The build replaces that hidden cost with approvals and an audit log, which is usually the real justification, not features.
Can internal tools connect to our customs broker?
Yes, through the broker's portal or API where one exists, which replaces the brittle scraped spreadsheet most Miami firms rely on. A developer who has integrated a customs-broker portal before will tell you up front whether yours offers an API or needs a more careful approach, rather than promising a clean feed that turns out to be another fragile scrape.