01Pharoah Technology · WhatsApp & Telegrampartial
Pharoah WhatsApp Order Menu
A digital menu site for your restaurant or cafe, with ordering built straight into WhatsApp. Customers browse, order and pay — no app, no commission-hungry delivery platform.
Live · menu.pharoahtechnology.com£29 a month11 parts · 5 probe-verified
Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)menu.pharoahtechnology.com
02What it is
The facts, from the register.
| Product | Pharoah WhatsApp Order Menu |
| Register key | pharoah-whatsapp-order-menu |
| Owner | Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50) · powered by app-builder |
| Live at | menu.pharoahtechnology.com · HTTP 200 on 9 September 2026 |
| Price | £29 a month · [object Object] |
| Built from | 11 register parts, 10 live, 5 probe-verified |
What it does
A restaurant menu site that takes the order on WhatsApp, where your customers already are — no app for them to download.
Runs on
Site lead capture
White-label client editor
White-label site engine
Stripe payments
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 pay a platform a third of the order to reach a customer already messaging them.
Source: register pain_pointThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose
What it does instead.
A digital menu site for your restaurant or cafe, with ordering built straight into WhatsApp. Customers browse, order and pay — no app, no commission-hungry delivery platform.
A restaurant menu site that takes the order on WhatsApp, where your customers already are — no app for them to download.
The parts doing the work
Site lead capture verified
Public Supabase edge fn (honeypot, CORS, service-role) -> partner_site_leads, tagged by site_slug. Every white-label site form posts here; intel flows
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
White-label site engine verified
One renderer for many branded client sites; live tenant Pages proof plus source contract and publish queue guard.
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 menu.pharoahtechnology.com on 9 September 2026 · real-content-verified
5/11
register parts verified by probe
HTTP 200
functional surface probe
Open menu.pharoahtechnology.com 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.
[PARITY] 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_competition (18 August 2026)Named 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.
Not in the register yet an audience. This slide stays blank until the register carries it; nothing here is invented.
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
Basis: [object Object]
Buying route
Payment on enquiry
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.
| Part | Category | State | Verified |
|---|
| Site lead capture | backend | live_wired | |
| White-label client editor | backend | live_wired | |
| White-label site engine | backend | live_wired | |
| Stripe payments | backend | live_wired | |
| Hospitality ops (HospSnap) | full-stack | spec | |
| Tenant-scoped data (RLS) | data | live_orphaned | |
| Supabase auth | backend | live_orphaned | |
| WhatsApp Order & Menu — restaurant menu site + WhatsApp ordering CTA | ui | live_orphaned | |
| WhatsApp delivery rail | integration | spec | |
| White-label site deploy (Cloudflare Pages) | integration | live_wired | |
Source: product_parts joined to builder_blocks · 10 of 11 shown probe-verified not yet
11Why packaging matters
Bought as a price.
Delivered as a scope.
What the buyer hears
£29 a month
A number to compare with the last number.
the gap
disputes · churn
unpaid work
What the provider means
A scope
11 parts, some verified, some not, plus everything that is excluded.
Packaging is the instrument that makes the scope as visible as the price.Thesis
12Why packaging matters
Five things a package does that a price cannot.
1Scope becomes visible. The parts are named, so nothing is assumed.
2Boundaries are explicit. What is outside is written down before the first invoice.
3It is auditable. A package is a documented process, which is what the operator's own audit looks for.
4Buyers compare like for like. A referral needs a defined thing to refer.
5Switching 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
Pharoah WhatsApp Order Menu, as a package.
backend
Site lead capture
Public Supabase edge fn (honeypot, CORS, service-role) -> partner_site_leads, tagged by site_slug. Every white
verifiedWhite-label client editor
Identity-first Supabase edge fn: founder edits any site, a partner edits only their owner_tag rows. GET list/l
verifiedWhite-label site engine
One renderer for many branded client sites; live tenant Pages proof plus source contract and publish queue gua
verifiedfull-stack
Hospitality ops (HospSnap)
HospSnap — booking engine + rooms (frontend)
verifiedQr Ordering Host
Registered from existing live product_parts during 2026-07-05 Codex register-integrity repair. Products: whats
missingdata
Tenant-scoped data (RLS)
live_orphanedui
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,
live_orphanedintegration
WhatsApp delivery rail
WhatsApp group delivery + MAYA routing rail. Twilio inbound webhook -> wa_group_messages (idempotent ingest) -
specWhite-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
live_wiredSource: product_parts grouped by builder_blocks.category5 groups
14Anatomy of the packageOn one page · 9 items of work left, filed
A package reads like a control document.
Inside the scope
- Site lead capture
- White-label client editor
- White-label site engine
- Stripe payments
- Hospitality ops (HospSnap)
Evidenced, and how
- Live URL probed: HTTP 200 on 9 September 2026
- 5 parts probe-verified, latest 9 September 2026
- Functional surface: HTTP 200
- Register row updated with every probe
Outside the scope today · work left
- Human WhatsApp service round trip and ownership or continuity of +34670631458 are not proved; page is explicit
- 6 parts still to verify by probe
- 2 register fields to fill (vs_competition_unsourced, audience)
Who signs, and where the work sits
- Pharoah Technology Ltd owns the product and the data layer
- 1 build packet proposed · 8 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.
Anaïs AIgateway.pharoahtechnology.com
Anaïs AI (LLM router / reseller)anaisai.co.uk
Anaïs AI (working app)anaisai.co.uk
Pharoah TechnologyPharoah WhatsApp Order Menumenu.pharoahtechnology.com
ATS Résumé Scanner (free)ats.pharoahtechnology.com
Aurora AIauroraai.pharoahtechnology.com
Aurora Guardauroraguard.co.uk
Source: register rows sharing client_key pharoahOne house, many doors
16Close
Three things to take back to your desk.
One
Open the URL on slide 6. Test it before you trust it.
Two
The parts and their verification state are on slide 10.
Three
A package is a compliance instrument, not a price list.
See it live
menu.pharoahtechnology.com
Talk to us
via menu.pharoahtechnology.com
Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)Pharoah Technology