Internal pricing review · July 13, 2026

John Deere Pricing Response Pack

Combined internal research, proposal comparison, procurement-risk audit, component-level cost table, and a Deere-ready response draft for Betsy Rios’s review of the 644 P-Tier and 333 P-Tier proposals.

Internal working draft · not sent

Executive Findings

7.9%Current lesson/walkaround total above SmartGrade’s discounted total; the original list rate is identical.
20% vs 10%Current machine-framework Pico/PC uplift versus the prior shared SmartGrade framework uplift.
2.2×644P RWC total versus 333P RWC total, with no component-level explanation in the proposal.
$691,080Combined 644P/333P framework and modeling lines—47.2% of those two machine totals.
Bottom line: Betsy’s comparisons are reasonable. The lesson variance is explainable by SmartGrade’s prior discount. The framework uplift, RWC spread, repeated “new” material-system language, and absent reuse credits are not yet explained well enough for procurement. The correct move is transparency and restructuring—not a blanket defense of every line.

Verified Cost Comparison

Component644 P-Tier333 P-TierSmartGrade comparatorFinding
Physics and scoring framework$85,000 Meta
$17,000 Pico/PC
$102,000 total
$85,000 Meta
$17,000 Pico/PC
$102,000 total
$85,000 Meta
$8,500 Pico/PC
$93,500 total
Same Meta base; current platform uplift doubles from 10% to 20%. Per-machine reuse credit is not shown.
Modeling, texturing, rigging$247,000 Meta
$24,700 Pico/PC
$271,700 total
$195,800 Meta
$19,580 Pico/PC
$215,380 total
No direct SmartGrade machine-model comparator644P is $56,320 higher. Both lines include a “new” diggable-material system, so shared-core versus machine-specific work must be separated.
Guided lesson or walkaround line$27,200 Meta
$5,440 Pico/PC
$32,640 total
$27,200 Meta
$5,440 Pico/PC
$32,640 total
Original: $32,640
Discounted: $30,240
The current list rate matches SmartGrade’s original rate exactly; it is 7.9% above the discounted rate.
Real World Controls$85,000 Meta
$17,000 Pico/PC
$102,000 total
$38,500 Meta
$7,700 Pico/PC
$46,200 total
Existing RWC framework referenced644P is $55,800 higher (2.2×). The proposal names hardware but does not disclose engineering hours, custom interfaces, calibration burden, or reuse credit.
Sandbox or Challenge mode$35,000 Meta
$7,000 Pico/PC
$42,000 each
$35,000 Meta
$7,000 Pico/PC
$42,000 each
SmartGrade final:
$36,960 each
Current rates are above a discounted precedent and should identify what is incremental versus the existing mode framework.
Machine total$755,540$708,700SmartGrade contract:
$540,040
Frameworks, models, and RWC account for 57.3% of the combined 644P/333P total—the concentration procurement will scrutinize first.

All values above are directly stated in the June 15, 2026 644/333 proposal or January 15, 2026 SmartGrade proposal. No subcomponent costs were invented.

Component-Level Breakout To Provide

Framework Integration

  • Shared XR architecture and data-layer reuse
  • Machine-specific physics: articulated steering versus track dynamics
  • Loader arm, bucket, digging, lifting, and dumping behavior
  • Scoring, telemetry, and lesson-state integration
  • SmartGrade integration specific to the 333P
  • Per-platform implementation and QA by Meta, Pico, and PC
  • Explicit reuse credit for existing scoring, workflow, and material systems

Modeling, Texturing, And Rigging

  • OEM CAD cleanup and exterior model production
  • Internal component modeling by training requirement
  • Texturing and material authoring
  • Operational rigging and animation setup
  • Bucket, fork, SmartGrade-display, and support assets
  • Shared diggable-material core versus machine-specific adaptation
  • Environment assets and platform optimization
  • Cross-machine asset-reuse credit, including 644 P/G overlap

644P RWC

  • John Deere steering-wheel interface
  • Single multifunction joystick interface
  • Existing racing-pedal mapping
  • Any custom electronics, firmware, drivers, or adapters
  • Control-profile switching and calibration tools
  • Machine tuning, QA, documentation, and support
  • Provisional allowance until Deere selects the final control configuration

333P RWC

  • Dual multifunction-joystick interfaces
  • Existing racing-pedal mapping
  • SmartGrade and standard-control profile behavior
  • Calibration, tuning, QA, documentation, and support
  • Reuse from existing RWC framework
  • Provisional allowance until pedal and joystick mappings are confirmed

Procurement Objection Audit

Critical

Potential duplicate “new” material-system charges

The 644P model line includes a new diggable gravel system; the 333P model line includes a new diggable material system and environmental assets. Internal scope notes still leave gravel versus dirt unresolved. Fix: define one shared material core, separate machine/material adaptations, and show the reuse credit.

Critical

Two full framework charges without visible reuse economics

Both machines carry $102,000 framework totals while the proposal also describes reusable architecture and integration with the existing XR Training System. Fix: separate one-time shared work from machine-specific physics and show inherited components as credits or no-charge reuse.

High

Platform-uplift formula is inconsistent

The machine frameworks use 20%; SmartGrade’s shared framework used 10%; model lines use 10%; lessons, modes, and RWC use 20%. Fix: state the driver for each percentage—implementation, optimization, input adaptation, QA matrix, or release packaging—and apply it consistently.

High

RWC delta is unsupported and hardware is unresolved

The 644P RWC total is $102,000 versus $46,200 for 333P. Internal notes say both control configurations remain undecided. Fix: convert both to assumption-based allowances, list hardware/interfaces/hours, and finalize after Deere selects mappings.

High

SmartGrade overlap is not isolated

The 333P framework includes SmartGrade support, while the prior SmartGrade contract already funded a shared framework, workflow structure, UI behavior, and machine integration patterns. Fix: identify what is reused, what is a 333P-specific adaptation, and which prior deliverables create a credit.

High

Large model lines are catch-all bundles

$271,700 for 644P and $215,380 for 333P combine CAD cleanup, internals, attachments, rigging, materials, environment work, and optimization. Fix: disclose subcomponents and acceptance criteria so procurement can distinguish new IP from adaptation.

Medium

644 P-Tier and G-Tier reuse is not shown

The G-Tier adds $151,360 of model work and references training internals despite having no technical walkaround. Fix: document shared geometry/CAD/material reuse and reduce internal modeling to content actually needed for the two walkarounds.

Medium

Open scope decisions invite change orders

Material type, V-pattern loading target, 644/333 control choices, and some support assets remain unresolved. Fix: move unresolved items into a decision register with assumptions, owner, due date, and price impact before final approval.

Medium

Proposal QA weakens procurement confidence

Internal review found “Simulator” versus “System” terminology, a “Wheel Loade” typo, and summary numbering that jumps from item 3 to item 6. Fix: run a final commercial QA pass before presenting revised numbers.

Deere-Ready Response Draft

Recommended Proposal Revision

  1. Replace bundled pricing with a shared-versus-machine-specific schedule. Show one-time shared systems first, then 644P, 333P, and 644 G-Tier adaptations.
  2. Add explicit reuse credits. Credit SmartGrade workflow/UI patterns, existing XR architecture, scoring, RWC framework, common attachments, shared material systems, and 644 P/G geometry where confirmed.
  3. Normalize platform uplift. Tie every uplift to named work and evidence: input adaptation, optimization, QA devices, packaging, and release support.
  4. Make RWC provisional. Present allowances with hardware assumptions and a not-to-exceed value until Deere selects control mappings.
  5. Offer budget levers instead of an unexplained discount. Phase RWC, reduce internal modeling to hotspot needs, share one material core, defer optional modes, or narrow platform delivery timing.
  6. Run commercial QA. Correct terminology, numbering, typos, scope contradictions, and unresolved assumptions before the meeting.

Evidence And Sources