See every job, its stage and what you won, without opening your CRM.
The Jobs view reads your job pipeline from your CRM or booking platform the moment you open the tab, and it sits on the same dashboard as your leads and your ad spend. You count jobs, not leads, so the screen counts jobs too.
Which quote requests became jobs, and where does each one stand?
Open the Jobs tab and the table is already there: every job in your pipeline with its customer and its stage, under a Live badge. Click a row and it opens to its detail: the customer, the stage, and whether the job is closed. The stage text is the one your team set in your CRM or booking platform; nothing is renamed or re-scored on the way to the screen. Above the table sits a stat row, and the feed behind it returns four counts: jobs created, open, won and lost.
The read happens when you open the tab, every time. A job your office created an hour ago is on the screen the next time you open it, and the Refresh button in the topbar pulls again. Every tab, this one included, exports what it shows as a CSV.
The view reads. It never creates, edits or closes a job, and nothing you click here writes to your CRM or booking platform.
How does a lead on my website turn into a job on this screen?
Three systems sit side by side, each doing the one thing it is good at. Your website's form handler appends every submission to a lead sheet server-side and emails your team the moment it arrives; the Leads view reads that sheet newest first. Your team turns the request into a job in your CRM or booking platform and moves it through stages. The Jobs view reads those stages as they stand.
Where the platform holds a source, the screen uses it. On one instance we run, the website's quote form creates the lead in the booking platform the moment it is submitted and stamps its source from the link the visitor arrived on, a paid click or the website itself; the Leads list borrows that source for the same name, so a lead you paid for and a lead that arrived on its own are told apart. Where no matching record exists, the row carries no source label rather than a guess.
Once the platform is connected and its data holds up, the Overview funnel grows two stages, jobs created and jobs won. The path from search impression to won job then reads top to bottom on one card.
What does one job look like, from quote request to won?
Take a contractor whose pipeline runs New lead, Appointment set, Estimating, Approved, Permitting, Construction, and then Closed won or Closed lost. A homeowner submits a quote request on Tuesday. The lead sheet gets the row and your team gets the email the same minute. Your office creates the job, and it appears on the Jobs tab as New lead the next time anyone opens it.
Thursday the estimator moves it to Estimating, and the row's badge changes the next time the tab loads. The following week it reads Approved, then Construction. When the office marks it Closed won, the won count moves by one on the stat row and on the last stage of the Overview funnel. A job counts as won when its stage reads Closed won or it carries a close date, as lost when the stage reads Closed lost, and as open otherwise.
Records named test, and practice jobs filed against your own staff, are filtered out before the count is taken, so the funnel measures customers, not setup. You never type on this screen. The stages move in the platform your team already works in, and the tab reflects them.
Why is there no Jobs tab on my account yet?
Because your CRM or booking platform is not connected yet, or because its data is not yet worth putting in front of you. A business that does not run on such a platform never sees an empty Jobs tab; the tab is absent. A business whose connection exists but whose data is not yet trustworthy sees a coming-soon card: the view's title, a Coming soon badge, and one paragraph saying what will appear there.
Trustworthy has a specific meaning here. On one instance we run, the feed was wired and working, and after the setup records were filtered out it held three real jobs, one past New lead and none marked won. Publishing that table would have printed zero won as if it were a result, when it was a team that had not started working the stage field. The card stayed up instead. It flips to the live table by removing one setting, with no code change.
The same rule runs across the whole product: a tile is filled honestly or it is labelled. The nightly bake at 12:01am Central leaves the previous page up rather than ship an empty or broken one, so a failed pull never leaves the screen blank.
What runs on its own, and what stays with my team?
The reads run on their own. The page loads last night's snapshot first, asks a cache for the live payload, and if the snapshot is older than five minutes starts a pull in the background; the Jobs table itself is fetched from your platform on every open of the tab. Refresh starts an async pull that takes from two seconds to a little over three minutes, and the page reloads when the stamp moves; it never shows an error. The 12:01am Central bake rebuilds the fallback snapshot for every client from one registry, whether anyone is at a desk or not.
The stages stay with your team. Nothing on the dashboard writes to your CRM, your booking platform, your ads account, your site or your Business Profile. What the screen writes is short: an outcome on a lead, to the lead record; a website change request, or a content, keyword, category or targeting change request, to our team, logged. Budget and bid changes in your ad accounts are made by a person, never by a scheduled job.
Connecting it is our work, not yours. In week one of setup you grant access and our team connects your CRM or booking platform from the inside; in week two the first pull lands with your baselines. There is no wizard and no sign-in screen to click through on your side, and we never hold your passwords. The platform key lives server-side as a secret on the edge function behind your login, so the browser never carries it. Setup takes two to four weeks and is not billed.
What will the Jobs tab not tell me, and what should I check in the demo?
It will not show a job's dollar value today. The table carries the job, the customer and the stage, and the counts are counts; the money is on the Revenue view, read from Stripe where you take payment there. It will not call a job won that your team has not marked won: the count is only as good as the stage field, which is why the tab waits at coming soon until that field is being worked.
It does not print a cost per won job as one number. Spend and cost per conversion sit on the Google Ads view, the won count sits here and on the funnel, and dividing the one by the other is yours to do. Phone calls are counted only where your CRM or booking platform records them. No client instance reads an inbox, a calendar or card data. If your platform is unreachable for a moment, the card says it could not load right now and the funnel leaves its two job stages off until the next pull, rather than showing a stale count as current.
Your CRM or booking platform is the platform we read today. A different platform with an API that exposes the pipeline can be connected on request during setup; one that does not leaves the Jobs tab off while the Revenue and Leads views keep reading.
In the demo, check the shape rather than the tab. The fictional company in the demo runs on no booking platform, so it has no Jobs tab; what it has is the Overview funnel, from visitors down to closed won, which is the card the Jobs view extends on a connected account. Click a stage and watch it open, press Refresh and watch the header stamp move, and open the Leads view to see the ledger a job starts from. Every client runs the same engine code the demo runs, so what you see there is what your account will do.
What the Jobs view reads.
| What | Where it comes from | How fresh |
|---|---|---|
| Job pipeline | Your CRM or booking platform, through its API | Live, each time you open the tab |
| Job, customer and stage | Your CRM or booking platform | Live |
| Counts: created, open, won, lost | Derived from the pipeline; won reads the stage or a close date | Live |
| Funnel stages on the Overview | Jobs created and jobs won, added once the data holds up | Live |
| Visibility | Shown only when connected; a coming-soon card until trustworthy | Per account |
| Writes | None | Never |
No platform connected means no Jobs tab, a connection whose data is not yet trustworthy means a coming-soon card, and the screen never shows a pipeline it cannot fill.
Questions, answered.
Which job platform is supported?
Your CRM or booking platform, read through its API. Another platform with a pipeline API is connected on request during setup.
Does it change anything in my CRM or booking platform?
No. It reads the pipeline and never creates, edits or closes a job.
Why is my Jobs tab missing?
Your CRM or booking platform is not connected on your account yet. The tab appears once it is, and shows a coming-soon card until its data is trustworthy.
What does coming soon mean on the Jobs view?
The connection exists and the data behind it is not yet worth putting in front of you. Removing one setting flips the card to the live table, with no code change.
Is the pipeline live?
Yes. The table is read from your CRM or booking platform each time you open the tab, and the Refresh button pulls again.
Can I see cost per won job?
Not as one printed number. Spend and cost per conversion sit on the Google Ads view, the won count sits here and on the Overview funnel, and you divide the one by the other.
Is the Jobs view on every plan?
It is part of the Command Center dashboard, on all tiers, and it appears once your CRM or booking platform is connected.
Does a phone call count as a job?
Only if your CRM or booking platform records it. Nothing else on the dashboard listens for calls, and no client instance reads an inbox or a calendar.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.