garden
Garden, harvest and crop costing software
From bed to plate. Log what is planted where, harvest it when it is ready, and close the bed so you know what a kilo of your own basil actually cost to grow.
One map. Every input.
Tag your living space, a bed, a room, a delivery, a leak. Each input lands at its real address on the property map. Garden, kitchen, rooms, maintenance, same surface. The whole property breathes in one place.
Draw it on the map.
The garden admin drops a polygon on the live property map. The bed becomes a real place, pegged to the kitchen, two doors from the dining room. Every planting that follows lives at that exact address.
Other inputs show up.
Housekeeping flags a room ready. The chef marks a delivery. Maintenance pings the boiler. Each input lands at its real address, same map, different tags. The property breathes in one place, not seventeen tabs.
Day fourteen. Every status visible at a glance.
The bed grows. The room turns clean. The boiler check is done. Water nudges amber when the bed is due. Nothing lives in a separate dashboard, the map carries it all.
Bed to plate. Plate to guest.
One tap and the bed turns harvested. The basil arcs across the map to the kitchen. The menu marks the pasta 'de la huerta'. The reserve.roseiiɘs listing tells tonight's guests fresh from the garden today. One garden, every surface in sync.
What it covers
Plantings by bed
What is growing in each bed, since when, and what state it is in — sown, producing, or closed.
Harvest that costs itself
A harvest carries labour and supplies by bed-day, so the cost is the real one and not a figure typed in once.
Straight into the kitchen
A harvest arrives in the kitchen inbox as usable stock rather than as a note someone has to retype.
Trees and permanent plantings
Perennials are modelled as what they are — long-lived plantings, not crops re-sown every season.
Watering and supplies
Watering is recorded once, and costed inputs come out of the same inventory the rest of the property uses.