Why Dealer Software Hasn't Had a Linear, Stripe, or Figma

Why Dealer Software Hasn't Had a Linear, Stripe, or Figma

AI Summary

Across the past decade, the broader SaaS landscape produced multiple category-redefining vendors. Linear redefined project management against Atlassian and Asana. Stripe redefined payments against the legacy gateway category. Figma redefined design tooling against Adobe. Each captured meaningful share, raised at premium multiples, and forced the incumbents to respond from defense. The dealer software category, across the same decade, produced no comparable vendor. The incumbents consolidated. Pricing held. Feature parity converged. The dealer principal who shopped the category in 2014 and again in 2024 was choosing between what was effectively the same set of products on slightly different brand labels.

The reasons for the dealer software category's flat curve are structural. The OEM customer dynamic insulates the incumbents from buyer-side defection pressure. The franchise law framework limits the kinds of disruption a new vendor can attempt at the contract layer. The buyer-side fragmentation across thousands of independently owned franchise dealers slows procurement of any net-new tool. The DMS layer's deep technical lock-in raises the cost of any tool that needs to read DMS data. None of these conditions are eternal. The conditions for a Linear-of-dealer-software are now in place.

Source: Brevmont Labs, dealer software category-disruption analysis, February 2026.

---

The categories that produced category-redefining vendors

Linear's emergence in the project management category followed a pattern. The incumbent set, including Atlassian's Jira and the various Asana-era tools, had commoditized around feature parity. The differentiation surface had moved to brand and to pricing. A new vendor entered with an architectural argument that the incumbents could not match without rewriting their products. The new vendor captured a generation of developer-tool buyers who had grown up inside the incumbents' workflow and had decided that the incumbents' workflow was wrong.

Stripe's emergence in payments followed a similar pattern. The incumbent set, including the legacy payment processors and the gateway-and-merchant-of-record services, had commoditized around feature parity. The new vendor entered with a developer-first architecture and a pricing model that gave it pricing power inside an apparently price-sensitive category. The incumbents responded with PR and with marketing-layer feature additions, but the architectural difference was structural. The incumbents could not compress their underlying integration cost to match Stripe's curve.

Figma's emergence in design tooling, against Adobe, followed the same pattern. The incumbent set had commoditized around feature parity in single-user design tools. Figma entered with real-time collaboration as the architectural primitive. Adobe responded by acquiring Figma in a deal that ultimately did not close, validating the threat structurally. The collaboration architecture was a category-redefining decision the incumbent could not make from inside its own product.

The pattern across the three is consistent. A commoditized incumbent set, a new vendor with an architectural argument, and a buyer audience ready to absorb the new architecture. The buyer is the one who completes the curve. Without an audience prepared to switch, the architecture would not have produced share.

The dealer software category's flat curve

The dealer software category, across the same decade, did not produce a comparable curve. The incumbent set commoditized, as documented in our earlier essay on the consolidation decade. Cox Automotive absorbed VinSolutions and DealerSocket. CDK Global absorbed ELead and went private under Brookfield. Reynolds and Reynolds remained the long-running independent. Feature parity converged. Pricing held.

The vendors that entered the category as challengers in this period, and there were several, did not capture share at scale. Some closed inside their first three years. Some pivoted to adjacent categories. The few that survived did so as point tools that the incumbents added to their integration directories, not as category-redefining alternatives. None of them had a Linear-style or Figma-style trajectory.

The category therefore looks, from a venture-investment standpoint, like a deeply unattractive vertical. The buyer is fragmented. The incumbent set is consolidated under PE ownership that prices for retention. The OEM customer relationship is opaque. The franchise law context is unfamiliar to most generalist investors. The total addressable market is meaningful but the path to capture is not legible from outside the category.

This is why the dealer software category did not see a Linear, a Stripe, or a Figma. The conditions that produced those categories' breakouts did not align in dealer software. Until they did.

The OEM customer as a structural barrier

The first structural barrier to disruption in dealer software is the OEM customer dynamic. The major dealer software vendors are not, strictly speaking, selling to dealers. A meaningful share of their revenue runs through OEM program enrollments, OEM compliance reporting, and OEM-mandated lead routing. The vendor's product roadmap optimizes for OEM compliance, not for dealer experience.

A new vendor entering the category against this dynamic faces an asymmetric competitive surface. The vendor cannot win the OEM relationship without years of qualification, compliance certification, and program negotiation. The vendor that wins on dealer experience alone, without the OEM credential, has captured a tier of value that does not reach the OEM-funded revenue line. The incumbent's revenue model is not the new vendor's revenue model.

This is what insulates the incumbents from buyer-side defection pressure. A dealer principal who would prefer the new vendor's product cannot fully defect to the new vendor because the OEM-mandated layer continues to require the incumbent. The new vendor sees fractional share rather than full defection. The economics of fractional capture do not produce a category-redefining trajectory at the speed Linear or Figma produced theirs.

The OEM customer dynamic is therefore a moat the incumbents did not have to build for themselves. The franchise system built it for them. The new vendor that enters the category has to architect around the moat rather than directly attack it.

The franchise law moat around incumbents

The second structural barrier is the franchise law framework that governs the U.S. dealer-OEM relationship. The framework constrains the OEM's ability to coerce the dealer into specific vendor relationships, but it also constrains the dealer's ability to substitute one vendor for another inside an OEM-enrolled category. The dealer cannot, in many cases, simply replace the OEM-mandated CRM with a new vendor's CRM and continue operating in the OEM's program.

This produces a layer of legal scaffolding around the incumbent set that any new vendor has to either work around or wait out. Working around it requires architecting the new product as a layer above the incumbents rather than a replacement for them. Waiting it out requires a longer time horizon than most early-stage venture capital is structured to support.

The legal scaffolding is also opaque to most generalist software investors. A typical seed or Series A partner evaluating a dealer software pitch has not built a model for franchise law's contribution to the moat. The model that does exist inside automotive-specialist investors is calibrated against the existing incumbents' reasoning, which is to invest in the incumbent set's continued retention rather than in the disruption of the incumbent set. The capital that would have funded a Linear-of-dealer-software has been routed elsewhere.

The buyer-side fragmentation that slows procurement

The third structural barrier is the buyer-side fragmentation. The U.S. franchise dealer market includes more than seventeen thousand new-vehicle franchise rooftops, owned by several thousand independent dealer groups. The decision-making authority for software procurement is distributed across the principal, the GM at each rooftop, the marketing director, the IT generalist where one exists, and sometimes the F&I director. No single buyer aggregates enough rooftops to produce a fast procurement curve at the category level.

A new vendor entering the category cannot ship a product, sign a hundred logos in the first year, and produce the trajectory that a horizontal SaaS vendor can produce against a centralized procurement function. Each rooftop is a separate sales cycle. Each dealer group is a separate negotiation. The sales motion's economics are slower and more expensive than the categories that produced Linear and Stripe.

This is what made earlier challengers in dealer software die at scale. The product was sometimes good. The sales cycle was always long. The cash burn against the long cycle exceeded the runway. The challenger closed before the trajectory could compound into category share.

The conditions for surviving this fragmentation are now improving. Dealer group consolidation has accelerated. The largest groups now represent a hundred or more rooftops under unified procurement. Selling to a group at this scale is closer to selling to a horizontal SaaS customer than it was a decade ago. The aggregation curve is finally on the new vendor's side.

The DMS layer's deep technical lock-in

The fourth structural barrier is the DMS lock-in at the bottom of the dealer's technical stack. The DMS holds the inventory ledger, the deal history, the customer master record, and the accounting close. Any new vendor whose product needs to read DMS data faces a vendor relationship with the DMS provider that is structurally adversarial. The DMS providers do not publish open APIs at the depth a new vendor would need. The DMS providers offer integration partnerships under terms that preserve the DMS's data lock.

A new vendor whose product can be built without DMS data has more architectural freedom. A new vendor whose product requires DMS data has to navigate the DMS layer's commercial barriers. The architectural decision in front of any dealer software entrant therefore weighs whether the product can ship without DMS dependency.

Above-stack architectures, including the layer this lab is building, sit above the DMS rather than alongside it. The integration job is the rep's session inside the dealer's tools, not a webhook into the DMS. This decouples the new vendor from the DMS lock-in. The barrier becomes navigable rather than blocking.

What the conditions look like for a Linear-of-dealer-software

The conditions that produced Linear, Stripe, and Figma are now in place for dealer software. The incumbents have commoditized. The pricing structure has plateaued. The dealer principal has become articulate about the gap between what the dashboard reports and what the floor does. The dealer group consolidation has produced procurement scale that a new vendor can sell into. The technical environment, particularly browser extension architecture, has matured to the point where above-stack integration is feasible without vendor cooperation.

The next vendor that ships at scale into this category captures the decade. The category has been waiting twenty years for a Linear, a Stripe, or a Figma. The conditions are finally aligned. The lab is building toward this curve.

---

*Brevmont Labs publishes original research on the execution layer beneath relationship-driven sales. The category-disruption framework in this essay draws on broader SaaS-market analysis with parallel applicability to vertical software in regulated industries.*