The Challenge
Owner-developers running growing multifamily portfolios face a particular kind of operational friction that doesn't show up cleanly on any single P&L line.
Cost discipline across active projects requires real-time visibility into what's been committed, what's been paid, what's at risk, and how every variance traces back to a specific decision made weeks or months earlier. Document control across the same portfolio requires the same discipline applied to drawings, RFIs, submittals, change orders, and the institutional memory that holds an entire project together. Both have to happen continuously. Both have to remain visible to capital partners and lenders who increasingly expect real-time access to the same operational truth the development team is working from.
The standard approach to managing this — a construction management platform owned and operated by the GC, accounting in a separate system, capital partner reporting assembled manually each quarter — produces a particular kind of operational tax. The development team spends substantial portions of every week translating between systems, reconciling discrepancies, and producing reports that the underlying systems weren't designed to produce natively. The translation work compounds as the portfolio grows. By the time a multifamily-focused owner-developer is running five to ten active projects, the operational tax of running across multiple disconnected systems has become measurable, and the cost of not solving it shows up in capital deployment cycles, capital partner relationships, and the senior team's bandwidth for strategic work.
Rubin Equities reached this inflection point during a phase of meaningful growth in their multifamily and mixed-use portfolio. The work was getting done. The portfolio was performing. But the operational layer underneath the work was demanding more of the senior team's attention than the work itself, and the friction was becoming visible in capital partner conversations that the firm wanted to be running more efficiently than the legacy stack allowed.
The team came to Jet.Build with a clear set of requirements. Real-time cost tracking across the portfolio. Document control that scaled across multiple active projects without requiring proportional headcount. Capital partner visibility that didn't depend on quarterly reporting cycles. And the operational tempo to support continued growth without the operational tax growing in lockstep.
The Approach
Rubin Equities deployed Jet.Build as the unified operating platform for their development portfolio. The migration followed the rapid deployment pattern documented in our Switching Platforms Playbook — historical project data ingested by Jenny, Jet.Build's built-in AI assistant, the team going live with active projects continuing throughout the migration window.
The migration followed the rapid deployment pattern documented in our Switching Platforms Playbook — historical project data ingested by Jenny, Jet.Build's built-in AI assistant, the team going live with active projects continuing throughout the migration window.
The structural shift came from how the platform changed where the firm's project information lived and who controlled it.
Cost data, document control, schedule activity, change order workflows, and capital partner reporting all moved onto a single platform owned and operated by Rubin Equities directly. The GCs the firm worked with continued to operate inside the platform as participants — exactly the dynamic described in our Owner's Guide to Construction Visibility. The development team did not need to ask their GCs for status updates, financial summaries, or document logs. The information was visible in real time, on the platform Rubin controlled, generated continuously as the work happened.
The implications compounded across the portfolio.
Cost tracking became continuous rather than episodic. The firm's CFO no longer waited for weekly status reports to know where active projects stood financially. Variances surfaced as they emerged. Forecasts updated as new commitments were made. The reconciliation work that previously consumed substantial portions of the finance team's week largely disappeared.
Document control became automatic. The latest set of revised drawings was always findable. The RFI history on a specific scope was queryable in seconds. The submittal log across the portfolio was a structural property of the platform rather than a manually maintained spreadsheet. Jenny answered the questions that previously required document archaeology — "What was the original scope assumption for the mechanical package on Sunset Park, and how does it compare to what we've actually committed?" — in seconds, with full citations.
Capital partner visibility became continuous. Investors and lenders who previously waited for quarterly reporting cycles could be given direct, role-based access to dashboards reflecting real-time portfolio status. The trust dynamic shifted. Capital partners no longer depended on Rubin's reporting interpretation — they could see the underlying data themselves, in the same platform the development team was working from.
The Outcome
The team's first observations after migration matched the patterns we now see consistently across owner-developers making this shift.
Senior team time recovered. The reporting and reconciliation work that previously consumed substantial portions of the senior development team's week became continuous and automatic. The hours got back to strategic work — pre-acquisition analysis, capital partner cultivation, and the operational decisions that determine how a growing development firm scales effectively.
Capital partner relationships strengthened. Real-time portfolio visibility produced a different kind of capital partner conversation. Partners stopped asking for status updates and started asking strategic questions about pipeline and deployment. The relationship dynamic moved from reactive reporting to proactive partnership — and the operational evidence supporting Rubin's growth narrative became visible in real time rather than retrospectively.
Portfolio capacity expanded without proportional operational growth. The firm has been able to take on additional projects without the operational tax growing in lockstep. The translation labor that previously scaled with portfolio size has effectively been eliminated, which means each new active project adds construction work to the firm rather than coordination overhead.
Document control became a structural property rather than a discipline. The institutional memory of every project lives in the platform, queryable in plain English. New team members ramp faster. Senior team members spend less time explaining historical context to junior staff because the platform itself is the institutional memory.
In Their Words
We were running a growing multifamily portfolio on a stack that wasn't built for the way owner-developers actually need to operate. The translation work between systems was eating our senior team's weeks. Capital partner reporting was a quarterly scramble. Moving to Jet.Build changed all of it. We have real-time visibility into our own portfolio, on a platform we control, and our capital partners can see exactly what we see whenever they want it. The senior team got their time back. The growth math finally works the way we always thought it should.
— VP of Development, Rubin Equities
What This Validates
The Rubin Equities engagement validates the operational thesis at the heart of how Jet.Build serves owner-developers — and the broader argument we make in our guide library about how modern multifamily and mixed-use developers should be running their portfolios.
Owner-developers do not need to depend on their GCs for portfolio visibility. They do not need to maintain parallel systems for capital partner reporting. They do not need to absorb the translation tax that running across disconnected platforms has historically imposed. The combination of capabilities that allows an owner-developer to run their portfolio on a platform they control — with their GCs operating inside it as participants and their capital partners seeing real-time data directly — is now available, and the firms that adopt it produce measurable operational separation from their peers.
The strategic framework underlying this shift is documented in detail in our Real Estate Development Operating System playbook and our Owner's Guide to Construction Visibility. Rubin Equities demonstrates the framework in execution, on a real multifamily portfolio, with the operational outcomes the firms making this shift consistently report.
For owner-developers still running on legacy stacks and weighing whether the platform shift is worth the migration effort, Rubin's experience offers a clear pattern. The operational tax is real. The platform shift recovers it. The capital partner dynamic improves. The portfolio capacity expands. The senior team's bandwidth shifts toward the strategic work that actually determines whether the firm grows the way it intends to.
Rubin Equities is a multifamily and mixed-use development firm with a growing portfolio of active projects, including Sunset Park (1.3M SF) and Avon Hall (27K SF). The firm runs its development portfolio on Jet.Build as the unified operating platform.