Fractional CMO · 90-Day Plan
The ten steps

Prepared for Mahendra · The Monk · SPF Foods · August 2026

Proposal · Fractional CMO · 90 days

A plan to build four things
The Monk does not have yet.

Measurement you can read weekly. Guests you can identify. A channel you can reach them through without paying a commission. And a written procedure, so branch six inherits all three on the day it opens.

Ten steps, in dependency order. Each one states what gets built, what it produces, what it depends on, and how you know it worked.

90Days
10Steps, in order
5Branches, plus the sixth
12kAEDPer month, for three months

01 · Where things stand

The starting position, as I understand it.

From our call and from what is publicly visible. If anything below is wrong, it changes the plan — so it is worth correcting before we go further.

Already working

  • Fifteen years, five branches, a sixth opening
  • Order volume is up — guests are ordering more often
  • A direct ordering site already exists at order.themonk.ae
  • Corporate catering already exists as a service
  • Filmfare Middle East’s Favourite Casual Dining Restaurant, 2025
  • A premium position that has held while cheaper competitors opened around you

Not in place

  • No guest is identifiable after they have eaten — dine-in or delivery
  • Five WhatsApp numbers on five phones, with no shared list behind them
  • Around half of volume routed through platforms that take a commission
  • No weekly per-branch number that you and five managers read from
  • Nothing written down, so branch six starts from scratch like branch five did
  • No way to tell which of the last four marketing attempts did anything

On the ticket falling while volume rises. That pattern normally means the same guests are ordering more often, in smaller and more solo occasions. It is a base, not a decline — a weekday habit is the hardest thing to build and you already have it. The work is to raise what a solo order is worth (step 05) and to add the larger occasions on top of it (steps 06 and 09), rather than to discount your way back to bigger tables. Whether that reading is right is the first thing step 01 tests.

02 · What the plan is actually building

Four capabilities. Everything else is a consequence.

Marketing activity is not the point. These four are the point. Every one of the ten steps builds exactly one of them, which is how you can check the plan rather than take my word for it.

A

Measurement

One sheet per branch, every Monday, that you and five managers read the same way. Without it, nothing after it can be proven — which is the position the last four attempts were judged from.

Built by steps 01 · 02
B

Identity

Knowing who ate, at which branch, through which channel, and when they last came. Today a guest of fifteen years is indistinguishable from a first-timer.

Built by step 03
C

Reach

A way to contact those guests that you own, that costs almost nothing per message, and that does not disappear when an ad budget stops.

Built by steps 04 · 06 · 07
D

Repeatability

The above, written as a procedure with a checklist and an owner, so opening a branch is a process rather than a fresh improvisation each time.

Built by step 10

Steps 05, 08 and 09 are revenue work — ticket, local search and catering. They sit on top of A to D, and they are deliberately scheduled after them, for the reason set out in section 04.

03 · The plan

Ten steps. Twelve weeks.

Each step is a thing that exists at the end of it. “Done when” is written so that you, not I, decide whether it happened.

01 · Week 1Measurement

Baseline audit

BuildPull twelve months of POS data, every aggregator dashboard, Google and Meta into one sheet per branch. Item-level margin where the POS allows it. On site at all five branches in this week.
ProducesYour real figures: actual ticket, actual channel split, actual food cost, actual commission rate per platform per branch.
NeedsPOS access or exports, aggregator logins.
Done whenEvery assumed number in section 05 of this page has been replaced by one from your own systems — including the ones that make the case worse.
02 · Week 2Measurement

The weekly sheet

BuildOne page per branch, sent every Monday: covers, average ticket, channel mix, direct share, new versus returning, and cost per incremental order once there is spend to divide.
ProducesThe ability to tell whether anything after this point worked, and which branch it worked in.
NeedsStep 01.
Done whenYou and five branch managers receive sheet one before noon on a Monday, and you can read it without me explaining it.
03 · Week 3Identity

Capture at the table and in the bag

BuildA table QR into a menu-and-join flow, a printed card in every delivery bag, Wi-Fi capture, click-to-WhatsApp on all five Google profiles, and a short script for whoever takes payment.
ProducesOpted-in contacts, tagged by branch and by the channel they arrived through.
NeedsGoogle profile admin. A print run for table cards and bag inserts — small, and outside the fee.
Done whenContacts arrive daily from all five branches and the per-branch capture rate is a line on the weekly sheet.
04 · Week 4Reach

One inbox behind five numbers

BuildThe five WhatsApp numbers consolidated into one system. Guests keep dialling the same number they always have; staff answer from one place. Contacts from step 03 land here with their tags attached.
ProducesA list you own and can reach, with no commission on the conversation.
NeedsThe five numbers, and the person at each branch who currently answers them.
Done whenEvery branch replies from the shared system, and the contact count is on the weekly sheet and rising.
05 · Week 5Revenue · ticket

Menu and set architecture

BuildItem-level margin analysis from step 01. Build sets and attach prompts around what already sells. Rebuild the aggregator menus for the order people actually scroll, with the right items in the first screen.
ProducesA higher average ticket with no price rise and no discount.
NeedsItem-level data from step 01. If the POS cannot export it, this step gets slower and weaker — see section 06.
Done whenAttach rate and average ticket are both tracked weekly against the week-one baseline.
06 · Week 6Reach

A small number of automatic messages

BuildFive flows, deliberately no more: a thank-you and review request after an order, a nudge timed to each guest’s own reorder interval, a twenty-one-day quiet message, a forty-five-day one, and something for the top spenders. Written in your voice. No discounting.
ProducesRepeat orders at close to zero marginal cost, and a steady flow of Google reviews for step 08.
NeedsSteps 03 and 04. Needs a list with enough people on it to be worth messaging — which is why it is week 6 and not week 1.
Done whenOrders can be attributed back to specific messages on the weekly sheet.
07 · Week 7Reach

Make your own front door the default

Buildorder.themonk.ae becomes the link on every profile, every message, every bag insert and every reply. Guests who currently order through a platform get one clear, non-discount reason to order direct next time.
ProducesOrders that keep the commission currently paid to a platform — the single largest recoverable number in the business.
NeedsSteps 03 and 04. The aggregators stay on — this is about the second order, not the first.
Done whenDirect share of delivery volume is a tracked weekly line, and it is moving.
08 · Week 8Revenue · demand

Local search, five catchments

BuildAll five Google profiles rebuilt properly — categories, attributes, hours, photos, menu, questions. A page per branch on themonk.ae for its own catchment. A steady review flow coming off step 06.
ProducesNew guests who are already searching for what you sell, at no cost per click.
NeedsGoogle profile admin. Step 06 for the review flow.
Done whenMap-pack position and profile actions per branch are on the weekly sheet.
09 · Weeks 9–10Revenue · catering

A catering pipeline, not a catering page

BuildA named list of office buildings inside each branch’s delivery radius. Outreach, sampling, a proper catering menu, and one owner for enquiries. Paid geo-targeting inside each radius, on a budget you approve first.
ProducesRecurring, higher-ticket orders from a small number of accounts — the highest-value line available to you.
NeedsSteps 01 and 08. This is a pipeline with a sales cycle, not a campaign — see section 06.
Done whenThere is a named pipeline with stages and an owner, and the first accounts are ordering on a schedule.
10 · Weeks 11–12Repeatability

The branch playbook

BuildSteps 01 to 09 written as a procedure, with a T-minus-45-day checklist: what gets set up, by whom, in which week, before a new branch opens. Branch six is the first run of it.
ProducesThe reason to do this once rather than five more times.
NeedsAll of the above, actually done once. You cannot write down a procedure you have not run.
Done whenSomeone who was not in the room can open branch seven with the document and no other help.

04 · Why this order

Each step exists because the next one needs it.

This is the part that makes it a system rather than a list of marketing activities. The sequence is not a preference — reordering it breaks it.

First — nothing above this is provable without it

MeasurementSteps 01 · 02
IdentityStep 03

Then — these need a measured baseline and a named guest

ReachSteps 04 · 06 · 07
TicketStep 05

Then — new demand, once there is somewhere to keep it

Local searchStep 08
CateringStep 09
Paid, in radiusStep 09

Last — only writable once the rest has actually been run

The playbookStep 10 · branch six onward
Measurement firstBecause otherwise the verdict on this pilot is a feeling, which is exactly how the previous four were judged. Step 02 exists so that if this fails, it fails visibly and early, in front of you.
Identity before reachA channel with nobody in it is not a channel. Building messaging flows in week one, against an empty list, is the most common way this kind of work produces nothing.
Reach before demandPaying to attract guests you cannot contact again is renting attention. It is the most expensive way to grow and it stops the day the budget stops. Steps 08 and 09 are scheduled after there is somewhere for the new guests to land.
Playbook lastA procedure written before the work is a document. A procedure written after it is an asset. Branch six is the test of whether it is real.

05 · The arithmetic

What one unit is worth, and how many it takes.

I have not put a total return on this page, because any total I produce before step 01 is a guess with a decimal point on it. What follows is arithmetic you can check, and one illustrative scenario with every input visible.

First — what an order is actually worth

Per 58 AED orderYou collectCost of saleContribution
Dine-in58.0017.4040.60
Direct delivery58.0024.7733.23
Aggregator40.6018.9021.70
The gap, direct vs platform11.53 per order

Modelled at 30% food cost, a 30% blended platform take rate, 1.50 packaging, 5.00 own-fleet fulfilment and 1.5% payment fees. Published UAE commissions run 15–35% before service fees and placement costs, and they differ per platform and per branch. These are my assumptions, not your figures. Step 01 replaces all of them in week one, and the numbers below move with them — in either direction.

Second — what it takes to cover the fee

LeverOne unit is worthUnits per month to cover 12,000Per branch, per day
A delivery order moves off a platform11.531,041 orders6.9
One side or drink added to an order (+8 AED)5.602,143 orders14.3
A quiet guest orders once more~33.00364 orders2.4
An office account ordering weekly at ~1,200~2,640 / mo4.5 accounts

Read each row on its own and decide whether it looks achievable across five branches. That judgement is worth more than any projection I could write, because you know the floor and I do not. The plan runs all four levers, so in practice they share the load rather than any one carrying it.

Third — one scenario, with the inputs shown

Gross profit contributionMonth 1Month 2Month 3Assumption behind it
Orders moved off platforms4,60010,400400 then 900 orders a month, across five branches
Ticket, via sets and attach7,40013,9008% then 15% of orders take a +8 AED addition
Quiet guests returning9,90026,400300 then 800 orders from the messaging in step 06
Catering accounts7,90018,5003 then 7 accounts, ordering weekly
Month total029,80069,200Month one installs; it does not harvest
Ninety days99,000 gross profit against 54,000 of spend — 36,000 fee plus roughly 18,000 mediaNet positive by about 45,000

This scenario is deliberately modest and it is built to be missed visibly if it is wrong. Every input in the right-hand column is a line on the weekly sheet from week two, so by week six you will know which way it is going rather than finding out at day ninety. It assumes roughly 16,500 orders a month across five branches — my estimate, and one of the first things step 01 corrects. Exiting at a month-three rate near 69,000 a month against a 12,000 fee is the case for continuing; failing to reach it is the case for stopping, and section 09 says how.

06 · Limits

What I am not promising, and what I am.

You have paid for confident forecasts before. The useful thing I can offer instead is an honest account of where this plan is weak, so you can judge it on something other than tone.

Not promising

  • Footfall as such. Footfall is the output of food, location, price and consistency. Four of those are already yours and already working. I am not going to claim credit for a system I have not built.
  • That the ticket lift lands. Step 05 depends on item-level margin data. If the POS cannot export it, that step gets slower and weaker, and I will say so in week one rather than week twelve.
  • Catering inside ninety days. It is a pipeline with a sales cycle. It may produce very little by day ninety and a great deal by day one hundred and eighty. Judge step 09 on whether the pipeline exists, not on its revenue.
  • Capture rates without your managers. Step 03 depends on staff doing a small thing every shift, in five branches. This is the most likely part of the plan to underperform, and it is the part I cannot do alone.
  • That the commission gap is 11.53. If your contracted rates are materially below 30%, that lever shrinks and the arithmetic in section 05 weakens. Week one settles it.

Committing to

  • The ten steps get built, in the order given, and every asset is created in The Monk’s name from day one. Nothing sits behind a login of mine.
  • The weekly sheet arrives every Monday whether the numbers are good or bad, and it uses the same definitions every week so it cannot be quietly reframed.
  • Assumptions get replaced by your data in week one, including where that makes the case for this pilot worse.
  • A review at day forty-five. We read the sheet together. If it has not moved, we change the plan or you stop, and that is written into the agreement rather than offered verbally.
  • Hands on the work. This is installation, not advice about installation. On site at branches, in the accounts, writing the messages.

07 · How the work runs

The weekly rhythm, and what it costs you in time.

MondayThe sheetNumbers to you and every branch manager before noon. Last week, per branch, against the baseline.
WednesdayThe buildWhatever this week’s step requires — flows, menus, profiles, pages, scripts. Shipped, not planned.
ThursdayOn siteAt a branch, rotating. All five in month one. Steps 03 and 05 do not survive being run remotely.
MonthlyThe reviewSixty minutes with you. What moved, what did not, what changes next month.
Your time

About thirty minutes a week

One reading of the sheet, and decisions where a decision is needed. Plus roughly twenty minutes a week from one nominated person at each branch, which is the real dependency in step 03.

Scope

What this is not

Not an agency of record, and not a media buyer taking a percentage of your spend. Media is bought on your accounts, at a number you approve. Print, software licences and any production costs sit outside the fee and get quoted before they are incurred.

08 · What I need from you

Six kinds of access. Week one stalls without them.

POS accessOr a weekly export, per branch. Item-level if it exists.
Aggregator dashboardsEvery platform, read access is enough
Google Business ProfileAdmin on all five listings
Meta Business ManagerAdmin, plus the ad account
The five WhatsApp numbersMigrated, not replaced — guests keep dialling the same number
One nominated person per branchTwenty minutes a week each — step 03 depends on this more than on me

09 · Terms

12,000 a month. Three months. An exit at day forty-five.

01

The fee

12,000 AED per month. Invoiced monthly in advance. No setup charge, no success fee, no percentage of spend.

02

Media and costs

Media is proposed in week two, from the audit, with the reasoning attached. You approve the number and it is spent on your accounts. Print and software sit outside the fee and are quoted first.

03

The term

Three months. Month one commits, because a half-finished installation is worth less than none. Months two and three run month to month.

04

The day-45 review

We read the weekly sheet together. If it has not moved, we change the plan or you stop. Written into the agreement, not offered verbally.

05

Ownership

Every account, list, asset and document is created in The Monk’s name on day one, including the contact list and the playbook.

06

After day ninety

Either you run it with the playbook, or we agree a lighter arrangement to keep operating it. There is no renewal built into this proposal.

Next step

Correct the assumptions.

Before agreeing to anything, the useful next hour is opening the POS and the aggregator dashboards and replacing the estimated figures in section 05 with real ones. If they hold up, the plan stands. If they do not, you will have found that out for the cost of an hour rather than a quarter.