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

The facts, from the register.

ProductPharoah Suite — Advert Wall
Register keypharoah-suite
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atpharoah-suite.pages.dev · HTTP 200 on 9 September 2026
PriceFree
Built from3 register parts, 3 live, 2 probe-verified

What it does

The Pharoah Suite advert wall — 50 per-product advert pages plus a gallery, auto-refreshed and guarded against claiming more than the register proves.

Runs on

Advert Wall auto-refresh
Advert Wall generator (register-honesty guarded)
Advert Wall — 50 per-product advert pages + gallery
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.

A product catalogue has nowhere to be seen, and hand-built advert pages go stale the moment a product changes.

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

What it does instead.

All 52 Pharoah Suite products, one advert each — intelligence, compliance and automation for UK business and government.

The Pharoah Suite advert wall — 50 per-product advert pages plus a gallery, auto-refreshed and guarded against claiming more than the register proves.

The parts doing the work

Advert Wall auto-refresh verified

refresh_adverts.sh: pulls live register, regenerates 51 advert pages, deploys to CF Pages only on real change. Fail-closed (aborts on bad read/implaus

Advert Wall generator (register-honesty guarded) verified

generate_ads.py + products.json in ~/Documents/pharoah-suite: generates the 50 advert pages with prices honesty-guarded against the live register (com

Advert Wall — 50 per-product advert pages + gallery

50 per-product advert pages + gallery served on CF Pages pharoah-suite.pages.dev/ads/ — live-probed HTTP 200 on 2026-07-15. Built from dist/ in ~/Docu

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 pharoah-suite.pages.dev on 9 September 2026 · real-content-verified

2/3

register parts verified by probe

3

parts wired live

HTTP 200

functional surface probe

Open pharoah-suite.pages.dev 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: multi-page ad and landing management. Nearest rivals: Unbounce, Instapage, Leadpages, HubSpot Landing Pages, Webflow; strongest is Instapage for paid traffic. Our edge: rivals give one editor and expect the agency to hand-build and hand-maintain every variant, so an account with many ad pages becomes a maintenance job; we automate the set so pages stay consistent as the campaign changes. How we beat them: per-page and per-conversion pricing punishes exactly the agency running many pages, which is our 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.

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.

Free

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
Advert Wall auto-refreshbackendlive_wired
Advert Wall generator (register-honesty guarded)backendlive_wired
Advert Wall — 50 per-product advert pages + gallerybackendlive_wired
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 Suite, as a package.

backend

Advert Wall auto-refresh

refresh_adverts.sh: pulls live register, regenerates 51 advert pages, deploys to CF Pages only on real change.

verified

Advert Wall generator (register-honesty guarded)

generate_ads.py + products.json in ~/Documents/pharoah-suite: generates the 50 advert pages with prices honest

verified

Advert Wall — 50 per-product advert pages + gallery

50 per-product advert pages + gallery served on CF Pages pharoah-suite.pages.dev/ads/ — live-probed HTTP 200 o

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

A package reads like a control document.

Inside the scope

  • Advert Wall auto-refresh
  • Advert Wall generator (register-honesty guarded)

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 2 parts probe-verified, latest 9 September 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 (audience)

Who signs, and where the work sits

  • Pharoah Technology 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.

Anaïs AIgateway.pharoahtechnology.com
Anaïs AI (LLM router / reseller)anaisai.co.uk
Anaïs AI (working app)anaisai.co.uk
Pharoah TechnologyPharoah Suitepharoah-suite.pages.dev
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: audience. 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.