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

The facts, from the register.

ProductZivo
Register keyzivo
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50)
Live atzivo.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£399 a month
Built from8 register parts, 8 live, 6 probe-verified
Listed3 July 2026

What it does

A WhatsApp AI sales agent that answers customer enquiries from your own product catalogue, so quotes never drift from your listed prices. Try the live demo in the browser; v1 ships as a simulator before live WhatsApp sending.

Runs on

WhatsApp delivery rail
Stripe payments
First-party site analytics beacon
Expense Management
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.

Compliance monitoring reports problems after they have happened instead of preventing them.

Who carries it

SMEs handling customer sales enquiries over WhatsApp from a fixed product catalogue

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

What it does instead.

Zivo turns your WhatsApp number into an AI sales agent that quotes from your catalogue, books orders, and qualifies leads — 24/7, zero hallucinated prices.

A WhatsApp AI sales agent that answers customer enquiries from your own product catalogue, so quotes never drift from your listed prices. Try the live demo in the browser; v1 ships as a simulator before live WhatsApp sending.

The parts doing the work

WhatsApp delivery rail verified

WhatsApp group delivery + MAYA routing rail. Twilio inbound webhook -> wa_group_messages (idempotent ingest) -> dedupe gate -> MAYA intent route -> in

Stripe payments verified

First-party site analytics beacon verified

Public web-beacon edge fn (ofcjggvruhwhaqthdwxa/functions/v1/web-beacon, v3) + client tracker in Attoh _hubs/_shared/site-system.js initAnalytics() an

Expense Management

Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and reimbursement intents on the forge.invoicin

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

Proof it exists, not a roadmap.

200

HTTP status of zivo.pharoahtechnology.com on 9 September 2026 · real-content-verified

6/8

register parts verified by probe

8

parts wired live

HTTP 200

functional surface probe

Open zivo.pharoahtechnology.com 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: WhatsApp commerce and conversational sales. Nearest rivals: Wati, Interakt, Zoko, Charles, 360dialog; strongest is Wati among SMBs. Our edge: rivals sell an inbox and broadcast tooling that a human still has to staff — Zivo answers, quotes only from your catalogue and takes the deposit unattended, with catalogue-locked pricing so it cannot invent a price you do not offer. How we beat them: those tools price per seat and per conversation; we price the outcome at GBP399/mo flat for a number that sells overnight, and the catalogue guardrail is the thing none of them will promise.

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.

SMEs handling customer sales enquiries over WhatsApp from a fixed product catalogue

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.

£399 a month

Buying route

Payment link live
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
WhatsApp delivery railintegrationlive_wired
Stripe paymentsbackendlive_wired
First-party site analytics beaconintegrationlive_wired
Expense Managementfull-stacklive
Meeting Note Taker — universal transcript→notes enginebackendlive
Supabase + RLSintegrationlive_wired
AI model router (LiteLLM ai-proxy-gateway)integrationlive_wired
AI catalogue-locked price guardbackendlive_wired
Source: product_parts joined to builder_blocks · 8 of 8 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

Zivo, as a package.

integration

WhatsApp delivery rail

WhatsApp group delivery + MAYA routing rail. Twilio inbound webhook -> wa_group_messages (idempotent ingest) -

verified

First-party site analytics beacon

Public web-beacon edge fn (ofcjggvruhwhaqthdwxa/functions/v1/web-beacon, v3) + client tracker in Attoh _hubs/_

verified

Supabase + RLS

Multi-tenant Postgres rail with forced RLS, policy-derived least privilege, born-safe DDL and reviewed client

verified

AI model router (LiteLLM ai-proxy-gateway)

LiteLLM AI model router with pinned free/core aliases, cost-aware fallback routing, live health/model inventor

verified
backend

Stripe payments

verified

Meeting Note Taker — universal transcript→notes engine

ONE reusable engine closing the largest gap cluster (53 products needed "meeting note taker"). Reuses rail.llm

live

AI catalogue-locked price guard

Dual-layer compliance for AI sales replies: the prompt asks the model to stay catalogue-locked, this makes it

verified
full-stack

Expense Management

Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and rei

live
Source: product_parts grouped by builder_blocks.category3 groups
14Anatomy of the packageOn one page · 3 items of work left, filed

A package reads like a control document.

Inside the scope

  • WhatsApp delivery rail
  • Stripe payments
  • First-party site analytics beacon
  • Supabase + RLS
  • AI model router (LiteLLM ai-proxy-gateway)

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 6 parts probe-verified, latest 16 July 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 parts still to verify by probe
  • 1 register field to fill (vs_competition_unsourced)

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 0 build packets proposed · 3 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 TechnologyZivozivo.pharoahtechnology.com
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
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.
BrandPharoah Technology 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.

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.