The Eighty That Isn't

Every township has one. The Hoffman eighty, the Miller quarter, the piece behind the church. The names are older than anyone running equipment across them, and so are the acre counts that ride along. Ask how big the Hoffman eighty is and you'll get the answer the coffee shop has given for a generation: call it 75, the waterway's in there.

That number is about to price three passes of custom work.

The only quantity nobody measures

A custom operator's bill is quantity times rate, and the rate side gets plenty of attention. It's printed, argued over in the winter, adjusted when fertilizer moves. The quantity side is treated as settled, because the field has a name and the name has a number.

Walk through where the number came from. Nobody paced it off. The farmer's father and the applicator before you settled on 75 at a kitchen table sometime in the nineties: a deeded 80, minus a guess at the waterway and the pond corner. They rounded to something both men could carry in their heads. It was a negotiation, not a measurement, and like most negotiations it rounded toward the man paying.

Everything else in these industries gets measured at the moment of billing. Rock crosses a scale. Grain runs over a certified weigher at the elevator. Hours come off a timecard. Acres are the one billing quantity that gets remembered instead, and the memory belongs to the customer.

What makes this a strange leak is that the measured number already exists. Twice. The farmer's own FSA records carry the field at 76.8 tillable acres, measured from the air by the county. And the monitor in your sprayer logged 78.1 acres covered on the last pass, boundary plus end rows, written to a card that rides around in the cab. Two measurements, both sitting in filing cabinets, while the work order says 75 because the work order copies the field list, and the field list copies the kitchen table.

Corrected in one direction

A called acre would be harmless if the errors broke both ways. They don't, and the reason is who checks.

When a called number runs high, it gets caught fast. The farmer pays per-acre bills all year, seed, fertilizer, custom work, crop insurance, and he knows his tillable acres because his FSA paperwork and his crop insurance both carry them to the decimal. Bill the Hoffman eighty at 80 and the phone rings before the ink dries. You adjust, apologize, and the field list gets corrected. Downward.

When the called number runs low, which document speaks up? The invoice matches the work order. The work order matches the field list. The monitor card that knows better is in a drawer, and the FSA map that knows better is in the customer's drawer. Nothing in the paper trail disagrees with the paper trail. So over the decades a field list only ever moves one direction, one phone call at a time. An operation that's sprayed the same township for twenty years is running on the most thoroughly negotiated acres in the county.

Then the leak multiplies, because this isn't a miskeyed ticket that costs you once. The acres are wrong in the reference, so every pass inherits them. Burndown, in-crop, fungicide: the same missing ground leaks three times a season, every season, on every field whose call is light.

Put numbers on it with your own field list. An outfit covering 38,000 billed acres a year whose calls run 2.5 percent light, which is two quiet acres on an eighty, is covering something like 950 acres a season that never reach an invoice. At $9.50 an acre, that's roughly $9,000 of work performed and chemical hauled, billed to no one. Nothing was lost or stolen. The quantity was just agreed to, a generation ago, by somebody else.

flowchart TD
  A["Kitchen table, 1998: call it 75"] --> B["Field list: Hoffman eighty, 75 acres"]
  B --> C["Work order: 75 acres"]
  C --> D["Invoice: 75 acres, every pass"]
  E["FSA record: 76.8 tillable acres"] --> F["Nobody compares them"]
  G["Monitor: 78.1 acres covered"] --> F
  D --> F
  F --> H["2 acres leak, three passes a year"]

Put the acre on paper

The position worth arguing at the kitchen table is this: a field's billable acres should be a fact on file, measured once, not a story everyone agrees to retell. Use the FSA tillable figure, or measure the boundary yourself one afternoon with the same monitor you already own. If a longtime customer insists on the old call, fine, keep the business and keep the call. But write the measured number next to it, with a date. The two acres stop being a leak the moment they become a discount you chose, sized in dollars, reviewable at renewal like any other term.

The pushback is fair, and half of it is right. Machine acres include your overlap: the double-covered end rows, the wheel slip on point rows, the pass you repeated where the boom shut off. A farmer who pays monitor acres is paying for your driving, and he shouldn't. So cap the bill at the field's measured boundary and let the monitor serve as the check that you actually covered it, not as the invoice. The other half of the pushback, that the neighbors will talk if the eighty suddenly bills at 76.8, is real too. Neighbors talk. They also all farm fields whose calls are light, which is why this conversation pays for itself across the whole route.

What can't survive is the current arrangement, where the rate is printed to the dime and the quantity is folklore.

Nothing changes in the cab

The fix asks nothing of the person doing the work. No tablet mounted next to the monitor, no app the applicator has to feed between fields. The paper work order stays paper, filled out the way it always was. The monitor keeps logging what it logs.

What changes is behind the office door. The field list, with measured acres per field per customer, is reference data, keyed once when somebody actually decides. Per-acre rates by pass type are billing rules. The day's work orders get digitized as written, and one whose acres don't match the field's acres on file gets flagged that day, while the operator still remembers whether he sprayed the point rows or skipped them. Invoice totals assemble from tickets that cleared. That slice is Termco's: reading the paperwork the operation already produces, flagging what breaks a rule, holding the rules and the reference data, assembling the totals. Which number wins for a given customer stays entirely your call. It just gets made once, in daylight, instead of inherited forever.

Count your eighties

The test costs one evening at the desk. Pull your twenty biggest fields and write three columns: the called acres you bill, the FSA tillable acres your customer could read you over the phone, and the last monitor total you can find. Multiply the gap by your passes and your rate. Then decide which fields are discounts and which are just old.

If you'd like a second reader, send 10-20 sample tickets or work orders to hi@termco.ai and we'll send back what we find within 48 hours. The kitchen-table numbers tend to show up on the first pass through.