Lessons from the first three months

Aleph programme, July to September 2026. Prepared 1 October 2026 for the progress sitting. Every quotation below is copied exactly from a filed transcript or from an email in the mailbox, with its line number or its date. Transcripts are automatic, so names are sometimes misspelt in the quotes; they are left as they appear.

The agreement

The PDF is not on this page. It is on the Deep Hospitality SharePoint, in the Aleph folder under 08_Admin_Contracts.

Letter from Aleph dated 14 July 2026, signed by Nitin on 24 July 2026. Pages 1 to 4 are the letter. Pages 5 to 11 are Appendix A, our proposal of 2 July, which the letter makes the description of the services.

What it saysWhy it matters on Monday
Agreement: “They run one at a time.” The agreement, page 7
Three modules have run side by side since 4 August.
Agreement: “Two builds running at once is a second lane at the second-lane rate, never quiet pressure on this one.” The agreement, page 9
The agreement prices a second lane at AED 55,000 a month and three at AED 75,000 (page 11). We have invoiced AED 52,500 a month.
Agreement: “It is included with our compliments” The agreement, page 10
The half-day AI session for the leadership team is in the agreement. It has not been held.
Agreement: “Three one-to-one discovery conversations, thirty minutes each, week of 6 July.” The agreement, page 11
Listed as a next step. They did not happen; the kickoff on 8 July stood in for them.
Agreement: “restructured into one tagged, searchable library, tailored by brand tier” The agreement, page 7
Module 2 in the agreement is the whole library, which is Bani's picture. Jad narrowed it to two hotels on 6 July.
Agreement: “with SharePoint as the natural home; on any other platform we interface with an external service provider and that cost is passed through to Aleph” The agreement, page 7
The agreement assumed Microsoft. Aleph chose to stay on Google on 2 September, so an outside builder at Aleph's cost is what the agreement provides.
Agreement: “One page, agreed in minutes before the build starts” The agreement, page 9
Our own promise on charters. See the lessons for us.
Agreement: “monthly steering one-pager to the three of you. Five minutes of reading” The agreement, page 9
Our own promise on reporting. See the lessons for us.
Agreement: “initial term of three (3) months and shall continue thereafter on a rolling monthly basis” The agreement, page 2
The initial term ran from 3 July and ended on 3 October. From now either side can end it on 30 days' written notice (page 3).
Agreement: “invoiced monthly in arrears” The agreement, page 2
Payable within 30 days of a valid invoice.
Agreement: “including configured bots, prompts, restructured SOP content and drafted agreements, shall vest in and belong to the Company” The agreement, page 2
Clause 8.1. What we configure for Aleph is Aleph's. Clause 8.2 keeps our method and know-how with us.

Check before Monday. The copy on file carries your signature dated 24 July. The line for Bani Haddad on page 4 is blank. If a copy signed by Aleph exists, it is not in the folder.

1. How long each ask waited

Counted to the sitting on 5 October where still open.

What we asked forAskedAnsweredDaysStrength
The choice of template7 Aug, emailOpen59Solid
A named person to run the standards engine21 Jul on a call; 6 Aug in writing2 Sep27Solid
The Claude licence6 Aug, emailApproved 6 Sep; first training 29 Sep54Use with care
A dedicated sitting on the Business ReviewAgreed 2 Sep5 Oct, still to confirm33Solid
A sponsor for the intranet4 Aug, charter2 Sep29Solid
One trial balance5 Aug, emailOpen61Weak
Yes to the BIRD trial, and the Fairmas questions23 Sep, emailOpen12Use with care
Whether the portfolio work should be scoped6 Aug, emailOpen60Solid
July invoiceDue 23 AugPaid 16 Sep24Solid

2. The record, item by item

Click a line to open it. Green quotes are from recordings. Dark quotes are from emails. Amber quotes are from the agreement.

1The template was asked for on 7 August and has not been chosenSolid

What we advised or asked

Nitin to Satish, Rohit and Jad, copying Caroline: “All three templates carry the same content, the same automation and the same Aleph look: the choice is yours.” Email, 7 Aug 2026, 00:24 Dubai, "Your BRM template, drawn: one real month, three ways"
Same email: “Next steps once you have picked your template: we fold your notes into one consensus version; write and lock the master contents list with Rohit and Satish; stand up the folder pattern and choose the pilot property; shadow-run the September cycle alongside the real one; go live in October.” Same email

What happened

Jad: “Re the below email, I eill review by tomorrow COB as I am on intense travels in East Africa this week.” Email, 13 Aug 2026, 19:17 Dubai

We chased on 10 August, 18 August and 23 September. No choice has come back.

Neil (by content): “Aleph has a BRM format that we have determined is the appropriate BRM format, and that's what everybody gets.” Neil's call, 3 Sep, line 286
Jad: “I said probably by end of September.” Jad catch-up, 23 Sep, line 245
Jad: “I can't really wait too long.” Jad catch-up, 23 Sep, line 251

What it cost

The September owner review cannot go out in the new format. Jad had told owners to expect it by the end of September. Our 7 August plan was a trial run in September and live in October; both depended on the choice.

How to say it

The three templates have been with the team since 7 August. On 3 September Neil asked for one format for everyone. We need that one choice today, and the owners get it for the next cycle.

Where it is soft

  • Satish and Rohit were both on leave for part of August.
  • After Neil's ruling we said the three would be folded into one at the dedicated sitting. That sitting was not held, and we did not produce the single version ourselves.
  • Jad was a recipient of the 7 August email; on 23 September he asked who had the templates.
2The engine waited for a named person and a licenceUse with care

What we advised or asked

Nitin, 21 Jul: “if it's Fiona, then we'll work with Fiona. But if it's someone on property, we'll work with whoever's on property.” Standards scoping, 21 Jul, line 158
Caroline to Bani, Fiona and Abdellah, copying Jad, Neil and Nitin: “A name. One person, nominated by you, who we train to run the method.” Email, 6 Aug 2026, "Aleph SOP Engine - hand over & next steps"
Same email: “The licence. Claude seat/s (at least one Claude Max Plan allowing for 20x more usage than Pro), already agreed in principle.” Same email

What happened

Jad, 21 Jul: “So I'm not gonna rush. I'll wait.” Standards scoping, 21 Jul, line 212
Bani: “We will discuss internally and get back to you in the next couple of days” Email, 7 Aug 2026, 12:26 Dubai
Fiona, 2 Sep: “we could do this. So one can do the mechanics, one can do the reading” Project Update No. 2, 2 Sep, line 383
Jad: “Apologies for the late reply. Let us proceed with 2 seats at the suggested price range of $20-30 per motnh per seat.” Email, 6 Sep 2026, 19:33 Dubai

Seats were bought by 22 September. First training was 29 September.

What it cost

27 days from the written ask to a name, and 54 days to the first training. The owner date of end November was set by Aleph, not by us:

Abdellah (by content), 4 Aug: “So our deadline is end of November to to have everything in place, all categories.” Engine shown to Bani, 4 Aug, line 458

How to say it

We asked for a name and a licence on 6 August. The name came on 2 September and the first training was 29 September. That is seven weeks of the runway to November. Since then Fiona and Annette have moved fast.

Where it is soft

  • Do not say they chose the cheaper seat. Our 6 August email asked for at least one Max plan. Our own 3 September email then told Jad to buy the Team plan at about USD 20 to 30 a seat, and he approved exactly that.
  • Do not say we told them to appoint someone at the hotel. The 6 August email says only “one person, nominated by you”. The training manager was Abdellah's idea. On 2 September we said:
    Nitin: “It's not my gift to give, but it's entirely up to you all.” Project Update No. 2, 2 Sep, line 368
    and welcomed the outcome:
    Nitin: “The important thing is we have two named individuals, which is fantastic.” Project Update No. 2, 2 Sep, line 398
  • Part of September was our own rebuild of the engine (three versions between 31 August and 21 September).
  • On 3 September Caroline wrote that November stayed “comfortably in reach”. On 22 September we called it a stretch.
3The standards work was set to two hotels by Jad, and we flagged the portfolio in writingSolid

What we advised or asked

Jad, 6 Jul: “that's the urgent part of the SOP project. I want to fulfill that important owner need.” Call with Jad, 6 Jul, line 56
Fiona (by content), 17 Jul: “are we writing a luxury generic SOP, or we really only just customizing for these two properties?” Programme review, 17 Jul, line 227
Jad: “Customizing.” Programme review, 17 Jul, line 230
Nitin, 4 Aug: “definitely I would scope that separately” Engine shown to Bani, 4 Aug, line 515
Caroline to Bani, Fiona and Abdellah, copying Jad and Neil: “Each deserves to be scoped as its own piece of work rather than absorbed quietly into this one, and we would be glad to have those conversations whenever you are ready.” Email, 6 Aug 2026

What happened

Bani, 4 Aug: “most important is not these two properties, the portfolio and us how we build something sustainable for the entire company.” Engine shown to Bani, 4 Aug, line 296
Bani, 4 Aug: “that's the objective is to build the factory.” Engine shown to Bani, 4 Aug, line 362
Marc Matar (by content), 24 Jul: “So what I'm asking today is to add it on the scope, please” Food and beverage session, 24 Jul, line 368
Bani, 2 Sep: “Why are we building two engines?” Project Update No. 2, 2 Sep, line 278

Bani replied on 7 August that they would discuss internally and come back in a couple of days. Nothing came back on the portfolio question.

What it cost

The three principals have held different pictures of this module since July. The agreement describes the whole library:

Agreement: “restructured into one tagged, searchable library, tailored by brand tier” The agreement, page 7
Two hotels were Jad's instruction on 6 July; the whole company is Bani's aim. Nobody has asked us to scope the second.

How to say it

The two hotels were the urgent ask in July and that is what the charter says. On 6 August we offered to scope the wider portfolio as its own piece of work. We are ready to do that now.

Where it is soft

  • Nitin, 4 Aug: “Yes, we want to give you a Ferrari factory. That's the charter.” Engine shown to Bani, 4 Aug, line 359
    Bani can fairly have heard that as a factory for the whole company.
  • Caroline, 2 Sep: “that would be a different engine” Project Update No. 2, 2 Sep, line 275
    That sits awkwardly beside the factory line.
  • The group-wide proposal we promised on 4 August has not been written.
  • What we are building for the two hotels is not what Module 2 in the agreement describes. The change sits in our charter of 25 July, which nobody at Aleph signed.
4The Business Review sitting agreed on 2 September took five weeks to happenSolid

What we advised or asked

On 2 September the hour ran out before the Business Review. Bani's ruling in the room:

Bani: “I suggest we split the call” Project Update No. 2, 2 Sep, line 806

What happened

It was not scheduled. On 24 September Neil asked for an in-person update. Zhaira's first slot for all three was 5 October.

Neil: “Let's schedule an in-person catch up please. Bani, Jad and I could use a full progress update on what has actually been achieved thus far, agree timelines and what next priorities should be.” Email, 24 Sep 2026, 08:33 Dubai

What it cost

33 days in which the template choice, the trial and the Fairmas question had no room to be decided.

How to say it

On 2 September we agreed the Business Review needed its own sitting. This is that sitting. Three decisions have been waiting for it.

Where it is soft

  • The 8 September session did cover the Business Review and BIRD with all three in the room, so “nothing was held” overstates it.
  • We asked Zhaira once on 3 September and did not press.
5We advised one connected place for the data; the decision is still openUse with care

What we advised or asked

Nitin, 6 Aug: “Maybe I'll just introduce you all to Rudolf” Rohit and Satish, 6 Aug, line 557
Nitin, 8 Sep: “The idea is to actually bring it to one place as much as possible” Regional Vice Presidents session, 8 Sep, line 326
Nitin and Caroline to Bani, Neil and Jad: “To achieve what you have asked for, the data needs to sit in one place that an AI such as Claude/Codex can access. A dashboard alone will not achieve this.” Email, 22 Sep 2026, 19:13 Dubai
Nitin to Neil, copying Bani, Jad, Satish and Rohit, five asks: “Neil: a yes in principle to the pilot.” Email, 23 Sep 2026, 22:24 Dubai, "Business Review: the way forward"

What happened

Rohit, 6 Aug: “let's wait for what we can do with Fairmas” Rohit and Satish, 6 Aug, line 566
Neil, 8 Sep: “Fairmas, we already have. We're in it.” Regional Vice Presidents session, 8 Sep, line 335
Bani, 8 Sep: “it does not resolve the BRM for me” Regional Vice Presidents session, 8 Sep, line 365
Jad, 23 Sep: “Let me let me check the commercial terms and the the termination terms as well.” Jad catch-up, 23 Sep, line 143

None of the five asks of 23 September has been answered. The Fairmas cost and contract were asked again on 1 October.

What it cost

The automated review and the alerts Bani asked for both need the data in one place. Until Aleph decides how Fairmas and BIRD sit together, neither can be built.

How to say it

We are not asking you to replace Fairmas. We proposed keeping it and adding one view above it, and Rudolf has offered the trial free. We need a yes or a no, and two numbers from finance.

Where it is soft

  • BIRD was our introduction, made after Rohit had said to wait. The Fairmas or BIRD question now holds the work up, and it can be laid at our door.
  • Our position moved: on 6 August no data platform was needed; by 23 September nothing could be done without one.
  • We have told Aleph three times that we have no commercial interest in BIRD. The partnership conversation with Rudolf must be settled before that line is tested.
  • Do not carry Rudolf's remarks about Fairmas into the room.
6The Business Review brief grew five times, each time at Aleph's requestSolid

What we advised or asked

These were not advice ignored. They are why the date moved, and each is on tape.

What happened

Bani, 8 Jul: “the priority is not the time, the priority is the actual content, and the second priority is the time.” Kickoff, 8 Jul, line 194
Bani, 17 Jul: “I'm wondering if it's not worth also selecting two or three hotel owners and talking to them as well.” Programme review, 17 Jul, line 212
Jad, 6 Aug: “This is for your kind consideration as we need t report a slide on marketing in the BRM.” Email, 6 Aug 2026, "FW: Monthly Reporting Marketing Slides"
Neil (by content), 3 Sep: “that's what everybody gets.” Neil's call, 3 Sep, line 286
Bani, 8 Sep: “What should be the action in the next 3060, 90 days for the GM?” Regional Vice Presidents session, 8 Sep, line 587

What it cost

Two months on the Business Review. Owner conversations alone ran from 17 July to 31 August, because the introductions needed Bani's own chase on 7 August.

How to say it

The brief in July was to cut the time. Since then it has become better content, owner input, marketing, one format and action plans. Each was the right call, and each added weeks.

Where it is soft

  • The corporate team asked for one uniform template on 6 August, so one format is not new on 3 September.
  • Alerts and correlations were Bani's ask from the start. Do not present them as late additions.
  • We welcomed each addition in the room and did not say what it would cost in time.
7The intranet had no sponsor for a month and an earlier build that Neil called unusableUse with care

What we advised or asked

Our charter of 4 August named Jad as the expected sponsor, to be confirmed. We asked again in the room on 2 September.

Nitin, 2 Sep: “If we if we can have a point person amongst y'all who we can work with a little more closely, like a sponsor, that would be fantastic.” Project Update No. 2, 2 Sep, line 770

What happened

Neil, 2 Sep: “I'm happy to be the point person for the internet.” Project Update No. 2, 2 Sep, line 782
Neil (by content), 3 Sep: “We built something that is unusable.” Neil's call, 3 Sep, line 215
Neil (by content), 3 Sep: “let's start from scratch because we haven't done anything on it yet.” Neil's call, 3 Sep, line 59
Neil, 2 Sep: “the preference is to remain on Google where we are” Project Update No. 2, 2 Sep, line 752
Aline, 1 Oct: “I was a bit confused of who's leading the project.” Aline and Estelle, 1 Oct, line 749

What it cost

29 days without a sponsor. The module started from nothing in September, with a supplier already paid a deposit and no usable build.

How to say it

The intranet got its sponsor on 2 September. Neil told us the next day the earlier build could not be used. Since then we have the scope written and HR's needs in it. Today we need the route.

Where it is soft

  • Do not say they rejected SharePoint. Nobody did. Say what the agreement says:
    Agreement: “with SharePoint as the natural home; on any other platform we interface with an external service provider and that cost is passed through to Aleph” The agreement, page 7
    Aleph chose to stay on Google on 2 September. An outside builder at Aleph's cost is what the agreement provides, and that is the route now being priced.
  • Do not say Bani asked for HTML. The word was ours first:
    Nitin, 2 Sep: “these are basically HTML renderings.” Project Update No. 2, 2 Sep, line 461
  • Do not say they refused the workshop. It was proposed only in the charter, never with a date, and we set the platform ourselves first.
  • Our own position on platform moved several times, ending on 1 October with:
    Nitin: “or with something else. Doesn't matter.” Aline and Estelle, 1 Oct, line 758
  • Neil's remarks on 3 September were made on a private call. Use the substance, not the quotation, and nothing he said about individuals.
  • On 1 October you told HR:
    Nitin: “the intranet is not with us” Aline and Estelle, 1 Oct, line 764
    Neil introduced you on 3 September as leading it.
8The agreement includes a half-day AI session for the leadership team; it has not been heldSolid

What we advised or asked

Agreement: “One combined session, half a day, hands on, built around Aleph's own use cases” The agreement, page 10
Agreement: “It is included with our compliments” The agreement, page 10
Agreement: “Share the deck or outline from your previous AI training” The agreement, page 11
Nitin, 2 Jul: “one of the ways we usually do is we start with an immersion, so we bring the senior leadership team together” Pitch, 2 Jul, line 500
Nitin, 23 Sep: “We should have a half a day workshop using Claude.” Jad catch-up, 23 Sep, line 122

What happened

Bani, 2 Jul: “I don't know if our team requires an immersion on AI” Pitch, 2 Jul, line 521
Jad, 23 Sep: “I'll book half a day and suggest to you sometime.” Jad catch-up, 23 Sep, line 131

Neither session has been held.

What it cost

On 3 September Neil said the three of them left the 2 September meeting confused about what had been achieved. A shared session at the start would have given them the picture.

How to say it

The agreement includes half a day together, at no charge, so everyone can see how this works. We have not held it. I would like to book it today, on your own numbers.

Where it is soft

  • We never put a date to it, and we never received the outline of their earlier training that the agreement asks for.
  • Nobody said “no need”. Bani voiced a doubt and Neil said they had already run a workshop.
  • You conceded it yourself:
    Nitin: “then I'm not going to force it” Pitch, 2 Jul, line 536
  • Do not say they dismissed meeting people. General Manager interviews were approved at once
    Neil, 8 Jul: “Of course.” Kickoff, 8 Jul, line 533
    and the owner conversations and the Rohit and Satish session were Bani's own suggestions. What did not happen is the three one-to-ones in the agreement:
    Agreement: “Three one-to-one discovery conversations, thirty minutes each, week of 6 July.” The agreement, page 11
9The trial balance was asked for once and never arrivedWeak

What we advised or asked

Nitin to Rohit, copying Satish, Bani, Neil, Jad and Caroline: “Could we see one trial balance, for any single property and month? It is the one document that lets us verify a figure rather than only check it for consistency.” Email, 5 Aug 2026, 19:11 Dubai

What happened

Not supplied. Still shown as pending on the data register.

What it cost

Without it we can check that the numbers in a pack agree with each other, but not that they are right.

How to say it

Only if asked what is missing: one trial balance, asked for on 5 August.

Where it is soft

  • We did not raise it on the 6 August call and never chased it.
  • On 11 September we learned Ajnesh handles it; we have not asked him.
10Three modules have run at once on a one-at-a-time fee, and invoices have run lateSolid

What we advised or asked

Agreement: “Two builds running at once is a second lane at the second-lane rate, never quiet pressure on this one.” The agreement, page 9
Agreement: “The single-lane rate does not move with scope; capacity changes only by adding lanes” The agreement, page 11
Jad, 6 Jul: “I am suggesting maybe one and a half or one and 2/3 project at the same time.” Call with Jad, 6 Jul, line 140
Nitin, 6 Jul: “we'll definitely do parallel” Call with Jad, 6 Jul, line 155

What happened

Three modules have been live since 4 August. The agreement prices one lane at AED 35,000 a month, two at AED 55,000 and three at AED 75,000. We have invoiced AED 52,500 a month. The July invoice was due 23 August and paid 16 September. The August invoice was due 25 September and is unpaid.

What it cost

24 days late on the first invoice; 10 days and counting on the second.

How to say it

Only if the fee is questioned: the agreement is one module at a time, with a second lane at AED 55,000 and a third at AED 75,000. We have run three since August and invoiced AED 52,500.

Where it is soft

  • We agreed to run in parallel in the room and never settled the price. Raising it now opens a commercial conversation, which is better had with Jad alone.
  • Keep invoices in the finance channel unless you are asked directly what you are being paid for.

3. Do not say these: the record does not support them

You said the second and third of the seat and operator claims to Aline and Estelle on 1 October:

Nitin: “They dismiss both and they said they're going to give it to Fiona.” Aline and Estelle, 1 Oct, line 677

If it is repeated to Bani, he may ask for the evidence. It is better corrected first.

4. Lessons for Deep Hospitality

It goes both ways. These are ours, with the evidence, so nothing in the room is a surprise.

AWe wrote far more than three busy people could read, and we were told on day one
Neil, 8 Jul: “I have developed a, an allergy to AI-generated emails and AI-generated text in general” Kickoff, 8 Jul, line 71
Neil, 8 Jul: “your proposal was good, but painful to read, frankly” Kickoff, 8 Jul, line 77
Nitin (by content), 3 Sep: “are you all able to spend time to read any of the stuff I'm pushing?” Neil's call, 3 Sep, line 76
Neil (by content), 3 Sep: “I would much prefer not to have to read AI-generated English, which is awful.” Neil's call, 3 Sep, line 94

By 3 September the programme dashboard ran to about 13,900 words and there were 27 hosted pages. Neil warned us on 8 July. The short board in Aleph's own look went up on 3 September, 57 days later. That gap is ours.

What worked once we changed:

Neil (by content), on the one-page email: “was actually not bad” Neil's call, 3 Sep, line 119
Bani, 8 Sep, on the session page: “At least now we have some understanding” Regional Vice Presidents session, 8 Sep, line 107

Praise from the principals on tape is thin. The pivot was right, but do not claim they were complimentary beyond these two lines.

BMethod: too much on paper, too little where it counted

What the agreement promised, in our own words:

Agreement: “One page, agreed in minutes before the build starts” The agreement, page 9
Agreement: “monthly steering one-pager to the three of you. Five minutes of reading” The agreement, page 9
Agreement: “two working sessions a week” The agreement, page 9

What we built instead: three charters, two data registers, a decision record, a five-stage method on a dashboard, 30 hosted pages. The light method was already written down. We did not follow it.

What we did not get:

  • A scope agreed by all three. No charter carries a client signature or a written yes from Bani, Neil and Jad. The standards charter was marked agreed on 25 July on our own word after the scoping calls with Jad and Fiona. The intranet charter is still a draft naming Jad as sponsor.
  • An owner per module from the start. The standards operator and the intranet sponsor were both named on 2 September.
  • A meeting that decides. We proposed a monthly half hour on 24 July. The sessions of 4 August and 2 September became demonstrations. The first sitting set up to decide is 5 October.
Nitin, 4 Aug: “we have to follow the charter, right? Because that's been signed off.” Engine shown to Bani, 4 Aug, line 338

If Bani asks who signed it, the answer is nobody on his side. Do not lean on that line.

Neil (by content), 3 Sep: “Jack felt maybe it was all being overcomplicated.” Neil's call, 3 Sep, line 33
Neil (by content), 3 Sep: “we need something simple and straightforward.” Neil's call, 3 Sep, line 34
Neil (by content), 3 Sep: “I don't necessarily want to or need to know what it is or how to do it.” Neil's call, 3 Sep, line 142
Neil (by content), 3 Sep: “we need to see some output.” Neil's call, 3 Sep, line 54

Did we jump the gun? In three places. We began on 3 July and the agreement was signed on 24 July. We took the scope of the standards work from one principal. We ran three modules against an agreement written for one at a time. Moving fast was right for this client. What was missing was small: one page of scope that all three had said yes to, one owner per module, and half an hour a month with the decisions listed beforehand.

In fairness to them: they open hotels, they travel, and this is not their day job. A method that costs them hours will be skipped. It has to cost them minutes.

CWe said yes in the room and did not say what it would cost in time
Nitin, 6 Jul, on running modules side by side: “we'll definitely do parallel” Call with Jad, 6 Jul, line 155
Nitin, 8 Jul: “I'll make it fast, I promise.” Kickoff, 8 Jul, line 413
Nitin, 8 Jul: “August onwards, we want to make sure that becomes business as usual” Kickoff, 8 Jul, line 344

Owner conversations, marketing slides, one format, action plans, the portfolio: each was welcomed and none came with a date. See items 3, 6 and 10.

DOther slips on our side
  • The 2 September update left the principals unsure what had been achieved.
    Neil (by content), 3 Sep: “I'm confused.” Neil's call, 3 Sep, line 27
    Bani, 2 Sep: “I'm not getting it.” Project Update No. 2, 2 Sep, line 599
  • First contact with corporate finance came four weeks after the kickoff.
    Nitin to Rohit: “Bani suggested at the kick-off that we set up a session with you and Satish, and I should have written sooner.” Email, 5 Aug 2026
  • We said the engine took 1.3 minutes a standard.
    Caroline, 4 Aug: “takes about 1.3 minutes” Engine shown to Bani, 4 Aug, line 158
    Caroline, 10 Sep, internal: “genuinely, I made a mistake with that” DH internal prep, 10 Sep, line 368
  • We said the build was nearly done, then rebuilt it three times.
    Caroline, 4 Aug: “But we're 90% there.” Engine shown to Bani, 4 Aug, line 62
    Caroline, 6 Aug: “We have since completed our side of the build.” Email, 6 Aug 2026
  • A gap in September while we were away, 15 to 19 September.
    Nitin to Jad, 23 Sep: “I haven't done my job, which is to update you, right?” Jad catch-up, 23 Sep, line 14
  • Bani has said on tape that he sees little AI in the standards work.
    Bani, 2 Sep: “I see very little AI in it.” Project Update No. 2, 2 Sep, line 638
  • The first operators did not use the method as we built it. They prompted for a luxury version, and the standards grew from about one and a half pages to six.
    Fiona, 1 Oct: “took me all day to read 20.” Fiona and Annette, 1 Oct, line 50
  • We introduced BIRD after finance had said to wait for Fairmas. The choice between them now holds up the Business Review. See item 5.
EFrom here: seven working rules for this client
  • One screen, their colours, shown in person. Nothing longer unless they ask.
  • Your voice, short. If it reads as machine-written, it is not read.
  • Working output first. The method stays behind the curtain.
  • One page of scope, a yes from all three, before anything new starts: the portfolio engine, the intranet route, the BIRD trial.
  • One owner per module, named, with the authority to decide.
  • Half an hour a month. Decisions listed beforehand. Every yes to an addition comes with its date.
  • The agreement on the table. One page charters, a monthly one-pager, one module at a time. It is what both sides signed up to.

5. If asked “what are we paying for, if Claude can do it?”

The best answer is Aleph's own, in writing, from the person who runs the engine:

Fiona to Aline and Estelle, copying Caroline and Nitin: “We just need to clarify that the work shown yesterday is via the Claude engine built by Deep Hospitality. All we did was change the prompts within the engine.” Email, 1 Oct 2026, 15:03 Dubai, "SOP feedback"
Same email: “We advised Caroline and team that we tested on a free trial Claude system this morning with the same prompt to see what it would have produced and was nowhere near the same deliverable.” Same email

And what Aleph people have said about the work:

Fiona, 1 Oct: “this is really excellent quality.” Fiona and Annette, 1 Oct, line 254
Abdellah (by content), 4 Aug: “the outcome is something to be really, really happy with.” Engine shown to Bani, 4 Aug, line 548
Estelle, 1 Oct: “They were great.” Aline and Estelle, 1 Oct, line 668
Satish, 11 Sep: “it's an eye opener” Fairmas and BIRD call, 11 Sep, line 528

What exists today that did not on 1 July: six General Manager conversations and two owner conversations on record; the monthly review mapped; three templates on a real month; a standards engine in Aleph's hands and in daily use; a written scope for the intranet with HR's needs in it; a free trial on offer for one view across the systems.

Transcripts and the agreement are on the Deep Hospitality SharePoint; the references give the meeting and the line. Sources: 16 filed transcripts under 01_BRM, 02_SOPs_Morocco and 03_Intranet (01_Discovery in each), and emails read from the Deep Hospitality mailbox on 1 October 2026. Speaker names marked “by content” are inferred where the transcript gives only a speaker number. Day counts run to 5 October 2026 where an item is still open. Built by script; every transcript quote was matched to its source line before this file was written.