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

The facts, from the register.

ProductPharoah FieldAssist
Register keyfieldassist
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atfieldassist.pharoahtechnology.co.uk · HTTP 200 on 9 September 2026
Price£7 a month · [object Object]
Built from6 register parts, 6 live, 4 probe-verified
Listed3 July 2026

What it does

Hands-free AR field-service HUD that runs web-first on any device — equipment ID, step-by-step guided procedures, live remote-expert annotation into the technician's view, and auto-generated service reports. Interactive demo live (camera POV + AI verify simulated; on-device CV for Meta Ray-Ban Display glasses + WebRTC expert video ship in Phase 2).

Runs on

Stripe payments
Cloudflare Pages + Netlify deploy
Expense Management
Meta Wearables in-lens HUD (web path)
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 field technician works from a paper manual with both hands full, then writes the service report hours later from memory.

Who carries it

Field service technicians working hands-free from equipment manuals

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

What it does instead.

Pharoah FieldAssist — web-first AR field-service HUD: guided procedures, live remote-expert annotation, auto-generated service reports. £7 per user per month.

Hands-free AR field-service HUD that runs web-first on any device — equipment ID, step-by-step guided procedures, live remote-expert annotation into the technician's view, and auto-generated service reports. Interactive demo live (camera POV + AI verify simulated; on-device CV for Meta Ray-Ban Display glasses + WebRTC expert video ship in Phase 2).

The parts doing the work

Stripe payments verified

Cloudflare Pages + Netlify deploy verified

One deploy/rollback pattern for all sites (distinct from the assemblable deploy block).

Expense Management

Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and reimbursement intents on the forge.invoicin

Meta Wearables in-lens HUD (web path) verified

Generic in-lens heads-up display for Ray-Ban Meta / Display via the Meta Wearables Device Access Toolkit (web path). Renders a data overlay (vitals, s

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

Proof it exists, not a roadmap.

200

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

4/6

register parts verified by probe

6

parts wired live

HTTP 200

functional surface probe

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

AxisWhere we stand
AR remote assistance (live video + annotation)not yet
Hands‑free step‑by‑step work instructionsnot yet
Smart glasses/HUD integrationlevel
Real‑time collaboration with remote expertnot yet
AI‑driven contextual guidancenot yet

Position

Reposition as a connected‑worker productivity suite that pairs field‑level HUD with meeting notes, expense tracking, and payments for frontline teams.

Evidence: capterra.com · librestream.com

Source: register vs_competition (9 September 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.

Field service technicians working hands-free from equipment manuals

Only we do

Universal meeting note taker (transcription + LLM‑generated notes)
Expense management (capture, approval, reimbursement, receipt handling)
Payments (Stripe integration)
Source: register audience, serves_niches, vs_competition ADJACENT (verified)One 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 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
Stripe paymentsbackendlive_wired
Cloudflare Pages + Netlify deployintegrationlive_wired
Expense Managementfull-stacklive
Meta Wearables in-lens HUD (web path)full-stacklive_wired
Meeting Note Taker — universal transcript→notes enginebackendlive
AI model router (LiteLLM ai-proxy-gateway)integrationlive_wired
Source: product_parts joined to builder_blocks · 6 of 6 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 FieldAssist, as a package.

backend

Stripe payments

verified

Meeting Note Taker — universal transcript→notes engine

ONE reusable engine closing the largest gap cluster (53 products needed "meeting note taker"). Reuses rail.llm

live
integration

Cloudflare Pages + Netlify deploy

One deploy/rollback pattern for all sites (distinct from the assemblable deploy block).

verified

AI model router (LiteLLM ai-proxy-gateway)

LiteLLM AI model router with pinned free/core aliases, cost-aware fallback routing, live health/model inventor

verified
full-stack

Expense Management

Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and rei

live

Meta Wearables in-lens HUD (web path)

Generic in-lens heads-up display for Ray-Ban Meta / Display via the Meta Wearables Device Access Toolkit (web

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

A package reads like a control document.

Inside the scope

  • Stripe payments
  • Cloudflare Pages + Netlify deploy
  • Meta Wearables in-lens HUD (web path)
  • AI model router (LiteLLM ai-proxy-gateway)

Evidenced, and how

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

Outside the scope today · work left

  • Verify integration with multiple smart‑glass platforms and edge deployment
  • Add AI‑driven contextual guidance engine (LLM‑based task‑aware prompts using live sensor/data)
  • Implement real‑time expert collaboration suite (video call, annotation, session control)
  • Create smart‑glass‑agnostic AR overlay SDK (support RealWear, HoloLens, etc.)
  • 2 parts still to verify by probe

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 6 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 FieldAssistfieldassist.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.

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.