The whiteboard in your Gisborne packhouse office is a production system. It has no backup, no audit trail, and it gets wiped every Friday.

NZ$18,000 to NZ$35,000 for a single offline capture tool with payroll export, delivered in five to eight weeks. Adding rostering and a supervisor board takes it to NZ$35,000 to NZ$65,000. That is the realistic band for something production-grade with proper offline sync, not a prototype that only works on office wifi.

Try it first, genuinely, because if it works you have saved yourself a project. It fails in Gisborne for two reasons: it needs a live connection, which you do not have in many blocks past Te Karaka, and its calculation layer is not where you want your minimum wage compliance logic sitting. Airtable is excellent for the office side and a poor fit for the paddock side.

New Zealand law requires that a worker on a piece rate still earns at least minimum wage for the hours actually worked, and you must keep accurate wage and time records. A custom tool captures start, finish and break times alongside the tally, calculates the effective hourly rate per worker per pay period, and flags anyone under the threshold before payroll runs so you can top them up rather than argue about it later.

Usually yes. PayHero, Smartly, iPayroll and Datacom all have import paths or APIs, and the practical approach is a structured export mapped to your provider's format, validated against a real pay run before go-live. Budget two to three weeks for the integration and testing rather than treating it as a final week task.

It sits idle for eight months, which is normal and fine, and that shapes how you should contract support. Rather than a flat monthly retainer for twelve months of a tool used for twelve weeks, negotiate a lighter off-season arrangement with a pre-agreed block of hours in January for the changes you always discover.

Yes if the underlying units are similar, no if the rules diverge sharply. Grape picking measured by bin, citrus by tray and squash by weight can share one system if you design the unit and rate model generically at the start. Retrofitting a second crop with different rules into a tool built for one is where these projects blow their budget.

Delete it, formally, on the day you go live, and give the person who owned it a role in the new system so they are not defending their territory. The tool also has to be faster than the spreadsheet for the office user, not just the field user, or the office will quietly rebuild it. Test the office workflow as hard as the field one.

Yes, and it matters more at this size, not less. Small tools get orphaned when an agency loses interest in a small client. Insist on the repository in your own account, a documented deployment process, and no proprietary runtime you cannot host yourself. That way a contractor in Napier or Auckland can pick it up if you need them to.

If you start in September, comfortably. If you start in January, be very careful. A five to eight week build finishing in mid-February means you are training crews during the busiest fortnight of the Gisborne year, which is how good tools get rejected. Better to build now, run it in shadow for one season, and make it the system of record next year.

Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.

Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.

Agency rates in markets like Gisborne typically run $100 to $200 per hour against $25 to $60 offshore, but the hourly rate is not the project cost. Across 2,000+ Digital Heroes projects, the setup that consistently works is a hybrid: senior architects and a named lead for your project with a distributed build team behind them, which lands total cost well below all-local without the rework cycles that pure lowest-bid offshore engagements produce. Compare bids on total delivered cost with maintenance included, never on rate cards.

A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.

The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.

Ask to see two or three internal tools they have shipped and whether those clients still use them daily, because internal tools fail on adoption, not code quality. Good signs: they ask to see your current spreadsheet or process before quoting, they propose a phased build instead of one big launch, and they spell out who handles training and post-launch changes. Walk away from anyone who gives a fixed price before seeing your actual workflow, since internal tools live or die on process details.

For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.

The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.

Digital Heroes builds custom internal tools systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Gisborne. You can chat with the team directly, and every form gets an email reply within 24 hours.