For years, an American farmer could own a $400,000 John Deere tractor outright and still not be allowed to fix it. Not because the repair was hard. Because the tractor would throw an electronic fault code, and the only tool that could read and clear that code lived with an authorized Deere dealer. Your machine, your field, your busted part, and you still had to wait for the dealer and pay the dealer, because Deere held the one key that turned it back on.

On July 8, that ended. The Federal Trade Commission, along with five states, settled an antitrust suit that forces Deere, for the next ten years and under federal oversight, to give farmers and independent repair shops the same repair resources it gives its own dealers. That means the ability to read, clear, and reset fault codes, reprogram electronic components, restart a machine out of emissions "limp mode," and search the technical manuals that used to be dealer-only.

Read the FTC's own description of what Deere was doing and it stops being a farm story. "Deere makes the only software repair tools capable of performing all electronic repairs on Deere equipment," the Commission wrote, and it "made such tools available only to its authorized dealers." That is not a farming problem. That is a software problem wearing overalls. And it is sitting, right now, in a lot of small-business software deals.

The lock is always the same shape

Strip the tractor away and the mechanism is simple. A vendor sells you something you depend on. Then the vendor keeps the one key you need to actually operate or leave it. As long as they hold the key, they set the terms.

In software the keys are easy to name once you go looking for them. The source code to the custom app someone built you. A real export of your own data, in a format you can actually use somewhere else. The admin credentials to your own site, your own analytics, your own ad accounts. Control of the domain your whole business runs on. The ability to move your email off a platform without losing five years of history.

It took a federal antitrust suit, five co-plaintiff states (Illinois, Arizona, Michigan, Minnesota, and Wisconsin), and a year and a half of litigation to get farmers a key they should have had with the purchase. Small businesses rarely get that cavalry. They find out they were locked out at the worst possible moment: the developer goes quiet, the agency raises its rates, the SaaS tool sunsets the plan you're on, and suddenly the thing you paid for is a thing you're renting from someone who knows you can't leave. We've written before about what happens when the only person who understands your software walks out the door, and about how to build integrations you can walk away from. The Deere settlement is the same lesson at national scale, with the government doing the walking-away on the farmers' behalf.

Here's the uncomfortable part. Deere's lock-in was illegal enough to draw an FTC suit and a ten-year consent order. Most software lock-in is perfectly legal, because you agreed to it. It's in the contract you signed, or more often, in the contract you didn't read and the questions you didn't ask.

Get your keys at the signing table, not the courthouse

Farmers needed the FTC to pry the keys loose after the fact. You don't have that luxury, and you don't need it, because you get to negotiate before the relationship starts. The leverage is highest on the day you're about to hand someone money. Spend it there.

A few keys worth asking for in writing, whether you're commissioning a custom build or buying into a platform. Who owns the source code when the project is done, and do you get a copy of it? Can you export all of your data, in full, in a usable format, on your own, without asking permission? Are the accounts your business depends on, your domain, your hosting, your analytics, registered in your name with you as owner, not under an agency's umbrella login? And if you and this vendor part ways on bad terms, what exactly can you take with you, and how? A good partner answers those plainly, because a good partner was never planning to hold your business hostage. The answers you have to fight for tell you everything.

This is how we think about building software for people and how we connect the tools a business already runs on: the goal is a system you own and could hand to someone else tomorrow, not a leash with our name on the handle. Ownership isn't a favor a vendor grants you when a regulator makes them. On a tractor or in a codebase, it's the whole point of buying the thing.

The farmers got their keys back this week. The better move is to never hand yours over in the first place.