Internal Live: 2 April 2026Public Launch: Mid April 2026Today: 23 March 2026Layered build strategy applied
Overall completion0%
0
Done
0
Total
0
Remaining
01
Visual Roadmap
Layered build strategy
Three-layer strategy: Layer 1 (structural core) is non-negotiable and built first. Layer 2 items are stubbed in Airtable now but automated later. Layer 3 is deferred entirely until there is a proven use case. This gets PPN operational by 2 April while keeping build scope tight and risk low.
Early Event form opportunity: The Event Request form can go live as soon as Tally is configured and Airtable exists — even before the Match Engine is built. Submissions write to Airtable via Tally webhook. Lou & Katie work the queue manually until automation is ready. This could mean real leads arriving from around 28 March.
02
Go-Live Checklist
Click to mark complete
Phase X items are shown for reference but are not included in the progress count.
Now — 27 Mar
Phase 0 — Decisions & Setup
Pre-build
▶
Design & Branding
Confirm Tally white-label settings
Logo, primary colour, custom domain if applicable. Seamless theme used as placeholder until PPN brand is ready.
Tally
Agree remaining open design decisions
Supplier threshold before Event form goes public. Score suppression logic. Ops runbook owner.
Design
Accounts & Access
Create Airtable workspace & base — Pro plan
$24/mo. Invite Lou, Katie, Seamless as collaborators.
Airtable
Create Make.com account — Core plan
$9/mo. Covers all Phase 1–2 scenarios. Connect to Airtable.
Suppliers CC this when quoting. Forward to Lou's inbox. Connect to Make via OAuth.
Gmail
Generate Airtable Personal Access Token
Scopes: schema.bases:read/write, data.records:read/write. Store securely — never expose client-side.
Airtable
Connect Airtable MCP to Claude
Settings → Connectors. Enables direct schema build from this conversation.
Airtable
Connect Make MCP to Claude
Settings → Connectors. Enables scenario building from this conversation.
Make
Connect Tally MCP to Claude
Settings → Connectors via OAuth. Enables form building from this conversation.
Tally
Legal & Compliance
Draft Privacy Policy for PPN
Must cover data collected, sharing with suppliers, retention, right to deletion. Required before any form goes public. Use Iubenda or Termly for speed.
Check for failed runs every morning. Resolve before they compound. Set up email alerts for failures.
Make
Create Phase X backlog (Airtable table or Notion)
Single place to capture enhancement requests from Lou, Katie, and early users. Review monthly.
Design
Post-launch
Phase X — Deferred Features
Layer 3 · not counted
▶
Communications
WhatsApp Business API — register dedicated number
Requires Meta Business verification (allow 1–2 weeks when ready). Decide: existing PrePitched number or new PPN number.
Phase X
Make — WhatsApp notification module
Add WhatsApp send step after every email trigger. Comms_Preference field controls routing. SMS fallback via Twilio.
Phase X
Portal
Softr — Supplier dashboard
Quotes, referrals, commission history, activity feed. Contacts table is the Softr user directory — already built and ready.
Phase X
Softr — Organiser portal
For repeat/multi-event organisers. Enable Portal_Enabled on Events Contacts when triggered.
Phase X
Update action_base_url Data Store → Softr URLs
Single variable change. All 14 email CTAs update simultaneously. No scenario rebuilding needed.
Phase X
Scoring & Incentives
Activate Supplier_Score — surface in views and Softr
Fields already built from Phase 1. Enable once minimum 3 reviews per supplier exist (~Month 2–3).
Phase X
Score-based subscription discounts
Score ≥ 85 → 10% off monthly fee. Add Score_Discount_Pct formula to Subscriptions table.
Phase X
Match priority by Supplier_Score
Make Match Engine sorts matched suppliers by score before sending ITQs. Top scorers get first pick.
Phase X
Ops
Write internal ops runbook
How to: manually process an enquiry if Make fails, check Honesty Loop queue, apply referral credits, handle commission disputes. Essential before Katie's maternity leave (Aug 2026).
Phase X
03
Testing Protocols
Industry standard
Focus area for PPN: Data integrity and automation reliability, not load testing. The real risk is silent failures — a scenario that doesn't fire, a formula that calculates incorrectly — discovered only when a supplier complains. Test the edges, not the middle.
Smoke Test
Run immediately after every build session. One test record through each form, confirm it appears in Airtable with correct values. Takes 10 minutes. Do it every time.
Regression Test
Run after any schema change. Re-run the end-to-end flow to confirm existing automations still work. Adding a new field can break a Make module that references a fixed field index.
UAT
Lou & Katie use the system as real users — no guidance, no prompts — and note anything confusing, missing, or broken. 2 April internal live week. Budget 2 hours. Record feedback formally.
Boundary Test
Test edge cases: supplier with no postcode, event with identical duplicate key, quote with no referral, Honesty Loop for a cancelled event. Systems break at boundaries, not in the middle.
04
Risk Register
Flagged items in amber
Risk
Likelihood
Impact
Mitigation
Privacy Policy not ready by public launch Forms legally cannot go public without it
High
Blocker
Start drafting this week. Use Iubenda or Termly for speed — customise later.
Katie maternity leave (Aug 2026) Key operational knowledge leaving the business
Certain
Medium
Write ops runbook before August. Airtable views should be self-explanatory for a new operator.
Supplier non-compliance with Honesty Loop Commission goes uncollected silently
Airtable API key exposed client-side Tag suggestion fetch uses client-side JS in form mockup
Medium
High
Proxy via Make webhook. Form calls Make, Make calls Airtable. API key stays server-side.
Chicken & egg — insufficient suppliers at launch Events submit with no one to match
Medium
Medium
Open Supplier onboarding first. Set a minimum threshold (10–15) before Event form goes public.
Make scenario silent failure Email not sent, record not updated — no alert
Medium
Medium
Enable Make error alerts by email. Daily 5-min log check from day one.
Tally / Airtable field mismatch after schema change Webhook mappings break silently
Low
Medium
Finalise Airtable schema before building Tally forms. Any post-build addition requires re-checking webhook map.
05
Outstanding Design Decisions
Resolve before build
These must be resolved before Tally forms and public-facing output can be finalised. They do not block the Airtable schema build, which can start immediately.
PPN Brand Colours & Logo
Seamless theme is the current placeholder. Tally white-label and Softr portal need real brand colours, logo, and font. When available: provide hex codes + logo file. Forms and portal will be updated in one session.
Minimum Supplier Threshold Before Event Form Goes Public
How many active, onboarded suppliers are needed before the Event Request form opens? Recommended: 10–15 covering a spread of UK regions. Prevents organisers submitting with no one to match — which damages trust on first contact.
Supplier Score — Suppression Until Data Exists
Score fields are built from Phase 1 so data accumulates. Confirm: suppress score from any supplier-facing view until a minimum of 3 reviews per supplier exist (approximately Month 2–3).
Ops Runbook — Owner & Timeline
A short internal document covering how to manually handle enquiries if Make fails, how to check the Honesty Loop queue, how to apply referral credits, and what to do if a supplier disputes a commission. Must exist before Katie's maternity leave in August 2026. Who writes the first draft?