A quick tour of the fields you're considering

• Tell me about the fields you want to include in this engagement, including crops, typical field size, and dominant soil textures
• In a typical season, how many distinct fields would you consider eligible for a pilot or variable-rate program Options: 1-5 fields, 6-20 fields, 21-50 fields, More than 50 fields
• Walk me through the last time you changed planting or fertilizer plans for a field, what triggered the change and what happened next
• Which of these data sources do you regularly collect for these fields Options: Grid soil samples, Composite soil samples, Yield maps, Satellite NDVI or vegetation indices, Drone imagery, Topography/DEM, Weather station data
• In your experience, what minimum contiguous acreage makes a field a useful test case for a representative pilot Options: Under 50 acres, 50-150 acres, 151-500 acres, Over 500 acres
• If a pilot showed no measurable ROI after one full season, what condition would make you stop further trials immediately

Where your current approach is costing you money

• Where in your operation do you suspect flat-rate inputs are costing you the most per acre Options: Seed placement/density, Starter or phosphate, Nitrogen timing and rate, Pesticide overlap, All of the above, Unsure
• Estimate your current target ROI per acre for seed and for nitrogen, using ranges if exact figures aren't available Options: Negative to $10/acre, $10-$30/acre, $31-$60/acre, Over $60/acre, No target defined
• Which inputs do you suspect are most often overapplied across productive zones, and which are most often underapplied in marginal zones Options: Seed, Nitrogen, Phosphorus, Potassium, Crop protection, Not sure
• When you overlay recent yield maps with last season's input spend, what patterns surprised you or contradicted expectations
• How do you currently quantify lost opportunity from misapplied inputs or missed zones of potential Options: We model ROI per zone, We use consultant estimates, We rely on gut/experience, We do not quantify it
• Which single financial or agronomic metric would make you expand from a pilot to a full program immediately Options: Net ROI per acre, Percentage yield lift, Payback period in months, Reduction in input spend, Operator time savings

Who needs to sign off when the plan changes

• Who signs off to change seeding rates or nitrogen plans across your operation, and how long does that approval usually take Options: Owner, 1-2 weeks, Operations manager, 1-3 days, Independent consultant, 1-2 weeks, Shared decision, variable
• Which roles must be engaged for a pilot to proceed, for example owner, operations manager, crop consultant, or equipment lead Options: Owner/CEO, Operations manager, Independent crop consultant, Equipment operator/lead, Agronomist on staff, Procurement/legal
• Describe how decisions are made during narrow application windows like planting or sidedress, including who is consulted and typical timing
• If the pilot delivers your target ROI, what approvals or contracts would be required to begin paid deployment the following season Options: Budget sign-off, Operational readiness confirmation, Commercial agreement, No barriers
• Which person or role can commit budget for a scaled program within 30 days if the pilot proves the number

Data and equipment reality check

• If we needed prescription-ready files this week, which of your monitors or farm systems could accept them without file conversion Options: Major OEM monitor formats, ISOXML-compatible displays, Shapefile plus CSV workflow, Custom vendor format with conversion, No direct acceptance
• Which file formats and export methods are available today for your planters, spreaders, and sprayers Options: ISOXML/ADF, Shapefile plus CSV, Proprietary vendor file, API transfer, Unknown
• Describe the cleanliness, centralization, and known gaps in your yield and soil datasets, including how often files are updated and where they are stored
• Which role maintains equipment monitors and acts as the primary contact for prescription uploads Options: Farm technician/equipment lead, Operations manager, Independent consultant, IT/precision ag specialist, Other
• Are automated exports or APIs available from your farm management system to push field data to a partner platform Options: Yes, APIs available, Yes, scheduled exports, No, manual exports only, Not sure
• What single data gap would prevent us from running a representative pilot inside your planting or application window

Pilot design, metrics, and what success actually looks like

• If you could only run a single field pilot this season, which field would best prove value and why
• Which prescription modules do you want to test in the pilot Options: Seeding rate, Fertilizer by zone, Crop protection placement, Hybrid/variety placement, All of the above
• How will you structure side-by-side controls in the pilot, strips, whole-field randomized plots, or another design Options: Longitudinal strips, Paired whole-field control, Randomized plots, Farmer-designed comparison, Unsure
• Which success metrics are must-haves for you to sign and scale after the pilot Options: Net ROI per acre, Yield lift percent, Reduction in input cost, Operational time saved, Farmer/driver acceptance
• Which operator role will run the equipment during the pilot and what experience do they have importing prescription maps Options: Experienced in-file import, Some experience with help, No experience, will need training, Contract operator
• If the pilot hits the stated ROI target, what internal or external approvals would need to clear before you could sign a scaled commercial agreement Options: Procurement/budget, Legal contract, Operational readiness, No additional approvals

Obstacles, compliance, and things that stop pilots

• What has caused past pilots or trials on your operations to stall or fail to convert to a paid program Options: Timing missed planting window, Poor data quality, Operator errors on downloads, No clear ROI, Internal politics
• Are there regulatory, cooperative membership, or crop-label constraints that could limit variable-rate application on these acres Options: Yes, regulatory constraints, Yes, co-op or supplier restrictions, No constraints known, Unsure
• Which roles or departments would need to sign data-access, privacy, or liability agreements before we can ingest and use your field files Options: Owner/management, Legal/procurement, Crop consultant, Cooperative rep, Other
• How quickly could your team resolve an equipment integration failure during peak season, and who would lead that effort Options: Within 24 hours, in-house, 48-72 hours with outside help, Longer than 72 hours, No plan in place
• If a regulatory or equipment delay pushed prescriptions past your application window, would you proceed, pause, or cancel the pilot Options: Proceed with adjusted timing, Pause until next window, Cancel this season

Other paths you may be weighing

• What other solutions, incumbent providers, or internal plans are you actively comparing us against right now Options: Incumbent third-party provider, Internal build plan, Co-op or local consultant, No direct alternative yet
• Have any internal team members proposed solving this capability in-house, and if so who would lead it and what timeline did they propose Options: Yes, operations would lead, Yes, agronomy would lead, No internal proposal, Unsure
• For the option you are most likely to keep, what would have to be true about its performance for you to stay with it instead of switching Options: Meets ROI targets, Simpler operational workflow, Lower cost, Better data control
• Which internal concerns about switching providers are strongest right now, for example data ownership, operator training, or integration effort Options: Data ownership, Operator training, Integration with monitors, Cost and contracts, Other
• If the pilot meets your target ROI this season, what would convince you to switch to a new provider this season rather than wait until next year Options: Immediate budget available, Operational readiness confirmed, No procurement blockers, Other

Readiness checklist and the decisive questions

• If everything in the pilot matched expectations, what internal milestone would allow you to sign a commercial agreement within 30 days Options: Budget approval, Operational lead sign-off, Legal review complete, No milestone required
• Which legal, procurement, or insurance steps must finish before a paid pilot can begin Options: Standard master services agreement, Data processing agreement, Proof of insurance, No formal steps required
• Are there budget windows or fiscal timing constraints that would prevent you from starting a paid deployment next season Options: Yes, seasonal budget only, Yes, fiscal year constraints, No timing constraints, Unsure
• Which role must give final approval to sign a scaled agreement and how quickly do they typically respond Options: Owner/CEO, quick response, Operations manager, within a week, Procurement/legal, multi-week, Depends on season
• What single unresolved issue today would make you pause or cancel the project immediately
• Would you prefer the next engagement step to be a technical onboarding call, a pilot scoping session, or a commercial terms discussion Options: Technical onboarding call, Pilot scoping session, Commercial terms discussion, Not sure, need guidance

• Prescription Walkthrough

• Confirm the current state and its cost to your operations
• You confirm the stated current state and the costs it creates for input spend, timing risk, or trial validity.
• Provide soil, yield, and representative imagery exports for the proposed pilot fields.
• Seller to run the prescription build for the provided pilot fields and deliver equipment-ready files plus an ROI-per-acre comparison before the follow-up session.
• Show how layered data builds management zones for your fields
• You confirm the demonstrated zone and prescription workflow produces equipment-ready files that match your monitor format and agronomic expectations.
• Walk through prescription generation and equipment file export
• You accept the modeled ROI per acre comparison as a credible basis for a pilot and identify any assumptions that need refinement.
• Define and share the side-by-side trial layout and acceptance criteria for pilot success.
• You agree on pilot fields, success metrics, and the next deliverables required to start the trial.
• Compare expected outcomes against your baseline
• Validation question
• Agree pilot scope and next steps for trial execution

• Prescription Walkthrough
• Prescription Walkthrough Deck
• Prescription Walkthrough Brief

• meeting
• slides
• document

• Enroll Fields and Import Boundaries
• Ingest and Normalize Soil Sampling Grids
• Ingest and Process Historical Yield Maps
• Integrate Satellite Vegetation Imagery
• Integrate Weather and Topography Models
• Build Management Zones from Layered Data
• Generate Agronomist-Calibrated Seed Prescriptions
• Generate Agronomist-Calibrated Fertilizer Prescriptions
• Generate Agronomist-Calibrated Crop Protection Prescriptions
• Convert Prescriptions to Equipment-Ready Files
• Validate Prescription Files on Cab Displays
• Deploy Pilot Side-by-Side Comparison Strips
• Season-Long Satellite Monitoring and Triggered Updates
• Post-Harvest Yield Ingestion and Zone Refinement

Enroll Fields and Import Boundaries

• How many fields and total acres do you want enrolled for this pilot? Options: < 500 acres, 500-2,000 acres, 2,000-10,000 acres, > 10,000 acres
• Which file formats do your current field boundaries exist in? Options: ESRI Shapefile, GeoJSON, KML, CSV (lat/long), Drawn in-platform
• Do you have management unit boundaries (existing zones) that should be preserved during enrollment? Options: Yes, No, Some fields only
• Who on your team will be responsible for uploading boundary files and validating georeference (e.g., farm manager, consultant)? Options: You will upload, External consultant will upload, We need seller assistance, Other
• Which coordinate reference system do your boundary files use or require (for example WGS84 or a state plane)? Options: WGS84, State Plane / Local projection, Unknown — need help identifying

Ingest and Normalize Soil Sampling Grids

• Which soil sampling scheme do your lab results follow for the enrolled fields? Options: Regular grid samples (e.g., 2.5 acre), Management-zone composites, Field composites, Strip samples
• Which file or data formats contain your soil lab results and GPS points? Options: CSV with GPS, Shapefile with attributes, Direct lab portal export, PDF lab reports
• Attach or list the soil nutrient units your lab uses so we can normalize (for example ppm, lb/acre, meq/100g).
• Identify the sample depths represented in your soil files (for example 0-6 in, 0-8 in, 0-24 in). Options: 0-6 in, 0-8 in, 0-12 in, 0-24 in, Mixed depths
• Are there lab quality documents (chain of custody or lab certificates) to attach for QA on samples? Options: Yes — attach, No, Available on request from lab

Ingest and Process Historical Yield Maps

• How many years of yield monitor data do you have per enrolled field? Options: None, 1 year, 2-3 years, 4+ years
• Which yield file formats can you provide from your combines (for example aggregated shapefile/CSV or machine header logs)? Options: Aggregated yield shapefile/CSV, Harvester header logs, GeoTIFF yield rasters, Other
• Describe how your team currently handles moisture correction for harvester yield data and whether corrected yields are available. Options: Moisture-corrected available, Raw yields only, We need assistance performing correction
• Specify any known GPS offset or combine header calibration notes that affect yield alignment in fields.
• Do you want yield maps processed to remove headland passes and machine noise as part of normalization? Options: Yes — remove headlands and noise, No — keep raw traces, Only remove headlands

Integrate Satellite Vegetation Imagery

• Which satellite vegetation indices do you want used for zone-building and in-season triggers (NDVI, OSAVI, NDRE, others)? Options: NDVI, NDRE, OSAVI, Custom index
• Which imagery cadence and cloud-tolerance do you require for season monitoring (for example weekly with <10% cloud cover)? Options: Daily (cloud permitting), Weekly, Bi-weekly, Monthly
• Do you have ground truth points (scouting notes or in-field sensor readings) to calibrate satellite indices for your crop types? Options: Yes — GPS-tagged scouting points, No, Some fields only
• Indicate any fields where tree cover, irrigation pivot geometry, or small field size will limit usable satellite pixels.
• Would you like imagery layers delivered as tiled rasters or clipped vector summaries per management polygon? Options: Tiled rasters, Clipped vector summaries, Both

Integrate Weather and Topography Models

• Which weather data sources can you provide or want used (on-site weather stations, national gridded models, third-party stations)? Options: On-site station, Gridded public model, Third-party commercial feed, No preference
• What temporal resolution do you need for weather inputs (hourly, 3-hourly, daily)? Options: Hourly, 3-hourly, Daily
• Which digital elevation model (DEM) resolution is available or acceptable for your fields? Options: 1-3 meter, 5-10 meter, 30 meter, Unknown — need recommendation
• List any topographic features to model explicitly (e.g., terraces, seasonal drainageways, knolls) for water- or nutrient-related zoning.
• Are there installation or sensor maintenance restrictions for installing a temporary on-farm weather station if we recommend it? Options: No restrictions, Requires farm approval, Not allowed

Build Management Zones from Layered Data

• Which zoning method do you prefer for the pilot: clustering of data layers, rule-based agronomic zones, or hand-drawn expert polygons? Options: Clustering (data-driven), Rule-based (thresholds), Expert-drawn, Hybrid
• What target number of management zones per field do you want as a starting point? Options: 2-3 zones, 4-6 zones, 7-10 zones, Custom
• Specify the minimum practical zone size for your equipment and field operations (for example acres per zone to avoid excessive switching). Options: < 1 acre, 1-5 acres, 5-10 acres, >10 acres
• Indicate which layers must be mandatory in zone delineation (for example soil P, yield history, NDVI mid-season).
• Who on your side will approve the initial zone map before prescriptions are generated? Options: You (farm manager), Independent consultant, Group approval required, Seller approval only

Generate Agronomist-Calibrated Seed Prescriptions

• Provide the seeding rate units and typical target populations you use (for example seeds/acre or pounds/acre) for the crop in each enrolled field.
• Which seed varieties or maturity groups must be mapped to zones as constraints for seed prescriptions? Options: Single variety across field, Multiple varieties by zone, Variety mapping not required
• Specify any planter controller limitations we must respect when generating ramping or rate-change rules (for example max change per second or min segment length).
• Do you require agronomist notes embedded in the prescription files for operator reference (for example target population and rationale per zone)? Options: Yes — include notes, No
• Estimate the maximum and minimum seeding rates you are willing to accept in any zone (for safety and seed inventory planning).

Generate Agronomist-Calibrated Fertilizer Prescriptions

• Which nutrient units must prescriptions use (e.g., lb N/acre, lb P2O5/acre) and do you require conversion to product blend rates? Options: lb N/acre, lb P2O5/acre, Product blend rates required, Other
• Indicate allowed application timing for variable-rate fertilizer (pre-plant, sidedress, in-season topdress). Options: Pre-plant, Sidedress, In-season topdress, Multiple
• Specify any maximum single-point or field-average rate caps required by your risk tolerance or product label constraints.
• Do you need prescriptions expressed as blend maps for spreaders (product A + product B) or only as nutrient-rate maps? Options: Blend maps, Nutrient-rate maps only, Either — we will decide
• Who will approve the final fertilizer prescription before file conversion for equipment? Options: You, Independent agronomist, Both

Generate Agronomist-Calibrated Crop Protection Prescriptions

• Which crop protection application types should support variable prescription (early-season herbicide, targeted fungicide, insecticide strips)? Options: Herbicide, Fungicide, Insecticide, All of the above
• Specify regulatory or label constraints we must encode in prescriptions (maximum gpa, buffer distances from waterways, pre-harvest intervals).
• Do you require zone-level product restrictions (for example do-not-apply zones such as sensitive habitat or organic-certified strips)? Options: Yes — list restrictions, No
• Indicate whether section-control resolution (minimum strip width) is constrained by sprayer boom section size that we should model. Options: Yes — provide section width, No constraint, Unknown — need to confirm
• Who on your team is authorized to sign off on crop protection prescriptions given label and compliance risk? Options: You, Licensed applicator, Third-party consultant

Convert Prescriptions to Equipment-Ready Files

• Which equipment file formats must we produce for your cab displays and controllers (for example ISOXML, shapefile-based prescription, CSV rate table)? Options: ISOXML, Shapefile prescription, CSV rate table, Other
• Specify whether prescriptions need to be converted into per-row prescriptions or field-wide rate maps for your planters and applicators. Options: Per-row prescriptions, Field-wide rate maps, Either
• Define the discretization tolerance for rates when converting continuous zone rates to equipment step sizes (for example 1 lb/acre increments).
• Who will receive the equipment-ready files in the cab (operator, agronomist, service tech) and how will files be transferred (USB, in-cab upload, cloud sync)? Options: Operator via USB, In-cab upload via telemetry, Cloud sync to integrator, Other
• Identify any equipment firmware or controller versions we must target to ensure compatibility with generated file types.

Validate Prescription Files on Cab Displays

• Who will perform in-cab validation tests for prescription files (operator, you, third-party service), and where will tests take place? Options: Operator, You (farm manager), Third-party service, Seller assistance required
• Select the visualization checks you require in-cab before application (rate legend, zone boundaries, per-row rates, layer visibility). Options: Rate legend, Zone boundaries, Per-row rates, Layer visibility
• How many test-load fields or sample points do you want validated in-cab prior to full deployment? Options: 1 field/sample, 2-3 fields/samples, 4+ fields/samples
• Provide the acceptable tolerance for load/display mismatches (for example visual mismatch < 5% of area or rate delta < 5 lb/acre).
• What evidence will validate successful in-cab validation (for example screenshots from cab, operator sign-off form, or test-application logs)? Options: Cab screenshots, Operator sign-off form, Applied test logs, Combination

Deploy Pilot Side-by-Side Comparison Strips

• Which fields or acres do you nominate as pilot strips for side-by-side comparison?
• Select the trial layout you prefer: paired strips within fields, randomized strips across fields, or whole-field comparisons. Options: Paired strips within fields, Randomized strips across fields, Whole-field comparisons
• How many replications per treatment do you require to achieve your desired statistical confidence? Options: 1 replication, 2-3 replications, 4+ replications
• Who will be responsible for application execution and operator training for the trial strips? Options: You / your operator, Independent consultant, Seller provides training
• What acceptance criteria will define a successful pilot trial for you (for example yield delta >= X bu/acre or economic return > $Y/acre)? Options: Absolute yield delta threshold, Economic ROI threshold, Statistical significance at p<0.05, Custom — describe

• Master Services Agreement (MSA)
• Statement of Work (SOW) — Pilot & Deployment
• Order Form and Subscription Agreement
• Data Processing and Access Agreement (DPA)
• Pilot Acceptance Criteria and Trial Protocol
• Integration Specification and Equipment File Format Annex
• Service Level Agreement (SLA) — Platform Access
• Change Order Agreement

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate and Trial Close (around day 90)
• Quarterly Success Review (ongoing)

• Circulate a quarterly performance summary showing ROI per acre, prescription refinement accuracy, and open enhancement counts.
• Re-run zone delineation incorporating the most recent imagery and soil updates, then publish updated prescriptions.
• Document and close the top three root causes preventing target prescription execution, with validation steps.
• Restate acceptance criteria from Pilot & Scope
• Produce a documented acceptance decision against each Pilot & Scope target, with the formal decision captured.
• If any criteria failed, agree a remediation plan with resolution timelines and verification steps.
• Confirm next steps to ingest post-harvest yields and execute zone refinements for the next season.
• Document the acceptance decision and record the signatory for the trial close in the project record.
• Ingest final post-harvest yield files and run zone refinement, then publish revised prescriptions within the agreed window.
• Execute incumbent system decommission or set to read-only, archive legacy data, and confirm no operational fallback remains.
• Rolling ROI and yield trend review
• Confirm whether rolling ROI per acre remains at or above the target recorded in Pilot & Scope and surface reasons for any drift.
• Agree the prioritized list of enhancements and issue resolutions for the next quarter, with deadlines.
• Verify ongoing adoption levels and schedule any required operator refresher training.
• Schedule ingestion of the next set of soil and yield data and run zone refinement ahead of the next planting window.
• Deliver fixes for the top two operational issues in the backlog and provide verification reports.
• Re-confirm success criteria and owners
• Confirm the data pipeline and equipment-file exports are operational for all pilot fields.
• Validate that operators have completed required tests and can load a prescription file into their monitors.
• List all critical blockers with resolution dates and owners documented for immediate follow-up.
• Fix any data ingestion or formatting errors identified in pilot fields and validate with a test prescription load.
• Schedule and complete a cab test run for each equipment model in the pilot and submit a pass/fail report.
• Publish the go-live verification checklist and the open-issue register for the pilot.
• Present first measurement dataset
• Determine whether yield difference per acre is trending toward the Pilot & Scope targets and document any variance.
• Agree a remediation plan to raise prescription execution rate to the target recorded in Pilot & Scope, with deadlines.
• Confirm the timeline and data sources required to reach the acceptance gate.
• Deliver corrected equipment-ready files or parameter updates for remaining trial acres within the agreed timeline.
• Deployment and data pipeline validation
• Post-harvest data and zone refinement status
• Present outcome data vs each criterion
• Root-cause diagnosis for gaps
• Operator and user onboarding status
• Open issues and enhancement backlog
• Document pass / fail per criterion and formal decision
• Agree corrective actions and timelines
• Adoption and operational metrics
• Early signals and sanity checks
• Confirm measurement plan to acceptance gate
• Remediation plan for any failed criteria
• Open issues and immediate remediation
• Quarter plan and escalation thresholds
• Post-harvest ingestion and zone refinement plan
• Incumbent system wind-down checkpoint