Your Kelowna harvest, tour-dispatch, and crew-scheduling logic lives in one fragile Airtable nobody else can edit
A custom internal tool in Kelowna runs $30,000 to $90,000 over 2 to 5 months. You build custom when the spreadsheet or Airtable that runs harvest scheduling, tour dispatch, or crew rostering has become a single point of failure: one person owns it, it breaks under the September load, and a wrong cell stalls a crush or strands a tour group. Retool and Airtable get you started, but seasonal operations hit limits exactly when the cost of failure is highest.
The orchard's pick schedule, the winery's tank assignments, and the tour company's daily dispatch all run on spreadsheets that started as a clever idea and became load-bearing. They work in February. In late September, when you've got 40 seasonal workers, six tanks in play, and back-to-back tour departures, the same spreadsheet is being edited by five people at once, the formulas have grown beyond anyone's understanding, and one fat-fingered cell sends a crew to the wrong block.
Airtable and Retool buy you a layer of structure, and for a while that's enough. But they assume modest concurrency, simple permissions, and data that fits their model. A crush operation with real-time tank states, a tour fleet with capacity and weather constraints, or a crew roster with BC labour rules and seasonal overtime quickly exceeds what a no-code grid handles before it slows down or forces ugly workarounds. The tool that was supposed to reduce risk becomes the risk.
Why the usual tools struggle in Kelowna
- One person owns the spreadsheet and the whole operation stops when they're off during peak season
- Concurrent edits during harvest corrupt data or overwrite each other in Airtable
- Tour dispatch and tank scheduling have grown past what no-code formulas can hold reliably
- No real permissions, so a seasonal hire can break the master sheet with one bad edit
What a custom internal tools build changes
You build custom when a tool that runs core operations can't be allowed to fail during your busiest weeks, and the no-code version is failing. A custom internal tool gives you proper roles and permissions, real-time concurrency that survives 40 people in September, validation that stops bad edits before they cascade, and logic complex enough for tank states, tour capacity, or labour rules without contortions. It turns a fragile, one-owner spreadsheet into shared operational infrastructure your seasonal crew can use safely.
The features that matter for Kelowna
What we build under internal tools in Kelowna
The engagements Kelowna teams bring us most often:
- A spreadsheet or Airtable runs core operations and breaks under peak-season load
- Only one person fully understands the tool and that's an operational risk
- Concurrent editing during harvest or peak tour season corrupts your data
- You need real permissions and validation that no-code can't enforce
- The tool is genuinely simple and low-concurrency and Airtable handles it
- Your team is small enough that one owner and a spreadsheet is fine
- You can't commit to owning and maintaining a custom tool after launch
- Retool plus your existing data already covers the workflow acceptably
Internal Tools pricing in Kelowna: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Single workflow tool replacing one critical spreadsheet | $25,000 to $45,000 | 2 to 3 months |
| Multi-user operational tool with permissions and validation | $45,000 to $80,000 | 3 to 4 months |
| Connected suite of internal tools across operations | $80,000 to $140,000 | 4 to 6 months |
From kickoff to launch: the schedule
Exactly what you get
You get the one workflow that's actually breaking, rebuilt as reliable infrastructure: real concurrency for your whole seasonal crew, permissions that let seasonal hires work without risking master data, validation that blocks the bad edit before it strands anyone, and logic complex enough for tank states, tour capacity, or BC labour rules. It works on a phone in an orchard block and tolerates weak rural signal. Every change is logged so a harvest mishap is traceable. Crucially, you get a tool scoped to the real problem, not a mini-ERP nobody asked for.
How to choose a developer in Kelowna
Find a team disciplined about scope. The biggest risk in internal tools isn't capability, it's a builder who turns a $40k scheduling tool into a $120k system. Ask them to scope only the spreadsheet that's failing and to push back on extras. They should ask about concurrency, field conditions, and who owns the tool after launch before they quote. Make sure their approach connects to your erp, field-service-management, and project-management needs so the tool fits your wider stack instead of becoming another island.
- Reliable concurrent access for a full seasonal crew without overwrites or corruption
- Role-based permissions so a seasonal hire can do their job without endangering the master data
- Validation and guardrails that catch a bad entry before it strands a crew or a tour
- Logic that handles real complexity: tank states, tour capacity, weather holds, BC labour rules
- An audit trail so when something goes wrong at harvest you can see exactly what changed
- You lose the instant, anyone-can-tweak flexibility of a spreadsheet for structure and change control
- Smaller, genuinely simple tools may never justify the cost of leaving Airtable
- Custom tools still need an owner and a maintenance budget once the build team leaves
- Over-building is a real risk: scope creep can turn a $40k tool into a $120k mini-ERP
- !They want to rebuild everything as a mini-ERP: ask them to scope the one tool that's actually breaking
- !No plan for concurrency: ask how the tool handles 40 simultaneous editors in September
- !They ignore field conditions: ask about mobile and offline access for orchard blocks
- !No permissions design: ask how a seasonal hire is prevented from breaking master data
- !They can't show a comparable operational tool: ask for a reference under real load
Most Kelowna 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 is Airtable or Retool no longer enough?
When the tool runs core operations and can't be allowed to fail, and it's hitting concurrency, permission, or logic limits. Airtable is excellent for low-concurrency, simple-permission workflows. The moment 40 people edit it during harvest, or the formulas grow past anyone's understanding, or a seasonal hire can break the master sheet, you've outgrown it and the failure cost justifies custom.
How do we avoid over-building an internal tool?
Scope to the single workflow that's actually failing and resist the urge to fold in adjacent processes. A good team will push back when you ask to add 'just one more thing' and will ship the breaking tool first. Over-building is the most common way these projects balloon from $40k to $120k, so discipline on scope is the main cost control.
Will the tool work in the field with poor signal?
It can and should if your crews work orchard blocks or rural tour routes. That means mobile-friendly design and offline tolerance so a field worker can record a pick or a dispatcher can adjust a route without a solid connection, syncing when signal returns. Raise this in discovery because retrofitting offline support later is expensive.