All decks
Pharoah Comms HubPharoah Technology · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductPharoah Comms Hub
Register keypharoah-comms-hub
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atcommshub.pharoahtechnology.co.uk · HTTP 200 on 9 September 2026
PriceFree · [object Object]
Built from3 register parts, 1 live, 0 probe-verified
Not in the register yet a public blurb. This slide stays blank until the register carries it; nothing here is invented.

Runs on

Comms-hub AI-drafted / human-approved replies
Security Core alerts → comms-hub → Pulse (Phil's Telegram)
Comms Hub — Meta inbound webhook (WhatsApp/IG/Messenger)
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 buyer's own change-control.

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

A control between the work and the submission

Check 2

A process fit for this buyer, not a generic one

Check 3

Readiness for the next rule change

Frame chosen by BRG as a summary of the buyer's own change-control. 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.

Customer messages arrive across WhatsApp, Instagram and Messenger into three separate inboxes.

Who carries it

Customer support teams managing WhatsApp, Messenger and Instagram messages for their business

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

What it does instead.

Every customer message from WhatsApp, Messenger and Instagram captured into one place.

Not in the register yet a purpose or blurb. This slide stays blank until the register carries it; nothing here is invented.

The parts doing the work

Comms-hub AI-drafted / human-approved replies

comms-hub drafts a suggested WhatsApp reply on the GBP0 gateway (free/fast) and delivers it to Phil on Pulse/Telegram labelled "DRAFT (not sent)" for

Security Core alerts → comms-hub → Pulse (Phil's Telegram)

comms-hub /security-alert endpoint (commit 5849ea7): fail-closed X-Pharoah-Signature HMAC verify + Pulse push. Wires the surveillance-core PharoahWire

Comms Hub — Meta inbound webhook (WhatsApp/IG/Messenger)

Meta -> /webhook (x-hub-signature-256 verified with APP_SECRET, fail-closed 403 if unset) -> comms_inbox (RLS on) + Pulse ping to Phil's Telegram. PRO

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

Proof it exists, not a roadmap.

200

HTTP status of commshub.pharoahtechnology.co.uk on 9 September 2026 · real-content-verified

0/3

register parts verified by probe

1

parts wired live

HTTP 200

functional surface probe

Open commshub.pharoahtechnology.co.uk 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.

Category: its category. Nearest rivals: Twilio, Zendesk, Intercom; strongest is Twilio. Our edge: Pharoah Comms Hub captures every customer message and notifies users without auto-reply, ensuring message review before response. How we beat them: Target developer forums and B2B SaaS communities; wedge on message capture and review; hook on 'no auto-replies, just capture and notify'. Source: product_market_analysis, analyst gtm-loop-worker; rivals re-checked against the product's own promise 2026-08-29.

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.

Customer support teams managing WhatsApp, Messenger and Instagram messages for their business

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.

Free

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.

PartCategoryStateVerified
Comms-hub AI-drafted / human-approved repliesbackendstaged
Security Core alerts → comms-hub → Pulse (Phil's Telegram)backendactive
Comms Hub — Meta inbound webhook (WhatsApp/IG/Messenger)backendactive
Source: product_parts joined to builder_blocks · 3 of 3 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 buyer's own change-control 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

Pharoah Comms Hub, as a package.

backend

Comms-hub AI-drafted / human-approved replies

comms-hub drafts a suggested WhatsApp reply on the GBP0 gateway (free/fast) and delivers it to Phil on Pulse/T

staged

Security Core alerts → comms-hub → Pulse (Phil's Telegram)

comms-hub /security-alert endpoint (commit 5849ea7): fail-closed X-Pharoah-Signature HMAC verify + Pulse push.

active

Comms Hub — Meta inbound webhook (WhatsApp/IG/Messenger)

Meta -> /webhook (x-hub-signature-256 verified with APP_SECRET, fail-closed 403 if unset) -> comms_inbox (RLS

active
Source: product_parts grouped by builder_blocks.category1 groups
14Anatomy of the packageOn one page · 6 items of work left, filed

A package reads like a control document.

Inside the scope

  • Comms-hub AI-drafted / human-approved replies
  • Security Core alerts → comms-hub → Pulse (Phil's Telegram)
  • Comms Hub — Meta inbound webhook (WhatsApp/IG/Messenger)

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 0 parts probe-verified
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • Register parts gap: 0/3 parts live — close with parts-evidence flip or correct stale parts rows (GhostWire pre
  • 3 parts still to verify by probe
  • 2 register fields to fill (vs_competition_unsourced, public_blurb)

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 1 build packet proposed · 5 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 Comms Hubcommshub.pharoahtechnology.co.uk
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
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 buyer's own change-control. Verify the wording of the three checks with the body before external use.
BrandPharoah Technology 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 buyer's own change-control; 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.
  • Fields missing from the register for this product: public_blurb. Fill the register, regenerate; do not improvise on stage.

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.