All decks
WhatsApp Order & MenuATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductWhatsApp Order & Menu — restaurant menu site with WhatsApp ordering
Register keywhatsapp-order-menu
OwnerATTOH LTD (Companies House 14079382) · powered by app-builder
Live atattoh.tech/whatsapp-order-menu · HTTP 200 on 9 September 2026
Price£29 a month · stripe-price-object-read-2026-08-21
Built from11 register parts, 10 live, 10 probe-verified

What it does

Boost restaurant profits with AI-powered WhatsApp ordering. Our platform personalizes menus, drives upsells, and automates re-engagement to increase average order value by 15-25%. Get started from just £39/month and turn chats into bigger sales.

Runs on

White-label site engine
White-label client editor
Hospitality ops (HospSnap)
Tenant-scoped data (RLS)
Source: estate register (products, product_parts, builder_blocks) · deploy probe 9 September 2026Evidence live
03The frameWhat this buyer's profession checks

We will measure it against the operator's own audit.

Three checks a buyer in this field applies, whether or not they name the standard. We use them as the frame for everything that follows.

Check 1

Booking and pricing accuracy every day

Check 2

Licensing and safety records current

Check 3

Reviews answered from the record

Frame chosen by BRG as a summary of the operator's own audit. Verify the wording with the body before external use.No accreditation is claimed
04Why it's better · 1 of 6Check 2 · fit for purpose

The job as the register describes it.

Restaurants hand a third of the order value to a delivery platform to reach a customer who is already messaging them.

Who carries it

Restaurants taking and upselling customer orders over WhatsApp

Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose

What it does instead.

A menu people can order from where they found you, instead of a PDF that opens badly on a phone.

Boost restaurant profits with AI-powered WhatsApp ordering. Our platform personalizes menus, drives upsells, and automates re-engagement to increase average order value by 15-25%. Get started from just £39/month and turn chats into bigger sales.

The parts doing the work

White-label site engine verified

One renderer for many branded client sites; live tenant Pages proof plus source contract and publish queue guard.

White-label client editor verified

Identity-first Supabase edge fn: founder edits any site, a partner edits only their owner_tag rows. GET list/load, PUT save (validated), POST publish

Hospitality ops (HospSnap) verified

HospSnap — booking engine + rooms (frontend)

Tenant-scoped data (RLS) verified

Source: register purpose, public_blurb, product_parts joined to builder_blocks4 of 11 parts shown
06Why it's better · 3 of 6Check 1 · controls

Proof it exists, not a roadmap.

200

HTTP status of attoh.tech/whatsapp-order-menu on 9 September 2026 · real-content-verified

10/11

register parts verified by probe

10

parts wired live

HTTP 200

functional surface probe

Open attoh.tech/whatsapp-order-menu during the talk. Anything the deck claims should be visible there.

Source: register deploy_probe_code, deploy_probed_at, product_parts.verified_by_probeProbed, not promised
07Why it's better · 4 of 6Against the market, honestly

Where we lead, and where we don't.

Top-5: Menubly ($9.99/mo Pro), Ainisa (Meta partner), WAAYU (zero-commission), MenuTiger ($17/mo w/ payments), Toast ($69+/mo full POS). This product is LIVE and already demoed to 4+ real hospitality prospects (not theoretical) - assembled on the reuse-first white-label site engine, so buyers get a full branded site + zero-commission WhatsApp ordering as ONE package vs a bolt-on widget. Honest tension: Menubly/MenuTiger undercut on pure price (£8-13 vs £19) if the buyer only wants the ordering widget alone - the win is the bundled package, not the cheapest point-solution. Real market validation (live demos) is stronger evidence than most rows here.

Evidence: here.

Not independently sourced This verdict was written from an analysis whose only source was the model itself, not scraped competitors (analyst gtm-loop-worker). Treat the competitor names and positions as a working hypothesis until the market research is re-run; do not quote them to a buyer.
Source: register vs_competitionNamed competitors are the register's, not the presenter's
08Why it's better · 5 of 6Check 2 · fit for purpose

Built for one kind of buyer.

Restaurants taking and upselling customer orders over WhatsApp

Source: register audience, serves_nichesOne buyer, not everyone
09Why it's better · 6 of 6Price is part of the scope

What it costs, in one line.

£29 a month

Intro offer: [object Object]

Basis: stripe-price-object-read-2026-08-21

Buying route

Payment link live
software
Scope named on the next slides, so the price has a boundary
Source: register price_gbp, billing_interval, pricing_basis, payment_link_activeNo hidden rate card
10What's inside

The parts, with their verification state.

PartCategoryStateVerified
White-label site enginebackendlive_wired
White-label client editorbackendlive_wired
Hospitality ops (HospSnap)full-stackspec
Tenant-scoped data (RLS)datalive_wired
WhatsApp Order & Menu — restaurant menu site + WhatsApp ordering CTAuilive_wired
Stripe paymentsbackendlive_wired
White-label site deploy (Cloudflare Pages)integrationlive_wired
Site lead capturebackendlive_wired
Supabase authbackendlive_wired
WhatsApp delivery railintegrationlive_wired
Source: product_parts joined to builder_blocks · 10 of 11 shown probe-verified   not yet
12Why packaging matters

Five things a package does that a price cannot.

1
Scope becomes visible. The parts are named, so nothing is assumed.
2
Boundaries are explicit. What is outside is written down before the first invoice.
3
It is auditable. A package is a documented process, which is what the operator's own audit looks for.
4
Buyers compare like for like. A referral needs a defined thing to refer.
5
Switching fear drops. The move is inside the package, not a project bolted on the front.
Source: BRG packaging doctrine; frame from slide 3Packaging = a compliance instrument
13This packageCut by what each part does

WhatsApp Order & Menu, as a package.

backend

White-label site engine

One renderer for many branded client sites; live tenant Pages proof plus source contract and publish queue gua

verified

White-label client editor

Identity-first Supabase edge fn: founder edits any site, a partner edits only their owner_tag rows. GET list/l

verified

Stripe payments

verified

Site lead capture

Public Supabase edge fn (honeypot, CORS, service-role) -> partner_site_leads, tagged by site_slug. Every white

verified
full-stack

Hospitality ops (HospSnap)

HospSnap — booking engine + rooms (frontend)

verified

Qr Ordering Host

Registered from existing live product_parts during 2026-07-05 Codex register-integrity repair. Products: whats

missing
data

Tenant-scoped data (RLS)

verified
ui

WhatsApp Order & Menu — restaurant menu site + WhatsApp ordering CTA

Branded restaurant/venue menu site: a grouped, priced menu section + a floating WhatsApp deep-link CTA (wa.me,

verified
integration

White-label site deploy (Cloudflare Pages)

Builds a site from its live DB config and deploys to brg-site-<slug>.pages.dev (self-provisions the Pages proj

verified

WhatsApp delivery rail

WhatsApp group delivery + MAYA routing rail. Twilio inbound webhook -> wa_group_messages (idempotent ingest) -

verified
Source: product_parts grouped by builder_blocks.category5 groups
14Anatomy of the packageOn one page · 2 items of work left, filed

A package reads like a control document.

Inside the scope

  • White-label site engine
  • White-label client editor
  • Hospitality ops (HospSnap)
  • Tenant-scoped data (RLS)
  • WhatsApp Order & Menu — restaurant menu site + WhatsApp ordering CTA

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 10 parts probe-verified, latest 6 July 2026
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • No build gap recorded in the register
  • 1 part still to verify by probe
  • 1 register field to fill (vs_competition_unsourced)

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 0 build packets proposed · 2 management items pending
  • Change log kept in the register
Source: product_parts (inside), deploy and part probes (evidenced), v_deck_work_left (work left; filed to manager_work and build_packets by deck_work_left_sync)One page
15Across the family

Where it hands over.

A1 Elitea1elite.pages.dev
Accounts & Filingattoh.tech/accounts-law/
AddressSnapattoh.digital/snap/addresssnap/
ATTOHWhatsApp Order & Menuattoh.tech/whatsapp-order-menu
AIEmploymentattoh.tech/aiemployment/
AIFreightaifreight.uk
AITransportaitransport.uk
Source: register rows sharing client_key attohOne house, many doors
1 / 16
Arrow keys or space · N narration · P print
Slide 1Narration Words Running total

Production guide

How to turn these sixteen slides into a presentation video. Same structure as every deck in the family, so a crew that has made one can make them all.

1 · Deliverable

ItemSpec
Format16:9, 1920×1080, 25 fps, H.264 MP4 plus WebM. Burned captions and a sidecar SRT.
RuntimeNarration below plus screen captures of the live product; typically 8 to 12 minutes.
Framethe operator's own audit. Verify the wording of the three checks with the body before external use.
BrandATTOH family palette as rendered here. Green only for verified and live states; red only for exclusions.
VoiceCalm, exact, never theatrical. Read figures and dates in full. Numbers are the register's, and the register is cited on every slide.

2 · Runtime plan

#SlideNarrationWordsStarts

3 · Screen captures

4 · Full narration

5 · What this deck must not say

  • No numbers that are not on a slide with a register source.
  • No accreditation by the operator's own audit; the frame is a lens, not a badge.
  • No named competitor read aloud unless the audience asks; the register's names are on slide 7 for the presenter.
  • No client names, volumes or tenure unless the register carries them.

6 · Regenerate

This deck is generated from the estate register. Update the product row, re-run the deck build, redeploy. Do not hand-edit this file.