Farm management.
Full control of milk, feed, and herd cost.

On most farms, this number does not exist. There are approximations, there is experience, and there are year-over-year comparisons.

But the exact technical cost, calculated from invoices, crop-production costs, feed recipes, and matched with current milk purchase prices, is impossible without a system that collects data from all operational areas and merges it automatically.

Origami Effect builds that system.

What does it look like before implementation?

The accountant receives invoices for fertilizers, feed, plant-protection products, and services, then books them. But one fertilizer invoice does not say whether it belongs to feed-crop production or external crop sales.

Someone must assign it manually, or no one does and the cost remains in a generic purchases category. The zootechnician knows what is happening in the herd. They log veterinary events, observe milk quality, and know which cows had problems last month.

But this data lives in notebooks or spreadsheets and never turns into statistical patterns that can predict anything.

The finance manager controls budget, but budget is only the plan set at the season start. Is it still valid after a feed recipe change by the zootechnician? Often nobody knows.

The owner receives reports only when someone finds time to prepare them. Once a month, maybe once a quarter. At that point, data is already weeks old.

Who does what, data flow and roles

The ecosystem is designed so each person does exactly what belongs to their role, in tools they already know. The system collects, merges, and processes without assigning anyone the role of data bridge.

The accountant puts invoices in a dedicated folder. Echo pulls them automatically, recognizes them, and maps them to categories. No extra systems. No process disruption.

The finance manager maintains current Demeter: budgets, feed plans, and financial forecasts for the season. Once Demeter is updated, each invoice from Echo is automatically matched against plan.

The zootechnician does two things. First, they define feed recipe composition in Demeter: which mix, for which animal group, in which period. This is the foundation for calculating feed cost per group. Second, they enter veterinary activity and herd events into Hebe through dedicated Excel sheets or PowerApps: events, illnesses, milk quality observations, and lab sample results.

The agronomist logs agrotechnical treatments and plant-protection product applications in Gaia. Gaia identifies which costs relate to internal feed production and passes this to Clio, where it is merged with Demeter and Echo into a complete feed-cost picture.

Clio gathers data from all sources, processes it by defined logic, and generates reports, alerts, and dashboards.

The owner gets the full view in Iris without anyone preparing it manually.

Five tools, how each one works

Demeter, planning, budgeting, and feed recipes

Demeter is the farm operations model that derives outcomes from business physics. The finance manager tracks current operating budgets for crop production, feed purchasing, milk, and herd. These budgets remain the benchmark throughout the season. Every invoice entering via Echo is automatically compared with this plan.

The zootechnician defines feed recipe composition in Demeter: which mix for which herd group, in what ratio, and in what period. This is critical for real feeding cost per group. When recipe changes, Demeter recalculates demand and budgets automatically.

Demeter forecasts feed demand by type, month, and herd group, considering herd status, nutrition standards, and seasonality. The system alerts if a specific feed may run out at current purchasing pace, 14 days in advance, not when storage is empty.

Echo, invoices and cost identification

Echo pulls invoices automatically from a dedicated folder. The accountant does not change workflow, they place invoices where they always do. Echo handles the rest.

Farm invoices are often aggregated. One fertilizer invoice may include both internal feed-crop and external-sales crop costs. Echo records the invoice, Gaia identifies crop split, Demeter provides recipe context. Clio combines these layers to calculate real feed cost per herd group.

The zootechnician sees remaining budget by feed category in a dedicated view, without asking finance or accounting.

Gaia, agrotechnical data and crop-production cost

Gaia logs agrotechnical treatments and plant-protection product applications. The agronomist enters plot number, date, product, dosage, operator, and area in a dedicated sheet.

Gaia identifies crop-production costs: which expenses belong to feed crops and which to cash crops. This goes to Clio where it is combined with Echo and Demeter into full in-house feed production cost.

Plant-protection documentation is generated automatically from Gaia data in compliance-ready format, ready for ARiMR submission or inspections. Zero retyping, zero risk of incomplete documentation.

Alert layer: if plant-protection cost on a specific plot deviates from historical patterns, Clio detects anomaly and alerts the agronomist.

Hebe, intelligent zootechnical records

Hebe is not a cost system, it is intelligent zootechnical records. Its role is to capture what happens in the herd and translate it into statistical patterns enabling prediction and reaction. The zootechnician enters data through dedicated Excel sheets or PowerApps, simplified input, no complex system burden.

Veterinary events, diseases, milk-quality observations, lab sample results (fat %, protein %, somatic cell count), wet events, and herd-group changes.

Hebe powers Iris dashboards:

• Milk overview + AI, production, quality, and feeding with AI interpretation. The system detects correlations humans miss in tables: feed recipe shifts vs next-week milk quality, wet-event patterns preceding yield drops in specific groups.
• Milk quality, fat %, protein %, monthly trends, and norm deviations. Laboratory metrics, common indicators, averages, and group/period comparisons.
• Wet events, disease trends, year/disease filters, and wide monthly cycle tables to detect seasonality, age-group concentration, and cross-event correlation.
• Herd size, status by category/year and group movements.
• Feed consumption, usage by herd groups, diet composition, monthly trends.
• Feed quality, quality parameters, monthly trends, per-feed sections.

Hebe is not about records only, it translates herd health into numbers and detects statistical patterns 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 outputs to the right people in the right format at the right time. Milk cost in Iris is built from four streams: aggregated invoices from Echo, crop-cost identification by Gaia, detailed identification from Demeter plus zootechnician feed recipes, compiled by Clio into one metric: true production cost per liter, margin, and invoice-category structure.

• Weekly farm digest, every Friday at 18:00, owner receives full weekly view: herd status and deviations, milk results, feed purchases, budget execution, completed agrotechnical treatments, generated plant-protection documentation. Delivered by WhatsApp, Discord, Teams, or email. No one prepares it manually.
• Alert system, crop-cost anomalies, milk-quality threshold breaches, budget overruns, feed shortage risk, missing required data. Alerts are delivered where people work.
• Plan vs actual report, Demeter budget matched with Echo execution, live view updated with each new invoice.
• ARiMR documentation, generated automatically from Gaia data, submission-ready with no manual work.

Iris, dashboard by role

Iris is an interactive React dashboard directly on Clio database. Data from all modules is available in one place and updated in real time. Each role gets its own view.

Owner, full picture. Milk costs, budget execution, herd status, and alerts across all areas, with drill-down to detail.

Zootechnician, role-specific view: milk overview with AI, milk quality, lab metrics, wet events, herd size, feed consumption and quality, milk costs. Dashboards are designed around herd operations logic, not finance logic. Finance manager, budgets, execution, variances, feed forecasts. Agronomist, plots, treatments, plant-protection costs, and documentation.

Who it is for

• Dairy farm owners who need real production cost visibility and data-backed pricing decisions.
• Multi-site and multi-division farms with fragmented data requiring one reporting standard.
• Teams reporting to banks, investors, or cooperatives where consistency and timeliness are critical.
• Organizations that need less manual reporting and faster operational and financial decisions.