Your dispatch board is a whiteboard and your tide table is taped to the wall next to it
Custom internal tools for a Nanaimo marine, forestry, or tourism operation run $25,000 to $90,000 over 2 to 6 months. Retool and Airtable are fine until your operation lives on a dock, runs on a tide, and coordinates crews by radio. The off-the-shelf builders assume a clean office with reliable wifi and discrete records. Your reality is a yard, a wharf, and a vessel where the real tool has to work offline, read a tide, and survive being used in the rain.
Your office runs a dozen spreadsheets and an Airtable base to stitch together what the whiteboard in the dock office already knows. The dispatcher reconciles crew assignments, tide windows, and which vessel is where by walking between the wall and the screen. When something changes, the spreadsheet lags the wall by an hour, and the wall lags reality by however long since someone last updated it.
Retool would help if your data were already clean and your staff were already at a desk. They're not. The deckhand needs the assignment on a phone that loses signal past the breakwater, the yard foreman wants to scan a load and move on, and the tide window has to drive the schedule, not sit in a separate table nobody links. Generic internal-tool builders give you a prettier spreadsheet, not a tool that fits the dock.
- Your real dispatch board is a whiteboard and the spreadsheet always trails it
- Field staff lose signal where the work happens, so browser-only tools fail
- Tide and weather windows should drive scheduling but live in a disconnected table
- Staff spend hours a day re-keying between the wall, the spreadsheet, and memory
- Your team works at desks with reliable wifi and discrete, clean records
- Airtable plus a few automations already covers your workflow
- You have no field or offline component to your operation
- You can't commit to maintaining a tool past the launch
- One dispatch view of crew, vessel, and tide window that the office and the dock both trust
- Offline-capable mobile tools so a deckhand's assignment survives losing signal past the breakwater
- Tide and weather windows wired into the schedule, not stranded in a table nobody opens
- Scan-and-go yard and load tracking that fits a foreman who can't stop to type
- Hours of daily re-keying between the whiteboard and the spreadsheet eliminated outright
- You maintain it; a custom tool has no vendor pushing free updates while you sleep
- Scope creep is real, because once one workflow is digitised every department wants theirs next
- A small office may genuinely be fine with Airtable plus discipline, and custom would be overspend
- Offline sync logic adds cost and complexity that a desk-bound tool would never need
Internal Tools pricing in Nanaimo: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single-workflow tool (dispatch or yard scan) | $25k to $45k | 2 to 3 months |
| Connected ops suite (dispatch + crew + tide) | $50k to $90k | 4 to 6 months |
| Mobile layer over existing Airtable data | $20k to $40k | 2 to 3 months |
The features that matter for Nanaimo
What we build under internal tools in Nanaimo
The engagements Nanaimo teams bring us most often:
Exactly what you get
A tool that fits the dock, not a prettier spreadsheet. Concretely: a mobile dispatch board for crew, vessel, and tide windows, offline-first capture that syncs when signal returns, scan-and-go yard tracking, and role views for deckhand, foreman, and office. You also get source code and integrations to your booking, field-service, and CRM systems so the wall and the screen finally agree. What you don't get is a tool that only works at a desk with full bars.
How to choose a developer in Nanaimo
Find a team that asks to stand in your dock office before quoting. If they assume clean data and a desk, they've never built for a wharf. Ask for a reference where the tool had to work offline and outdoors. A strong partner will scope tightly, connect the tool to your booking software, field-service management, and business intelligence dashboards, and tell you honestly when Airtable plus discipline is genuinely enough.
From kickoff to launch: the schedule
- !They assume reliable wifi everywhere; ask how the tool behaves past the breakwater
- !They've never built offline-first; ask for a field-operations or marine reference
- !They treat the tide window as out of scope; ask how it should drive the schedule
- !They quote a desktop-only build; ask how the deckhand and foreman actually use it
- !No migration plan for your spreadsheets; ask how existing data comes across cleanly
Most Nanaimo 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
Why not just use Retool over our database?
Retool is great for desk-bound admin panels. It struggles when the tool has to work offline on a phone past the breakwater and read a tide window into the schedule. The gap is that your work happens outdoors, on the move, often without signal, which is exactly where browser-only builders break down.
Can it really work without signal?
Yes, with offline-first design. The tool captures data locally and syncs when signal returns, so a deckhand's assignment and a foreman's load scan survive the dead zone past the breakwater. That sync logic adds cost, but it's the whole reason custom beats Airtable for dock work.
We already have Airtable. Do we throw it out?
Not necessarily. Many builds put a custom mobile layer over your existing Airtable data, keeping what works and adding the offline dock tooling that's missing. That's the $20k to $40k path and it's often the smartest first step.