
On most farms, this number simply does not exist. There are approximations, gut feelings, and comparisons with the previous year.
But the exact technical cost — calculated from invoices, crop production costs, feed recipes, and cross-referenced with the current purchase price — remains unattainable without a system that gathers data from all operational areas and blends them automatically.
Origami Effect builds that system.
What does it look like before implementation?
The accountant receives invoices — for fertilizers, feed, plant protection products, services — and logs them. But an invoice for fertilizer does not say on its own whether it relates to crop production for internal feed or external sales.
Someone has to allocate it manually — or no one does, and the cost remains buried in the generic “purchases” category. The zootechnician knows exactly what is happening in the herd. They log veterinary events, observe milk quality, and know which cows had issues last month.
But this data lives in a notebook or spreadsheet and never translates into statistical patterns that could predict future issues.
The finance manager keeps an eye on the budget — but the budget is a plan set at the beginning of the season. Is it still accurate after the zootechnician changes the feed recipe composition? Often, no one knows.
The owner receives a report only when someone finds the time to prepare it. Once a month, maybe once a quarter. By then, the data is several weeks old.
Who does what — data flow and roles
The ecosystem is designed so that each person does exactly what belongs to their role — using the tools they already know. The system collects, links, and processes everything without forcing anyone to act as a human data bridge.
The accountant places invoices in a designated folder. Echo downloads them automatically, recognizes them, and assigns them to the correct category. No extra systems. No change in the workflow.
The finance manager maintains the current Demeter — budgets, feed plans, and financial forecasts for the season. Once Demeter is updated, every invoice that flows through Echo is automatically cross-referenced with the plan.
The zootechnician does two things. First, they define the feed recipe composition in Demeter — which mix, for which group of animals, and during which period. This forms the foundation for calculating feed costs at the individual group level. Second, they enter data about veterinary activity and herd events into Hebe — via a dedicated Excel spreadsheet or PowerApps. Events, illnesses, milk quality observations, and laboratory sample results.
The agronomist logs agrotechnical treatments and plant protection product applications in Gaia. Gaia identifies which of these costs relate to internal feed production — and passes this information to Clio, where it is combined with data from Demeter and Echo to form a complete picture of feed costs.
Clio gathers data from all sources, processes it according to defined logic, and generates reports, alerts, and dashboards.
The owner receives a comprehensive view of the entire operation in Iris without anyone having to manually prepare it.
Five tools — how each of them works
Demeter — planning, budgeting, and feed recipes
Demeter is the farm’s operational model that derives outcomes from the actual physics of the business. The finance manager monitors current operational budgets — for agro production, feed purchases, milk, and the herd. These budgets serve as a benchmark throughout the season. Every invoice entering through Echo is automatically compared against this plan.
The zootechnician sets the feed recipe composition in Demeter — which feed mix for which group of animals, in what proportions, and over what period. This is the critical element for calculating the actual feeding cost of each herd group. When the zootechnician changes a recipe, Demeter automatically recalculates demand and budgets.
Demeter forecasts feed requirements broken down by type, month, and animal group — taking into account herd status, nutritional standards, and seasonality. The system alerts you if a specific feed is at risk of running out at the current purchase pace — 14 days in advance, not when the warehouse is empty.
Echo — invoices and cost identification
Echo pulls invoices automatically from a designated folder. The accountant does not change their routine — they place invoices right where they always have. Echo handles the rest.
Invoices on farms are often bulk orders — a single invoice for fertilizers can apply to both internal feed production and crops meant for external sale. Echo registers the invoice, Gaia identifies the split regarding crop production, and Demeter provides the recipe context. Clio merges these three layers to provide the data needed to calculate the actual feed cost allocated to each group of animals.
The zootechnician can see exactly how much budget remains in each feed category in a dedicated view — without needing to ask the finance manager or accountant.
Gaia — agrotechnical data and crop production costs
Gaia logs agrotechnical treatments and plant protection product (PPP) applications. The agronomist enters data via a dedicated sheet: plot number, date, product, dosage, operator, and surface area.
Gaia identifies costs within crop production — distinguishing which expenditures belong to feed crops and which to cash crops. This information goes to Clio, where it is combined with data from Echo and Demeter to build a full picture of internal feed production costs.
PPP documentation is generated automatically from Gaia’s data — in a format fully compliant with regulatory requirements, ready to be submitted to ARiMR or presented during inspections. Zero re-typing. Zero risk of incomplete documentation.
Alert system: when the PPP cost on a specific plot deviates from historical patterns, Clio detects the anomaly and alerts the agronomist.
Hebe — intelligent zootechnical records
Hebe is not a cost-tracking system — it is an intelligent zootechnical record system. Its role is to capture what is happening in the herd and translate it into statistical patterns that allow you to predict and react. The zootechnician enters data via a streamlined Excel sheet or PowerApps — in a simplified format, without having to navigate a complex software system.
Veterinary events, illnesses, milk quality observations, laboratory sample results (fat %, protein %, somatic cell count), wet events, and group movements.
Hebe powers the Iris dashboards:
- Milk Overview + AI — production, quality, and feeding with AI interpretation. The system sees correlations a human might miss when scanning a spreadsheet — such as the link between feed recipe composition and milk quality the following week, or a pattern of wet events preceding a drop in yield for a specific group.
- Milk Quality — fat %, protein %, monthly trends, and deviations from the norm. Laboratory metrics — most common metrics, mean value analysis, group and period comparisons.
- Wet Events — illness trends, year/illness filters, wide monthly cycle tables. It allows you to see if a specific disease is seasonal, if it affects a particular age group, or if it correlates with other events.
- Herd Size — status by category and year, movements between groups.
- Feed Consumption — usage by animal groups, diet composition, and monthly trends.
- Feed Quality — quality parameters, monthly trends, sections per feed type.
The goal of Hebe is not just record-keeping — it is about translating herd health into numbers and searching for statistical patterns that allow for proactive rather than reactive action.
Clio — orchestration, reporting, and alerts
Clio gathers data from all sources — Demeter, Echo, Gaia, Hebe — processes it, and distributes it to the right people in the right format at the right time. The milk costs displayed in the Iris dashboard result from blending four streams: bulk invoices from Echo, crop production cost identification by Gaia, and detailed identification by Demeter alongside the zootechnician’s feed recipe — all compiled by Clio into a single metric: the actual production cost of a liter of milk, profit margins, and invoice categories.
- Weekly Farm Digest — every Friday at 6:00 PM, the owner receives a complete summary of the week: herd status with anomalies, milk yields, feed purchases, budget execution, completed agrotechnical treatments, and generated PPP documentation. Sent via WhatsApp, Discord, Teams, or email. No one has to manually prepare it.
- Alert System — crop cost anomalies, milk quality drops below thresholds, budget category overruns, feed shortages, or missing data by required deadlines. The alert reaches people wherever they are.
- Plan vs. Actual Report — the budget from Demeter set against execution data from Echo. A live view updated with every single new invoice.
- ARiMR Documentation — automatically generated from Gaia’s data, ready for submission without manual paperwork.
Iris — a dashboard for every role
Iris is an interactive dashboard built in React sitting directly on top of the Clio database. Data from all modules is accessible in one place, updated in real time. Each role has its own view.
Owner — the entire picture. Milk costs, budget execution, herd status, and alerts across all areas. They can drill down to the finest detail.
Zootechnician — their specific area: milk overview with AI, milk quality, laboratory metrics, wet events, herd size, feed consumption, feed quality, and milk costs. Dashboards are engineered around how they think about the herd — not how a financial manager thinks. Finance Manager — budgets, execution, variances, feed forecasts.
Agronomist — plots, treatments, PPP costs, and documentation.
Who is it for
- Farm owners with dairy production who want to know the true cost of production — calculated, not estimated.
- Multi-division and multi-site farms where data lives with different people and never aggregates into a single report.
- Owners who report to banks, cooperatives, or investors and need an up-to-date financial picture without a week-long delay.
- Farms that want to automate PPP documentation, feed controlling, and milk yield reporting — because these processes consume too much time for staff who could be doing higher-value work instead.
Implementation
Origami Effect builds every tool for a specific farm — its herd structure, crop profile, documentation requirements, and reporting needs.
We start with an analysis: where data comes from, who inputs it, who needs it, and in what format. Based on this, we design a system that integrates seamlessly into these processes — without disrupting your team’s workflow.

