The Challenge
A particular kind of operational architecture has carried more development firms further than the construction technology industry tends to acknowledge.
Excel. Google Sheets. Email threads. Shared drives organized by hand. A single brilliant analyst who knows where everything lives because they built half of it. The senior PM whose mental model of the active portfolio is more reliable than any system the firm pays for.
This architecture works. It has built portfolios. It has closed deals. It has produced returns. The firms running on it are not behind the times — they are operators who recognized early that off-the-shelf construction software was built for general contractors and didn't fit how owner-developers actually work, and they built a homegrown operating model that did fit. For years, the spreadsheet stack carried the firm faster, cheaper, and with more flexibility than any commercial platform would have allowed.
Until the day it didn't.
The shift happens at a particular inflection point, and most operators recognize the moment when it arrives. The pipeline grows beyond what any single analyst can hold in their head. Active projects span multiple markets, time zones, and capital structures. Capital partners begin asking for reporting that the spreadsheet stack technically supports but only through Friday-afternoon scrambles that consume the senior team's bandwidth. The institutional memory of every project lives in five different team members' heads, and onboarding a new hire requires six weeks of one-on-one knowledge transfer because there is no system to point them to.
The spreadsheet stack got the firm here. It will not, the operators sense, get the firm to the next stage.
AMS Acquisitions reached this inflection point during a phase of meaningful expansion in their national development pipeline. The team's homegrown operating model had served them well across years of disciplined growth. The work was getting done. The portfolio was performing. The firm's reputation was strong. But the operational architecture was beginning to show the strain that always emerges when a firm scales beyond what spreadsheet-based coordination can structurally support.
The team came to Jet.Build with a clear-eyed assessment. We have built something on Excel that has worked for a long time. It is starting to break. We need to replace it with something that scales — without losing the operational discipline we built into the spreadsheets in the first place.
The Approach
AMS Acquisitions deployed Jet.Build as the unified operating platform across their national pipeline. The migration followed the rapid deployment pattern documented in our Switching Platforms Playbook — but with a structural difference from migrations off other commercial platforms.
When a firm migrates off Procore or Autodesk Construction Cloud, the historical project data exists in defined, structured formats. The platform exports the data; the new platform ingests it. The migration is fundamentally about translating between systems that share architectural assumptions.
When a firm migrates off a spreadsheet-and-email stack, the historical data is everywhere and nowhere. Active project context lives in a thousand places — files, email threads, shared drive folders, internal naming conventions that only specific team members can decode, formulas built years ago that nobody quite remembers how to maintain. The migration is fundamentally about capturing institutional knowledge that was never structured to begin with.
Jenny — Jet.Build's built-in AI assistant handled this work directly. Across the firm's active pipeline, the platform ingested years of email threads, document libraries, financial spreadsheets, and project records, and reconstructed the institutional memory in queryable form. The five team members whose heads previously held the firm's institutional knowledge no longer needed to be the only access points. The platform itself became the institutional memory, with citations to the original sources for any team member who wanted to verify.
The structural shift came from how the platform changed which work the team had to do.
Capital partner reporting that previously required Friday-afternoon scrambles became continuous. The portfolio dashboard that the team had been manually assembling each week now rendered in real time. Cost tracking across the national pipeline — which previously required reconciliation between project-specific spreadsheets and the firm's underlying accounting system — became a structural property of the platform. Document control across geographically distributed projects, which had previously depended on rigorous discipline by individual team members, became automatic.
The senior analyst whose comprehensive knowledge of every spreadsheet had carried the firm for years was no longer the single point of failure for the operation. Her time shifted from maintaining the spreadsheet stack to working on the strategic analysis the firm always wanted her to focus on but had never had the operational room to allow. Two of the team members whose roles existed primarily to translate between systems were reassigned to higher-leverage work — pre-acquisition diligence and capital partner cultivation, the activities the firm had wanted to invest in for two years but had never quite had the bandwidth.
The Outcome
The team's first observations after migration matched the patterns we now see consistently across firms making the spreadsheet-to-platform shift.
The single point of failure dissolved. The firm's institutional memory no longer lived in five team members' heads. It lived in the platform, queryable in plain English, accessible to any authorized team member at any moment. New team members ramped meaningfully faster. Senior team members spent less time explaining historical context. The firm became more resilient to staff transitions and less dependent on any single individual's working memory.
National pipeline coordination became continuous rather than episodic. Projects spanning different markets, time zones, and capital structures all rendered on the same dashboard. The senior team could see the entire active pipeline at once, in real time, without anyone having to assemble the view manually. The geographic distribution that had previously compounded the spreadsheet pain became a structural advantage — the platform handled the distribution natively.
Capital partner reporting compressed from weeks to minutes. The Friday-afternoon scrambles disappeared. The reporting capital partners increasingly expected became a continuous, real-time output of the platform rather than a manually produced quarterly artifact. Some of the firm's capital partners now have direct, role-based access to live dashboards rather than receiving periodic summaries.
The team's bandwidth opened in unexpected ways. The hours that previously went to spreadsheet maintenance, manual reconciliation, and institutional-memory translation moved to the strategic work the firm had always intended to invest in. Pre-acquisition diligence accelerated. Capital partner cultivation deepened. The firm's pipeline expanded in directions that had previously felt out of reach because the operational architecture could not have supported them.
In Their Words
We had built something on Excel that worked. For years, it worked. We were proud of it. But by the time our pipeline had spread across markets and we were running real volume, the spreadsheet stack was holding the firm together with what felt like increasing fragility. Migrating to Jet.Build wasn't about adopting a fancier tool. It was about replacing an operating model that had carried us as far as it could carry us. Jenny ingested years of context that had only ever lived in our team's heads, and within weeks the platform was the institutional memory rather than five of our senior people. We have national pipeline visibility we never had before. The team is doing the strategic work we always wanted them to do. The growth we couldn't quite reach on the old stack is suddenly reachable.
— Managing Principal, AMS Acquisitions
What This Validates
The AMS Acquisitions engagement validates a pattern that owner-developers operating on homegrown spreadsheet stacks need to recognize earlier than most of them do.
The spreadsheet stack is not a permanent architecture. It is a stage in the firm's evolution — and the firms that successfully transition to the next stage do so by replacing the operating model deliberately, before the spreadsheet pain compounds into operational failure. The firms that delay the transition are not running on lower cost. They are running on higher hidden cost. The senior team's bandwidth, the capital partner relationship strain, the institutional-memory fragility — all of these are taxes the firm is paying continuously, just in forms that don't appear on any P&L line.
The strategic framework underlying this shift is documented in detail in our True Cost of Manual Coordination guide and our Real Estate Development Operating System playbook. The Coordination Cost Guide quantifies the operational tax that disconnected and manual systems impose. The Operating System playbook describes what a firm becomes capable of when that tax is eliminated. AMS Acquisitions demonstrates the pattern in execution — a firm that built its homegrown architecture deliberately, recognized when it was beginning to break, and made the platform shift on its own terms before the spreadsheet stack forced the issue.
For owner-developers still running on Excel, Google Sheets, email threads, and shared drives — and the firms whose institutional memory currently lives in two or three senior team members' heads — AMS's outcome offers a clear reference point. The transition is real. The institutional knowledge translates. The single point of failure dissolves. The firm becomes capable of growth that was previously out of reach.
The window to make this shift on the firm's own terms — before the spreadsheet stack fails at a moment that was not chosen — is open. The firms that recognize the inflection point and act on it reset the trajectory. The firms that delay continue to operate on architecture that was never designed to carry them where they intend to go.
AMS Acquisitions is an owner-developer with a national pipeline of multifamily and mixed-use development projects, including Silk Lofts (404K SF) and Biron Woods (117K SF). The firm runs its development portfolio on Jet.Build as the unified operating platform.