The Project
Vikings Lakes is one of the most distinctive sports-anchored real estate developments in the country.
Spread across roughly 200 acres in Eagan, Minnesota, the master plan brings together the Minnesota Vikings headquarters, TCO Stadium, the TCO Performance Center, the Omni Hotel Viking Lakes, and a broader mixed-use community of office, residential, retail, and amenity space. The full program totals roughly 3.3 million square feet of development at completion — a generational footprint that will shape the surrounding region for decades and will continue evolving in phases over years to come.
Building developments at this scale and in this category creates an operational complexity that few real estate organizations encounter. The work spans a franchise headquarters, professional sports infrastructure, hospitality, mixed-use commercial, and the community amenities that connect all of the components into a coherent destination. Each category of work carries its own design standards, regulatory environment, financing structure, capital partner expectations, and operational tempo. The development team coordinating across all of it operates within a layered set of stakeholder relationships that reach into franchise operations, league requirements, public-private partnership obligations, and the long-horizon stewardship responsibilities that come with building infrastructure that will define a region for fifty years.
The Vikings organization came to this development with the discipline of a sophisticated real estate operator and the long-term thinking of a franchise that builds for generations. The platforms supporting that work needed to match.
The Challenge
Master developments of this scale do not run cleanly on the construction technology built for individual projects.
The standard construction management platform assumes a single project, a single GC, a single design team, and a single owner with a relatively narrow set of stakeholders. Vikings Lakes has none of those simplifying assumptions. Multiple components are at different phases simultaneously. Different general contractors, different specialty trades, different design partners, and different capital structures coexist within the same master plan. Reporting requirements vary by component — what an institutional capital partner expects on the hospitality component looks very different from what franchise operations needs on the headquarters component.
Running this complexity on disconnected systems creates a particular kind of operational tax. The translation work between systems consumes substantial portions of the development team's bandwidth. Capital partner reporting requires manual synthesis from multiple underlying data sources. Schedule coordination across components depends on individual team members' working memory rather than structural visibility. The development team faces a continuous choice between hiring additional translation capacity or accepting that the operational architecture cannot quite keep pace with the development's ambition.
The Vikings organization needed an operating layer that could carry this complexity natively — across components, across phases, across capital structures, across the long horizon over which a master development of this scale operates.
The Approach
The Minnesota Vikings deployed Jet.Build as the unified operating platform across the Vikings Lakes Master Development. The migration followed the rapid deployment pattern documented in our Switching Platforms Playbook. Active components continued through the migration window. The team went live within the standard deployment timeline.
The structural shift came from how the platform changed where the project information for each component lived and how it could be synthesized at the program level.
Every component of the master development — the headquarters and stadium adjacencies, the Performance Center, the Omni Hotel Viking Lakes, the mixed-use commercial and residential phases — runs on the same unified platform. The general contractors and specialty trades operating on individual components plug into the platform as participants in a single, coherent system rather than each working in their own siloed environment. Schedule, cost, document control, and decision history accumulate continuously across every component, in formats that allow program-level visibility without requiring manual synthesis from disparate sources.
Jenny — Jet.Build's built-in AI assistant handles the work of synthesis at the program scale. Questions that previously would have required a development analyst to spend a half-day pulling from multiple sources are now answered in seconds, with full citations to source documentation. "What's the schedule risk across all active components heading into the next quarter?" — "Show me every change order over $250,000 across the master development, with originating decision and current status." — "Generate the capital partner brief covering current-quarter activity across the full program." The work that previously consumed senior development team weeks became continuous and queryable.
The implications compound across a master development of this scale.
Capital partner reporting compresses dramatically. The synthesis work that the development team previously performed manually each quarter now happens continuously, in formats that allow capital partners visibility into their specific components or the program as a whole, depending on their relationship with the development.
Franchise stewardship of the long-horizon program becomes structurally easier. The institutional memory of every decision, every change, every approval accumulates permanently in the platform — accessible years from now to whatever team is operating the development at that point in its evolution. The platform becomes the long-term record of a development that will outlast individual team members, individual capital partners, and individual phases of construction.
Component-level execution remains uncompromised. Each general contractor and specialty trade operating on a specific component continues to do their work the way they do it best. The platform's role is to make their work visible at the program level rather than to constrain it at the component level. The result is the operational tempo individual GCs need at the project scale, plus the program-level visibility the development organization needs at the master plan scale.
The Outcome
The development team's first observations after migration matched the patterns we now see consistently across master developments and multi-component programs operating on Jet.Build.
Program-level visibility became continuous. The senior development team can see the entire master development at once, in real time, without anyone having to assemble the view manually. The geographic and component complexity that previously compounded the operational tax became a structural advantage — the platform handles the distribution natively.
Capital partner relationships strengthened across the program. Real-time visibility produced a different kind of capital partner conversation. Partners on specific components could be given direct, role-based access to dashboards reflecting their specific exposure rather than receiving periodic synthesis. The trust dynamic moved from reactive reporting to continuous transparency.
Long-horizon stewardship became structural. The development's institutional memory now lives in the platform rather than in individual team members' heads. The decision history for every component, every approval, every change order accumulates permanently. Whatever team operates the development in the next phase of its evolution will inherit a coherent operational record rather than reconstructing one from spreadsheets and email threads.
Component-level GCs maintained their operational tempo. The general contractors and specialty trades operating across the master plan continued to execute at the cadence their work requires. The platform's role was structural rather than constraining — visibility at the program level without slowing execution at the component level.
In Their Words
Vikings Lakes is a generational development. The components, the phases, the capital structures, and the long-horizon thinking all required an operating layer that most construction technology was not built for. Jet.Build gave us program-level visibility across the entire master plan without compromising the operational tempo our individual general contractors needed on their specific components. The institutional memory of every decision now lives in the platform rather than in our team's heads. Whatever the development becomes over the next twenty years, the operational record will be coherent. That continuity matters when you are building something this consequential.
— Senior Real Estate Development Leader, Minnesota Vikings
What This Validates
The Vikings Lakes engagement validates a pattern that should matter to every owner-developer running multi-component master developments — and to the GCs and specialty trades who execute on them.
Master developments do not need to fragment across siloed component-level systems. The visibility that program-level operators require can coexist with the operational tempo that component-level GCs and specialty trades need at the project scale. The architectural assumption that has historically forced this tradeoff — that construction software is fundamentally project-scaled rather than program-scaled — is no longer required. Modern unified platforms now operate at the program scale natively, with component-level execution unconstrained underneath.
The strategic framework underlying this shift is documented in detail in our Real Estate Development Operating System playbook. The Vikings Lakes engagement demonstrates the framework executing at one of the most distinctive sports-anchored development scales in the country.
For owner-developers running master developments — whether sports-anchored, mixed-use, institutional, or any other multi-component program — the Vikings Lakes outcome offers a clear reference point. The operational tax of running components on disconnected systems is real. The platform shift recovers it. The capital partner dynamics strengthen. The long-horizon stewardship of the development becomes structural rather than dependent on individual team members' working memory.
Generational developments deserve operating systems that match their ambition. The Minnesota Vikings demonstrate what that looks like in execution.
The Minnesota Vikings are a National Football League franchise. Vikings Lakes is the team's master development campus in Eagan, Minnesota — a roughly 200-acre, 3.3M SF mixed-use community anchored by the team's headquarters, TCO Stadium, the TCO Performance Center, and the Omni Hotel Viking Lakes. The development runs on Jet.Build as the unified operating platform.