01 / What it is
The Ignition Dashboard exists to answer a single question in real time for the client and their strategist: how much are we spending to book a job, and is that number moving in the right direction. Everything on it either shows that number (CPBJ, Cost Per Booked Job), a supporting driver of it (close rate, average job value, first response time, missed call recovery), or a lever that changes it (ad spend, lead channel, review flow).
02 / Program tiers
The dashboard is the same object for every tier. What changes is the review cadence and which optional widgets are turned on. Widgets are cumulative, so each tier inherits the one below it.
| Tier | Cadence | Extras beyond the 8 metric tiles |
|---|---|---|
| Spark | Monthly | Core 8 tiles only |
| Blaze | Monthly + channel | Adds CPBJ by channel |
| Wildfire | Bi-weekly | Adds Marketing revenue MoM + GBP widget |
| Firestorm | Weekly + QBR | Adds Revenue vs prior month + Reputation + full native widget row |
Every tier including Spark shows CPBJ. No tier escapes the Formula Editor dependency.
03 / Architecture
| # | Layer | Scope | Deployment |
|---|---|---|---|
| 1 | Pipeline (6 stages) | Standard sales pipeline every client uses | Scripted |
| 2 | Custom fields (12, opportunity-model) | Data the workflows write and the metrics read | Scripted |
| 3 | Custom values (4) | Account-level constants (mgmt fee, LSA spend, baselines, targets) | Scripted |
| 4 | Workflows (6) | The bookkeeping that turns lead events into clean data | Scripted |
| 5 | Custom metrics (8, plus 3 widget-level) | Formula Editor definitions the tiles read | Scripted (Reporting API) |
| 6 | Dashboard (8 tiles + optional native widgets) | The visible page the client and strategist see | Scripted (Reporting API) |
Every layer above is scriptable. The whole template can be redeployed to a fresh sub-account without a manual UI session, which is what makes this a real snapshot product and not a one-off build.
04 / Data flow (plain English)
1. Lead comes in
Speed-to-Lead fires within seconds, sends the first outbound, stamps first_response_at.
2. Contact is worked
Contacted Stamp moves the opportunity to Contacted, computes first_response_seconds.
3. Missed call happens
Missed-Call Text-Back flags missed_call = Yes and sends the recovery text; on reply, missed_call_recovered = Yes.
4. Opportunity reaches Job Booked
Booked-Job Stamp marks the opportunity Won, sets is_booked_job, captures booked_job_value. This is what CPBJ counts.
5. FSM completes the job
FSM Inbound Sync writes fsm_job_id, job_revenue, and moves the stage.
6. Job marked completed
Completed & Review Request stamps job_completed_at, review_requested, sends the review request.
Ad spend feeds the ratio
Google Ads and Meta spend flow in through the native ad modules. The eight custom metrics combine opportunity data + spend to produce CPBJ, ROAS, ROI, close rate, and the recovery ratios that populate the eight dashboard tiles.
05 / Per-client deployment
The template is captured as a snapshot and pushed to each client sub-account. The scripted layers land automatically. The remaining steps per client are:
| Step | Owner | Notes |
|---|---|---|
| Push snapshot to client sub-account | Us | Standard snapshot flow |
| Set the four custom values (mgmt fee, LSA spend, baseline CPBJ, response target) | Us at onboarding | 1 minute |
| Connect Google Ads (native) | Client + us | Ad-spend tiles start populating within one refresh |
| Connect Meta Ads (native) | Client + us | Same as above |
| Connect Google Business Profile (native) | Client + us | Powers GBP widget (Blaze+) |
| Configure FSM Inbound Sync webhook | Us + client FSM | The only step that needs a live FSM sample payload |
| Live test: New Lead to Job Booked to Completed | Us | Confirms every stamp fires and dashboard tiles populate |
Once the ad accounts are connected, all eight metric tiles read real numbers. Nothing else is per-client custom work.
06 / Template objects (in the account today)
Live status
Every workflow is Published. The builder-level error counter reads zero across the whole account. Ad-dependent tiles show "Ad account configuration required" in the template, which is expected. See the Build Plan tab for the full field, tag, workflow, and metric detail.
07 / Brand
Naming
Always "Ignition Dashboard". Never reference the underlying platform in front of clients.
Tone
Direct, outcome-oriented, action-first. Every metric answers a question the client cares about.
08 / Reference documents
All object IDs and API recipes are held internally and are not published on this page.