The Command Center is now a product you can license. Open the demo

Integrations

Your pipeline on the first screen you open, read live from your own sub-account.

GoHighLevel is the CRM the Command Center connects today. The funnel on your Overview reads the pipelines and opportunities in your own sub-account, live, and nothing on the screen writes back to them.

Which GoHighLevel account feeds my dashboard?

Your own sub-account feeds the dashboard. Two connections exist, and they are different. The first is your business's contact record in our CRM: one record, with our notes and tasks against it, so our team keeps your engagement on one thread. The second is your own GoHighLevel sub-account, the location you run your pipeline from and, where we post for you, your social from. The dashboard reads the second. Both sit under one client identity in our per-client map, so they are never confused for each other, and the panel our team uses shows only the last four characters of your sub-account id.

Our team connects your sub-account from the inside in the first week of setup, with access you grant. There is no wizard and nothing for you to press. The sub-account id and its token stay server-side and are stripped from every response that could reach a browser, including yours. Where we post your social through the same sub-account, the Social view reads its post analytics from there as well.

Two connections, one client
Your record in our CRMone contact, our notes and tasks
Your own sub-accountpipelines, opportunities, sources
Shown to our team asConnected, last four characters
Sent to any browsernever the id, never the token

How does my pipeline show up on the Overview?

Your pipeline shows up as a funnel on the Overview: one bar per stage, widest at the top, a count in each and a line of context beside it. Setup builds the stages from the sources you connect: search impressions, site sessions, form leads and, where your CRM pipeline is connected, the opportunities it holds. The connection reads the pipelines in your sub-account by name and the opportunities in each. On the account reading today, a funnel row counts the contact-form cards in one named pipeline, the one your form writes to. Cards from other sources in the same pipeline are told apart by source and counted beside it, so the number is real submissions, not tracked events.

Click a stage and a panel opens with its volume and what the stage counts. A stage that fills and does not drain is visible the moment you open the page, with no report to build, which is why the funnel sits on the first screen. If your jobs live in a booking platform, a separate Jobs view sits beside it, so the sales pipeline and the job pipeline each read from where they actually live.

Pipeline, read from your sub-account
Pipelinesby name
Stagesby name
Opportunitiescounted per pipeline

Can I see which channel each deal came from?

Yes. The connection reads the source field on each opportunity, alongside its value and its status as your CRM records it: open, won, lost or abandoned. The source is read as written, with no attribution model layered on top. A revenue by channel card exists on the Overview where it is set up for a client; today the one account that carries it builds it from payment records, not from the CRM source field.

Two records feed that screen, and the screen says which is which. The revenue view reads payments from Stripe. The source on a deal comes from your CRM. A lead's source on your own forms is a separate record, captured when the form is submitted; the glossary entry on how a source is captured and carried covers that one.

What the connection reads on each deal
Valueas recorded
Statusopen, won, lost or abandoned
Sourceread as written
Contactthe record it belongs to

How fresh is the number in front of me?

Live. Your CRM is a live source, and the page refreshes because you opened it. It loads last night's snapshot first so there is something on screen at once, fetches the live payload from a cache, and if that snapshot is older than five minutes a pull runs behind the page. The Refresh button in the top bar starts a pull, two seconds to a little over three minutes depending on the sources, and the page reloads when the time stamp moves. It never shows an error.

A nightly bake at 12:01am Central writes a fallback copy for every client, and a failed pull leaves the previous page up, never an empty one. The header stamp says how old the numbers in front of you are. The live data page says what live means for every other source on the screen.

The Google Ads view: five stat cards for spend, conversions, cost per conversion, ROAS and impression share, and an active campaigns table with spend, conversions, cost per conversion and a Running status per campaign.

What does it need from me, and can it change my CRM?

Read access to your sub-account's pipelines, opportunities and contacts, granted by you during setup. Where we also post your social through the same sub-account, that access includes publishing those posts. The Integrations view lists the connection as Connected. We do not hold your GoHighLevel password, or a password for any other account on the dashboard.

The screen never writes to your pipeline, opportunities or contacts. Setting a lead outcome writes to the lead record on the Leads view. A request for a website, content, keyword, category or targeting change goes to the team and is logged. None of the screen's write paths touch Ads, your site or your Business Profile directly. The Security page lists every write path.

The search view: stat cards for organic clicks, keywords ranking, keywords in the top 3, referring domains and domain rating, and a top keywords table with position, change and monthly volume.

What if my CRM is not GoHighLevel?

GoHighLevel is the only CRM the Command Center connects today. Ask for another during setup, and this page will name it once it is reading on a real account. If your business runs its jobs on your CRM or booking platform, that is already a separate connection with its own view.

One CRM named truthfully beats a wall of logos. The full list of connections is what reads on a real account today, and each one says what it reads and how fresh it can be. A view whose source is not connected does not appear; it never fills itself with a sample.

The Command Center Overview on the demo company Meridian: four headline cards for marketing-sourced pipeline, revenue, AI-visibility score and assets published, a pipeline funnel from visitors down to closed won, revenue by channel bars, and a grid of workstreams each marked Running.
The spec

What the GoHighLevel connection reads.

WhatWhere it comes fromHow fresh
Pipeline and opportunity countsForm-submission cards in a named pipeline in your own sub-account, told apart from other cards by sourceLive
Deal value and statusEach opportunity's value and its status as your CRM records it: open, won, lost or abandonedLive
Source per dealThe source field on each opportunity, read as writtenLive
Social post analyticsSocial Planner in the same sub-account, where we post for youOn the networks' schedule
Your record in our CRMOne contact with our notes and tasks, used by our teamNot a dashboard source
Writes to your pipeline, opportunities or contacts from the screenNoneNever
Two records, named honestly

Where your forms feed a lead sheet, the Leads view counts the submissions and the funnel counts the opportunities your CRM holds, two records of the same buyer, and the screen says which is which.

FAQ

Questions, answered.

Do I need to give you my GoHighLevel password?

No. Our team connects your sub-account from the inside during setup with access you grant. The sub-account id and its token stay server-side and never reach a browser.

Does the dashboard change anything in my CRM?

No. It never writes to your pipeline, opportunities or contacts. Setting a lead outcome writes to the lead record, and change requests go to the team and are logged.

Is the funnel live?

Yes, the CRM read is live. The page refreshes when you open it, a snapshot older than five minutes triggers a pull, and the Refresh button starts one on demand. Rows built from GA4 or Search Console carry those sources' delay, and the header stamp says how old the numbers are.

Does it read my own stage names?

Yes. The connection reads the pipelines and stages in your sub-account by name, with the opportunities in each. On the account reading today a funnel row counts the contact-form cards in one named pipeline; a bar per CRM stage is not yet built on a real account.

Do phone calls show up in the funnel?

Only when your CRM records the call as a lead. We do not run a call-tracking system. Where a funnel stage is built from tracked site events, a phone tap on your site counts there as a contact action, and the stage says so.

Which CRMs do you connect?

GoHighLevel, today. Ask for another during setup. A business whose jobs live in a CRM or booking platform gets a Jobs view through that connection.

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.