The Challenge
Most real estate development firms specialize. Multifamily firms run multifamily. Mixed-use developers concentrate on mixed-use. Hospitality operators stay close to hospitality. The specialization makes operational sense — each asset category carries its own design conventions, capital structures, regulatory environment, and execution rhythm, and most developers find that depth in a category produces better outcomes than breadth across categories.
A small number of national developers operate differently. They run portfolios that genuinely span asset categories — mixed-use towers alongside large-scale residential communities, urban developments alongside lifestyle and hospitality assets, all under the same firm, often in the same active development phase. The strategic logic is real. Diversified portfolios produce different exposure profiles, attract different capital partner relationships, and allow the firm to deploy expertise across the full spectrum of real estate work the market produces.
The operational logic is harder.
Running mixed-use, residential, hospitality, and lifestyle development simultaneously creates a particular kind of architectural challenge. Each category carries its own conventions. Each category requires reporting tailored to the specific capital structure underneath it. Each category coordinates with a different specialty contractor and design partner ecosystem. Running all of this on disconnected systems forces the development team into continuous translation work — reformatting outputs from one category's tools to fit another category's expectations, reconciling cost data across capital structures that report differently, producing portfolio-level summaries from underlying systems that were never designed to roll up across category boundaries.
Kushner's portfolio reaches deep into this complexity. Monmouth Square is mixed-use. Colts Neck Manor is large-scale residential community development. Wave Spa is lifestyle and hospitality. Lower Broadway is urban mixed-use. Each project alone is a substantial development. Together, they represent the kind of category breadth that most construction software was not built to coordinate at the program level.
The team came to Jet.Build with a question that few platforms could credibly answer. Can a single operating platform actually carry this much category diversity without forcing each category into a one-size-fits-all template that compromises the work?
The Approach
Kushner deployed Jet.Build as the unified operating platform across the firm's active development portfolio. The migration followed the rapid deployment pattern documented in our Switching Platforms Playbook. Active projects continued through the migration. The team went live within the standard deployment timeline.
The structural insight that made the deployment work is worth naming directly: a unified platform does not require uniform workflows.
Each asset category continued to be executed in the way that category demanded. Mixed-use components ran with the cadence and stakeholder coordination that mixed-use development requires. Residential community work operated with the trade coordination, infrastructure sequencing, and lifecycle thinking that residential at scale demands. Hospitality and lifestyle development operated with the FF&E coordination, brand-standard alignment, and operational handoff requirements that distinguish hospitality from the rest of the portfolio. The platform did not flatten these distinctions. It accommodated them.
What the platform unified was the operational layer underneath the category-specific execution.
Schedule, budget, document control, change order workflows, and capital partner reporting all run on the same platform across every component of the active portfolio. The development team can see all four anchor projects, in real time, across all four asset categories, on a single dashboard. Jenny — Jet.Build's built-in AI assistant handles the synthesis work that previously required senior team members to reconcile manually across systems. Questions like "Show me every change order over $250,000 across the active portfolio, regardless of asset category, with originating decision and current approval status," return answers in seconds rather than triggering a multi-day reconciliation effort.
Capital partner reporting compresses dramatically as a result. Partners with exposure to specific projects receive reporting tailored to those projects. Partners with exposure across the portfolio see the rollup. Partners on hospitality components see the FF&E and operational handoff dimension that matters to them; partners on mixed-use components see the schedule and cost dimensions that matter most for their structures. The platform produces all of this from a single underlying truth rather than requiring the development team to assemble each report individually.
The result is a portfolio that operates with category-specific rigor at the project level and program-wide visibility at the portfolio level — a combination that disconnected systems structurally cannot produce.
The Outcome
The development team's first observations after migration matched the patterns we now see consistently across multi-category developers operating on Jet.Build.
Portfolio-wide visibility became continuous across asset categories. The senior development team can see every active project across mixed-use, residential, hospitality, and lifestyle work in real time, on a single dashboard, without anyone having to assemble the view manually. The category diversity that previously compounded the operational tax became a structural advantage — the platform handles the diversity natively.
Category-specific execution remained uncompromised. Each asset category continues to be executed in the way that category requires. Mixed-use cadence remained mixed-use cadence. Residential community work remained residential community work. The platform's role was structural rather than constraining — visibility across the portfolio without flattening the distinct operational tempo each category requires at the project level.
Capital partner reporting compressed dramatically. Partners with different exposure profiles across the portfolio receive reporting tailored to their specific positions, generated from the same underlying truth. The synthesis work that previously consumed substantial senior team bandwidth became continuous and automatic. Partner relationships have strengthened across the portfolio as a result.
Senior team time shifted toward strategic work. Hours that previously went to reconciliation across category-specific systems moved to the strategic decisions that determine how a multi-category developer continues to grow. Pre-acquisition diligence accelerated. Capital relationship cultivation deepened. The bandwidth the firm had wanted to invest in strategic work for years suddenly existed.
In Their Words
Running mixed-use, residential, hospitality, and lifestyle development under the same roof creates an operational complexity that most construction technology was not designed for. We had been running these categories on systems that did not talk to each other, and the translation work between them was eating our senior team's bandwidth. Jet.Build let us unify the operating layer without flattening how each category actually needs to be executed. Mixed-use still runs the way mixed-use needs to run. Hospitality still runs the way hospitality needs to run. But the portfolio-level visibility now exists where it never could before. The capital partner conversations have changed. The growth math finally works the way the diversification was always supposed to allow.
— Senior Development Leader, Kushner
What This Validates
The Kushner engagement validates a pattern that should matter to every owner-developer running multi-category portfolios — and to the GCs and specialty contractors who execute on them.
Multi-category portfolios do not need to fragment across siloed category-specific systems. The visibility that program-level operators require can coexist with the category-specific operational rigor that mixed-use, residential, hospitality, and lifestyle development each independently require. The architectural assumption that has historically forced this tradeoff — that construction software is fundamentally category-aligned rather than portfolio-scaled — is no longer required. Modern unified platforms now operate across category boundaries natively, with category-specific execution unconstrained underneath.
The strategic framework underlying this shift is documented in detail in our Real Estate Development Operating System playbook. The Kushner engagement demonstrates the framework executing across one of the most operationally diverse development portfolios in the market.
For owner-developers running multi-category programs — whether the diversification spans residential and commercial, mixed-use and hospitality, urban and suburban, or any other combination of asset types — the Kushner outcome offers a clear reference point. The operational tax of running categories on disconnected systems is real. The platform shift recovers it. The capital partner dynamics strengthen across exposure profiles. The portfolio capacity expands without proportional operational growth.
Multi-category portfolios deserve a single operating layer. Kushner demonstrates what that looks like in execution.
Kushner is a national real estate developer with a portfolio spanning mixed-use, residential, hospitality, and lifestyle development. The active portfolio includes Monmouth Square (1.5M SF), Colts Neck Manor (1.74M SF), Wave Spa (175K SF), and Lower Broadway (223K SF). The firm runs its development portfolio on Jet.Build as the unified operating platform.