How your bootcamp automation is built

01Overview

The PBC system runs Premiere Bootcamp events across four regions, each with up to six scheduled dates at any time. Its defining feature: an admin changes any event's date, time, or venue from one form, and every downstream email, reminder, and registration page updates itself.

The build separates the data (event dates and details) from the logic (registration, reminders, payments). Dates live in one place; everything else reads from there. That separation is what keeps the system maintainable and lets it scale to new regions or events.

This page is the plain-English overview. To see every workflow, open its flow diagram, and trace each tag, custom value, field and funnel both ways (which workflow uses it, and what it touches), use the live dashboard:

02Connection map

This diagram shows how the whole system connects, end to end. Custom values (event data) sit at the centre; the per-event tag applied at registration is the switch that starts the reminder and payment journeys.

flowchart TD
  %% Paul AI Solutions Mermaid standard palette (node-type colours)
  classDef trigger fill:#00E5FF,stroke:#0490a8,color:#04323a,font-weight:bold;
  classDef wf fill:#ffffff,stroke:#052848,color:#052848;
  classDef data fill:#052848,stroke:#052848,color:#ffffff,font-weight:bold;
  classDef wait fill:#A78BFA,stroke:#7c5fd0,color:#1f1340;
  classDef tag fill:#FFB400,stroke:#c98f00,color:#3a2a00,font-weight:bold;
  classDef done fill:#34D399,stroke:#1f9d72,color:#053a28,font-weight:bold;

  ADMIN["Admin: Event Update Form"]:::trigger --> UCV["Update Custom Values
REGION 1-6"]:::wf
  CVUF["Funnel: PBC Event Dates - CV Update"]:::trigger --> ADMIN
  UCV --> CV[("Event Custom Values
N_region_event_name/date/
location/time/venue")]:::data
  DATESPG["Funnel: PBC Event Dates page"]:::trigger -. reads .-> CV

  ORDERF["Funnel: Premiere Bootcamp order"]:::trigger --> REGF["Registration Form"]:::trigger
  REGF --> REG["Registration REGION"]:::wf
  CV -. read .-> REG
  REG --> TAG{{"Tag: pbc region event N"}}:::tag
  TAG --> REM["Reminders 30/14/7/1"]:::wf
  TAG --> PAY["14-Day Payment Reminder"]:::wf
  CV -. read .-> REM
  CV -. read .-> PAY
  REM --> ESD["event_start_date + appointment-relative waits
email / SMS"]:::wait

  DEP["Order: Deposit / PIF product"]:::trigger --> ONB["AU Onboarding
Deposit / PIF"]:::wf
  ONB --> OPP["Opportunities + Membership access"]:::done
  BALF["Balance two-step order form"]:::trigger --> BAL["Balance Paid - All Options"]:::wf
  BAL --> GOAL{{"Tag: pbc-payment-complete"}}:::tag
  FAIL["Payment failed"]:::trigger --> DUN["Failed Payment
invoice + dunning"]:::wf

  CHGF["Funnel: Change Event PBC"]:::trigger --> CHG["Change Date Request
Paid / Free"]:::wf
  CHG --> RES["Re-scheduled Events email"]:::wf
  CHG -. admin re-slots .-> ADMIN

  LOGIN["Member portal login"]:::trigger --> PLT["Portal Login Tracking"]:::wf
  OFFER["Offer access granted"]:::trigger --> QN["Questionnaire Reminder to Completed"]:::wf
  GRAD["Opportunity: graduate stage"]:::trigger --> DELIV["Post-Bootcamp Deliverables"]:::done
      

Cyan = entry points (funnels, forms, payments) · White = workflows · Navy = event data (custom values) · Purple = timing (event date + waits) · Amber = tags (the join keys) · Green = outcomes.

03The dynamic-date engine

This is the core idea and the reason the system is low-maintenance. Every event slot's details are stored as account custom values, named by slot, region, and field.

# Naming pattern
{N}_{region}_event_{field}
# Examples
1_au_event_name   1_au_event_date   1_au_event_location   6_us_event_time

{
  "type": "update_custom_value",
  "custom_value_id": "<slot field id>",
  "new_value": "{{contact.event_date_update}}"
}

{
  "type": "event_start_date",
  "event_start_type": "custom_field",
  "value": "{{custom_values.1_au_event_date}}"
}

04System layers

05Workflow reference

Registration (per region)

Reminders & payment reminders

Payment lifecycle (AU complete set)

Member, compliance & post-bootcamp

06Funnels

The account holds 82 funnels. The ones below are the pages that connect directly into the PBC automation. The remainder are event-registration pages for other programs (One-day Premiere Events, masterclasses, webinars) and are outside the PBC system.

PBC-connected funnels

Other funnel groups in the account

07Custom value registry

Each region holds six event slots; each slot carries this field set, edited through the admin form.

08Scaling & handover

The region pattern is fully repeatable. To launch a new region (or resell the system), the repeatable unit is:

• 6 event-update workflows wired to that region's custom values
• 1 registration workflow with per-event tags
• 1 reminder workflow and 1 payment-reminder workflow
• the custom-value set, the registration funnel, and the products / offers

Only the data and identifiers change; the structure, event branching, date logic, and reminder cadence stay identical.

Recommended clean-ups before packaging

• Standardise tag naming — AU uses underscores (pbc_au_event_1), other regions use spaces (pbc - nz event 1).
• Reconcile custom-value field names so the engine writes and reminders read the same fields.
• Finalise draft workflows (Event Date Catcher, Event Attendance) before they ship.
• Archive unused funnels (do-not-use / backup / test) to declutter the account.