From brief to launch, without the chase

An operating model for how Shamal takes a project from idea to open, and the team that builds it with you and runs the doing.
Prepared for Donna Glasper · Shamal  |  25 August 2026  |  A concept for discussion
What we heard

The work is not the problem. The absence of a shared path is.

THE BRIEF from the CEO by phone a different version each by WhatsApp Development Asset management Brand and marketing BROUGHT IN LAST × ×
Three teams. Three versions. No shared view.
You know how to tackle the problem. What is missing is the room to do it.
The route every project follows

One critical path, from feasibility to launch

The same formula, written down once, with brand and positioning brought to the front where the value of a project is actually decided.
01
Feasibility
How much can it make, what will it cost, can we afford it. Brand joins here, not at the end, to shape who we build for and where the price point comes from.
02
Concept
The idea takes shape. Positioning, buyer research and new revenue streams are set now, while they can still change the plan.
03
Design
Architecture and detailed design, briefed against a positioning that is already agreed. Fewer loops back to the drawing board.
04
Develop
Contractors appointed, build underway. Every team works to the same brief, visible to all, with no separate WhatsApp version.
05
Launch
Marketing, brand and comms deliver against a plan set months earlier, not handed a finished thing to sell.
How it works

Three layers, built to sit together

A path to follow, a rhythm to run it, and an intelligent layer that answers questions and does the work.
Layer 1
The critical path
One stage-gated route every project follows. At each gate, the deliverables and the person who owns them, across development, asset management, brand and marketing, HR and legal. The formula is written down once, so no project starts from a blank page and brand sits at the front where the value is set.
Layer 2
Agile ways of working, on top
The cadence that made the Naia launch work, made standard. A scrum rota, sprint planning and short stand-ups that move work rather than report on it. Development and asset management work inside the same rhythm, not shoehorned in beside it.
Layer 3
The intelligent layer
One place leadership can ask questions of. Abdullah or Sudhin ask where a project stands and what is at risk, and get an answer. You pull positioning status without chasing three teams. And it does the doing: it drafts the naming rationale in Arabic, the appointment announcement, the signage brief, the deck, and places each in your drafts for a yes or a no. Approvals in a tap, not a group chat.
Why this is possible now

The technology quietly crossed a line

Until recently, software could track work but not do it. That has changed. AI agents can now read a brief, apply the rules of a stage gate, produce the work that follows, a draft, a naming rationale, a status update, and place it in front of the person who approves it. They push that status into the tools your teams already use, then wait for a yes or a no.

This is the shift that turns a project tracker into something that carries the work forward. We build on the current generation of these systems, chosen for security and fit, and kept current as they improve. The value is not the tool. It is the judgement of what to automate, where a person must stay in the loop, and how the whole thing serves the decision at hand.

What makes this different

Deep Hospitality does the doing

You do not need another framework handed over and left on a shelf. The principle you liked in the room applies to us too. We do the doing, not just the advising.
We map it
We build the critical path and the roles with your teams, from your real projects, not a template off a shelf.
We install it
We stand up the agile cadence with the people who need it, and coach it until it holds on its own.
We build it
We build the intelligent layer on Shamal's own data, with the widgets and views each leader wants to see.
We run it
We run it alongside you through the first project, so it is working before we step back, not a slide you are left to implement.
Our approach

Prove it by hand, then automate it

We do not begin by automating. We make the model work on paper first, prove it on a real project, then let the technology run it from end to end.
1
The model
On paper
The critical path and agile ways of working, designed and run by people.
2
The prototype
Naia
We ran the model by hand on the Naia launch. It held together where the usual way did not.
Proven
3
Automated
End to end
The agents now run the doing and the reporting. The same model, without the chase.
This is not a first attempt. It is the automation of something that already works.
Where we start

One project, a working model in weeks

We prove it on a single live project, Naia or Kite Beach, rather than a company-wide programme on paper. A model you can see and use, not a deck.
01Map the path. We map the project's full critical path and the roles at each gate, with the teams involved.
02Install the cadence. We stand up the agile rhythm, scrum rota, sprint planning and stand-ups, across development, asset management and brand.
03Build the board. We build the queryable view on the project's own data, with the widgets each leader wants.
04Ship the first doing. The naming rationale, an announcement draft, a status Abdullah can ask questions of. Real output, not a demo.
What changes for you

The result

Brand at the front
You are in the brief, shaping the buyer and the price point, on every project.
Strategic time back
The admin of updating, chasing and typing is done for you. Your brain is on the problem.
Leadership self-serves
Abdullah and Sudhin ask the board directly. No status meeting to prepare, no archaeology.
A path that repeats
Every future project inherits the same route, so the model compounds instead of resetting.
Why Deep Hospitality
Selected work
Deep Hospitality is already putting AI to work inside hospitality operators, including Aman Hotels and Resorts and Aleph Hospitality, on real operational problems rather than pilots for their own sake.
Proven with you

We already ran agile ways of working on the Naia launch, and it worked. This makes that repeatable.

Operating depth

Twenty-five years each across hospitality and real estate. We know how the teams actually work, and where the friction sits.

The doing, built in

The AI capability you saw in the room, applied to your own workflow, so the busy work is done rather than described.

Next step: a short working session with Donna to choose the pilot and lock its path

This is the first step of the discovery phase. Ninety minutes to pick the project and agree the critical path. Then Deep Hospitality builds. Investment is shaped to the pilot scope and shared once the project is agreed.

Caroline Hardman & Nitin Thariyan · Deep Hospitality
+971 56 537 2122