01 · What comes out
Maps, curves, prescriptions. All in one portal.
Every reading — camera or caliper — feeds the same V4 platform. You get the spatial picture and the time picture, side by side, and the prescription file three clicks later.
{outputs.map((o, i) => (
= 2 ? '#fff' : '#0F1410', backgroundSize: 'cover', backgroundPosition: i >= 2 ? 'left top' : 'center' }} role="img" aria-label={o.t} />
))}
{/* Premise ============================================ */}
The premise
Fruit size is the profit lever.
Tonnage gets the headlines; distribution into the right size bins sets the packout price. Most growers manage size by feel. We replace feel with two pieces of hardware and one platform — every tree, every week.
"Fruit size distribution drives seasonal profit more than raw tonnage. Manage what you measure."
{ e.preventDefault(); setRoute('revsizer'); }} style={{ display: 'inline-flex', alignItems: 'center', gap: 6, marginTop: 'var(--space-3)', fontFamily: 'var(--font-mono)', fontSize: 13, letterSpacing: '0.04em', color: 'var(--accent)', fontWeight: 600, textDecoration: 'none' }}>See how fruit sizing works →
Block-level growth curve · weekly measurements → predicted final size
{/* Two-device hardware grid =========================== */}
02 · The hardware
Same family. Two ways to measure.
Some seasons you need the whole block; others you need 200 spot checks. Both devices speak the same protocol and land in the same place.
{devices.map((d, i) => (
{d.isVideo ? (
) : (
)}
{d.tag}
{d.name}
{d.sub}
{d.claim}
{d.copy}
{d.stats.map((s, j) => (
-
{s.k}
{s.l}
))}
))}
{/* Drive the row (full-bleed video) =================== */}
03 · The drive
Drive the row. Watch the block fill in.
One pass between the rows is enough. Every tree gets counted, sized, and pinned to GPS as you go — both sides simultaneously.
{/* 6-step workflow ==================================== */}
04 · The workflow inside RevToolbox
From row drive to yield prediction, in six steps.
Drive the rows once; the platform runs the rest. Raw field counts → per-tree aggregation → block raster → 5-zone map → calibration to field truth → block yield prediction. Outputs flow back to your packhouse and your spreader.
{workflow.map(s => (
-
{s.n}
{s.tag}
{s.t}
{s.d}
))}
{/* Calibration ======================================== */}
05 · Calibration
Calibrate before or after the scan.
Both paths happen inside RevToolbox · Block Inspector · Yield Prediction. The RevField mobile app captures the field counts; the portal builds the regression and applies it across the block.
{calibMethods.map((m, i) => (
{m.tag}
{m.title}
{m.copy}
{m.hint}
))}
{/* Outputs (now relocated above) ===================== */}
{/* Audiences ========================================== */}
06 · Who it's for
One forecast, four teams aligned.
Linking markets and producers means one number drives Monday-morning decisions across the chain.
{audience.map((a, i) => (
))}
{/* Getting started =================================== */}
07 · How to start
From first measurement to weekly forecast, in three.
{[
{ n: '01', tag: 'WEEK 0', t: 'Pick a device — or both', d: 'Order Rev-Sizers for spot-checking, book a RevScout S survey for whole-block coverage, or do both. Calibrated, shipped from Stellenbosch.' },
{ n: '02', tag: 'WEEKS 1–14', t: 'Measure on your cycle', d: 'Weekly Rev-Sizer readings, or one camera pass per phenological window. Wi-Fi sync at the office or on the bakkie. Day zero is full bloom.' },
{ n: '03', tag: 'CONTINUOUS', t: 'Read the forecast in RevToolbox', d: 'Growth curves and predicted distributions update live. PDF reports go to packhouse and marketing. Prescription files export to your spreader.' },
].map((s, i) => (
))}
{/* CTA ================================================ */}
Bring fruit size into focus.
Hardware, RevToolbox V4 trial, agronomy walk-through — let's talk through what fits your farm.
);
};
Object.assign(window, { RevScoutSPage: window.RevScoutSPage });