Inside The Cube: A Project Viability Case Study

Before any major development moves forward, it must pass through rigorous viability analysis, a structured assessment of whether a proposed project makes financial, operational, and strategic sense given available information about market demand, construction costs, and realistic return expectations. The Cube, Apavou Group’s mixed-use development, offers a useful case study in what this kind of project viability analysis actually involves for a complex, multi-functional development.

Defining the viability question precisely

Project viability analysis begins by precisely defining the question being asked, not simply “will this project make money,” but more specific questions like “does this project generate returns that justify its risk relative to alternative uses of the same capital,” and “does this project’s specific risk profile fit within the broader portfolio’s risk tolerance.” For a mixed-use project like The Cube, this required disaggregating the viability question into components for each functional element- office, retail, shared infrastructure- since each carries distinct demand drivers, cost structures, and risk profiles that don’t necessarily move together. Precisely specifying the question in this way, rather than pursuing a vaguer, more generalised notion of “project success,” makes the subsequent analysis both more rigorous and considerably easier to act on once the results are in hand.

This disaggregated approach to defining viability is more analytically demanding than assessing a single-use project, but it produces a more accurate picture of where a project’s genuine risks and value drivers actually lie, rather than relying on a single blended return figure that might mask significant variation in performance across different components of the same development.

Demand-side analysis across multiple use categories

Viability analysis for The Cube required separately validating demand for office space and retail space within the specific catchment area the project would serve, a more complex exercise than validating demand for a single asset type, since office and retail demand respond to different underlying economic drivers (business formation and employment growth for office demand, versus population, tourism, and consumer spending patterns for retail demand).

This demand-side analysis typically draws on a combination of macro-level indicators (broader economic growth projections, employment trends) and more granular, comparable-project analysis (how similar mixed-use developments have performed in Mauritius or comparable regional markets), triangulating between these different sources of evidence to arrive at demand assumptions robust enough to support a major capital commitment decision.

Establishing the analytical team’s independence from project advocacy

A subtle but important element of rigorous viability analysis involves ensuring some degree of independence between the team conducting the analysis and the team advocating for the project’s approval. When the same individuals who conceived a project and are most enthusiastic about its potential are also solely responsible for validating its viability, there is a natural risk that optimism bias creeps into the underlying assumptions, even without any deliberate intent to mislead. Building in some structural separation, whether through an internal team with a distinct reporting line, external advisory review, or simply a formal requirement that key assumptions be validated by parties without a direct stake in the project’s approval, helps counteract this natural bias and produces a viability analysis more likely to reflect genuine market conditions rather than the enthusiasm of the project’s original champions.

Cost-side analysis and construction risk assessment

On the cost side, viability analysis for a mixed-use project must account for the specific construction complexities inherent in combining multiple functions within a single structure, the more sophisticated building systems required to serve differentiated tenant needs, the more complex vertical circulation required to manage distinct traffic patterns for office and retail visitors, and the coordination overhead associated with managing multiple, functionally distinct construction workstreams simultaneously.

This cost analysis needs to account not just for a base-case construction budget, but for realistic contingency reserves informed by how actual construction costs have historically deviated from initial projections on comparable projects, a particularly important consideration in the Mauritian context given the island’s dependence on imported construction materials and the associated exposure to supply chain and shipping cost volatility.

Sensitivity analysis and stress testing

Robust viability analysis doesn’t rely on a single base-case projection; it tests how a project’s returns would be affected under a range of less favourable scenarios: slower-than-expected leasing, higher-than-projected construction costs, or a broader economic downturn affecting both office and retail demand simultaneously. This sensitivity analysis helps identify which specific assumptions a project’s viability is most dependent on, allowing developers to focus risk mitigation efforts on the factors that matter most, rather than spreading attention evenly across every assumption regardless of its actual importance to the project’s overall viability.

For The Cube, this stress testing likely included scenarios examining what happens if either the office or retail component underperforms significantly relative to projections, testing whether the overall project retains adequate viability even if one functional component falls meaningfully short of its individual target, given that shared infrastructure costs are borne across both components regardless of how each performs individually.

Accounting for the option value of phased commitment

Sophisticated viability analysis sometimes incorporates the concept of option value, recognising that committing to a project in phases, with defined decision points at which the project can be scaled up, modified, or halted based on how initial assumptions are validated by actual market response, carries a different risk profile than committing fully to a fixed design and scale from the outset. For a project as complex as The Cube, structuring at least some elements of the development with this kind of phased optionality, even if the overall vision remains fixed, can meaningfully reduce the downside risk associated with committing fully to assumptions that later prove overly optimistic, while still preserving the ability to capture the full upside if those assumptions prove accurate. This approach requires more sophisticated planning during the design phase, since the physical structure needs to accommodate this kind of phased flexibility without compromising the overall coherence and functionality of the finished development, but the resulting risk reduction is often well worth this additional planning complexity for a project of significant scale.

Accounting for interdependency between components in the viability model

A distinct challenge for mixed-use viability analysis, beyond simply disaggregating assumptions by component, involves modelling the genuine interdependencies between those components; the office component’s employees represent a captive lunchtime and after-work customer base for the retail component, for instance, while the retail component’s amenities can serve as a genuine differentiator supporting office leasing in a competitive market. Purely siloed viability analysis, which evaluates each component in complete isolation, risks understating the genuine value created by these interdependencies, just as it risks overstating individual component viability if the interdependencies assumed don’t actually materialise as expected once the project is operational.

Modelling these interdependencies accurately requires judgment informed by how comparable mixed-use developments have actually performed, since the theoretical case for functional synergy between office and retail components doesn’t always translate into the assumed real-world benefit, particularly if the specific tenant mix or physical layout doesn’t genuinely encourage the cross-visitation that the synergy case depends upon.

Timing viability analysis against evolving market conditions

Because major projects like The Cube typically take years to move from initial viability analysis to actual construction completion, the original analysis needs to explicitly account for how market conditions might reasonably evolve over that intervening period, rather than assuming that conditions prevailing at the time of the original analysis will remain static throughout the project’s development. This might involve building in explicit assumptions about how office and retail demand are likely to trend over the following several years, informed by broader economic forecasts and observable trends already underway, rather than simply extrapolating current conditions indefinitely into the future.

Involving operational expertise early in the viability process

A frequently underutilised source of insight in viability analysis is the operational team that will eventually be responsible for managing the completed asset, property managers and leasing specialists whose day-to-day experience with how similar buildings actually perform once operational often surfaces practical considerations that purely financial or design-focused analysis might overlook. Involving this operational perspective early in the viability process, rather than treating operational management as a consideration only relevant once construction is complete, helps ground the viability analysis in realistic assumptions about how the completed project will actually be used and managed, rather than purely theoretical projections that may not fully anticipate the practical realities of day-to-day operation.

Comparative benchmarking against alternative capital uses

Viability analysis ultimately needs to answer not just “is this project viable in isolation,” but “is this project a better use of available capital than realistic alternatives”, whether that alternative is a different type of development, a different location, or simply maintaining capital in reserve for future opportunities. This comparative benchmarking requires maintaining a consistent analytical framework across different potential projects, allowing genuinely comparable evaluation rather than each project being assessed against a different, potentially inconsistent set of standards.

Translating viability analysis into go/no-go decisions

Ultimately, viability analysis needs to translate into a clear decision: proceed, decline, or proceed with modifications that address identified concerns. This translation requires defined decision criteria established before the analysis begins, reducing the risk that a compelling narrative or strong initial enthusiasm for a project overrides what the underlying analysis actually indicates about genuine viability.

What The Cube’s viability case study offers other developers

Studying how a project like The Cube likely moved through viability analysis offers several transferable lessons:

Disaggregate viability analysis by functional component for any mixed-use project, rather than relying on a single blended assessment.

Triangulate demand assumptions using multiple, independent sources of evidence rather than a single data source.

Size contingency reserves based on actual historical cost and schedule variance, not optimistic best-case assumptions.

Stress test assumptions individually to identify which specific factors viability is most sensitive to.

Maintain consistent evaluation criteria across different potential projects to enable genuine comparative benchmarking.

Conclusion

The viability analysis underlying a project like The Cube illustrates the depth of rigour required before committing significant capital to a complex, multi-functional development. Precisely defined viability questions, disaggregated demand and cost analysis, robust sensitivity testing, and consistent comparative benchmarking together provide the analytical foundation that separates disciplined development decision-making from the kind of optimistic, insufficiently tested assumptions that too often underlie failed development projects.