# WDF Demo Runbook — setup + script for the conceptualisation pitch

Everything data-side is already built & seeded. This covers the ~15 min of **UI setup** (clicks only
you can do) and the **demo script**. Logins: Twenty admin = `admin@wdf.co.za` / your password.

---

## PART A — Make Twenty look like a command centre (~15 min, one-time)

### A1. The 8-stage journey board (the centrepiece)
1. Open **Churches** (left sidebar).
2. Top-left view dropdown → **Add view** → choose **Kanban**.
3. **Group by → Journey Stage.** Name it **"Church Journey"**.
→ You now see churches as cards flowing across the 8 stages (Application → … → Released). *This is
the "process engine, not a CRM" money shot.*

### A2. A "Needs attention" church view
1. In Churches → **Add view → Table**, name it **"Needs Attention"**.
2. **Filter:** Status *is* Stuck/Overdue **or** At Risk.
3. **Sort:** Next Deadline ascending.
→ The room sees exactly what's slipping, worst-first.

### A3. The task board (you stressed this — it's wired)
1. Open **Tasks**.
2. **Add view → Kanban → Group by Status** → name it **"Field Tasks"** (To-do / In-progress).
3. Add a **Table view "By Priority"**: filter Priority *is* High, sort by Due date.
4. Show that each task opens to reveal its **linked church + responsible officer**.
→ Proves real orchestration: filter by priority/province, sort by due, grouped by status.

### A4. A dashboard (optional, strong visual)
1. **Dashboards** (sidebar) → **New dashboard "WDF National"**.
2. Add chart widgets from Churches: **count by Journey Stage** (funnel), **count by Province**,
   **sum of Payment Due**.
→ Leadership's at-a-glance national view.

### A5. Two role logins (object-level scoping — the licensed RLS is the next tier)
1. **Settings → Members → Invite by Link** → make a link for **National** and one for **Provincial**;
   open each link (incognito) and set a password. *(No email needed.)*
2. **Settings → Members → Roles → Create Role** "Provincial (EC)" → Permission tab → give **See** on
   Churches/Officers/Members/Tasks, **hide Settings**. Assign to the provincial user.
3. Mention: *"row-level 'only Eastern Cape' is Twenty Enterprise (the licence) — here's the Rules
   screen where it's set."* Show the scoped **result** via the portal if you want the visual.

---

## PART B — The demo script (what to click + say)

**Open with the problem (10 sec).** *"You're going into 6 provinces and can't watch every church.
Here's the system that watches it for you."*

1. **The journey board** (A1). *"Every church sits on one of 8 stages — from first application, through
   the R350 and R3,500 payments, compliance, provisioning, to support released. You see the whole
   rollout in one screen."* Drag a card forward to show movement.

2. **Needs Attention** (A2). *"And instantly — who's stuck, worst-first, with who's responsible."*

3. **The AI** (`wdf-chat.solune.co.za`). Ask: *"Which province is most behind, and who do I call
   first — name and phone?"* → it answers from the live data. *"Same brain runs on WhatsApp for the
   officers on the ground."*

4. **Tasks** (A3). *"Nobody hunts for work — the system pushes each officer their list, filtered and
   prioritised."*

5. **Roles** (A5). Log in as the Provincial user. *"Each person sees only their world — a provincial
   officer sees their province, a pastor only their church. That scoping is Twenty's Enterprise tier,
   which is in the platform licence."*

6. **The map / national view** (portal or dashboard). *"And leadership gets the national picture —
   every province, live."*

**Close.** *"This is ~80% standard platform configured to WDF, plus a few integrations — payments,
provisioning, the map. Here's the 8-stage spec; let's drill each stage together and lock what's in
Phase 1."* → opens the spec doc + the 7 WDF decisions.

---

## PART C — What we DON'T claim (keep trust)
- We don't move money (track + gate + bank export).
- We don't auto-file CIPC/SARS (track + prepare; staff submit).
- Row-level scoping = Twenty Enterprise licence (a cost line, not a hack).