A 190-year-old industrial company merged software and steel — and the lesson is not the acquisition history. It is the operating-model choice.
Deere & Company, founded in 1837, is one of the oldest continuous industrial manufacturers in the world. Its brand is built on physical hardware — tractors, combines, planters, sprayers. By the mid-2010s, agriculture was being reshaped by precision, sensing and data economics that traditional manufacturers were not organisationally positioned to serve.
The publicly-documented problem was that the value of a modern tractor was increasingly moving from the steel to the software running on it — precision guidance, variable-rate spraying, yield mapping, telematics, and data services. Farmers were becoming customers of both the physical machine and the operating layer on top of it, and the companies best positioned to serve the second layer were not necessarily traditional manufacturers.
Deere invested progressively in precision-agriculture capabilities across the 2010s. The 2017 acquisition of Blue River Technology, publicly reported at around 305 million US dollars, brought See & Spray — a computer-vision-guided precision spraying capability that identifies individual weeds and treats them selectively rather than blanket-spraying a field. Earlier acquisitions and internal work covered GPS guidance (NavCom and related), telematics, and the data platform underneath the equipment fleet. Deere publicly began describing itself as a company that combined software and steel. Executives repeatedly framed the strategic move as a business-model reengineering, not a technology upgrade programme.
**SOURCE CLAIM:** Deere's own investor communications and Harvard Business Review coverage over 2018–2022 describe Deere as one of the clearest examples of a legacy industrial manufacturer building durable software and data capability alongside its hardware business. The precision-agriculture segment became a strategic priority in Deere's public financial framing. **JETTIFI ANALYSIS:** the durable outcome, distinct from any specific acquisition or product launch, is that Deere positioned its software and data capability as a first-class business alongside — not subordinate to — the manufacturing business. That framing is the reengineering.
The most instructive part of the case is not the acquisition history. It is that Deere made the operating-model choice to treat software and data as a first-class business rather than as a service organisation supporting the hardware business. In many legacy manufacturers, digital capability is organised as an IT function reporting to a chief information officer whose primary charter is to keep the manufacturing engine running. That reporting structure produces predictable outcomes — the digital function optimises manufacturing rather than opening new business territory. Deere chose to organise differently.
The reengineering lesson is that where digital capability reports, and to whom it is accountable, determines what it will produce. If a legacy manufacturer wants software and data to become a business, the operating model has to make that possible — reporting lines, capital allocation, executive scorecard, and P&L visibility. If digital capability reports as IT, it will behave as IT.
For a legacy manufacturer, distributor, or industrial operator, the practical implication is that the first move is not to authorise a large digital-transformation programme. The first move is to decide whether the digital capability will be organised as an IT function or as a business — and to structure reporting, capital and accountability accordingly. That choice, made once, is more consequential than any specific technology decision made later.
**JETTIFI RECOMMENDATION:** approach this class of engagement by starting at the organisation-design layer. Diagnose where digital capability currently reports, what its charter is, and what its scorecard rewards. If the answer to any of those is 'it supports manufacturing / distribution / the physical business', the operating model needs to be reengineered before a technology programme is authorised. Reversibility matters here — a small structural experiment is often the right way to test whether the operating-model change will hold.
Discuss a legacy manufacturer challenge
Talk to Jettifi →For the underlying working paper, read The Digital Reengineering pillar. For the executive edition, read the Guide. Site name: Jettifi.