Vine-by-vine tracking, season over season

Every vine, every season, one record.

You walk one lap around the perimeter of the block, tapping as you go, and a professional-grade vine-by-vine map is drawn on the spot. That map is the base. From then on, vine status is collected row by row on the same phone: flag a vine, remove it, replant it, take it on and off a secondary irrigation line — and the history stays with that vine, season after season.

Request a demo See how it works

Runs on the phone already in your pocket. No RTK rover, no drone, no GIS specialist or program, no signal.

Ready to walk

0 vines · 0 rows · 0.00 ac

The problem

A planted block doesn't change. What's in each vine space does.

The vine by vine grid of every block is set the year the block goes in — so many rows, so many vine spaces. As seasons go by, the vine spaces don’t change, the vine status at each position changes: a vine dies here, goes symptomatic there, gets pulled and replanted over there.

In the field

Decisions are per vine

Which vine gets pulled, which gets tested, which gets replanted. If the map is wrong, a healthy vine dies and the sick one keeps spreading.

On paper

Records are kept per block

“Some virus in Block 3” doesn't say which vines. By winter, that answer lives in somebody's memory.

The gap

One can't guide the other

Every season, vine-level decisions get made from records that can't track a vine. That is the gap VineIQ closes.

Reporting, spray rates and yields all hang on block acreages; VineIQ's are exact. But the larger problem is seasonal: without an accurate vine map, vine-by-vine tracking is impossible.

VineIQ produces exact vine counts and gives each vine an address. As seasons go by, vines maintain the same address, making seasonal vine-by-vine tracking an exact science.

Know your vineyard, vine-by-vine.

Farming by the vine

The best wine is produced from precision farming.

The stakes

One vine, about one bottle

At ultra-premium yields a vine gives a bottle or two a year. Every decision about that vine — how much water, how much crop, whether it stays — is a decision about that bottle.

The problem

A block is an average. The tank isn't.

Inside one block, vines differ: vigor, age, a replant, a wet corner, a virus nobody has caught yet. Farm the average and the weakest vines set the floor. A few symptomatic vines picked with the rest go into the same tank.

The opportunity

The crew is already at every vine

Suckering, shoot thinning, leaf pulling, cluster thinning, green drop, harvest. Every one of those passes goes down every row, and everything they find is lost unless it lands on the vine.

A great block is a uniform block, and uniformity is made vine by vine.

At the top of the market the wine is decided in the vineyard, before the fruit reaches the winery. The winemaker can only work with what the block gives. What separates a good block from a great one is not the average vine — it is how few vines drag on it: the ones ripening late, the ones carrying too much or too little crop, the ones that should have come out two seasons ago.

Ultra-premium farming has always been per-vine farming. Crop is set by the vine, not by a tons-per-acre target. Weak vines get a second drip line. Young replants are picked separately so their fruit stays out of the top wine. Symptomatic vines are flagged, tested and pulled before the block pays for them. None of that is possible from a block-level record. It needs an address for every vine and a history on it, season after season.

What farming by the vine looks like

Crop set vine by vine. Cluster counts and green drop recorded on the vine that got them, not averaged over the block.
Water where it's needed. Weak vines and dry corners on a second line, mapped, so the whole block ripens together.
Replants tracked by age. Every young vine on record, so its fruit is picked apart from the old vines around it.
Virus found early, by address. Flagged in August, tested in the fall, out in the winter — before the neighbors are infected.
Harvest by the part of the block that is ready. Sub-blocks drawn on the same map, picked on their own day.
Every pass written down. Whatever the crew sees at the vine — shoot count, trunk damage, gopher, trellis — stays with that vine.

VineIQ is the record that kind of farming has always needed: a permanent address for every vine, every pass written onto it, every season beside the last. It is how a good block becomes a great one, and stays that way.

Who built it

Built by a viticulturist, for viticulturists.

I have spent more than twelve years managing vineyards in the Napa Valley, where a real vine-by-vine answer took extensive GIS skills, expensive equipment, and overtime.

Nobody has all three to spare in the middle of a season. So vine statuses remained organized by row in a spreadsheet, with no way to identify exactly which vines had what status from year to year.

VineIQ is what I built instead — in the block, on a phone, assuming no equipment, no specialists and no signal, because most days I had none of the three. It works for one block or four hundred.

Emily Kuhn Founder · Napa Valley, California ✉ Contact Emily

12+ years in vineyard management Cornell University Field-tested on real blocks, not in a demo

Formerly — Michael Wolf Vineyard Services Continuum Estate Harlan Estate UCCE Napa

Emily Kuhn standing at the end of row 50 in a Napa Valley vineyard in full canopy, hills behind. — The office, most of the year.

What it takes

No rover. No drone. No GIS department.

Mapping a vineyard vine by vine has always been possible. It just meant hiring somebody.

Requirement	Mapping a block the old way	With VineIQ
Equipment	An RTK GNSS rover, or a drone and a flight plan	The phone already in your pocket
Who runs it	A GIS technician or a survey contractor	Whoever is already walking the block
Software	A GIS license, and somebody trained to use it	A browser — the dashboard is the map
In the block	A separate mapping pass, taken vine by vine	One lap — the map rides along with the count
Signal	Cloud tools expect service where there isn't any	None needed — your phone will automatically sync with the dashboard once it’s back in service
Turnaround	Hours, if not days, at the computer	The block is drawn before you leave it
Accuracy	Aerial imagery and AI cameras estimate — canopy hides trunks, doubles merge, holes get skipped	A census that must reconcile — a count that doesn't close fails loudly, in the field. The app will tell you your count is off before you leave the vineyard.
Skill required	Specialist training, or a consultant on retainer	If you can count a row, you can do this

And it scales in your favour: walking every row grows with the acres, VineIQ builds your map with the edge. Quadruple the block and every-row quadruples — the VineIQ lap only doubles. The bigger the block, the more one lap saves. See below for animation.

The difference

Every row, or one lap.

The same block, counted both ways, both walkers moving at the same pace. Watch the right-hand one finish.

Counting every row walking

0 ft0:00 min in the block

One lap, with VineIQ walking

0 ft0:00 min in the block

Walking every row	—
One lap, with VineIQ	—
Less walking	—
Time saved	—

A 34-row block, — vines, about two acres. Both walkers at 1.7 mph.

How it works

One lap makes the map. After that, every part of the operation can be farmed vine by vine.

The lap is the only step that always comes first: it gives every vine in the block an address. From then on, whatever you already do in the block — scouting, sprays, irrigation, crop, harvest, phenology — can be recorded and managed against that address instead of against the block average.

First, always

Map the block

One lap, the day the block is first walked

STEP 1

One lap of the block

Count the first row end to end, cross the headland tapping how each row differs from the last — minus two vines, plus one, same — then count the far row and continue collecting row deltas on the opposite side on the way back. One lap around the block, and nobody walks every row.

STEP 2 · AUTOMATIC

The block draws itself

Those differences rebuild every row, every vine in it, the outline and the acreage. The far row count has to agree with the first taking into account the deltas around the outside, and when it doesn't, it will say so before you leave the vineyard.

STEP 3 · AUTOMATIC

It syncs with the VineIQ Dashboard

The phone syncs when it finds a signal. Every counter's data lands in one dashboard, and edits made in the dashboard are received back on the phone map. Every vine now has an address: its row and its position.

From then on

Farm it vine by vine

Every season, every job, on the map you already made

IN THE ROW

Open the mapped block

The phone already knows every row and how many vines are in each. Pick the row you are standing at and the phone counts along with you: row 14, vine 37 of 112. No GPS is used at the vine — the address is the position.

AT THE VINE

Record whatever the job is

A symptom, a dead vine, a replant. A spot spray on these twelve vines. The vine that went onto a second drip line. A cluster count, a trunk repair, a gopher. Fields you define. One tap files it to that vine's address.

AUTOMATIC

It's on the vine, for good

The same vine lights up on the dashboard, on the printed map for the crew, and again next season. Tap any vine for its history, across every kind of record that has ever been filed to it.

vine statusvirus symptomsspot spraysirrigation linesphenologycluster countscrop thinningreplant yeartrellis repairfertilizer rate…anything worth pinning to a vine

Vine status is where most growers start, and for virus it is the record that matters most. It is not where the map stops. Every module below works on the same addresses, and nothing is re-entered.

Seen in the field

This is what comes back from one lap.

The VineIQ vine grid overlaid on satellite imagery of a real block: 65 rows and five sub-blocks of dots aligned with the planted rows beneath them. — **The map, on the ground.** A real walked block — 65 rows, five sub-blocks, every vine is represented by a dot sitting on the row it grows in. Satellite view is one toggle; the grid is the record. Imagery © Esri.

The VineIQ counting screen on a phone, mid-walk: currently at row 11, 564 vines counted, GPS recording, and the minus-three to plus-three delta pad. — **Mid-walk, on a phone.** The whole job is that row of +/- buttons: how does this row differ from the last.

What you get

One map. Everything else builds on it.

The lap gives you the map, and the map gives every vine an address. The modules are what you do with those addresses. Take the ones the job calls for — they all work on the blocks you have already mapped, and nothing is re-entered.

spot sprayfertilizer ratevirus symptomsreplant yearfrost damagegopher damagetrellis repairsecond drip linegraft failurecrop thinning…anything worth pinning to a vine

Map

base

The lap, the count that has to close, and a professional-grade map the day the block is walked. Every account starts here.

Every vine as a point on real imagery, plus rows, boundary and exact acreage
An address for every vine: row and position, the same next season
Printable, numbered north-up block maps and ranch maps
Shapefile and GeoJSON, opening in ArcGIS, QGIS, Google Earth and farm platforms
Numbered vine list as CSV; vineyard statistics by block, ranch and variety
Miscounts flagged on the spot — a walk that doesn't close says so in the field
A block you can sell from: hand the map to a fruit buyer, an appraiser or a lender
The dashboard is the map — nothing to install, unlimited users

Phenology

included with Map

Bud break, bloom, veraison, harvest and pruning dates for every block
Entered on one sheet like a spreadsheet, or block by block from the phone
Season over season, on the same grid

Vine status

add-on

Dead, missing, symptomatic, replanted, treated — logged vine by vine as you walk the rows
Every record on the map at its address, colored by status
Tap a vine for its history; this season sits beside last season's
Printable north-up map of flagged vines for the removal crew
Flagged vines out as shapefile, GeoJSON or CSV

Vineyard database

add-on

Everything else the operation records, on the same vines. One add-on, and it keeps growing.

Applications. Sprays from the phone, by block or drawn sub-block. Product list, work orders, use report.
Irrigation. Lines, double poly, valves and zones on the vines that carry them. Printable irrigation map.
Harvest and yield. Crop estimates from cluster counts on named vines, then what actually came off: pick dates, tons and bins by block and sub-block.
Labor. Crews, tasks and hours against the blocks they worked. coming

Coming next: labor records inside the Vineyard database, then camera mapping and disease scanning as modules of their own.

Viruses don’t care about your block average.

There is no cure. Managing red blotch — or leafroll — means finding the infected vines and getting them out before it spreads, and a block-level note can never do that. “Some virus in Block 3” is a worry; row 18, vine 22 — flagged in August, confirmed by the fall test, pulled in the winter, replant tracked the next spring — is a plan. Vine-level records over the seasons are how a block outruns a virus.

Who it's for

One block or four hundred, the walk is the same.

What changes with size is how many different people have to get it right.

Vineyard management companies

Every block gets the same record no matter who walked it — and you get exact maps to share with owners or fruit buyers. One login, every ranch, every counter.

Growers & estates

Find out what's actually planted, holes included — then walk the rows each season and watch it move: replants vine by vine, mortality year over year, and a count that is current the day the block is appraised or sold.

Wineries sourcing fruit

Know what you're contracting for: real counts, real acreage, real boundaries — tied to a map instead of a number in an email.

PCAs & consultants

Write recommendations against a block with an address for every vine, with the permit and site IDs on the same record.

Why it holds up in the field

Designed around the block, not around the office.

No signal needed: Counting, mapping and records all work with no service. The phone syncs later.
No extra hardware: No drone, no RTK rover, no survey crew — a phone and a walk you were doing anyway.
29 blocks, 103,000 vines: Walked and mapped on twelve Napa Valley ranches in the 2026 season. Row orientation measured from the walk matched hand-drawn ground truth on every block we checked it against.
Nothing is thrown away: Deleted blocks stay recoverable, and every night's backup is verified by actually restoring it.

Pricing

Priced on the acres you've mapped, not the people who log in.

One price per account, billed annually, with as many users and blocks as you need. Map is the base, and every account starts there. Vine status and the Vineyard database are add-ons: take one, both, or all of it together. The price is on the page, because you shouldn't have to book a sales call to find out what something costs.

Map

The base

Required · every account starts here

$30

per mapped acre, per year · $1,000 minimum

Pays for itself in minutes. Two maps a year and it has already earned its keep. Make only four and that is $250 a map for a professional-grade, georeferenced vine map — a fraction of what a GIS professional charges to draw one.

Unlimited blocks, walks, counters and users
Every vine on the map, on real imagery
Full GIS export — shapefile, GeoJSON, CSV
Printable, numbered block maps

Vine status

add-on

$15

per mapped acre, per year

Symptoms and statuses on every vine
Season over season, on the same permanent grid
Rollups by block, row and ranch
Flagged-vine exports for the removal crew

Vineyard database

add-on

$20

per mapped acre, per year

Applications — sprays and tank mixes from the phone, a master product list with rates and REIs, printable work orders, the pesticide use report
Irrigation — primary and secondary lines, double poly, valves and zones on the block record
Harvest and yield — crop estimates from cluster counts on named vines, then what actually came off: pick dates, tons and bins by block and sub-block
Labor — crews, tasks and hours against the blocks they worked coming

All of it together — Map, Vine status and the Vineyard database: $50 per acre, per year. Small growers and consultants are priced case by case — get in touch.

Vineyard	Map	Vine status	Vineyard database	All of it, per year
40 acres	$1,200	$600	$800	$2,000
100 acres	$3,000	$1,500	$2,000	$5,000
250 acres	$7,500	$3,750	$5,000	$12,500

What that comes to

A 100-acre estate · Map + Vine status

Map · 100 mapped acres × $30	$3,000
Vine status · 100 mapped acres × $15	$1,500
Per year, one account, every user and every block	$4,500

Billed annually. Updates and support included. Year one is billed on your estimate of the acreage and trued up at renewal to what you actually mapped.

No charge to try it on one block. Walk a block, look at what comes out, and decide after you've seen your own numbers rather than ours.

The acres are the acres you mapped. VineIQ measures them from your own count and spacing — not a number anyone types in — and you can see the figure in your dashboard at any time.

Your data stays yours. Leave whenever you like and take the shapefiles, GeoJSON and CSV with you — it is not pooled with anyone else's and it is never sold.

The Vineyard database keeps growing at the same price. Labor records are the next addition. Camera mapping and disease scanning will follow as modules of their own, layered onto the same vine records — the map never loses a feature to a module, and you only pay for the ones you use.

Questions

The ones growers ask first.

How long does a block take to count?

One lap of the block. There's no setup, no second pass and no walking every row — the mapping rides along with the count.

What if the counter makes a mistake?

The block has to close, and when it doesn't, VineIQ says so before the counter leaves. Any entry can be corrected afterwards without re-walking.

What about the AI camera systems?

They're real, and useful — we're building a camera module ourselves. But a camera counts what it can see, and canopy hides trunks, merges doubled vines, and skips holes: the result is an estimate. The lap is different in kind — the far row has to reconcile against the first, so the count is exact or it fails loudly before the crew leaves. Cameras will layer onto the walked record. They won't replace it.

Do we need RTK, a drone, or somebody who knows GIS?

None of the three. The block is mapped from the walk plus one line drawn along a row on satellite imagery — if they can count a row, they can map a block.

Do we need to replace the software we already use?

No. Export your maps to Shapefiles, GeoJSON and CSVs — it opens in the programs you already run.

Who can see our data?

Your account, and nobody else's. It's your vineyard data — not pooled, not sold.

Does it work on old phones?

It runs in the browser — nothing to install. If the phone can open a web page, it can count a block, and it keeps working after that with no service.

Your first season

From the first lap to a record that builds.

Kickoff

An account and a first block

Logins for the team, and half a day on site walking the first block together. Most crews are counting on their own before lunch.

Mapping

One lap per block

Fitted around the season's work. Counting vines doesn't depend on the canopy, so mapping runs through harvest and dormancy. A block is done when its walk closes and it appears in the dashboard.

First records

Walk the rows with a job in hand

Scouts file symptoms by address in the symptom window; sprays, irrigation lines and crop counts go on the same vines as the season calls for them. Every action taken on a vine is recorded on it.

Next season

The same addresses, again

Next year's walk lands on the vines it did last year. The record builds, and the decision about which vine comes out gets more precise every season.

Request a demo

Bring us one block. We'll show you the whole thing.

Watch a block you already know get walked, counted and mapped in one lap. Compare it to your current counts — then keep using it: walk the rows, log individual vines by symptom and category, and the block's record has begun.

Email us hello@vine-iq.com