The Foundational Engagement

Who is this place for? What exactly is the programming that will make it successful? And who is the right operator to steward it and service the end customer?

These are not design questions. They are not marketing questions. They are pre-development questions, and they need to be resolved before anyone picks up a pencil — because the brief can only be as good as the strategic clarity behind it.

The Foundation Engagement covers the full pre-development process, from first principles to consultant team in place. It runs in three sequential phases, each one building directly on the last.

Phase 1 — Place and Program Strategy

Before the brief can be written, the project needs a clear identity grounded in what makes this site, this market, and this moment distinct. This phase establishes the strategic foundation: an analysis of the site's ecosystem and competitive context, a definition of the target buyer and the emotional experience the project is selling, and an experience master plan that describes the programming and day-in-the-life of the property before any architecture is committed to. Where deeper research or brand development work is required — buyer segmentation studies, visual language development, investor positioning — I scope and manage those specialist engagements on the developer's behalf, integrating their output into the next phase rather than treating them as a separate workstream.

The output of Phase 1 is a clear, defensible answer to the question every consultant will ask and most developers can't answer cleanly: what are we actually building, and why will someone pay for it?

Phase 2 — Development Brief

With Phase 1 complete, I author the development brief: the document that translates strategic intent into development requirements. This is the brief the architect works from, not the one they write for you. It articulates project identity, target guest profile, experience priorities, operational requirements, and the design constraints that should be non-negotiable versus those that are open to interpretation. It is the single document every consultant should be able to point to when a decision needs to be tested against original intent — which means it needs to be precise enough to hold them accountable and flexible enough to survive a multi-year design process.

Phase 3 — Operator Selection and Consultant Assembly

With the brief as the filter, I conduct a structured operator evaluation: long list to short list to recommended selection, with supporting rationale tied explicitly to the brief and the project's positioning. Most operator decisions are made relationally, based on who the developer knows or who approaches them first. A brief-led selection process produces a fundamentally different result — one where the operator is chosen because they are the right steward of this specific project, not because the conversation happened to start with them.

Finally, I assemble the consultant team: architect, interiors, landscape, and any specialty consultants the project requires. Evaluated against the brief, not by reputation alone.

The result is a project that enters design with a clear identity, a brief the whole team is accountable to, the right operator aligned before the wrong commitments are made, and a consultant team selected to execute the actual vision.