Automation Could Change What Is Worth Growing
Streamline's snips-per-pound problem illustrates how affordable repeated work could change crop choices and the economics of neighborhood food production.
Editorial visualization · evidence, proposals, and future scenarios are labeled in the article.
The cost of harvesting a crop can decide whether it gets planted at all.
We ran into that at Streamline with cherry tomatoes. The labor required per pound made them uneconomic for us. I call it snips per pound: too many individual picking actions for the value of the finished pound.
Cherry clusters can also ripen unevenly. Collecting the ready fruit can require returning to the same plants repeatedly.
For a household eating tomatoes across the week, that progression can be useful. For an operation paying people to accumulate saleable pounds, it adds work.
The same biological trait can be a liability or an advantage depending on the work and market around it.
That is the larger opportunity agricultural robotics raises: a change in the cost of work could change which production patterns are viable.
A selective harvest involves more than picking. Someone has to reach the crop, inspect it, prepare the equipment, perform the work, and handle the result. Gathering more output during one visit helps spread those costs.
A system designed around frequent small harvests has to make the repeated visits worthwhile.
A robot dispatched across town to collect a handful of tomatoes could be an expensive way to obtain lunch. A qualified machine already working on the property presents a different case. If it can add the harvest without substantial travel, setup, or intervention, the smallest worthwhile job could become smaller.
The mechanism matters. Affordable repetition would come from reducing the resources needed per visit and per accepted harvest. Putting the word autonomous in front of the existing workflow does not establish that reduction.
It also changes what should be measured. Pounds picked are insufficient if the work damages fruit, leaves unsuitable product in the container, or requires someone to correct it. Accepted food and total resources used are the relevant comparison.
Our cherry-tomato experience therefore supplies a specific test. Compare the old labor constraint with the complete cost of a proposed work system under an actual harvest schedule. Determine whether selective picking becomes economical at the required quality and service level.
If it does, growers gain another design option. Concentrated ripening can serve bulk collection. A succession of ripe fruit can serve recurring meals when frequent attention is affordable. The appropriate trait depends on the intended use.
That reasoning extends beyond tomatoes to crops and tasks whose economics are sensitive to the size and frequency of the job. It does not establish that every small plot or demanding variety should be grown. Equipment, crop fit, dependable demand, and fulfillment still determine the result.
The distributed-farm scenario follows one possible consequence: specialized farms could support smaller sites whose harvests serve nearby consumption. Professional growers could contribute starts, crop expertise, and reliable volume alongside household production.
The food might replace a household purchase, be sold, or enter an agreed exchange. Each is a different form of value; the output should be counted once, against the resources used to produce and handle it.
That is what it means to design biology, autonomy, and unit economics together. Crop characteristics affect machine requirements. Work costs affect crop choices. Customer use determines what the result is worth.
Snips per pound explains why cherries failed our earlier economics. It gives us a concrete reason to test the decision again if the work changes.
The larger question is which food systems become viable when small, frequent jobs can finally pay their way.
From the thesis to the operating system.
See what Streamline OS does today, examine the evidence behind the current build, or bring us a greenhouse problem worth reconstructing.