Omay Partners

Process

"One team, from first sketch to handover" is the core of how we work — this page explains what that actually means in practice: the stages a project moves through, who is accountable for what, and why keeping design and delivery under one roof changes the outcome.

The stages

  1. 01

    Brief

    We listen first — your goals, your users, your constraints, your budget and timeline. This stage ends with a written brief we both sign off on before any design starts.

  2. 02

    Concept

    Early spatial ideas and options, tested against the brief. You approve a single direction before we take it further.

  3. 03

    Design Development

    The concept resolved into real materials, finishes, systems and costs — the point where a design becomes something that can actually be built, and priced.

  4. 04

    Construction Documents

    Detailed drawings and specifications, sufficient for accurate pricing and for permitting.

  5. 05

    Construction / Fit-Out

    We build it — either directly, or as project manager coordinating contractors you already trust. Either way, the same team that designed it stays on site through delivery.

  6. 06

    Handover

    Snagging, as-built documentation, and a walkthrough before you move in.

Who holds the contract

Depending on the project, we hold either a single design-and-build contract, or act as project manager coordinating contractors you already trust. Either way, the same team is accountable from the first sketch through handover — there is no separate design firm to hand off to, and no separate contractor to hand off from.

Why one team matters

When design and construction sit with two separate firms, a gap opens between them — the architect points at the contractor for poor execution, the contractor points at the architect for impractical drawings, and the client is left in the middle resolving a dispute that isn't theirs to resolve. Keeping one team responsible for both closes that gap: the people who drew it are the same people responsible for building it, so problems get solved on site, not argued over in correspondence.

What we need from you