AI built around how a forest operation runs.
For growers and managers of forest space. From the cruise that sets the plan to the load leaving the block, with levies and contractor pay settled without the spreadsheet.
Real numbers from real operations.
Every figure traces to a working paper. Where a number is unproven, we say so.
Four phases, from standing timber to settled account.
Every forest operation runs the same cycle, whatever the licence and whatever the ground. Here is where the information breaks down at each stage, and what changes when it does not.
Plan & Sell
Cruise · forest inventory · bid · standing sale
A cruise is a sample taken on a date, and the stand has not stopped growing since. Some of those surveys are a year or more old. Growth outruns the estimate in one block and falls short in another, and the evidence to tell which is which sits in a legacy system nobody can refresh cheaply. Meanwhile you are bidding and selling against that picture as though it were still true.
Quarri refreshes an ageing cruise against what the ground actually yielded, so you bid on the stand you have today rather than the one you surveyed last year.
- Ageing surveys refreshed against delivered volume
- Estimate against actual, block by block
- Bids priced on real supply, not a stale cruise
- Stand movement carried into the margin picture
A block delivering 71% of its cruise estimate is a bid problem and a budget problem, not just a harvesting one.
Harvest & Measurement
Fell · skid · measure · cut log
Who took what, from where, and under which entitlement. That question is a compliance obligation before it is an operational one, and the record answering it is usually paper: cut logs, stand reports and contractor dockets that were never designed to be compared with each other. On top of that, the weather decides when crews can work at all, and frozen ground and spring breakup move volumes far more than crew performance does.
Quarri reads your paper cut logs and ties every load to its block, licence and entitlement, so the compliance record builds itself as you cut.
- Paper cut logs and stand reports made comparable
- Every load tied to block, licence and entitlement
- Volume cut reconciled against bid and estimate
- Contractor splits preserved exactly as written
- Operability rated daily, a fortnight ahead
The compliance answer to who took what from where, built out of the paper the crews already produce.
Haulage & Delivery
Load · way slip · haul · deliver
Who moved what, where to, and on whose account. The answer arrives as way slips and bills of lading, mostly on paper, in volume, and often weeks after the load ran. The hard part is not the haulage itself but the allocation: a single load can carry entitlements for a landowner, a contractor and a levy, each governed by a different rule, and those rules change more often than anyone would like.
Quarri splits every load by rule rather than by hand, so who is owed what stays consistent across thousands of way slips and changes the moment you change the rule.
- Paper way slips read in volume, never keyed
- Complex splits applied by rule, not by hand
- Rules edited by your team, no release needed
- Hauler pay from the record that proves it
A single load carrying three entitlements, each on a different basis. Doing this by hand is where the leakage lives.
Scale & Settlement
Scale · accrue · reconcile · release
This is where the whole cycle has to add up. Scale data proves the volume, the levy accrual turns it into a liability, and an invoice arrives from the authority months later to be matched against it. Compare at the month total and it ties. Compare at the load and a timing difference, a rate error and a load that never should have been charged stop looking alike.
Quarri matches the accrual to the invoice at bill-of-lading level, so a rate error stops looking like a timing difference and nothing unmatched disappears into a monthly total.
- Accrual drafted from live scale data
- Matched per bill of lading, on your tolerances
- Anything unmatched ages in view, never absorbed
- Release written back as a postable file
Over 1,400 bills of lading released across 76 invoices in one cycle, surfacing an $80k over-accrual credit.
AI at the foundation. Not retrofitted.
Most software for this chain was built as a form. Quarri was built as a model of your operation.
- Their fields, your words mapped in
- Exceptions become change requests
- Paper is a keying job
- Every run costs a model call
- New questions join the queue
- Reports you wait to receive
- Scale by hiring around the gaps
- Your words, from day one
- Exceptions become rules you edit
- Paper read at volume, deterministically
- 100x cheaper per execution
- Questions asked in plain English
- Dashboards and scripts you build yourself
- Scale by pointing it wider
Ask it in plain English. Across all four phases.
Because cruise, cut log, way slip and scale ticket all land in one governed layer, a question can cross the whole cycle instead of stopping at a system boundary. That is not only a smoother way to operate. It is a margin lever, because the questions worth asking are the ones nobody could previously afford to ask.
- Any question across the cycle, in plain English
- Numbers computed, so the answer matches the ledger
- Dashboards and scripts your team builds and shares
- Alerts when a rate drifts or a tolerance breaks
Margin after haulage and levies, per block. The question crosses four systems; the answer does not care.
A forestry operation
Reconciling timber levies by hand across 116 files a month, regulator and authority invoice PDFs and Excel backup, was consuming days of the finance team's month.
Quarri drafts the accrual from live scale data, reads every scanned invoice, matches at bill-of-lading level and posts the release. One cycle covered over 1,400 bills of lading across 76 invoices and surfaced an $80k over-accrual credit. It also caught a fuel surcharge accrued at $1.50/tonne but invoiced at $9.00, a rate gap nobody had spotted. Read the case study.
Your whole operation, on the map.
Everything above is answered in tables. The one question a forest operation asks constantly, and a table answers badly, is where. Blocks, licences, haul routes and remaining volume are all spatial, and right now you read the map in one system and the numbers in another. We are building the version where they are the same screen.
- Blocks shaded by volume remaining on contract
- Haul distance and route cost in the margin picture
- Harvest plans and operability read on the map
A design sketch rather than a screenshot. It is not in the product today, and we would rather show you early and hear what it needs to do.
Most operators sit on more than one link.
See it on your own data.
Live in two weeks, on the systems you already run.