Case study · illustrative · 4 min read

Specialty café JLT — Growth System

Illustrative case study: how a f&b brand in the UAE could run Reels + Maps + creator seeding. Scenario-based, not a claimed client result.

Illustrative scenario, not a client engagement. Numbers are planning bands, not audited outcomes. The method, the 90-day structure and the full caveats are set out once on the case studies hub.

Baseline problems

Before media spend, the scenario opens with structural issues that make “more leads” the wrong first request:

Great coffee, weak Maps presence: incomplete hours, few geo-tagged photos, and reviews unanswered.
Reels are irregular; when they post, there is no offer path beyond "visit us."
Creator seeding is random free drinks with no tracking (unique code, time window, or story link).
Office lunch rush is underserved online; residents see the brand more than weekday workers.
No distinction between brand content (craft, origin) and performance content (this week’s pastry + map pin).
Delivery apps take margin; first-party visit growth is not instrumented.

The 90-day system

Days 1–14: GBP completeness, photo blitz, review reply SOP, Instagram profile as a visit machine (hours, map, WhatsApp for catering). Define content pillars: craft, menu drops, community, JLT moments.

Days 15–45: Reels cadence 4–5/week; Maps posts; micro-creator seeding with clear visit windows; light Meta boost only on proven organic clips.

Days 46–90: Catering offer for JLT offices via WhatsApp; loyalty mechanic; UGC repost system; seasonal calendar (Ramadan hours, summer indoor push).

Channel tactics for f&b

The stack Reels + Maps + creator seeding is not a buzzword salad. Each piece has a job in this industry context:

Reels: Process shots, latte art speed ramps, new pastry drops timed to lunch and weekend brunch; always geotag JLT; captions with cluster landmarks.
Maps: Weekly Google posts, menu photos, attribute accuracy (outdoor seating, Wi-Fi), Q&A seeding with real answers.
Creators: Micro over mega; brief for 1 story + 1 reel; unique code or sticker for 7-day window; rights to remix as ads.
Ops: Staff trained to mention review politely; catering PDF + WhatsApp number for offices.

Metrics dashboard (directional)

Metric	Baseline (illustrative)	90-day directional band
Maps profile actions	Baseline low	Rising calls/direction requests
Reel reach → profile visits	Weak link	Stronger with CTA discipline
Creator-attributed redemptions	None tracked	Measurable per code
Weekday lunch covers (proxy)	Flat	Mild lift with office catering + content
Review rate & reply SLA	Inconsistent	Steady + same-week replies

Owner-facing reporting stays short: one money metric, a few drivers, and decisions. Vanity charts without actions do not ship.

UAE-specific notes

JLT is cluster-based navigation — people search by cluster number and landmark. Summer heat pushes indoor dwell time and iced-menu content. Ramadan hours and iftar boxes need early creative planning. Multicultural staff and customers reward bilingual menu highlights. Delivery platforms are competitors for attention; Maps and WhatsApp catering defend first-party margin.

Risks and failure modes

A growth system fails in predictable ways. This scenario watches for:

Paying large influencers for vanity reach that does not convert to JLT footfall.
Boosting every post without creative winners — burns budget.
Inconsistent hours on Maps during Ramadan — trust damage.
Over-rotating menu for content and stressing kitchen ops.

What Shabang would own

In a real engagement shaped like this scenario, ownership is explicit so the client team is not guessing:

Organic social system and creator seeding playbook.
GBP/Maps excellence and review ops.
Selective paid amplification and rights management.
Simple weekly scorecard for the owner, not a 40-row analytics dump.

If you are building a similar system, start with the service lines and playbooks that map to this stack:

Services

Guides