Growing, food and forestry

Costs are up, and every audit still wants the same records in a different layout

We cannot change grape, apple or log prices, the tariff or the price of diesel. We build software that records the spray, harvest, crew and contractor facts once, on the block or the boat, and lays them out for whoever asks, so compliance takes less of your season.

1 · Where the money and the hours go

Lower prices, higher costs, and the same record wanted five ways

Grape contracts are hard to get, the US tariff has eaten into apple returns, and diesel has hit everyone with a ute, a skidder or a boat. Then the NZGAP auditor, the marketer, the winery and WorkSafe each want the same facts in their own layout: spray diary and withholding periods, bins by block, who was inducted, which contractor was on the skid site and when. Those facts sit in a notebook in the ute, a whiteboard in the packhouse and three spreadsheets, and someone pulls them together at night or the week before the audit. After the 2025 floods, many owners also had to rebuild dates, photos and costs by block for an insurer or a recovery grant.

A grower, winery, seafood or forestry businessTodayWith the software in place

Audit and compliance recordsThe same spray, harvest, hygiene and training facts are written onto separate forms for NZGAP, the marketer or winery and other schemes, then pulled together by hand before the audit.Each fact is captured once when the job is done, linked to the block, lot or crew, and laid out for whichever audit or buyer asks. Your own responsible person decides what must be kept and signs it off.

Contractors and health and safety recordsContractor sign-ins, inductions and hazard notes on paper at the gate, the skid site or the wharf, hard to find when someone asks.Sign-in, induction and hazard notes on a phone, kept against the site and the date, so the records you need as a PCBU can be found. The software keeps records; it does not make a site safe.

Cost per block, bin, tonne or tripYou find out what a block, contract or harvest really cost after the season, if at all, from the payroll, fuel cards and invoices.Hours, inputs, fuel, cartage and packing tied to each block, lot or trip as they happen, so decisions to mothball, renegotiate or defer are made on your own numbers. It shows the costs; it cannot change the price.

Seasonal crewInductions on paper, rosters changed by text, hours or bin counts re-entered for the pay run on Sunday night.Induction and crew lists on a phone, hours or piece rates captured once by the crew leader, pay-run inputs ready for payroll.

Floods and adverse eventsLosses rebuilt from memory, phone photos and receipts for the insurer or the recovery grant.Damage logged with photo, location, block and date as you walk the property, and costs and clean-up hours collected against the event, ready to hand over. It does not guarantee any payout.

We cannot change grape, apple or log prices, the tariff or the weather. We can make the records take less of your season and show your costs by block, lot or trip. Your responsible people decide what must be kept and sign it off.

Watch it happen Try it yourself

2 · Automate the process

Watch a trade order from website to paid

A restaurant orders twelve cases from a winery. Watch it go from the website order to the payment matched in Xero, with a voice-over. Or have one written for your own operation. The businesses, people and prices are made up.

Booking: the customer fills in the form on the website.
Chat: the AI assistant asks the questions a good office person would ask.
Plan: the chat becomes a job sheet with tasks, materials and a time estimate.
Quote: priced from the price list, approved by the owner, then sent.
Schedule: booked into the first free time and confirmed by the customer.
Updates: texts go out as the work moves.
Paid: the payment is matched to the invoice in Xero.

Try it yourself

Live demos set up for your kind of business

Each demo opens on an example that fits this page. They are illustrations: a business version needs your own rules, information and agreed connections.

Enquiries for a winery

Ask a fictional winery about tastings, group visits or an order and see what the assistant collects.

Try it as a winery

Invoice inbox with a packaging invoice

See a packaging supplier's invoice read, checked and prepared for your accounts.

Try the invoice inbox

Run sheet for a contracting crew

Arrange a vineyard and orchard contracting crew's field jobs into a run sheet. It illustrates scheduling field work; it is not a harvest, forestry or production-planning system.

Try the scheduler

3 · Stand apart

Then add something the others do not have

Once the routine work runs by itself, the same records can do more for you and your customers. These are possibilities we can scope around your operation.

One record, every audit

Capture spray applications, withholding periods, harvest, hygiene and training once, and produce the layout each scheme or buyer asks for (NZGAP, marketer or winery requirements, contractor records). Scoped with your auditor and responsible person; it prepares records for review and promises no audit result. A three-person team can build this on forms, a database and report templates.

Speak the work record

A crew leader says what was done on the block or the boat; the software drafts a structured record (block, date, product, rate, crew) for someone to check and confirm. Works offline in the orchard, vineyard, forest or at sea and syncs later. Speech-to-text plus a confirm step, never an unchecked entry.

Cost per block, bin or trip

Pull hours, inputs, fuel and cartage from the records and accounting system you already have and join them to the block, lot or trip, so you can see which blocks, contracts or runs lose money. Your own numbers only, with no outside benchmarks.

Lot traceback on request

When a marketer, buyer or MPI asks where a lot came from, show which blocks, bins, pickers and dates went into it from records already captured. It speeds up the answer; it does not improve food safety or biosecurity outcomes.

First step

A sensible first project

Choose one record your team completes regularly, such as a work sheet or delivery record. Identify who enters it, who checks it and where the details go next.

Build and trial that workflow with the people using it before extending it to other records or teams.

Questions

Questions before you start

Can it work where the internet is unreliable?

Connectivity needs to be part of the design from the start. We assess your locations and workflow before recommending an approach.

Can it support traceability or required records?

We can assess software against the records and checks you specify. Your responsible people need to confirm the applicable requirements and validate the result.

Can temporary staff use it?

The workflow should use clear instructions and only the fields needed for the task. Testing needs to include the people who will use it during busy periods.

See all industries · See all live demos

Based in Nelson, working with businesses across Nelson Tasman and the top of the South. Meet the team