FireRock Marketing / Builds / Ignition Dashboard Template
Snapshot Build Plan Testing Result How To Use (SOP)

FireRock Marketing  /  Build Plan

Ignition Dashboard: Build Plan

A live preview of the full Ignition Dashboard template build (9 workflows, 25 metrics, 4 tier dashboards). Explore the end-to-end system map, then open any workflow to see its exact trigger, action sequence, tags, and custom fields.

The Plan

How we turn leads into clients, step by step

Built and tested

This build is complete and tested in the template account. Comment on anything to add, change, or remove and we will update the template and refresh the snapshot.

Definition of Done

How we will prove the build works before handover

The build is only marked complete when every outcome below passes a live end-to-end test.

Data Sources

What feeds the dashboard

Full Build Map

Every path, end to end

Scroll to zoom, drag to pan. Use Present for fullscreen.

Scroll to zoom · drag to pan

Pipeline

Opportunity stages

Workflows

Click any workflow to preview its structure

Each card opens the trigger, the action sequence as a diagram, and the exact tags and custom fields it reads or writes.

Build Primitives

Custom fields and tags the build needs

Custom fields

Tag taxonomy

Spec v1.1 Alignment

How the build maps to the Ignition Dashboard Build Specification v1.1

Each row is a point in the spec, what was built, and whether it matches. Items marked Needs definition, Spec conflict or Not built are open questions for the spec owner.

Spec sectionSpec saysWhat is builtStatus
2, 3, 12Custom Metrics need the SaaS Pro ($497+) planCustom Metrics work on FireRock's current plan (built and tested in the template account). No upgrade needed for this dashboard.Better than spec
3, 5LC Phone with a tracking number per channel, UTM standard, GA4 connectedSet up in each client account. Added to the SOP checklist.Per client
4.1New Lead is created by a call, form or chat triggerThe snapshot does not create the deal. Each client's intake workflows send leads to Ignition Pipeline, New Lead (SOP Part B, step 1), so existing intake is not duplicated.Built differently
4.1, 6Contacted on first outbound contact; computes first_response_secondsAn outbound call moves the deal to Contacted. Email or text-only first contact is moved by hand. Speed-to-Lead stamps First Response At and records 0 seconds for the instant reply; measuring a person's response time needs a paid code step.Built differently
4.1Lost with reasonDeals at Lost are marked Lost. No lost reason is captured.Partly built
4.2first_response_at is Date/TimeBuilt as a Date field (day only).Minor difference
4.2review_completed set by the new-review triggerNot set: the review-received trigger is not tied to a contact. Review Request Rate uses review and request counts instead.Not possible
4.4Invoiced revenue counts marketing-sourced jobs onlyInvoiced Revenue sums Job Revenue on every completed deal in the Ignition Pipeline (no channel filter). Marketing-Sourced Revenue is filtered to LSA, Search, Meta and GBP.Built differently
6Speed-to-Lead fires on form, chat or inbound callFires when the deal lands at New Lead, so each lead gets one reply.Built differently
6Six workflowsNine: adds Lead Channel Stamp, Appointment Set Stamp and Lost Stamp.Built (more)
8 ACPBJ trend vs onboarding baselineThe trend tile compares against the previous period. The formulas cannot read the baseline custom value, so the baseline is a reference for the client call.Built differently
8 E, 10Ad spend by channel in all tiers (section 8) vs Meta from Blaze (section 10)Followed section 10: Spark shows Google Ads; Meta Ads and ROAS start at Blaze.Spec conflict
8 ELSA panel (leads, CPL, rating, disputes) in all tiersNo LSA data source in the CRM. LSA is covered by CPBJ - LSA and Cost Per Lead - LSA (Blaze and up) with spend typed in.Not built
8 CFirst vs last touch (Wildfire)In Reporting > Attribution report. The dashboard panel has no first/last switch.Built differently
8 FReviews: new, total, average ratingNew reviews and average rating are on the dashboard; total reviews is not a separate tile.Partly built
8 GMulti-location rollup (Firestorm)Not built: each dashboard covers one client account.Not built
10Wildfire and Firestorm paid media "expanded" and local "advanced"Not defined in the spec. Wildfire and Firestorm sections E and F match Blaze.Needs definition
9All formulasCPBJ (media-only, all-in, by channel), close rate, average job value, ROAS, ROI (all-in), first response, missed-call recovery, marketing-sourced revenue, revenue vs prior month: built as written.Built
11FireRock colors, Ignition Dashboard name, scheduled reports, AI summary, client viewColors and names applied. Scheduled reports are set per client in Reporting > Custom reports. The AI summary is the Dashboard summary button (on demand); a weekly AI summary setting was not found. Client user access is set per client.Per client
12CPBJ checked against a manual calculation; test call and test form end to endNeeds real ad spend, a phone number and the client's intake form, so it is done at the first client load (SOP Part C).Per client
13Custom Metric filters are limitedMetrics filter directly by pipeline, stage, Won/Lost status and Lead Channel, so booked jobs and channel splits count correctly.Better than spec

Known Limits

What to know before rollout