Boilerplate Snapshot Evaluation | FireRock Marketing

Executive Summary

A solid attribution and lead-capture core, held back by unfinished automations and template clutter.

Verdict: Strong foundation, not deployment-ready as-is

The boilerplate has a genuinely good backbone: form capture, opportunity creation, GA4 and Meta conversion tracking, source attribution tagging, and a review-request engine. For a home-services lead-gen agency, the analytics and attribution layer is more advanced than most snapshots.

The problem is finish. More than half the workflows ship in draft, including the appointment reminders and lead nurtures that clients actually feel. The pipeline layer is duplicated and carries working notes in stage names. A large block of fields and a full ScoreCard form are themed for B2B LinkedIn marketing, not contractors, and a cluster of fields still carry auto-generated names. None of it is broken, but a new client provisioned today inherits the clutter and the switched-off automations.

The recommendations below are ordered so the highest-impact, lowest-risk fixes (publishing the dormant automations, consolidating pipelines) come first.

Inventory at a Glance

What the snapshot contains today

Workflows

5 live · 8 draft

Pipelines

2 overlap

What Is Working Well

Keep and build on these

Attribution and tracking

GA4 event tracking wired into form submissions and lead capture
Meta Conversion API workflow present for paid-social attribution
Traffic-source tagging (organic, paid search, paid social, referral, direct)
Source tags feed a dedicated attribution workflow

Lead handling and reviews

Form submitted to opportunity created to auto-response is live and clean
Internal notification on new lead is live
Review request engine published with email and SMS tag tracking
"Lead Engagement" pipeline has a logical, well-ordered stage flow
Discovery Call calendar uses a merge field so it ports per client

Findings and Recommendations

Prioritized cleanup before the next client deploy

High

8 of 13 workflows ship as draft

The following inherit as switched-off in every new sub-account: Appointment Reminders (confirmation and rebooking), Inbound Day 1-3 nurture, Inbound 5-Week nurture, Incoming Call tagging, Lead Engagement Meta CAPI, Add Facebook Messenger Tag, and Review Request with intent check. Appointment reminders and lead nurture are core revenue automations, so a fresh client silently launches without them.

Fix: Decide per workflow: publish and retest, or delete if superseded. The snapshot should contain only automations that are intended to run, in their finished state.

High

Three pipelines, with duplication and working notes in stage names

1. Main contains a single "New Lead" stage and is effectively dead. 2. Fixed carries unfinished markers in its stage names (Day 1-3**, Meeting Scheduled**, Missed Meeting/Reschedule**, 5 Week Lead Nurture**). Lead Engagement is the clean, complete one. New clients inherit all three and the confusion that comes with it.

Fix: Pick one canonical pipeline (Lead Engagement is the strongest), delete "1. Main", and either retire "2. Fixed" or strip the ** notes from its stage names. One pipeline, clean stage labels.

Medium

ScoreCard form and fields are themed for the wrong audience

The ScoreCard form and roughly 20 associated radio fields are about LinkedIn presence, ICP alignment, and B2B content marketing ("Is your LinkedIn profile up to date and aligned with your ICP?", "Are you using LinkedIn features like events, groups, or polls?"). FireRock's clients are home-services contractors (roofing, HVAC, plumbing, electrical, septic). This looks like leftover content from a different template and adds dead fields to every account.

Fix: Either rebuild the ScoreCard for the contractor vertical, or remove the form and its fields from the boilerplate and keep it as an optional add-on.

Medium

Auto-generated field names left un-renamed

Several fields still carry machine defaults: Radio 1mxiScore 1lzzRadio 3n5dRadio 3p8mRadio 15n9lRadio 19bphRadio 217gv These are unreadable in workflows, forms, and merge fields, and make the account hard to maintain.

Fix: Rename to describe their purpose, or delete if they are orphaned ScoreCard fragments.

Medium

Setup placeholders with no enforcement

Per-client values ship as stubs: custom values GA4 API Secret = 1 and GA4 MEASUREMENT ID = 1, and the trigger link Google Review Link points at google.com. If these are not replaced during onboarding, GA4 tracking and the review engine quietly send to the wrong destination.

Fix: Add a one-page onboarding checklist (or a setup workflow task) that forces these to be set per client. This ties directly into the snapshot in/out SOP and the existing GHL Accounts Checklist.

Low

Tag naming is inconsistent

Review tags mix counts and concatenated styles: emailreviewrequest1-3emailreviewtried1-2smsreviewtried1-3 alongside spaced tags like after hours. The email/SMS "tried" sequences also have mismatched lengths.

Fix: Standardize on one convention, for example review:email:request:1, and align the sequence lengths across email and SMS.

Low

No field organization and a stray voice agent

All ~32 custom fields sit in zero folders, which makes a 55-field list hard to navigate. Separately, a Voice AI agent named "My Agent 222" is present, inbound inactive and unconfigured.

Fix: Group fields into folders (Contact, Attribution, Business, ScoreCard). Either configure the voice agent as a real boilerplate asset or remove it so it does not ship half-built.

Suggested Order of Work

From this evaluation to a clean, deploy-ready snapshot

Publish or cut the dormant automations Review the 8 draft workflows, finish and publish the keepers (appointment reminders, nurtures), delete the rest.
Consolidate to one pipeline Keep Lead Engagement, remove the dead "Main", retire or clean "Fixed", strip ** from stage names.
Resolve the ScoreCard Rebuild for contractors or remove it and its orphan fields from the base snapshot.
Clean the fields Rename machine-named fields, delete orphans, group everything into folders.
Lock down setup placeholders Build an onboarding checklist that enforces GA4 keys, the Google review link, phone, A2P, and tracking numbers per client.
Re-cut the snapshot and version it Save as the next FireRock version, then update the snapshot in/out SOP so future changes have a clear push process.