All decks
Pharoah TradeSnap (Pharoah skin)ATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductPharoah TradeSnap (Pharoah skin)
Register keypharoah-trade
OwnerATTOH LTD (Companies House 14079382)
Live attrade.pharoahtechnology.co.uk · HTTP 200 on 9 September 2026
Price£89 one-off
Built from1 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

Pharoah TradeSnap (Pharoah skin)
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 CIPP Payroll Assurance Scheme.

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

Controls that reduce the potential for error

Check 2

Processes fit for the employer's requirements

Check 3

Preparation for legislative change

Frame chosen by BRG as a summary of the CIPP Payroll Assurance Scheme. 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.

Contractors deduct 20% CIS at source. The money sits with HMRC for up to a year and most subcontractors never work out what they are actually owed back.

Who carries it

Subcontractors in the UK construction industry needing to recover CIS deductions

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

What it does instead.

Pharoah-skinned door onto the TradeSnap engine (Phil parity doctrine: same product, own skin). It exists to solve: Contractors deduct 20% CIS at source. The money sits with HMRC for up to a year and most subcontractors never work out what they are actually owed back.

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

Pharoah TradeSnap (Pharoah skin)

Root block for Pharoah TradeSnap (Pharoah skin) — created so the app cannot be invisible. Probe settles its real maturity.

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 trade.pharoahtechnology.co.uk on 9 September 2026 · real-content-verified

0/1

register parts verified by probe

1

parts wired live

HTTP 200

functional surface probe

Open trade.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: HMRC CIS guidance class. Nearest rivals: HMRC CIS guidance, Crunch, FreeAgent, QuickBooks Self-Employed, Grunt; strongest is FreeAgent among UK sole traders. Our edge: Accounting tools handle the books once you already understand CIS, and HMRC publishes the rules rather than the answer. The trade wants one number — what lands in the bank after deductions. How we beat them: Free and instant on the number that matters, rather than a bookkeeping subscription that assumes the CIS position is already understood. Source: written 2026-08-30 from the product's own live page, observed this session.

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.

Subcontractors in the UK construction industry needing to recover CIS deductions

Niches

construction

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.

£89 one-off

Buying route

Payment on enquiry
Delivered from the live product
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 TradeSnap (Pharoah skin)full-stackbuilt
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 the CIPP Payroll Assurance Scheme 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 TradeSnap (Pharoah skin), as a package.

full-stack

Pharoah TradeSnap (Pharoah skin)

Root block for Pharoah TradeSnap (Pharoah skin) — created so the app cannot be invisible. Probe settles its re

built
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 TradeSnap (Pharoah skin)

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

  • No build gap recorded in the register
  • 1 part still to verify by probe
  • 1 register field to fill (public_blurb)

Who signs, and where the work sits

  • ATTOH 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.

Pharaoh Sovereign CEOsovereign.pharoahtechnology.co.uk
Pharoah AIEmployment door (Pharoah skin)employment.pharoahtechnology.com
Pharoah AIFreight door (Pharoah skin)logistics.pharoahtechnology.com
ATTOHPharoah TradeSnap (Pharoah skin)trade.pharoahtechnology.co.uk
Pharoah Autoauto.pharoahtechnology.co.uk
Pharoah BLACKLINE door (Pharoah skin)blackline.pharoahtechnology.com
Pharoah BOQ Pricer (Pharoah skin)boq.pharoahtechnology.com
Source: register rows sharing client_key One 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 CIPP Payroll Assurance Scheme. Verify the wording of the three checks with the body before external use.
BrandATTOH 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 CIPP Payroll Assurance Scheme; 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.