Aleph Hospitality
5 October 2026

Programme board

Where we stand, after the sitting of Monday 5 October

1 · Business Review

MappedDesignedBuiltIn useHanded over

Decided 5 October: one data layer that Aleph owns.

  • Fairmas, Medallia and CoStar first: the 3 sources already the same for every hotel
  • Claude reads the layer and produces the first half of each review: the numbers, the guest scores, what moved and why
  • HR, capex and the commentary stay with the hotel for now. Fairmas does not change.
  • A data engineer, hired by Aleph. Requirements from us by 7 Oct, Bani reviews, then issued. Bani has a candidate.
  • BIRD parked on cost. 1 question to Rudolf: build on Aleph’s own storage, and what that does to the price for small hotels.
  • No owner has the new review yet. First half-built review: about 8 weeks after the engineer starts.
The data layer, drawnIn numbersThe review as it runs nowWhat the owner sees, 3 levels
Decided in the roomOne data layer, Aleph’sBIRD parkedBani is point person

2 · SOPs Morocco

MappedDesignedBuiltIn useHanded over

Fiona and Annette are running it.

  • Rooms: every standard through in English, 6 sections
  • French under way, one section at a time
  • Every document read before release: the biggest time cost
  • 2 sets, each with the hotel’s own logo. On the Aleph shared drive until the intranet is live.
  • Trained 29 Sep. No further training needed for now.
  • Sent to the hotels so far: TBA by Fiona
  • All of Michlifen and Marchica done by: TBA by Fiona
  • Fiona’s next update: Tuesday 6 October
What is inside the engine
Decide in the roomNothing needed

3 · Intranet

MappedDesignedBuiltIn useHanded over

Decided 5 October: TopNotch builds it.

  • Neil negotiates the price directly with TopNotch
  • Deep Hospitality stays project manager
  • First build: the smallest version that works. The standards library, access for GMs and anyone on an Aleph address.
  • Live 6 weeks from a signed go
  • GO-Globe’s earlier work is not taken further
The 2 quotesScope of work (Excel)The mockupArchitecture optionsWhat the platforms cost
Decided in the roomTopNotchNeil on priceGMs first

DoneNowWaiting on a decisionTo come

The Business Review, drawn

Today, department by department

8 departments send in Put together by hand Then it travels Each from its own system or file. Every hotel, every month. Up through the region to corporate and the owner. Finance Sun, Sage, NetSuite profit and loss, receivables, cash Revenue Opera, STR occupancy, rate, segments, forecast Sales own files accounts, pipeline, promotions Marketing platform reports campaigns, social, press Food and beverage Micros outlets, covers, costs Guest experience Medallia, Booking, Google review scores, comments HR and training spreadsheets headcount, payroll, training records Engineering own files capital projects, maintenance One person collates the finance lead, the GM or a coordinator slides and sheets arrive by email numbers pasted in as pictures last month’s file copied forward 40 to 80 slides in PowerPoint The GM writes the commentary slide by slide Regional deck the hotel packs rebuilt by hand into a second deck Corporate reads it; questions go back, slides are corrected The owner meets on last month when this month is half gone What it takes 1 to 2 days chasing departments 10 to 20 hours management time per pack Day 15 to 20 before the review is read As the hotels and the corporate team told us in July and August. The hours are one cluster’s own estimate.

The same 8 inputs sit in all 3 levels. A gives each its own slide. B folds them into 5 questions. C shows only what moved.

From today to one view

1 · Today 2 · One place 3 · Connected Ten systems. The pack is built by hand each month. Two routes in, one view out, above the properties. Claude reads that one view. People decide. Operafront office Microsoutlets Sunledger Sageledger NetSuiteledger Fairmas17 hotels so far Excelby hand, each month PowerPoint40 to 80 slides Medallia, Booking, Googlereviews Emailto each owner Nothing talks to anything. Someone re-types it. directvia Fairmas One data layer owned by Aleph, above the properties finance and revenue from Fairmas guest scores from Medallia market index from CoStar (HR and capex come in version 2) one view by hotel, brand, region, portfolio Half-built reviewto the GM to finish Owner reportsone per owner Fairmas stays as it isat property level: forecast, budget, finance file read only Claude for the leadership team, RVPs included ask anything of the whole estate warned before a number turns red action plans drafted, sent once approved last month’s actions checked no fixed dashboard: your questions A person approvesbefore anything reaches a property or an owner The monthly review, assembledfrom the same data, checked, then sent Fairmas, Opera, Sun, Sage, NetSuite, Micros and Medallia are the systems in use today. The data layer is the store Aleph decided to build on 5 October. Claude is the assistant the standards engine already runs on.

The data layer, step by step

1Requirements writtenDeep Hospitality, to Bani firstBy Wednesday 7 October
2Reviewed and issuedBaniThe week after
3Engineer chosenAleph hires; Deep Hospitality qualifies the candidatesOctober
4DiscoveryThe engineer, with Fairmas, Medallia and CoStar; Rohit names the Fairmas contact2 weeks
5Model, loaders, 1 pilot hotelThe engineerWeeks 3 to 6
6Claude connected; first half-built reviewDeep Hospitality, with BaniFrom week 7
7Every hotel on the 3 sources, then HR and capexThe engineer, then version 2After the pilot

Fairmas is unchanged throughout. In parallel, Rudolf is asked whether BIRD could sit on Aleph’s own storage; both options come back to the 3 of you.

The data layer, in numbers

3 sources

Fairmas, Medallia, CoStar. Already clean and the same for every hotel.

Half

Of each review pre-built from the layer. Neil’s bar for version 1.

10 to 20 hours

To build one pack by hand, every month. One cluster’s own figure.

8 weeks

Our first shape, from the engineer’s start to the first half-built review. The engineer confirms it after discovery.

Fairmas stays at every hotel it serves. Nothing spent on it is lost.

The intranet, 2 quotes

Scope of work (Excel): written after meeting HR on 1 October, checked against their answers, and shared with both suppliers as a first version.

GO-Globe

Its own platform. Proposal of 20 September; GO-Globe says it covers the scope of work.

AED 32,000
  • AED 12,000 already paid is credited: AED 20,000 more, half on approval, half at launch
  • Library, staff directory, a page per hotel, search, English, French and Arabic
  • 3 weeks to build. End October was the launch date offered.
  • AI search, job board, learning and a chatbot priced on top
  • Scope of work sent 1 October. GO-Globe says it matches its proposal: same price, no change.

TopNotch

A custom build. Proposal of 2 October, against the scope of work.

AED 60,500
  • The standards library, fixed price, before VAT. Live for the 2 Morocco hotels in week 5 after sign-off.
  • Approval flow: AED 24,860 more, live in week 7. AED 85,360 for both.
  • Running costs about AED 400 a month for the pilot, AED 900 to 1,100 for the whole estate
  • Aleph owns the code and the accounts
  • Options: AI assistant AED 8,360 plus usage; upkeep AED 13,200 a year
Read the proposal

Decided 5 October: TopNotch. Neil negotiates the price directly. Both suppliers had the same scope; TopNotch priced it line by line. GO-Globe’s proposal stays here for the record.

Waiting on

The Fairmas contact

0days

The account manager’s name, from Rohit. The engineer’s first conversation.

The data engineer

0days

Requirements from us by 7 October, Bani reviews, Aleph hires. Bani has a candidate to introduce.

Rudolf’s answer

0days

Can BIRD sit on Aleph’s own storage, and what is the price for a 70-room hotel. Asked this week.

Timeline

1 July to 30 November. Work under way, a dot for each thing delivered · Waiting on a decision · Planned, or starts when you say so

JulAugSepOctNov
1 · Business ReviewData layer from October
Delivered Kickoff 8 Jul · 6 General Manager interviews and corporate by 6 Aug · 3 templates 7 Aug · owners 13 and 31 Aug · BIRD session 8 Sep · technical hour 11 Sep · trial proposed 23 Sep · sitting held 5 Oct, data layer decidedWaited on a decision What the owner sees: asked 7 Aug, settled 5 Oct by the data layer · this sitting: agreed 2 Sep, first slot 5 Oct · yes to the trial: asked 23 Sep, parked 5 Oct
2 · SOPs MoroccoIn use since 29 September
Delivered Scoping 21 and 24 Jul · engine shown working 4 Aug · handover plan 6 Aug · training 29 Sep · Rooms through in English 4 OctWaited on a decision Operator and licence: asked 6 Aug · operators named 2 Sep · licence approved 6 Sep · seats bought by 22 Sep · training offered for 25 Sep, held 29 Sep
3 · IntranetLive 6 weeks from a signed go
Delivered Charter and options 4 Aug · mockup 29 Aug · platform costs 2 Sep · HR met and scope of work 1 Oct · 2 quotes 2 Oct · TopNotch chosen 5 OctWaited on a decision Sponsor: asked 4 Aug, named 2 Sep · the route: a sitting agreed 2 Sep, decided 5 Oct
4 · Owner-Pitch BotWhen you say so
5 · LOI to HMAWhen you say so
HandoverAleph runs it without us

Raised, not started: A a project tool for Fiona · B one tiered procedure library for the portfolio · C owner onboarding, signature to opening. Your call.

Agreement: 5 months, July to November; this is month 4. Invoices: July settled 16 September; August issued 26 August, due 25 September, open.

The record

Every document, by module

1 · Business Review

2 · SOPs Morocco

3 · Intranet