01Pharoah Technology · App Builderlive
Pharoah App Builder
Pharoah-branded partner App Builder skin/wearer that reuses the shared BRG/ATTOH builder engine and infrastructure rather than owning a separate engine.
Live · builder.pharoahtechnology.com/build36 parts · 14 probe-verified
Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)builder.pharoahtechnology.com/build
02What it is
The facts, from the register.
| Product | Pharoah App Builder |
| Register key | pharoah-app-builder |
| Owner | Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50) · powered by app-builder |
| Live at | builder.pharoahtechnology.com/build · HTTP 200 on 9 September 2026 |
| Price | priced at launch · [object Object] |
| Built from | 36 register parts, 36 live, 14 probe-verified |
What it does
Assembles app pages from proven Pharoah blocks instead of inventing a fresh build each time. It shows the preview, checks the route, and keeps the shared ATTOH engine behind the Pharoah-facing product.
Runs on
Stripe payments
Tenant site snapshot test
Supabase auth
Client Engine (white-label site generator)
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 Construction Playbook and CDM 2015.
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
Programme and cost certainty before commitment
Check 2
Duty-holder and site records kept current
Check 3
Supply chain verified before it is paid
Frame chosen by BRG as a summary of the Construction Playbook and CDM 2015. 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.
Every app starts from zero because the parts already built are invisible to the next build.
Who carries it
Pharoah Technology / Phil partner lane and its downstream app-building customers.
Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose
What it does instead.
Pharoah-branded partner App Builder skin/wearer that reuses the shared BRG/ATTOH builder engine and infrastructure rather than owning a separate engine.
Assembles app pages from proven Pharoah blocks instead of inventing a fresh build each time. It shows the preview, checks the route, and keeps the shared ATTOH engine behind the Pharoah-facing product.
The parts doing the work
Tenant site snapshot test verified
Proof harness covering config contract, generated outputs, deterministic rebuilds and public no-write Pages smokes for tenant sites.
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.
Source: register purpose, public_blurb, product_parts joined to builder_blocks4 of 36 parts shown
06Why it's better · 3 of 6Check 1 · controls
Proof it exists, not a roadmap.
200
HTTP status of builder.pharoahtechnology.com/build on 9 September 2026 · real-content-verified
14/36
register parts verified by probe
42%
readiness, register-computed
Open builder.pharoahtechnology.com/build 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.
[PARITY] Top-5: Bubble ($29-349/mo), Retool ($10-50/user/mo), Glide ($199+/mo Business), Softr ($49-269/mo). All are MANUAL drag-drop/block builders - the human still assembles every screen. app-builder's real edge: assemble_app + materialise_app RPCs auto-ASSEMBLE apps from a 893-block parts-shop (reuse-first), not manual dragging - AI-native composition vs manual construction. At £49-59/mo it sits inside the Bubble Starter-Growth / Softr band. Honest loss: Bubble/Retool have years of ecosystem maturity, plugins, and a huge builder community this can't match yet.
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_competition (18 August 2026)Named 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.
Pharoah Technology / Phil partner lane and its downstream app-building customers.
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: [object Object]
Buying route
Payment on enquiry
skinned-premium
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.
| Part | Category | State | Verified |
|---|
| Stripe payments | backend | live_wired | |
| Tenant site snapshot test | integration | staged | |
| Supabase auth | backend | live_wired | |
| Client Engine (white-label site generator) | ui | staged | |
| Site publish queue consumer | backend | staged | |
| App Builder — self-completing block generator | backend | live_wired | |
| App Builder — materialiser | full-stack | live_wired | |
| Partner site generator alias | backend | staged | |
| White-label site generator alias | backend | staged | |
| App Builder — parts-catalogue assembler | full-stack | live_wired | |
Source: product_parts joined to builder_blocks · 10 of 36 shown probe-verified not yet
11Why packaging matters
Bought as a price.
Delivered as a scope.
What the buyer hears
a price
A number to compare with the last number.
the gap
disputes · churn
unpaid work
What the provider means
A scope
36 parts, some verified, some not, plus everything that is excluded.
Packaging is the instrument that makes the scope as visible as the price.Thesis
12Why packaging matters
Five things a package does that a price cannot.
1Scope becomes visible. The parts are named, so nothing is assumed.
2Boundaries are explicit. What is outside is written down before the first invoice.
3It is auditable. A package is a documented process, which is what the Construction Playbook and CDM 2015 looks for.
4Buyers compare like for like. A referral needs a defined thing to refer.
5Switching 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 App Builder, as a package.
backend
Site publish queue consumer
Approval-gated site-editor task consumer that validates DB configs and rebuilds source without deploying or by
verifiedApp Builder — self-completing block generator
Gap-detection -> clone-and-scaffold -> LLM-enrich: emits spec blocks for missing capabilities (never live fake
verifiedintegration
Tenant site snapshot test
Proof harness covering config contract, generated outputs, deterministic rebuilds and public no-write Pages sm
verifiedInfisical shared-secret-vault
Every deploy's secrets — check the vault before asking for keys.
live_orphanedui
Client Engine (white-label site generator)
BRG-owned client engine surface composed from the white-label site generator, config contract, client editor a
verifiedfull-stack
App Builder — materialiser
Post-approval: provisions builder_projects + builder_pages, binds agent_hooks (ships-alive), generates thin gl
verifiedApp Builder — parts-catalogue assembler
Intent->resolve->wire->plan: maps a plain-English prompt to live capability blocks and emits a validated, gap-
verifieddata
Tenant-scoped data (RLS)
live_orphanedSource: product_parts grouped by builder_blocks.category5 groups
14Anatomy of the packageOn one page · 25 items of work left, filed
A package reads like a control document.
Inside the scope
- Stripe payments
- Tenant site snapshot test
- Supabase auth
- Client Engine (white-label site generator)
- Site publish queue consumer
Evidenced, and how
- Live URL probed: HTTP 200 on 9 September 2026
- 14 parts probe-verified, latest 9 September 2026
- Register row updated with every probe
Outside the scope today · work left
- Reconcile the historical inert/live=false partner proof with the currently reachable surface, prove the actual
- 22 parts still to verify by probe
- 2 register fields to fill (vs_competition_unsourced, price_gbp)
Who signs, and where the work sits
- Pharoah Technology Ltd owns the product and the data layer
- 1 build packet proposed · 24 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.
Anaïs AIgateway.pharoahtechnology.com
Anaïs AI (LLM router / reseller)anaisai.co.uk
Anaïs AI (working app)anaisai.co.uk
Pharoah TechnologyPharoah App Builderbuilder.pharoahtechnology.com/build
ATS Résumé Scanner (free)ats.pharoahtechnology.com
Aurora AIauroraai.pharoahtechnology.com
Aurora Guardauroraguard.co.uk
Source: register rows sharing client_key pharoahOne house, many doors
16Close
Three things to take back to your desk.
One
Open the URL on slide 6. Test it before you trust it.
Two
The parts and their verification state are on slide 10.
Three
A package is a compliance instrument, not a price list.
See it live
builder.pharoahtechnology.com/build
Talk to us
via builder.pharoahtechnology.com/build
Pharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)Pharoah Technology