Getting Acquainted: Where You Are Right Now

• Can you briefly describe your operation—total acres, crop mix, and how many distinct locations you manage?
• Who will be our primary contact and day‑to‑day champion for records and audit readiness? Options: Owner, Operations Director/Manager, Bookkeeper/Accountant, Precision Agronomist, IT/Systems Admin, Other
• How do you currently capture and store field activity and yield records? Options: Paper logbooks, Spreadsheets (Excel), Multiple OEM apps, Single farm management software, Accounting software only, Hybrid - mix of above
• Roughly how many different equipment monitor / telematics brands are in your active fleet today? Options: 1, 2, 3, 4–6, 7–11, 12 or more, Not sure
• When was the last time your operation faced a crop insurance audit or a landlord settlement dispute related to records? Tell us what happened and the outcome.
• How confident are you that your current records would pass a typical crop insurance audit right now? Options: Very confident, Somewhat confident, Neutral / Unsure, Not confident, I don't know how to assess

What's Keeping You Up at Night About the Next Audit?

• If the next audit denied your largest claim, how would that change your operation—and how quickly would you feel the impact?
• Which specific missing or unverifiable records worry you most when you think about an audit? Options: Spray/application dates, Seed and population records, Yield monitor files, Fertilizer/N inputs, Equipment logs/telematics, Field boundaries/tillage records, Other
• Give a concrete example of a time incomplete records cost you money or trust (estimate $ impact if possible).
• Who else in your operation or network is most anxious about audit risk and how do they usually respond? Options: Bookkeeper/Accountant, Operations Manager, Owner, Landlord(s), Crop Insurance Agent, Precision Agronomist, Other
• How much of an annual claim or settlement would need to be at stake for you to prioritize a full records solution? Options: <$10k, $10k–$50k, $50k–$200k, $200k–$500k, >$500k, Not sure
• When you imagine audit season approaching, what feelings come up for you—stress, anger, motivation to fix it, or something else? Options: Anxious / stressed, Frustrated / angry, Motivated to fix it, Indifferent, Other

When Records Don't Line Up: Tell Me the Story

• What’s the most obvious place your field records break down—and why do you think that happens?
• Which workflows or handoffs create the biggest data gaps (e.g., downloads from machines, paper transfer, multiple apps)? Options: Manual paper-to-digital transfer, Multiple OEM apps with no central import, Inconsistent operator logging, Seasonal/temp staff turnover, Accounting integration gaps, Telematics blackspots, Other
• How often do you need to reconcile yields between machines, bins, and accounting records? Options: After every harvest, Several times per season, Once per season, Rarely, Never
• List the brands and models of yield monitors and telematics units in your fleet (or note if you need help inventorying them).
• Have older machines or file formats produced data you couldn’t import into other systems? Describe the barrier and any workarounds you use.
• Where do you most often lose verifiable proof for spray or application dates—who signs off, and how is supporting evidence (tickets, photos) stored?

If Everything Went Right: The Audit‑Ready Farm

• Imagine the auditor says “these files are perfect”—what exactly did they see that made them say that?
• Which exact reports or document formats do your insurers and landlords require today? Options: RMA crop insurance worksheets, Landlord settlement statements, Field activity logs (spray, planting), Yield reconciliation reports, Input cost breakdowns by field/tenant, Other
• What acceptance criteria would make you comfortable signing off on our migration and connectivity work (be specific: accuracy %, report samples, SLA terms)?
• How quickly after harvest or an application do you need audit‑ready documentation to satisfy landlords and insurers? Options: Within days, Within 2 weeks, Within a month, Longer / Flexible
• What would passing the next audit change for your business—decisions about equipment purchases, financing, or tenant relationships?
• What would give your bookkeeper the greatest peace of mind about field-level financial accuracy? Options: Automated accounting integration, Reconciled cost-per-acre reports, Audit trails and timestamps, Human-reviewed verification reports, Other

What Would It Take to Bridge the Gap?

• What would it cost you—not just dollars but time, disruption, and risk—to close every record gap you have today?
• Which of the following barriers are most likely to block a successful rollout? Options: Aging equipment lacking compatible outputs, Limited cellular / data connectivity, Staff resistance to new workflows, Insufficient budget, Complex landlord contractual requirements, Multiple decision-makers / slow procurement, Other
• How flexible is your planting and harvest window for scheduling onboarding, data migration, and staff training? Options: Very flexible, Some flexibility, Tight—must align to narrow windows, Not sure
• What per‑acre pricing or commercial structure would feel fair at your scale and not be an automatic deal-breaker? Options: >$20/acre, $10–$20/acre, $5–$10/acre, <$5/acre, Depends on modules included, Unsure
• If hardware upgrades are required for some machines, who approves that spend and how quickly can those purchases be made?
• How much internal capacity (hours/week) can your team realistically commit to a rollout during critical windows? Options: <5 hrs/week, 5–15 hrs/week, 15–40 hrs/week, >40 hrs/week, Cannot commit during season

A Trial That Actually Proves It

• If we ran side‑by‑side for one planting or harvest, what would you insist we prove before you consider switching?
• Which three fields would you choose for a pilot that meaningfully tests mixed-brand ingest and yield reconciliation (describe soil type, field size, and why)?
• What success metrics would you require to call the pilot a win? Options: Yield variance within X%, Complete field activity logs for 100% of applications, Operator mobile app adoption rate, Insurer/landlord report acceptance, Time-to-generate reports, Other
• Who needs to sign off on pilot results (role and name if possible)?
• What sample data can you provide immediately to support a pilot: field boundaries, two years of yield files, spray logs, or accounting exports? Options: Field boundaries (shapefiles/KML), Yield monitor files (harvest), Operator spray logs, Accounting export of input costs, None yet — need assistance, Other
• How long do you consider a fair pilot period to demonstrate value—a few weeks, one season, or longer? Options: Few weeks, One planting/harvest season, Multiple seasons, Unsure
• What would be a non‑negotiable failure condition in the pilot that would stop further engagement?

Who's Holding the Pen — Decisions, Timing, and Next Moves

• If we delivered exactly what you need, what would stop this deal from moving to a signed agreement this quarter?
• What is your internal decision timeline and key procurement milestones for a solution like this? Options: Immediately, 30 days, 60–90 days, This season / this year, No timeline / ongoing evaluation
• Which stakeholders must approve commercial terms and deployment (roles)? Options: Owner, CFO / Bookkeeper, Operations Director, Precision Agronomist, Landlord(s), Insurance Broker / Agent, Other
• What contract terms or SLAs are important to you around connectivity uptime, data availability, and support response times? Options: 24/7 support with formal SLA, Business hours support, Response within X hours, Guaranteed data ingest windows, No formal SLA required, Other
• Is there a legal or procurement review that typically adds time—what specifically triggers that review?
• If budget is the final hurdle, would you accept a phased deployment (critical fields first) to spread cost and risk? Options: Yes — phased approach, Prefer all-at-once, Depends on cost, Unsure
• Would you like us to prepare a tailored pilot proposal with scope, cost estimates, success criteria, and timeline? Options: Yes — prepare proposal, Maybe — need more info, Not yet

• Data Intake & Current-State Confirmation
• Yield Reconciliation Workshop (Diagnosis → Proof)
• Insurer & Landlord Report Build and Validation
• Final Validation & Mutual Acceptance

• Host: Validate data integrity and return a short data health report flagging missing fields/obvious issues before the reconciliation workshop.
• Obtain customer validation on representative reconciled fields (forced confirmation that outputs match their expectations).
• Agree owners and deadlines for resolving exceptions before report generation for insurers/landlords.
• Host: Deliver the full reconciled yield report and exception log within 2 business days.
• Customer: Provide clarifications or source documents for top-priority exceptions (e.g., combine header CSVs, operator notes).
• Host: Implement agreed fixes (boundary merges, unit conversions) and re-run reconciliation for affected fields.
• Customer: Confirm availability for the insurer/landlord report validation meeting once fixes are applied.
• One-Sentence Future State Reminder
• Deliver insurer and landlord report samples built from customer data that demonstrate proof of compliance with audit and settlement needs.
• Obtain explicit acceptance criteria or formal signoff instructions from the customer and any external reviewer present.
• Agree to a final template version and a timeline to implement any requested changes.
• Host: Produce final report templates incorporating agreed changes and publish them to the shared workspace.
• Customer: Share report samples with insurer/landlord contacts and return acceptance or written change requests.
• Host: If required, perform one iteration of template updates and re-submit for final confirmation.
• Proof Artifacts Review
• Customer provides formal acceptance that the Solution Experience outputs meet their audit and landlord reporting needs.
• Mutually agree the solution demonstrably reduces the quantified consequence and define the next stage to proceed to (Solution Scope or Deployment).
• Identify and assign owners for any residual blockers with deadlines to remove them before deployment.
• Customer: Sign/confirm acceptance of the Solution Experience outputs or provide an explicit list of remaining blockers.
• Host: Produce a one-page Experience Summary (current state, consequence avoided, future-state sentence, artifacts) for contract/solution-scope use.
• Both: Schedule the Solution Scope kickoff and hand off validated templates, reconciled data, and exception resolution tasks to the deployment group.
• Obtain a customer-approved one-sentence current-state description.
• Agree and quantify the primary consequence(s) to make urgency explicit.
• Inventory and secure access to all datasets required to run the Solution Experience.
• Assign owners and deadlines for prework items so the next meeting can run against real data.
• Customer: Deliver agreed dataset package (boundaries, historical yields, telemetry logs, accounting export) to secure location.
• Customer: Provide credentials and contact for telematics/account integrations or supply export instructions.
• Introductions & Objectives
• Host: Circulate a runbook for the upcoming live reconciliation workshop (tools, sample records, expected outputs).
• Brief Recap: Current State & Consequence
• Produce a reconciled yield report sample using the customer's data that demonstrates the platform's reconciliation proof points.
• Identify and prioritize exceptions that materially impact audit exposure and quantify remaining risk reduction.
• One-Sentence Current State (Facilitated)
• Capture Report Requirements & Acceptance Criteria
• Reconciliation Method & Ruleset Overview
• Demonstrate Consequence Elimination
• Customer-led Validation Exercise
• Explicit Consequence Mapping
• Generate Sample Insurance Audit Report
• Live Data Ingest and Mapping
• Generate Sample Landlord Settlement Report
• Decision & Acceptance
• Required Dataset Inventory
• Reconciled Yield Results Walkthrough
• Exception Triage & Root-Cause Diagnosis
• Access & Prework Checklist
• Validation & Acceptance Exercise
• Next Steps & Owners
• Next Steps & Runbook
• Document Changes & Final Template Agreement
• Customer Validation Checks
• Agree Remediation Steps & Ownership

• Import and Clean Field Boundaries
• Migrate Historical Yield and Harvest Maps
• Normalize Yield Monitor Data to Fields
• Integrate Mixed-Brand Equipment Telematics
• Backfill Missing Telematics via CSV Uploads
• Deploy Mobile App with Offline Data Capture
• Digitize and Geotag Spray and Application Records
• Generate Crop Insurance Audit Reports
• Produce Landlord Settlement Statements
• Sync Field-Level Costs to Accounting Systems
• Per-Acre Cost Allocation and Profitability Reports
• Upload Variable-Rate Prescriptions and Device Exports
• Enable Time-Stamped Field Activity Audit Trail
• Train Field Crew on In-Field App Usage

Import and Clean Field Boundaries

• Do you have existing field boundary files to import? Options: Yes, No
• What file formats are your boundaries currently in? Options: Shapefile (.shp), GeoJSON, KML, EPSG/CSV (lat/long), Proprietary ag format, Other / Mixed
• How many fields or polygons need import and cleanup? Options: Less than 100, 100-500, 500-2,000, More than 2,000
• Are there known boundary issues to resolve (split/merged fields, out-of-date ownership, incorrect CRS)? Please list the primary problems.
• Do you require manual review and approval of cleaned boundaries before finalizing? Options: Yes - we require manual review, No - automated cleanup is fine, Partial - only flagged exceptions reviewed
• Are field boundaries tied to any internal identifiers (farm ID, lease ID, landlord) that must be preserved during import? Options: Yes - preserve IDs, No - new IDs acceptable, Some - details provided in notes

Migrate Historical Yield and Harvest Maps

• Which years of historical harvest/yield maps should be migrated? Options: 1 season, 2-3 seasons, 4-6 seasons, More than 6 seasons
• What formats do your historical yield files come in? Options: Yield monitor exports (CSV/TXT), Shapefiles/GeoTIFFs, OEM proprietary files (John Deere, Case IH, etc.), Spreadsheet with harvested totals, Other / Mixed
• Are the historical maps georeferenced and aligned to current boundaries, or do they need reprojection/re-alignment? Options: Already aligned, Require reprojection/re-alignment, Unknown - need sample assessment
• What is the acceptable completeness/accuracy threshold for migrated yield data (e.g., % of combined harvested acres must match)? Options: >95%, 90-95%, 80-90%, No strict threshold - migrate all available
• Do you need gap-filling or interpolation for missing harvest swaths in historical data? Options: Yes - interpolate/fill gaps, No - import raw only, Flag gaps for later review
• How should migrated historical maps be labeled/organized in the platform (by year, by crop, by harvest date)?

Normalize Yield Monitor Data to Fields

• Which combine/yield monitor brands produce your raw yield monitor files? Options: John Deere, Case IH/New Holland, AGCO/Fendt, Trimble/Precision Planting, Other / Mixed
• Do your yield monitor exports include necessary metadata (calibration, moisture, binning), or will those need to be provided separately? Options: Included with exports, Provided separately, Not available / unknown
• Do you require normalization for header/field names, units (bu/acre vs kg/ha), and moisture corrections? Options: Yes - full normalization, Partial - units only, No - vendor-normalized files
• What tolerance for spatial mismatch between yield swaths and boundaries is acceptable before requiring manual reconciliation? Options: <5 meters, 5-20 meters, 20-50 meters, Allow automatic snapping / flag above
• Do you want per-combine or per-operator segmentation retained in the normalized data? Options: Retain per-combine, Retain per-operator, Aggregate to field-level only, Not necessary
• Provide any calibration or baselining rules that must be applied during normalization (describe or paste sample)

Integrate Mixed-Brand Equipment Telematics

• Which equipment telematics providers and OEM brands are in your fleet? Options: John Deere/JDLink, Case/IH/AFS, AGCO/AgCommand, Trimble, Raven/Precision, Other / Mixed
• How many active telematics-enabled machines need connectors? Options: 1-10, 11-50, 51-200, 200+
• Which telemetry data streams are required (select all that apply)? Options: Location / GPS, Engine hours / runtime, Implement on/off, Product rates/flow, Speed/heading, CAN-bus parameters, Fuel usage, Other
• Do any machines use offline gateways or require scheduled uploads rather than continuous cellular streaming? Options: Real-time cellular, Gateway / episodic uploads, Satellite / other, Mixed
• Are there existing provider accounts/credentials we can use to connect, or will new integrations be provisioned? Options: We will provide existing credentials, Seller to provision/connect new, Some existing, some new
• Do you require SLA metrics for telematics connectivity (uptime %, data latency)? If yes, specify targets.

Backfill Missing Telematics via CSV Uploads

• Do you have CSV or other tabular exports prepared to backfill gaps? Options: Yes - ready, Yes - need template mapping, No - will produce on request
• What is the expected volume of backfill rows (est. records, e.g., 10k rows)? Options: <1,000 rows, 1,000-10,000, 10,000-100,000, 100,000+
• Which columns/fields must be present in CSV backfills (e.g., timestamp, lat, lon, machine ID, activity)
• Do timestamps use UTC or local farm timezone and do they need conversion? Options: UTC, Local timezone - specify, Mixed / unknown
• Should backfilled data be flagged as 'imported' and excluded from automated alerting until validated? Options: Yes - flag and hold, No - treat as live data, Flag with optional review
• Who will be responsible for preparing CSVs and validating the backfill (customer, dealer, or platform team)? Options: Customer, Dealer/Integrator, Platform services team, Mixed

Deploy Mobile App with Offline Data Capture

• What mobile device OS and minimum versions are in use by crews? Options: iOS (specify version), Android (specify version), Mixed / Unknown
• How many field devices/users need provisioning and mobile login accounts? Options: 1-10, 11-50, 51-200, 200+
• Is cellular coverage intermittent on your sites requiring robust offline workflows? Options: Yes - frequent outages, Occasional, No - good coverage
• Which in-field forms and data capture templates must be available offline (sprays, planting, harvest checks)?
• Do you require device management (MDM) provisioning, PIN/policy enforcement, or asset tagging for mobile devices? Options: Yes - MDM required, No - BYOD acceptable, Some devices managed, others BYOD
• What sync rules do you prefer for offline-to-cloud data (auto-sync when online, manual sync, scheduled)? Options: Auto-sync on connectivity, Manual user sync, Scheduled nightly sync, Combination

Digitize and Geotag Spray and Application Records

• Are current spray/application records paper-based, spreadsheet, or in another system? Options: Paper, Spreadsheet, Existing digital system, Mixed
• What level of geotagging is required (point-level operator GPS, field polygon, swath-level)? Options: Point-level (operator GPS), Field polygon, Swath-level / equipment track, Photo-only with location
• Which application attributes must be captured (product, rate, tank mix, nozzle, applicator, weather conditions)?
• Do you need attachments (photos, MSDS) attached to each application record? Options: Yes - photos and docs, Photos only, No attachments required
• Are there regulatory or insurer-specific fields/templates that must be included in the digitized records? Options: Yes - provide templates, No - standard fields ok, Unknown - need sample
• Should spray records be used to trigger downstream reporting (audit reports, landlord statements)? Options: Yes - include in reporting, No - store only, Flag for selective reporting

Generate Crop Insurance Audit Reports

• Which crop insurance form/report formats do your insurers require (AIP, XML, PDF templates, custom)? Options: Insurer-standard PDF, XML/structured export, Custom template - provide sample, Other
• What acceptance criteria do insurers use (swath-level timestamps, applicator signature, evidence of placement)?
• Which seasons/fields should be included in the audit report scope? Options: Most recent season only, Last 2 seasons, Custom field list (provide), All available history
• Do you require PDF-ready, signed-ready reports or machine-readable exports for insurer portals? Options: PDF for print/email, Machine-readable export, Both
• Are there common insurer rejections you want the report validation to catch before submission? Options: Missing timestamps, Unmatched field IDs, No applicator record, Moisture mismatch, Other
• Who will be the primary recipient of generated audit reports (insurer, loss adjuster, internal audit)? Options: Insurer/Loss Adjuster, Internal farm bookkeeper, Landlord, Other

Produce Landlord Settlement Statements

• Do landlord settlements follow a per-acre or revenue-share model for your leases? Options: Per-acre, Revenue-share/percentage, Custom formula per lease, Mixed
• How many landlords/leases will require settlement statement outputs? Options: 1-5, 6-20, 21-100, 100+
• What fields must appear on landlord statements (acreage by field, yield, gross revenue, deductions, inputs allocated)?
• Do landlords require signed/dated statements, custom branding, or specific export formats (PDF/Excel)? Options: Signed PDF, Excel export, Branded PDF, Other
• Should split-fields (multiple landlords on one field) be allocated automatically based on polygon ownership, or manually adjusted? Options: Automatic allocation, Manual adjustments, Provide allocation table
• Do you need a reconciliation report showing how costs/yields were apportioned to each landlord for audit purposes? Options: Yes, No, Optional

Sync Field-Level Costs to Accounting Systems

• Which accounting/ERP systems must be integrated (QuickBooks, Ag-specific, SAP, CSV export)? Options: QuickBooks Desktop/Online, Sage/Other, Farm-specific ERP, Custom/CSV only, Other
• Do you require real-time posting of field transactions or periodic batch exports? Options: Real-time/API, Daily batch, Monthly batch, Manual export only
• How should field-level costs map to your chart of accounts or cost centers (provide sample mapping or describe)?
• Are there multi-entity or inter-company allocations to support (e.g., seed company vs operator vs landlord)? Options: Yes - multi-entity, No - single entity, Some fields multi-entity
• What file format or API credential provisioning will your accounting system accept for integration? Options: API credentials available, CSV/Excel import, Manual journal entries only, Other
• Do you need validation rules (e.g., cost vs budget thresholds) enforced before syncing to accounting? Options: Yes - enforce, No - sync raw only, Optional/flagging

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Per-Acre Pricing & Commercial Terms
• Service Level Agreement (SLA) — Connectivity & Support
• Payment & Billing Schedule
• Pilot / Evaluation Agreement
• Mutual Acceptance Criteria — Audit & Report Outputs
• Data Migration, Ownership & Access Agreement
• Equipment & Telematics Compatibility Commitment
• Change Order & Scope Amendment Process
• Security & Data Processing Agreement (DPA)
• Termination, Cancellation & Refund Terms
• Signature Authorization & Primary Contacts

• Adoption & Success Review
• Audit & Landlord Report Confirmation Workshop
• Lessons Learned & Operational Retrospective
• Issues & Enhancements Triage (Recurring Governance)
• Financial Reconciliation & Landlord Settlement Review

• Update ticket assignments and sprint scope based on today's prioritization.
• Agree and document mutual acceptance criteria and sign-off process for future audits/settlements.
• Deliver updated report templates implementing agreed edits and circulate for final sign-off.
• Record and publish the mutual acceptance criteria document to the shared channel.
• Create follow-up tickets for any data gaps identified and assign owners with deadlines.
• Set Context & One-sentence State/Consequence/Future
• Capture a comprehensive list of deployment and adoption lessons with documented root causes.
• Prioritize a pragmatic backlog of operational improvements with owners and deadlines.
• Agree on how lessons and progress will be maintained and communicated in the shared channel.
• Create prioritized improvement tickets in the shared backlog and assign owners within 3 business days.
• Update onboarding and runbook documentation based on agreed lessons.
• Publish a retrospective summary to the shared channel and schedule a 30-day check-in.
• Review Open Tickets & Statuses
• Keep the issues and enhancements backlog groomed and prioritized for timely resolution.
• Enforce SLA targets and escalate any blockers that threaten audit/landlord readiness.
• Ensure the shared channel remains the single source of truth for statuses and communications.
• Opening & Objectives
• Publish SLA adherence metrics and a short status summary to the shared channel after the meeting.
• Escalate any blocker tickets to leadership with a recommended mitigation plan.
• Current Reconciliation State (one-sentence)
• Identify and document the root causes of financial reconciliation exceptions.
• Confirm accounting export mappings and obtain the bookkeeper's sign-off on sample exports.
• Agree on a verification checklist and cadence for landlord settlements and monthly reconciliations.
• Correct mapping issues and provide a new export sample to the bookkeeper for final confirmation.
• Create a reconciliation checklist and schedule monthly reconciliation meetings with assigned owners.
• Document any data-cleaning steps required to resolve exceptions and schedule a data-migration patch if needed.
• Ensure all stakeholders agree on current state, consequence, and the defined future state.
• Validate sample insurer and landlord reports produced from the customer's data and capture required edits.
• Create a timebound remediation plan with owners and a follow-up cadence to improve adoption and reporting completeness.
• Produce a remediation plan with discrete tasks to fix data gaps and deliver it within 5 business days.
• Schedule targeted training sessions for low-adoption user groups identified in the metrics report.
• Update any report mappings identified during the sample review and circulate revised samples for confirmation.
• Pre-work Check & Objectives
• Demonstrably map every required insurer/landlord field to platform output.
• Obtain explicit stakeholder validation or a clear list of required report edits.
• Current State (one-sentence)
• Timeline & Major Incidents Review
• Current State (one-sentence)
• Consequence (one-sentence)
• Triage New Items
• Consequence (one-sentence)
• Map Requirements to Outputs
• Prioritize Next Release / Patch
• Walkthrough Reconciliation Exceptions
• Root Cause Analysis
• SLA & Escalation Review
• Future State (one-sentence)
• Verify Export Mappings to Accounting
• Create & Prioritize Improvement Backlog
• Live Generate Report Samples (Proof)
• Assign Owners, Timelines & Communication Plan
• Landlord Settlement Sample & Checklist
• Force Validation with Stakeholders
• Adoption Metrics & Heatmap
• Communications & Shared Channel Hygiene
• Sample Report Proof
• Agree Mutual Acceptance Criteria
• Agree Ongoing Reconciliation Process
• Validation & Sign-off
• Action Plan & Owners