All decks
ReceiptSnapATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductReceiptSnap
Register keyreceiptsnap
OwnerATTOH LTD (Companies House 14079382)
Live atattoh.digital/snap/receiptsnap · HTTP 200 on 9 September 2026
Price£39 a month
Built from5 register parts, 5 live, 5 probe-verified
Listed14 August 2026

What it does

Turns a pile of receipts into a VAT return line you can actually file.

Runs on

Accounting OS
Site lead capture
SnapTools Governance Spine — the Governor choke-point pattern
Stripe payments
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.

Reclaimable VAT sits in a shoebox of receipts and gets written off at quarter end because nobody has time to sort it.

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

What it does instead.

ReceiptSnap exists to solve: Reclaimable VAT sits in a shoebox of receipts and gets written off at quarter end because nobody has time to sort it.

Turns a pile of receipts into a VAT return line you can actually file.

The parts doing the work

Accounting OS verified

BookSnap + accountant channel portal

Site lead capture verified

Public Supabase edge fn (honeypot, CORS, service-role) -> partner_site_leads, tagged by site_slug. Every white-label site form posts here; intel flows

SnapTools Governance Spine — the Governor choke-point pattern verified

Shared governance routes mounted across ALL SnapTools backends: /governance/payment-gate, /human-approval-gate, /robot-workflow-gate, /future-readines

Stripe payments verified

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

Proof it exists, not a roadmap.

200

HTTP status of attoh.digital/snap/receiptsnap on 9 September 2026 · real-content-verified

5/5

register parts verified by probe

5

parts wired live

HTTP 200

functional surface probe

Open attoh.digital/snap/receiptsnap 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.

Audit 2026-07-16 FURTHEST: Wave-2 skeleton, one live rule-based categoriser + wired-but-unpersisted Claude OCR. Misses accounting export, evidence vault, bank fetch, capture client.

Evidence: client.

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

£39 a month

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
Accounting OSfull-stackstaged
Site lead capturebackendlive_wired
SnapTools Governance Spine — the Governor choke-point patternbackendlive_wired
Stripe paymentsbackendlive_wired
White-label site enginebackendlive_wired
Source: product_parts joined to builder_blocks · 5 of 5 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

ReceiptSnap, as a package.

full-stack

Accounting OS

BookSnap + accountant channel portal

verified
backend

Site lead capture

Public Supabase edge fn (honeypot, CORS, service-role) -> partner_site_leads, tagged by site_slug. Every white

verified

SnapTools Governance Spine — the Governor choke-point pattern

Shared governance routes mounted across ALL SnapTools backends: /governance/payment-gate, /human-approval-gate

verified

Stripe payments

verified

White-label site engine

One renderer for many branded client sites; live tenant Pages proof plus source contract and publish queue gua

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

A package reads like a control document.

Inside the scope

  • Accounting OS
  • Site lead capture
  • SnapTools Governance Spine — the Governor choke-point pattern
  • Stripe payments
  • White-label site engine

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 5 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
  • 2 register fields to fill (vs_competition_unsourced, audience)

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.

A1 Elitea1elite.pages.dev
Accounts & Filingattoh.tech/accounts-law/
AddressSnapattoh.digital/snap/addresssnap/
ATTOHReceiptSnapattoh.digital/snap/receiptsnap
AIEmploymentattoh.tech/aiemployment/
AIFreightaifreight.uk
AITransportaitransport.uk
Source: register rows sharing client_key attohOne 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.
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 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.