Your ERP was built for a factory with a fixed recipe. Gisborne runs on brix readings, bin tallies and a wharf gate window.
A custom ERP (Enterprise Resource Planning) for a Gisborne wine, horticulture or forestry operation lands at NZ$120,000 to NZ$240,000 across 20 to 34 weeks, and almost nobody should build all of it at once. The pattern that works across Digital Heroes' 2,000+ delivered projects is staged: harvest and intake operations first, coolstore and dispatch second, finance layered on top of Xero last. Gisborne operators who attempt a single cutover in February are cutting over during vintage, and vintage does not pause for a data migration.
You bought NetSuite or Odoo because someone drew you a diagram where a purchase order becomes a work order becomes a finished good. That diagram assumes your input is a part with a code and your output is a unit with a barcode. Your input is nine hectares of Chardonnay whose brix moved half a point since the 6am sample, and your output is a tank blend that will be split three ways after malo. The system wants a bill of materials. You have a vintage that reallocates itself daily.
The same mismatch hits the other side of Gisborne. A squash grower loading kabocha for Japan needs the lot traced back to the paddock, the spray diary, the grade-out percentage and the phytosanitary certificate. A log exporter needs JAS grades, docket weights, the skid site, and a wharf gate booking at Eastland Port that changes when a ship shifts by twelve hours. Off-the-shelf ERP handles the invoice at the end of all of that beautifully and handles none of the middle. So people run the middle in spreadsheets, then rekey it, and the ERP becomes an expensive place to store yesterday.
Why the usual tools struggle in Gisborne
- Vintage intake is captured on paper weighbridge dockets and whiteboards, then keyed into the ERP days later, so tank volumes on screen never match tank volumes in the shed
- Block-level costing does not exist: you know what the whole orchard cost, not what the Wharekaka block cost per exported tray
- Log docket reconciliation between skid site, trucking, and the Eastland Port wharf gate is a manual three-way match done in Excel every Monday
- Grade-out and reject data lives in the packhouse and never reaches the ERP, so margin per line is a guess until the season is closed
What a custom ERP build changes
Custom wins here because your operational units are unusual and your reporting units are ordinary. Nobody needs a bespoke general ledger. What Gisborne needs is a bespoke intake, lot and yield layer that speaks fluent vintage, bin and docket, and then pushes clean, boring journals into Xero and clean, boring lot records into your export documentation. That split matters commercially: it keeps the custom surface area small enough to be maintained by two developers, and it means an accountant who has never seen your system can still audit it. Build the weird part, buy the standard part.
- Your intake, packing or blending process is the thing that actually differentiates you and no vendor models it
- You are running three or more spreadsheets that the ERP cannot see, and season close takes weeks
- You have multiple entities or grower suppliers with different settlement rules that off-the-shelf pricing tables cannot express
- An audit or an export customer has asked for traceability you currently assemble by hand
- Your operation is single-site, single-crop and under roughly 40 staff at peak
- Finance and inventory are the only real pain and Xero plus a good inventory add-on would close the gap
- You have no internal owner who can make decisions weekly for six months
- You are mid-acquisition or mid-restructure and the operating model will change inside a year
- Intake capture at the weighbridge and the skid site, with brix, moisture, grade and gross-tare recorded once and never rekeyed
- True cost per block and per lot, so you can see that the late citrus block cost more to pick than it returned before you plant it again
- Export documentation assembled from live data: lot, spray diary, grower declaration and MPI certification pack generated instead of compiled by hand
- A single reconciliation view across cartage dockets, wharf gate movements and invoices, replacing the Monday morning three-way match
- Vintage and harvest reporting that finance and the winemaker or orchard manager both trust, because both are reading the same record
- You are now responsible for the roadmap. Nobody ships you a compliance update when Fisheries NZ or MPI changes a reporting format
- A staged ERP means running two truths for a period, and the overlap window during a Gisborne harvest is genuinely painful to manage
- Total cost of ownership is not the build price: budget 15 to 22 percent of build annually for hosting, support and the changes you will want
- If your finance team is one part-time bookkeeper, a custom ERP can outgrow the people who have to operate it
The features that matter for Gisborne
Gisborne ERP: the full scope
Everything an ERP build here can cover: NetSuite customization, SAP integration, Odoo development, Microsoft Dynamics 365, ERP migration, cloud ERP and manufacturing ERP.
ERP pricing in Gisborne: the real numbers
| Project scope | Typical cost | Timeline |
|---|---|---|
| Harvest and intake module only, integrated to existing Xero | NZ$45,000 to NZ$80,000 | 10 to 14 weeks |
| Intake plus lot traceability, coolstore and export documentation | NZ$95,000 to NZ$160,000 | 18 to 26 weeks |
| Full staged ERP including finance, procurement and multi-entity settlement | NZ$160,000 to NZ$240,000 | 28 to 40 weeks |
| Annual support, hosting and enhancement | NZ$22,000 to NZ$48,000 | ongoing |
From kickoff to launch: the schedule
Exactly what you get
A working intake and lot spine, deployed in stages, with your finance system left intact. Stage one is capture: weighbridge, shed and skid site data entered once, on devices that keep working when the connection at Matawai or up the coast disappears. Stage two is the lot: every bin, tank and log parcel traceable back to a block, a picker crew and a date, which is what an export customer or an MPI auditor actually asks for. Stage three is the money: costs allocated to blocks and lots, journals pushed to Xero, and a season close that takes days instead of weeks.
You also get the boring assets that decide whether this survives you: documented data models, a migration script you can rerun, environment separation so nobody tests on live vintage data, and a handover pack written for the person who will run it in three years. Most Gisborne builds also touch adjacent systems, so expect the scope conversation to include inventory management software, a warehouse management system (WMS) for the coolstore, HR (Human Resources) software for seasonal payroll, and business intelligence (BI) dashboards once the data is finally clean enough to be worth charting.
How to choose a developer in Gisborne
There is no deep pool of ERP engineers in Tairāwhiti. EIT turns out capable people, and a handful of good developers work remotely from Gisborne by choice, but you are almost certainly hiring a team based elsewhere. That is fine. What is not fine is hiring a team that has never stood in a packhouse. Ask for one reference in primary industry, ideally seasonal, and ring them yourself.
Test three things before you commit. First, will they come here during a real intake, not a quiet Tuesday in July. Second, can they explain how their system behaves when a device loses signal for four hours and comes back with conflicting records, because that will happen. Third, ask what they will refuse to build. A team that says yes to everything in the sales meeting will say no to everything in week eighteen. Gisborne businesses build trust slowly for good reasons, so structure the engagement to earn it: a paid discovery you own the output of, then a small first module in production before the big commitment.
- !They quote before seeing your weighbridge and your packhouse. Ask them to spend a day on site during a real intake before pricing anything
- !They propose replacing Xero. Ask why, and expect a very specific answer that is not about their preferred stack
- !No plan for the harvest freeze window. Ask which weeks of the Gisborne calendar they will refuse to deploy in
- !They talk about modules, not about your blocks and lots. Ask them to describe your traceability chain back to you in their own words
- !Ownership of the code is vague. Ask for the repository transfer clause in writing before you sign
Most Gisborne teams pricing ERP end up comparing notes on internal tools, shopify, inventory management too; the systems share one data spine. Prefer to talk to the team that builds these? Digital Heroes handles ERP development end to end.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- In Gartner's 2025 AI in Finance Survey of 183 CFOs and senior finance leaders (fielded May-June 2025), 59% reported using AI in their finance function, with accounts payable process automation adopted by 37% of respondents (the second-highest single use case, behind knowledge management at 49%). Source: Gartner (2025) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
Tara leads React Native work at Digital Heroes, building apps that share one codebase across iOS and Android. She writes about where that sharing pays off, where native modules become unavoidable, and how to judge whether cross platform is the right call for a given product.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
What does a custom ERP actually cost for a Gisborne winery?
Budget NZ$120,000 to NZ$240,000 for a staged build covering intake, tanks and blends, lot traceability and Xero integration, delivered over 20 to 34 weeks. A narrower first stage covering vintage intake and tank movements alone runs NZ$45,000 to NZ$80,000. Digital Heroes usually recommends the narrow start, because a winery that has lived with real intake capture for one vintage writes a far better spec for stage two.
Can a custom ERP replace Xero, or do we keep it?
Keep Xero. It is the default in New Zealand for good reason, your accountant already works in it, and rebuilding a general ledger adds cost with no operational gain. The right architecture puts your custom intake, lot and costing layer in front and pushes summarised journals, bills and invoices into Xero. Be aware of Xero's published API limits of 60 calls per minute and 5,000 per day per organisation, which shapes how sync is batched during a heavy vintage week.
How do we handle GST and grower settlements in a custom system?
GST at 15 percent is applied at the invoice and bill layer, which stays in Xero, so your returns are filed the way they always were. Grower settlements are where custom earns its money: pool pricing, deductions for cartage and packaging, and progress payments across a citrus or squash season are exactly the rules that off-the-shelf pricing tables cannot express. Build the settlement calculation in your system and post the result as a supplier bill.
When during the year should a Gisborne build go live?
Not February to April. Gisborne picks the earliest grapes in New Zealand and squash is moving at the same time, so the first quarter is the worst possible cutover window. Aim to go live between June and September, run one shadow season alongside the old process, and hard-switch only after a full cycle has proven out.
We already have Odoo. Is it cheaper to extend it than start fresh?
Sometimes, and the deciding factor is how far you have already customised it. If Odoo is running close to standard and only the harvest side hurts, building a separate intake application that integrates cleanly is usually faster and cheaper than fighting the framework. If you have thirty custom modules and an upgrade you cannot take, extending it compounds a problem you will eventually pay to unwind.
How does an ERP handle log exports through Eastland Port?
The valuable part is docket reconciliation: skid site production, cartage weights, port receipts and the eventual sale need to agree, and today that is a manual three-way match. A custom module ingests carrier and port data, matches against your own production records, flags variances above a tolerance you set, and gives you tonnage by grade in near real time rather than a month later.
Who owns the code if we fall out with the agency?
You should, in full, with the repository transferred to an account you control from day one rather than at the end. Insist on source code ownership, infrastructure in your own cloud account, and documented deployment steps. Digital Heroes hands over repository access at project start precisely because a Gisborne business that cannot get a developer here on short notice needs the option to hire anyone.
Can we run this when the connection drops at a block up the coast?
Yes, and you must design for it explicitly. Anything used past Te Karaka, at Tolaga Bay or on a coastal skid site needs local storage on the device, a queue that survives an app restart, and a conflict rule you have agreed in advance for when two people record the same bin. Retrofitting offline behaviour later costs more than building it in, so raise it in discovery.
How long before we see anything useful?
Six to ten weeks for a first module in real use, if scope is honest. That normally means intake capture running in one shed with one crew while everything else stays on the old process. Anything that promises a full ERP live in three months is either very small in scope or about to become very late.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
How do I vet an agency for an ERP project?
Should I pick Microsoft Dynamics 365 Business Central or build a custom ERP?
Can I start with one ERP module instead of the full system?
Can we keep our current ERP and just build custom modules around it?
How do I calculate whether custom software will pay for itself?
Who can build custom ERP software for a business in Gisborne?
Digital Heroes builds custom ERP software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, so an operator in Gisborne gets an assigned senior team rather than a local account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other ERP software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
