In construction technology, some failures end up being more influential than successes. Such is the story of Flux, a Google X spinoff that, despite its eventual pivot and dissolution, helped shape the future of construction technology in ways that continue to reverberate through the industry today.
With a whopping $29 million Series B funding round and a team packed with exceptional talent, Flux seemed poised to revolutionize the construction industry through better data interoperability. Their mission was ambitious yet straightforward: help architects, engineers, and cost planners share information more seamlessly to design better buildings. Think of it as trying to create the G Suite for construction – a unified ecosystem where different tools could work together harmoniously.
But as former Flux CPO Anthony Buckley-Thorpe reveals, what seemed like a straightforward problem of technological innovation turned out to be a complex web of business and cultural challenges. “We had a great product, we had great feedback, we had some fantastic users,” he recalls. “It was really tough to let those people down.” The company’s eventual pivot wasn’t due to running out of money or lacking technical capability – it was about the fundamental challenge of monetizing their solution in an industry that wasn’t quite ready for it.
In this episode, Anthony Buckley Thorpe talks about the challenges of innovating in construction, lessons from Flux’s journey, and thoughts on building successful AEC tech products.
The Monetization Puzzle
One of the most fascinating insights from Flux’s journey was the disconnect between users and decision-makers. The people who loved and used Flux’s products were often computational designers and forward-thinking architects – but they weren’t the ones controlling the purse strings. As Buckley-Thorpe notes, they’d often find themselves in meetings where the head architect would point to a new graduate and say, “He told me about you guys.”
This highlighted a crucial lesson for construction technology startups: having great software for one type of user isn’t enough. You need to sell to the right person, and more importantly, you need to build a clear path to revenue from day one. The “we’ll figure out monetization later” approach that might work in consumer tech simply doesn’t fly in the construction industry.
The Collaboration Conundrum
Perhaps the most profound insight from Flux’s experience was what Buckley-Thorpe calls “the grease versus fat” dilemma. As their CEO once noted, “In construction, there is grease and there is fat, and you need to be careful which one you take out.” Flux’s dream of free-flowing information between parties ran headlong into a harsh reality: many industry players are actually incentivized not to share information.
Why? Because in an industry where substantial revenue can come from claims against other parties, transparency isn’t always desirable. While individual users might dream of better collaboration, their organizations often have structural reasons to maintain information silos. It’s a sobering reminder that technical solutions alone can’t solve what are essentially business model and incentive problems.
The Phoenix Effect
But here’s where the story takes an interesting turn. While Flux itself may have pivoted away from its original vision, its impact continues through a new generation of construction technology startups founded by former team members. Companies like Join.build, focused on pre-construction, and Rayon, working on innovative construction solutions, emerged from the Flux diaspora. Even companies not directly connected to Flux, like Speckle, acknowledge learning from Flux’s experiences.
What makes this particularly remarkable is that these talented engineers and entrepreneurs, despite experiencing setbacks, chose to stay in the construction industry. They could have easily moved to more traditional tech sectors, but instead, they remained committed to solving construction’s complex challenges.
Lessons for the Future
For today’s construction technology startups, Flux’s legacy offers several crucial lessons:
- Revenue First: Don’t leave monetization as an afterthought. In an industry with long project lifecycles, you need a clear path to revenue from day one.
- Understand the Real Buyer: Great user adoption doesn’t automatically translate to sales. You need to align your solution with the priorities of those holding the purse strings.
- Respect Industry Dynamics: Just because something makes logical sense (like better collaboration) doesn’t mean the industry is structured to embrace it.
- Think About Scale: Consider how your solution will work not just for one project or team, but across the complex ecosystem of construction.
Looking Ahead
The construction technology landscape today is markedly different from when Flux emerged from Google X. There’s greater awareness of digital solutions, more willingness to adopt new technologies, and perhaps most importantly, a better understanding of the industry’s unique challenges.
The new generation of startups emerging from Flux’s legacy seems to be taking these lessons to heart. They’re focusing more on specific, solvable problems rather than trying to revolutionize everything at once. They’re thinking about business models from day one. And crucially, they’re building solutions that work within the industry’s existing incentive structures rather than trying to completely reimagine them.
As Buckley-Thorpe puts it, “There’s 20 years of technological innovation just sitting there ready to be applied… It’s not the technology. It’s the business model.” For the next generation of construction technology entrepreneurs, understanding this distinction might be the key to turning innovative ideas into sustainable businesses.
