FruitScout is two independent product families — Field and Labor — each climbing the same ladder (instrumentation → manual management → agentic ops). The apps are delivery surfaces, not products. This session hardened the Labor family's instrumentation + wedge (the 4W's and the onboarding agent) against messy real data. The key correction to the earlier read: scouting is a Field-family product bundled into the FieldAgent app — it is not in the 4W's (Labor) MVP, so its unbuilt screens don't gate the labor product at all.
FruitScout is two independent product families — Field and Labor — each climbing the same three rungs. FieldAgent (mobile) delivers the instrumentation capture for both families; FarmAgent (web) delivers the management and agentic rungs. Status pills = commercial readiness, not code quality.
| Family | Instrumentation (capture) | Manual scheduling | Agentic scheduling |
|---|---|---|---|
| Labor | The 4W's — Who / What / When / Where, captured as executed (clock-in/out, tasks, roster). MVP · capture path built |
Build the schedule by hand — the console's schedule grid, crews, LFT-conflict checks. Coherent · largely built |
The agent builds & optimizes the schedule. Onboarding wedge built · agent-scheduling nascent |
| Field | Drone + phone data pipelines (CV inventory, piña sizing → Digital Twin); scouting (phone capture). Drone mature · phone scouting unbuilt |
Plan field ops by hand — flights, harvest windows, Register Fields, DT viewer. Built |
Agentic field ops — GIS co-pilot. Real tech · early |
Delivery vs product: FieldAgent (mobile) bundles Labor's 4W's capture and Field's scouting — but they remain separate products on separate roadmaps. The 4W's MVP does not include scouting, so the unbuilt scouting screens are not a labor-product blocker — they're Field-family instrumentation on its own timeline.
Scheduling is a trojan horse. The product isn't a scheduler — it's the Chief of Staff that ends up running the entire business.
The schedule is the one object that holds the whole operation — the who/what/when/where that ties labor and field together. So the agent that earns its way in by building the schedule is positioned to expand into running the business: compliance, payroll, procurement, field ops. Agentic scheduling is the beachhead, not the ceiling. Which reframes the original review's "the persona is thin, it goes quiet after onboarding" note from a minor gap into the gap — the distance between a templated onboarding bot and a persistent operating agent is the distance between the wedge and the actual product.
0.915 → 1.000 — the first quantified evidence the "magic trick" survives multi-source input.cos-onboarding.farmagent.fruitscout.ai) built from the discovery research. The whiteboard demo finally has customer-facing collateral.0.915→1.000. Still pending: a real-customer POC against a live, messy file (the eval is synthetic/curated, not a buyer's actual mess).FeatureGate is UI-only; and server-side compliance enforcement (validate still a stub) is not done.Readiness is per family, not per app — FieldAgent (mobile) and FarmAgent (web) each deliver pieces of both. The Labor 4W's is the near-term commercial product; Field is a separate, earlier-stage product on its own timeline.
validate is a stub (client-side only) — the real-now pre-launch items.| Move (from v2) | Status | Detail |
|---|---|---|
| 3 · Harden the wedge vs real data | Substantial | 038 multi-artifact reconcile + gap-ask + banded confirm shipped; eval 0.915→1.000. Needs one live-customer POC to fully close. |
| 1 · Make the pitch match the product | Started | Wedge marketing page shipped. Core deck rebuild, per-worker pricing, Spanish finish — not done. |
| 2 · Pre-launch gates + server-side compliance | Partial | Billing now real (Stripe). Entitlement breadth + server-side LFT enforcement still open. |
| 4 · Make the mobile hand-off real | Not started | The onboarding→crew QR activation bridge gates the 4W's MVP (hand-off to crews) — untouched. The mobile prod-config/CI + phone scouting are the Field family's 1.0, a separate timeline. |
| 5 · Crop-config layer for "omni-crop" | Not started | Still agave-coupled in the visible product; models documented but no per-customer config layer. |
| ★ The thesis — persistent COS agent | Build-ahead | Agentic scheduling → the Chief of Staff running the business. Today's COS is a templated onboarding bot; the persistent operating agent is unbuilt — and it's the actual product. |
The session moved the highest-leverage thing the first review named — hardening the Labor instrumentation + onboarding wedge against real, messy, multi-source data — and it worked (eval 0.915→1.000). Reframed correctly: the Labor 4W's is the near-term commercial product, and it's close — capture built, manual scheduling built, real billing and compliance depth — held back by a finishable pre-launch list (server-side entitlement + compliance, the QR activation bridge, one real POC, a corrected deck). Scouting and the next-gen mobile 1.0 are the Field family's separate, earlier-stage roadmap — not labor blockers. And the real prize sits one rung up: agentic scheduling is the beachhead for the Chief of Staff that runs the entire business — building that persistent operating agent is what turns a good scheduler into the category-defining product.