One operating system for every tomato hectare.
Version 25 transforms the original fertilizer workbook into a bright, high-contrast farm planning cockpit: crop nutrition, protection, irrigation, scouting, yield forecasting, economics, inventory, trials and a 22-week field programme in one place.
Season operating health
Critical numbers
Season yield: target, stress-adjusted, recorded
harvest timing is an ASSUMED shape · recorded = Trade OS lots + batchesBuild the production plan before the season builds itself.
Set hectares, population, spacing, expected harvest, price and operational assumptions. Pressing EXECUTE recalculates the model, rebuilds the field blocks from the real numbers, registers the farm and starts its season clock — nutrition, irrigation and the calendar only begin counting from that moment.
Land selection — draw your field on the satellite map; the total feeds AREA / HA and rebuilds the blocks
Field block architecture — rebuilt from area, plants and density at each EXECUTE
Planning assumptions
CACTUS season plan
EXTENDS THE FIELDS ABOVERegister a farm — the count grows every time you add one.
Add farms one at a time. Each registration is saved to your CACTUS&CO account, so the list and the total count are exactly what you've registered.
Register a new farm
Registered farms
0 farms| # | Farm | Owner | Location | Crop | Area (ha) | Contact | Registered | |
|---|---|---|---|---|---|---|---|---|
| No farms registered yet — use the form above to add the first one. | ||||||||
SANGTUS branding pipeline
0 orders| Farm | Design request | Order | Production status | Proof | Payment | Documents |
|---|
Registry controls
reads the registry above — nothing is duplicatedFarmers
| Farmer | Contact | Farms | Area ha |
|---|
Spreadsheet-grade formulas with field-scale intelligence.
Core formulas from the workbook are preserved and scaled by area and plant population. Weekly quantities can be reviewed, costed and exported.
22-week fertigation / top-dressing matrix
kg / week / areaFertilizer cost model
ZMW planning prices from workbook| Product | Quantity (kg) | Price/kg (ZMW) | Estimated cost |
|---|
Rotate protection intelligently. Record what happened in the field.
Workbook insecticide, fungicide and mite-control entries are converted into an operational register. Rates shown are transcription/calculation aids and must be checked against current labels and local agronomic guidance.
| Week | Category | Product | Target | Rate / 16 L | Cost / 16 L | 5×50m | 20×50m |
|---|
Convert crop demand into a repeatable irrigation plan.
Use this planning calculator to estimate water volume. Actual irrigation must be adjusted for climate, ET, soil texture, root-zone moisture, rainfall, emitter output and crop stage.
Relative water demand by stage REFERENCE
Water management checklist
Make field observations part of the production data.
Score pressure across pests, disease, water stress, nutrition and canopy condition. Store observations locally in the browser and use them to prioritize field walks.
| Date | Block | Overall risk | Pest | Disease | Water | Nutrition | Canopy |
|---|
Plan the crop backwards from harvest.
Use target yield, pack-out and market price to build harvest scenarios. Add actual harvests later to compare forecast versus realized performance.
Harvest curve
Yield conversion
Know the economics before the field spends the money.
Build a lightweight gross-margin scenario. Enter your own labor, irrigation, crop protection, fertilizer, transport and overhead assumptions.
Report summary
Generated at print time from the figures above — used to build the printable page.
Never discover an empty fertilizer or spray store on application day.
Track opening stock, planned consumption, reorder threshold and current balance. This module runs locally and can be exported.
| Item | On hand | Unit | Reorder point | Status | Supplier | Expiry | Action |
|---|
Use the farm as a learning system.
The supplied workbook's Ca+B trial is preserved here alongside an evidence interpretation layer.
Observed values
Interpretation
See the whole crop cycle as a field rhythm.
Twenty-two weeks of nutrition are laid out alongside protection events from the workbook. Once a plan is executed, each past week is cross-checked against fertigation, irrigation and scouting logs — this is the single place to see what you fell behind on.
Operating rhythm
Inputs → labor → water → equipment.
Apply only after field conditions and label checks.
Scout → record → compare → adjust next cycle.
One system per crop. Press a square, get the whole guide.
Each tile opens a full operating system for that crop, built from the grower guides this farm supplied. Every figure inside is transcribed from a named source, every adapted guide carries its adaptation note, and where a source had no data the system says so rather than filling the gap.
Live Lusaka distribution corridor map.
A schematic node network of Lusaka — CBD, surrounding compounds and key landmarks — with a simulated fleet moving produce, inputs and cold-chain exports between them. This is a planning simulation, not a live GPS feed: node positions are illustrative, derived from a reference city map, not surveyed coordinates.
Stop comparing gross prices. Compare contribution.
Enter the real cost stack for each destination — farm cost, packing, storage, transport, border, finance, shrinkage — and the engine shows what actually lands in your pocket per tonne and per consignment.
Add / update a destination
Destination comparison
contribution = gross − landed cost| Destination | Commodity | t | Gross/t | Farm | Pack | Store | Transport | Border | Finance | Shrink | Landed/t | Contribution/t | Total | Margin | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| No destinations yet — add one above to start comparing. | |||||||||||||||
Cost stack — selected destination
One consignment. One document pack.
Capture the transaction once and generate a purchase order, commercial invoice, packing list and delivery note as a single printable pack with a shared shipment reference.
Consignment details
Line items
| # | Description | Packages | Net kg | Unit price | Line total | |
|---|---|---|---|---|---|---|
| No line items yet. | ||||||
Generate the pack
The pack shares one shipment reference across all four documents, so the buyer, the transporter and your own records point at the same consignment.
Six buttons. No typing you don't need.
A deliberately blunt capture screen for people standing in a field with one hand free. Every record is saved to your account the moment you tap save.
Capture log
| When | Type | Detail | Quantity | Block / who | Sync | |
|---|---|---|---|---|---|---|
| Nothing captured yet — tap a button above. | ||||||
Record
Fill in what you know. Anything you leave blank stays blank.
Every batch gets a permanent reference and a scannable label.
Create a batch, get a structured identity, print a QR label, and move it along a chain of custody from field to settlement. The QR is generated on this device — no internet, no third-party service.
Create a batch
Batch register
0 batches| Batch ID | Crop | Block | Grade | Net kg | Harvested | Stage | |
|---|---|---|---|---|---|---|---|
| No batches yet. | |||||||
Batch label
Chain of custody
The rate on invoice day is not the rate you get paid at.
Model the gap between the sale value, the rate you booked, the rate at settlement and the time you waited. Cross-border agriculture loses margin here quietly and constantly.
Reference rates (per 1 USD)
Exposure calculator
Be the farm that already has the paperwork.
Lenders, insurers and institutional buyers ask the same questions. This assembles what your account already holds — farms, batches, field records, destinations and documents — into one reviewable package.
What the pack contains
drawn from your account| Section | Source module | Records | Status | What a lender usually wants here |
|---|
Produce the pack
Export gives you the raw records as JSON for your own accountant or system. Print gives you a formatted summary you can hand across a desk.
Every number, explained.
The maths behind CHITUKA Farm OS in plain language. Each card says what the number tells you, shows the equation and where it is used. Open one to see what every symbol means and to try it with your own data.
One state. Farm to payment.
The intelligence layer sits above every Farm OS module you already run. Nothing is duplicated: each view below reads the same CACTUS_STATE, so a tonnage, a price or a percentage is calculated once and shown everywhere. Level 1 is this strategic layer; Level 2 is the detailed engineering and field tools in the sidebar.
| Existing Farm OS | CACTUS intelligence layer |
|---|
| Time | Type | Entity | Action | Actor |
|---|
Farm → season → block → week → forecast.
Fed by the Farm Planner, Irrigation, Nutrition, Crop Protection, Scouting and Yield modules you already use. The season clock is the existing one — the Production Engine never starts a second timer. Health, water and energy adequacy are calculated from your logged irrigation, scouting and stress data.
Production stages
Blocks
0 blocks| Block | Farm | Crop | Area ha | Stage | Progress | Health | Water | Energy | Target t | Forecast t | Harvested t | Available t | Quality |
|---|
Weekly intelligence
select a blockCrop → volume → quality → buyer → price → net realization.
Volume comes from your yield forecast, price from the Farm Planner, pack-out from Yield & Harvest and logistics cost from Farm Economics and the Logistics Control engine. Net realized value is what reaches the farm after losses, freight, packhouse, cold chain, fees and border costs.
Season
—Net realized value
Cost assumptions — planning defaults, replace with your contract terms
Buyer network
| Buyer | Channel | Price / t | Demand t | Allocated t | Gross | Net realized | Realization | Terms |
|---|
Price charts for 25 core Zambian crops.
Every price is published by the CACTUS&CO market desk from the Command Center. Tap a crop to open its full charts: daily or weekly candles, the price trend line with its direction, and the supply and demand beneath.
All crops
tap a crop to open its chartsMaize
Region · Last updatedRecent prices
| Date | Crop | Region | O | H | L | C | Supply t | Demand | Source |
|---|
Lot → packhouse → cold chain → truck → border → buyer → payment.
The execution environment for produce leaving the farm. Harvest lots come from your blocks and from Batch ID & QR; trucks come from the existing Fleet OS; every step writes an audit event you can trace back to the field.
Harvest lots
| Lot | Crop | Farm / block | Harvested t | Available t | Grade | Quality | Type | Harvest |
|---|
Packhouses
| Packhouse | Location | Capacity t/day | Status | Shipments |
|---|
Shipment register
Invoices & payment
| Invoice | Shipment | Buyer | Qty t | Amount | Issued | Due | Status |
|---|
The agriculture layer above your Lusaka Corridor and Fleet OS.
One fleet, not two: trucks, corridors and dispatch are the existing Fleet OS. This layer adds payload per truck, a full ETA build-up, adjusted fuel, an explainable route score and shipment-level control. The corridor map remains a planning simulation, not live GPS.
Context
Control console
Payload
ETA engine
Fuel intelligence
Route intelligence
Fleet — existing Fleet OS with payload profiles
| Truck | Corridor | Fleet OS phase | Trailer | Capacity t | Speed km/h | Fuel L/100km | Reefer | Km since service | Rating |
|---|
Where did this consignment come from?
Pick a shipment or a lot and follow the physical product back through buyer, truck, route, packhouse, lot, block, farm and season — or forward from a lot to every load that carried it. Every major event is written to the audit trail.
Trace chain
Provenance
Every number here is calculated, never typed.
The Control Tower aggregates CACTUS_STATE: farms, seasons, blocks, lots, allocations, shipments, trucks and invoices. Nothing on this page is stored — if the state changes, the tower changes.
Yield → sale → settlement → document.
The document layer sits inside CACTUS&CO Intelligence OS. It reads the same farm state as Production, Market Intelligence, Trade OS and Traceability, so commercial documents are generated from the crop volume, buyer, price, lot, shipment and payment records already in the system.
Production → sale → payment → settlement
Every commercial record is connected to the same CACTUS&CO transaction chain.
Commercial Chain
LIVE STATEPayment Ledger
—| Reference | Method | Amount | Date | Status |
|---|
Document Lifecycle
AUDIT TRAILCACTUS&CO Business Identity
Document authority & presentation settings▣ Document Generator
CACTUS&CO branded · 15 registered types · saved to your accountDocument Register
0 documents| Document | Type | Order / Sale | Customer / Buyer | Status | Issued | Actions |
|---|