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

The facts, from the register.

ProductHaulageSnap
Register keyhaulagesnap
OwnerATTOH LTD (Companies House 14079382)
Live atattoh.digital/snap/haulagesnap · HTTP 200 on 9 September 2026
Price£199 one-off
Built from5 register parts, 5 live, 5 probe-verified
Listed14 August 2026

What it does

Margin per mile on every run, plus the driver compliance dates that cost you the licence if missed.

Runs on

Site lead capture
Logistics (FreightSnap/HaulageSnap)
Stripe payments
SnapTools Governance Spine — the Governor choke-point pattern
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 DVSA operator-licence undertakings.

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

Vehicle and driver records kept current

Check 2

Hours and maintenance evidenced

Check 3

Incidents traceable to a decision

Frame chosen by BRG as a summary of the DVSA operator-licence undertakings. 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.

Operators quote by the job and only discover at year end which runs lost money. Fuel, driver hours and empty return legs never make it into the price.

Who carries it

Haulage operators who need accurate per‑mile margin and driver compliance tracking

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

What it does instead.

HaulageSnap exists to solve: Operators quote by the job and only discover at year end which runs lost money. Fuel, driver hours and empty return legs never make it into the price.

Margin per mile on every run, plus the driver compliance dates that cost you the licence if missed.

The parts doing the work

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

Logistics (FreightSnap/HaulageSnap) verified

Freight/Haulage — dispatch + fleet + tracking (frontend)

Stripe payments verified

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

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/haulagesnap 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/haulagesnap 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.

VOID 2026-07-30 — the 2026-07-16 architecture verdict is STALE and was removed, not relabelled. It called this a lead-magnet decision-quiz API; live code contradicts that — it has a snap_core ledger port, require_user tenant scoping and 10 test files incl. tenant-isolation tests (verified in _modules/snaptools/ on origin/main f451ae23). NO competitive verdict is asserted here: the old one is void, and a new one is NOT invented. Re-audit against the 5 named rivals before any beats-all or sellable claim. Prior text preserved in _preserve_stale_vscomp_20260730.

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.

Haulage operators who need accurate per‑mile margin and driver compliance tracking

Niches

haulage · freight

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.

£199 one-off

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
Site lead capturebackendlive_wired
Logistics (FreightSnap/HaulageSnap)full-stackspec
Stripe paymentsbackendlive_wired
SnapTools Governance Spine — the Governor choke-point patternbackendlive_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 DVSA operator-licence undertakings 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

HaulageSnap, as a package.

backend

Site lead capture

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

verified

Stripe payments

verified

SnapTools Governance Spine — the Governor choke-point pattern

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

verified

White-label site engine

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

verified
full-stack

Logistics (FreightSnap/HaulageSnap)

Freight/Haulage — dispatch + fleet + tracking (frontend)

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

A package reads like a control document.

Inside the scope

  • Site lead capture
  • Logistics (FreightSnap/HaulageSnap)
  • Stripe payments
  • SnapTools Governance Spine — the Governor choke-point pattern
  • White-label site engine

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 5 parts probe-verified, latest 22 June 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 register field to fill (vs_competition_unsourced)

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 0 build packets proposed · 1 management item 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/
ATTOHHaulageSnapattoh.digital/snap/haulagesnap
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 DVSA operator-licence undertakings. 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 DVSA operator-licence undertakings; 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.