Standard Modular Snapshot — Report & Build Plan

Bottom line

1. The report — what is actually working

"Working" = published (live, running) across the fleet. These five run in 70–94% of all client accounts. They are the universal core.

Supporting layer (also near-universal)

Reference accounts (most mature — copy polished configs from here)

Ranked by published workflow count (battle-tested, actually in use):

2. The target — Standard Modular Snapshot

One snapshot. A core that's always on, a set of modules shipped as drafts you flip on per client, and the cruft removed.

3. Build plan

1. Clone Z to a working copy

   Duplicate "Z Automation Snapshot" into a fresh sub-account named FireRock Standard v1. Build there so the live Z stays untouched until v1 is validated.

2. Strip the cruft

   Delete the ScoreCard fields + ScoreCard form, the duplicate fields, and the Lead Engagement pipeline. Result: a clean field list (Service Requested, Referred By, Referrer Email + standard opportunity/contact fields only).

3. Lock the CORE and publish it

   Confirm the 5 core workflows are present and published; verify each step config against Acclaimed Roofing Arizona (the most mature account). Keep Main + Fixed pipelines, GA4 custom values (left blank as placeholders), Discovery Call calendar, tag taxonomy, Google Review link, Contact Us + Referrals forms.

4. Stage the MODULES as drafts with a clear naming convention

   Prefix every optional workflow with [OPT] and group them in an "Optional Modules" folder, so on/off is obvious at a glance. Core workflows go in a "Core" folder. This is what makes "turn on what we need" a 10-second job.

5. Write the per-client activation runbook

   The toggle checklist below — by client capability, not niche.

6. Save as the agency snapshot & smoke-test

   Save FireRock Standard v1 as an agency snapshot. Spin up a throwaway sub-account from it, confirm core fires on a test form submit (one verified send), then retire the old snapshot.

7. Roll into onboarding

   New client = load snapshot → fill the config knobs (GA4 IDs, calendar owner, business phone) → toggle the modules they need → publish. Done.

Per-client activation runbook (toggle on when…)

Config knobs to set per client (custom values)

4. Canonical spec — names, tags, folders

This is the single source of truth. Build the master exactly to these names so every account is identical and drift is instantly visible in the audit sweep.

4.1 Naming conventions

4.2 Workflow folders & canonical names

📁 01 · Core — Lead Capture
   ├─ All Leads Captured → Tag Sources → GA4 Events        [published]
   ├─ Forms: Any Form Submitted → Create Opportunity → Auto Response   [published]
   └─ Forms: Any Form Submitted → GA4 → Add Tags → Send Notification   [published]
📁 02 · Core — Reviews
   └─ Review Requests                                       [published]
📁 03 · Core — Utility
   └─ Mark All As Read                                      [published]
📁 04 · Optional — Appointments
   ├─ [OPT] Appointment Reminders — Confirmation            [draft]
   └─ [OPT] Appointment Reminders — No-Show Rebooking       [draft]
📁 05 · Optional — Nurture
   ├─ [OPT] Inbound Nurture — Day 1–3                       [draft]
   └─ [OPT] Inbound Nurture — 5-Week                        [draft]
📁 06 · Optional — Calls
   └─ [OPT] Incoming Call → Tag                             [draft]
📁 07 · Optional — Ads & Tracking
   ├─ [OPT] Add Facebook Messenger Tag                      [draft]
   ├─ [OPT] Facebook Lead Form Submitted                    [to add]
   └─ [OPT] Lead Engagement — Meta Conversion API           [to add]
📁 08 · Optional — Reviews+
   ├─ [OPT] Review Request — With Intent Check              [draft]
   └─ [OPT] Google Review Campaign — Past Clients           [draft]

4.3 Canonical tag taxonomy

Evidence-based: every tag below is already on 34/35 client accounts unless noted. Group, don't free-form.

4.4 Canonical pipelines & stages

4.5 Canonical custom fields & values

4.6 How we sync it canonically

1. One source of truth

   The FireRock Standard vN agency snapshot is canonical. Every new account is created from it, so names, folders, tags, pipelines and fields are identical on day one.

2. Names are the contract

   Because every object name + folder is fixed, the audit sweep can diff each live account against this spec and flag any drift (renamed workflow, stray tag, missing core folder) automatically.

3. Versioned changes

   Any improvement is made in the master, the version bumps (v1 → v1.1), and the change is logged. We re-push only the changed objects to existing accounts; client-specific edits live outside the Core folders so they are never overwritten.

4. Quarterly reconciliation

   Re-run the fleet sweep, diff against this canonical spec, and bring stragglers back in line. The audit dashboard is the scoreboard.