Company
How an engagement runs
Baseline, pilot, then scope — in that order, because a pilot without a baseline cannot be judged and a scope without a pilot is a guess.
01
The sequence
- 1 — Discovery
- What you already run, what you are obliged to report, and which date is forcing the change. If there is no date, there is no project.
- 2 — Baseline
- What the current season actually costs in hours and rework. Without it, nobody can say afterwards whether this helped.
- 3 — Pilot
- One crop, one region, one season, with the measures agreed in writing beforehand.
- 4 — Scope
- Priced against what the pilot showed, not against what the demo suggested.
02
What we will not scope
Anything that would live only in one browser. If a module cannot survive a lost laptop, it does not belong in a contract, and we would rather say so at the start than be found out at the first staff change.
That exclusion is not a small one, and its size should not be something you discover during a pilot. Roughly two dozen modules across the crop product have no first-class server model today: most of the off-farm ecosystem ring, several specialist registers, and both commercial capstones. Some of their records are now kept as durable files against the account rather than lost with the browser, which is better than it was and is still not the typed server record we would put in a contract. Ask which side of that line a module you care about sits on, and you get the list rather than a summary of it.