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

The facts, from the register.

ProductBELLA — Property Management SaaS
Register keybella-property-management-saas
OwnerATTOH LTD (Companies House 14079382)
Live atattoh.casa/bella · HTTP 200 on 9 September 2026
Pricepriced at launch · REVERTED 2026-09-06 on owner correction: this is a DEMO built for a company, not a Pharoah product for sale. Do not price it. Priced in error earlier the same day.
Built from32 register parts, 32 live, 18 probe-verified
Listed14 August 2026

What it does

Property-management SaaS for UK letting agents — replaces the 2006 back-office (spreadsheets, manual compliance, reactive maintenance) with AI-native operations.

Runs on

Client Engine (white-label site generator)
Stripe payments
Estate agent (EstateAgentSnap)
Compliance monitor (ZARA)
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 Propertymark and RICS client-money rules.

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

Client money protected and reconciled

Check 2

AML checks before the deal, not after

Check 3

A redress trail for every instruction

Frame chosen by BRG as a summary of Propertymark and RICS client-money rules. 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.

Letting agents run compliance and maintenance on spreadsheets, so deadlines slip and problems are handled only after a tenant complains.

Who carries it

UK letting agents using property management SaaS to replace spreadsheets and manual compliance.

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

What it does instead.

BELLA replaces the 2006 letting-agent back office — spreadsheets, manual compliance, reactive maintenance — with an AI-native operations spine. Compliance, invoicing, tenant comms and document generation, wired to live UK property data.

Property-management SaaS for UK letting agents — replaces the 2006 back-office (spreadsheets, manual compliance, reactive maintenance) with AI-native operations.

The parts doing the work

Client Engine (white-label site generator) verified

BRG-owned client engine surface composed from the white-label site generator, config contract, client editor and approval-gated publish queue.

Stripe payments verified

Estate agent (EstateAgentSnap) verified

EstateAgentSnap — AML/KYC + OFSI sanctions + Client Money Protection + ombudsman + Right-to-Rent compliance, advisory calculators (SDLT/fees/deposit),

Compliance monitor (ZARA) verified

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

Proof it exists, not a roadmap.

200

HTTP status of attoh.casa/bella on 9 September 2026 · real-content-verified

18/32

register parts verified by probe

32

parts wired live

HTTP 200

functional surface probe

Open attoh.casa/bella 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: UK lettings and property management software. Nearest rivals: Arthur Online, Fixflo, Alto by Zoopla, Reapit, PayProp; strongest is Arthur among portfolio landlords. Our edge: rivals organise the tenancy but leave compliance dates in spreadsheets and diaries; we hold every renewal date and certificate (gas, EICR, EPC, deposit protection) as the primary object, so the thing that carries a fine is the thing the system is built around. How we beat them: per-unit pricing at the incumbents punishes growth; we price the portfolio.

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.

UK letting agents using property management SaaS to replace spreadsheets and manual compliance.

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.

Not in the register yet a price. This slide stays blank until the register carries it; nothing here is invented.

Basis: REVERTED 2026-09-06 on owner correction: this is a DEMO built for a company, not a Pharoah product for sale. Do not price it. Priced in error earlier the same day.

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
Client Engine (white-label site generator)uistaged
Stripe paymentsbackendstaged
Estate agent (EstateAgentSnap)full-stackstaged
Compliance monitor (ZARA)agentlive_wired
IR35 risk (SHIELD)agentlive_wired
Instant Company Report Enginebackendlive_wired
Flow-home (intelligence_feed)agentlive_wired
Land Registry overnight sweep aliasdatastaged
Site lead capturebackendstaged
Document Generation Engine (HTML + PDF)full-stackstaged
Source: product_parts joined to builder_blocks · 10 of 32 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 Propertymark and RICS client-money rules 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

BELLA, as a package.

ui

Client Engine (white-label site generator)

BRG-owned client engine surface composed from the white-label site generator, config contract, client editor a

verified

Client dashboard (portal modules)

14 intent-driven portal modules + accountability panels (live portal; block-wire pending)

verified
backend

Stripe payments

verified

Instant Company Report Engine

Type a Companies House number, every agent reports back. SQL engine: company_help_map(text) report builder + e

verified

Site lead capture

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

verified
full-stack

Estate agent (EstateAgentSnap)

EstateAgentSnap — AML/KYC + OFSI sanctions + Client Money Protection + ombudsman + Right-to-Rent compliance, a

verified

Document Generation Engine (HTML + PDF)

Universal template-driven document generation: one structural spec renders to print-ready HTML and real PDF (p

verified

Booking / scheduling engine

Generic booking/scheduling engine — exists 6x in vertical snaps; extract once into a modular block (the modula

verified
agent

Compliance monitor (ZARA)

verified

IR35 risk (SHIELD)

producing

verified

Flow-home (intelligence_feed)

verified
data

Land Registry overnight sweep alias

Scalar register_coverage alias over data.land-registry for the proven 2026-07-06 HM Land Registry PPD overnigh

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

A package reads like a control document.

Inside the scope

  • Client Engine (white-label site generator)
  • Stripe payments
  • Estate agent (EstateAgentSnap)
  • Compliance monitor (ZARA)
  • IR35 risk (SHIELD)

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 18 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
  • 14 parts still to verify by probe
  • 1 register field to fill (price_gbp)

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 0 build packets proposed · 15 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/
ATTOHBELLAattoh.casa/bella
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.
FramePropertymark and RICS client-money rules. 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 Propertymark and RICS client-money rules; 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: price_gbp. 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.