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

The facts, from the register.

ProductPharoah Access
Register keypharoah-access
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live ataccess.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£7 a month · [object Object]
Built from1 register parts, 1 live, 1 probe-verified

What it does

Pharoah Access provides a formal process for granting and reviewing access to estates and systems. It is designed for organisations that need controlled, auditable entry to their assets, replacing informal, unreviewed methods with structured approval and periodic checks.

Runs on

Pharoah Access estate launcher
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 Propertymark and RICS client-money rules.

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

Client money protected and reconciled

Check 2

AML checks before the deal, not after

Check 3

A redress trail for every instruction

Frame chosen by BRG as a summary of Propertymark and RICS client-money rules. 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.

Access to estates and systems is granted informally and never reviewed.

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

What it does instead.

Formally grants access to estates and systems and conducts reviews.

Pharoah Access provides a formal process for granting and reviewing access to estates and systems. It is designed for organisations that need controlled, auditable entry to their assets, replacing informal, unreviewed methods with structured approval and periodic checks.

The parts doing the work

Pharoah Access estate launcher verified

Static single-page launcher (CF worker) — Phil's single door to every build, system and engine. Tile grid of links to auth-walled dashboards; no secre

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

Proof it exists, not a roadmap.

200

HTTP status of access.pharoahtechnology.com on 9 September 2026 · real-content-verified

1/1

register parts verified by probe

1

parts wired live

HTTP 200

functional surface probe

Open access.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.

Category: identity governance and access review. Nearest rivals: Okta, JumpCloud, Microsoft Entra ID Governance, SailPoint, Rippling IT; strongest is Okta. Our edge: rivals are identity providers first and treat access review as a governance module for enterprises with a dedicated IAM owner; we answer the two questions a small business actually has, which are who can reach what and how to take it away the day someone leaves. How we beat them: leaver risk is immediate and universal, while a full IAM deployment is a project most of this market never starts.

Not independently sourced This verdict was written from an analysis whose only source was the model itself, not scraped competitors (analyst pharoah). 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.

£7 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.

PartCategoryStateVerified
Pharoah Access estate launcheruilive_wired
Source: product_parts joined to builder_blocks · 1 of 1 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 Propertymark and RICS client-money rules 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 Access, as a package.

ui

Pharoah Access estate launcher

Static single-page launcher (CF worker) — Phil's single door to every build, system and engine. Tile grid of l

verified
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

  • Pharoah Access estate launcher

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 1 parts probe-verified, latest 10 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
  • 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
  • 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 Accessaccess.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
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.
FramePropertymark and RICS client-money rules. 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 Propertymark and RICS client-money rules; 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.