How BuildVision Uses Deck to Win Enterprise Customers Inside Legacy Systems

BuildVision structures construction data so manufacturers can automate decisions across billions of equipment permutations. With Deck as the interop layer, they prove automation fast — even inside legacy systems with no APIs.

Key metrics

• Billions of equipment permutations inside the workflows BuildVision automates
• Deck first — one branch built with Deck proves the full tree is possible before signing
• 3 to 6 months of engineering work deferred until after the contract is signed

The company

BuildVision converts construction documents into structured, machine-readable data. Their target: any process where information lives on one screen and software lives on another, with a person manually bridging the two.

"We target any process where you have information on one screen and software on another monitor — you're looking back and forth between the two." — Ben Lyddane, BuildVision

But those systems were built for users, not for the kind of automation BuildVision is selling. No APIs, no clean exports, just portals their customers navigate by hand.

The challenge: Proving complex automation inside legacy systems

BuildVision's workflows are complex by nature. One piece of equipment can carry thousands of attributes — some calculated, not selected — with rules that cascade across billions of possible permutations.

In enterprise sales, describing that problem is easy. Showing it solved is what closes deals.

But given the complexity of their workflows, building fully working integrations before a contract closes is expensive and slow. Doing that for every prospect wasn't viable.

"It would be very very expensive for our engineers to have to build everything every time individually for these demos."

The Deck difference: Build vs. buy, done right

Before getting a contract signature, BuildVision engineers need to show something real first, inside the manufacturer's own systems, before a single line of production code is written.

Deck makes that possible. BuildVision uses it to demonstrate one branch of a manufacturer's option tree — enough to show the whole tree is within reach — without committing engineering resources to a deal that hasn't closed.

"Sometimes to get to the magic moment for a manufacturer, you want to show them something actually working. And that's where a demo powered by Deck becomes extremely powerful."

The enterprise flow

• Demo powered by Deck: Working integration shown to manufacturer before any production build
• ~3 months: Enterprise contract negotiation and close
• 3 to 6 months: Full direct API integration built by BuildVision engineers

Deck handles the first stage. BuildVision's engineers handle the rest — but only after the deal is done.

Why Deck fits

Custom endpoints, matching the complexity of the flows

Deck also handles the unexpected: new edge cases, new manufacturer systems, new problems that appear mid-deal. Custom endpoints, built fast.

"I don't know what those problems are going to look like, but I know I can call you guys and hopefully you can get it done for us."

A team as responsive as their own

The partnership itself sets the pace. Via a shared Slack channel, Deck responds to active sales questions faster than BuildVision could dream of.

"There's been times that you guys have probably been even more responsive than our own internal employees in certain cases."