Vine-by-vine tracking, season over season
Every vine, every season, one record.
You walk one lap around the perimeter of the block, 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.
Runs on the phone already in your pocket. No RTK rover, no drone, no GIS specialist or program, no signal.
Ready to walk
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.
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.
Farming by the vine: why it makes the wine
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.
Know your vineyard, vine-by-vine.
The difference
Every row, or one lap.
No rover. No drone. No GIS department. Mapping a vineyard vine by vine has always been possible. It just meant hiring somebody.
The same block, counted both ways, both walkers moving at the same pace. Watch the right-hand one finish.
0 ft0:00 min in the block
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.
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.
The old way vs. VineIQ, line by line
| 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 | An exact census, checked 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 |
How it works
One lap makes the map. After that, every part of the operation can be farmed vine by vine.
The lap gives every vine in the block an address. From then on, whatever you already do in the block is recorded against that address instead of against the block average.
Map the block
One lap, the day the block is first walkedSTEP 1
One lap of the block
Walk once around the block with the phone in your hand, entering the count as you go. One lap, and nobody walks every row.
STEP 2 · AUTOMATIC
The block draws itself
From that one lap, VineIQ rebuilds every row, every vine in it, the outline and the acreage. The count is checked as you go, and when something doesn't add up, 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.
Farm it vine by vine
Every season, every job, on the map you already madeSee the steps
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.
What you get
One map. Everything else builds on it.
The map gives every vine an address. The modules are what you do with those addresses, and nothing is re-entered.
Map
baseThe lap, a count checked in the field, and a professional-grade map the day the block is walked. Every account starts here.
See everything
- 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 count that doesn't add up 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 MapBud break, bloom and veraison for every block, season over season.
See everything
- Bud break, bloom and veraison 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-onDead, missing, symptomatic, replanted: logged vine by vine, on the map at its address.
See everything
- 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-onEverything else the operation records, on the same vines. One add-on.
See everything
- 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.
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.
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; Vine status and the Vineyard database are add-ons.
Map
The baseRequired · every account starts here
$30
per mapped acre, per year · $1,000 minimum
What's included
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
What's included
- 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
What's included
- 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
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 |
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.
Billing, your acres and your data
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.
You pay for what is live today. The Vineyard database is Applications, Irrigation and Harvest and yield. Labor, 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.
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.
Questions
The ones growers ask first.
Who is it for?
What does the first season look like?
How long does a block take to count?
What if the counter makes a mistake?
What about the AI camera systems?
Do we need RTK, a drone, or somebody who knows GIS?
Do we need to replace the software we already use?
Who can see our data?
Does it work on old phones?
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.