What Do CAD and Real Estate Have in Common?
What Do CAD and Real Estate Have in Common?
You’re a mechanical engineer at a 60-person medical device company. You designed a housing assembly in SolidWorks last year, forty-seven parts, twelve custom, the rest COTS. The project shipped. The design files live on a shared drive, right where you left them.
Now procurement needs to know which assemblies use a connector that just went end-of-life. They can’t open your files. They don’t have SolidWorks licenses, and even if they did, they wouldn’t know how to navigate the feature tree. So they send you an email. You’re mid-sprint on a different program, but you stop what you’re doing, open the assembly, click through the BOM manually, and paste the results into a Slack message. Twenty minutes of your time, $250/hour fully loaded, to answer a question the files already contain.
The data is right there. Procurement can’t touch it. The file format is a locked vault, and the key costs $4,000 a year per seat.
Now you’re a first-time homebuyer in 2019. You want to know what houses are for sale in your zip code, what they sold for last year, and what the comparable pricing looks like within a mile radius. That data exists. Every bit of it. It’s sitting in the MLS, a database controlled by the National Association of Realtors, accessible only to NAR members and their clients. You can’t query it. You can’t download it. You can see whatever curated slice your agent decides to show you, filtered through their judgment about what you can afford, what neighborhoods you belong in, and which listings pay the fattest buyer-agent commission.
The data is right there. You can’t touch it. Access is controlled by a trade association, and the key costs 6% of the purchase price.
Two completely different industries. Same grift.
In both cases, the incumbents discovered something more valuable than their core service: artificial scarcity of information that their customers generate or pay for. Dassault Systèmes doesn’t sell CAD software. They sell the exclusive right to read your own design files. NAR didn’t sell real estate services. They sold the exclusive right to see the housing market. The actual engineering work, the actual home-selling work, those are just the cover charge. The real revenue model is the velvet rope around the data.
The pitch, if anyone ever said it out loud, would be: “Hey, how about you pay us a lot of money to look at your own fucking IP? Great. Cool. I’ll invoice you.”
Nobody says it out loud. They don’t have to. The file format says it for them.
NAR’s racket lasted decades. The MLS was the moat: if you wanted to list a house, you went through NAR. If you wanted to see listings, you went through an NAR member. Zillow and Redfin chipped at the edges, building consumer-facing portals that displayed MLS data through licensed feeds. But the underlying structure held. Sellers paid 5-6% commissions because the alternative was invisibility. Buyers accepted their agent’s curation because the alternative was blindness.
Then in October 2023 a jury in Missouri looked at the whole arrangement and said, basically, “this is a cartel.” The Burnett verdict hit NAR with $1.78 billion in damages. The subsequent settlement cost $418 million and blew open the compensation structure: sellers no longer automatically pay the buyer’s agent commission, commission offers can’t be advertised on the MLS, and buyers must sign written agreements with their agents specifying fees. The information asymmetry that powered the industry for thirty years is being dismantled by court order.
Scale of harm and breadth of victims forced the reckoning. Residential real estate touches nearly every American household. When a jury hears “you overpaid by tens of thousands of dollars because a trade association rigged the information flow,” the political math tips toward intervention. Enough voters got screwed that the legal system responded.
CAD has no equivalent constituency. The people harmed by proprietary file formats are a few hundred thousand engineers, procurement specialists, and quality managers at companies that already pay the license fees. They’re not sympathetic plaintiffs. They’re line items in a corporate IT budget. No jury is going to award billions because a defense contractor had to buy more SolidWorks seats.
And the CAD vendors are learning from NAR’s mistakes. They watched Dassault’s competitor PTC get dragged through licensing disputes. They watched the MLS get blown open. Their response: move the canonical data to the cloud. Onshape (owned by PTC, ironically) already runs entirely in the browser. Fusion 360 is halfway there. SolidWorks’ 3DEXPERIENCE platform is pushing the same direction. When the file lives on the vendor’s server, there’s nothing on your disk to reverse engineer. The DMCA question becomes moot because you never possess the bits. The vault moved from your building to their data center, and they changed the locks to biometric.
This is the real estate equivalent of NAR responding to the Burnett verdict by saying “fine, we’ll stop printing the listings entirely and you’ll have to come to our office to look at them on our screens.” Except in CAD, nobody’s suing, so the vendors can actually do it.
What’s left? The same move that works everywhere the data is walled off but the exhaust escapes: read the exports. STEP files carry geometry. BOM exports carry part identity and relationships. PDM systems expose revision metadata through APIs. Property fields in Altium and SolidWorks leak requirement annotations into formats that aren’t locked down. The engineer who types REQ-047 into a part property has just created a trace link that escapes the proprietary format every time someone exports the BOM as a CSV.
Will CAD ever have a Real Estate moment? I doubt it. the plaintiffs in real estate were consumers with emotional stakes and large dollar harms. The plaintiffs in a hypothetical CAD antitrust case would be corporations arguing about interoperability and switching costs. Judges understand “I overpaid $30,000 on my house.” Judges do not understand “I can’t query ECAD metadata without a seat license for a tool my procurement team will never use.”
So CAD files will stay opaque. The quiet revolution of making hardware engineering artifacts legible the way git made codebases legible is correct and inevitable. It’s also going to take a decade or more, if it happens at all, and it won’t be driven by piracy or litigation. It’ll happen when a defense prime puts “open format export with full metadata” into a procurement requirement, or when a regulatory body decides that classified programs can’t depend on vendor-controlled tooling for design data access. Slowly, grudgingly, through leverage rather than principle.
Sometimes I hate capitalism.