All decks
GFYM / Gym App OSATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductGFYM / Gym App OS
Register keygym-app-os
OwnerATTOH LTD (Companies House 14079382)
Live atamaya-app.vercel.app · HTTP 200 on 9 September 2026
Price£99 a month
Built from2 register parts, 2 live, 2 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

GFYM / Gym App OS Proof Pack
Memberships & Class Booking
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.

Gyms run memberships and class bookings on separate tools that never reconcile.

Who carries it

Fitness creators/influencers and their audiences; first vertical before Creator OS generalisation.

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

What it does instead.

Fitness-creator operating system combining a consumer app, agent-run content engine, lead funnel and future Creator OS/payroll generalisation; explicitly not a gym-management/booking/payments product.

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

GFYM / Gym App OS Proof Pack verified

Normalises GFYM to Gym App OS and assembles source packet, 16-case API smoke, fake live-row proof, SQL 433/RLS, inactive workflow, safe import row, op

Memberships & Class Booking verified

Recurring memberships and capacity-limited classes for a business's own customers. Plans with per-period class credits (NULL = unlimited, distinct fro

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

Proof it exists, not a roadmap.

200

HTTP status of amaya-app.vercel.app on 9 September 2026 · real-content-verified

2/2

register parts verified by probe

2

parts wired live

HTTP 200

functional surface probe

Open amaya-app.vercel.app 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: gym member apps and booking. Nearest rivals: Mindbody, Glofox, TeamUp, Gymcatch, ABC Trainerize; strongest is Mindbody on installed base. Our edge: rivals put the gym inside a shared marketplace app where members can see competing studios; we give the gym its own branded member app and booking, so the relationship is not intermediated. How we beat them: marketplace platforms monetise member discovery across gyms, which is a direct conflict for the operator paying the subscription.

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.

Fitness creators/influencers and their audiences; first vertical before Creator OS generalisation.

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.

£99 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
GFYM / Gym App OS Proof Packfull-stackstaged
Memberships & Class Bookingfull-stacklive_orphaned
Source: product_parts joined to builder_blocks · 2 of 2 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

GFYM / Gym App OS, as a package.

full-stack

GFYM / Gym App OS Proof Pack

Normalises GFYM to Gym App OS and assembles source packet, 16-case API smoke, fake live-row proof, SQL 433/RLS

verified

Memberships & Class Booking

Recurring memberships and capacity-limited classes for a business's own customers. Plans with per-period class

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

  • GFYM / Gym App OS Proof Pack
  • Memberships & Class Booking

Evidenced, and how

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

Outside the scope today · work left

  • Replace/approve the credit-funnel-shaped SQL 433 schema; prove enrichment/report completion; import and execut
  • 1 register field to fill (public_blurb)

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 1 build packet 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/
ATTOHGFYM / Gym App OSamaya-app.vercel.app
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 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.