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

Buying

Hand off the work. See every change we make.

Command adds the outbound engine, ad creatives and your full marketing team, always on, scoped per engagement. Every change our team makes lands in your account's own change history, sorted as ours, and the same daily watch that reads every mapped account reads it at 7:05am Eastern.

What do I get with Command?

Command adds the outbound engine, ad creatives and your full marketing team, always on on top of every tier below it, with the seats your tier carries: three on Starter, three on Launch, ten on Growth and unlimited on Command. Our team runs the work instead of you or a previous agency. Reach the team from the dashboard or by email, and every request is logged. Running the program, the cadence and the approvals, is the retainer, and it sits on top of any tier.

Seats are three on Starter, three on Launch, ten on Growth and unlimited on Command, each one a Member or an Admin. You read the same engine every client runs, and the numbers do not soften because we are the ones making the changes; the next section is why. Setup takes two to four weeks: access in week one, then the first pull, the baselines, the keyword set and the ads watch on your account.

Command, above the published tiers
Addsthe outbound engine, ad creatives and your full marketing team, always on
SeatsMember or Admin
Pricescoped per engagement

How do I see what your team changed?

Open your own Google Ads console and read the change history. Every change our team makes to your campaigns lands there under our login, and the daily change watch reads that history at 7:05am Eastern. The watch sorts each event by who made it: our own writes, routine noise, and material changes by anyone else. Our script writes are filed as routine and stay out of the morning post, with one exception: a script of ours that switches on AI Max or asset automation is raised that morning the same as anyone else's. A change one of our people makes at the keyboard, a budget, a bid strategy, network settings or a campaign status, appears in that morning's post for your account, worded as ours and naming who, as a note rather than an alarm. The history is Google's record, not ours. Read it in your own console for as long as Google keeps it, without asking us.

Access works the same way. The watch reads your account's user list directly every day, because Google's change events do not log who was granted access. Our access is a manager invitation you issued, and you can revoke it in your own console. We never hold your password.

One morning's watch, mapped accounts
Our script writesfiled as routine, kept in the record
Our keyboard changesin that morning's post, worded as ours, naming who
Routine noisesuppressed
Material, by anyone elseraised to the team the same morning
Account usersread directly, daily

How is Command priced?

Command is scoped per engagement, and the scope sets the figure. What it costs depends on how many accounts we run, what you turn on and how much of the program we carry for you. Two businesses on Command can be two different engagements, so a single number on this page would be a rate card for something that is quoted. The three tiers below it are published, identical on every page, and they are the bottom of the ladder.

We scope it with you, and you get one flat monthly figure. Month to month, with nothing metered behind it. Setup takes two to four weeks.

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.

What does the managed strategy retainer do for me?

The retainer puts strategy, optimization and approvals on our side, on any tier, scoped with you. The engines your tier carries still draft, score and watch on their own; sourcing is the outbound engine. Our team does the judged work: releasing a prospect send where the engagement is set to review, approving a content piece, deciding what to change next. Where the queue is set to release on the engagement's schedule, it does, and every send is logged.

Without the retainer, that judgment is yours, on whatever your tier carries. Where your tier carries the outbound engine, the review-first queue releases on the setting for your engagement and the view shows what is waiting. Where it carries the content engine, your team approves content or sets it to auto-publish. On every tier, your team decides what to ask for. Same engines, same record, different hands at the gate. The retainer is not Command: Command is the tier that adds the outbound engine, ad creatives and your full marketing team, always on; the retainer is strategy and approvals as an add-on. We settle which you need, or both, when we scope.

Retainer, on any tier
Pricescoped with you
Addsstrategy, optimization and approvals on our side
Enginesunchanged
Termmonth to month

How do I hold your team accountable?

Two mechanisms run whether anyone remembers to check or not. The first is the review-first queue. A prospect email leaves it when a person releases it, or when the queue releases on the schedule set for the engagement, and every send is logged with the draft that went, the mailbox it went from and the time. No budget or bid strategy changes without a person making the change, and that change sits in the account's change history with who made it and when. On a managed engagement the person is ours, and the same records are kept. Sourcing, drafting, scoring and watching run on a schedule; budget decisions do not.

The second is the daily watches. The ads change watch reads your account's change history at 7:05am Eastern and raises material changes the same morning, including Google's own auto-applied recommendations and any change to who has access. The lead watch runs at 7:20am Eastern on an instance whose forms feed the sheet and compares the leads your site recorded against what Ads and GA4 counted. A dead tag surfaces in days, not after a campaign has been cut for it.

Your requests go through the same door. Ask for a website change, a new topic, a keyword or a targeting change from inside the screen and it lands with your team, logged. None of those requests writes to your Ads account, your CRM, your site or your Business Profile directly. A person does that, and the record says so. Underneath it all, the nightly bake at 12:01am Central keeps a page on screen even when a pull fails, so a stale morning is visible instead of blank.

What runs against a managed account
Human gatespend changed by a person; sends logged with draft, mailbox, time
Ads change watchdaily 7:05am ET; our own changes sorted as ours and kept in the record
Lead watchdaily 7:20am ET on an instance whose forms feed the sheet; sheet vs Ads vs GA4
Your requeststo the team, logged, never a direct write
Nightly bake12:01am Central, so the page is never blank

What do I keep if I stop?

You keep the account, the history, the content and the leads. You stop at a month boundary, the default term on every tier and on the retainer. Drop the retainer and approvals return to your team; nothing else changes. Leave Command and what it adds, the outbound engine, ad creatives and your full marketing team, always on, stops. Leaving altogether, you revoke our manager access in your own Google console. The change history of what we did stays in your account for as long as Google keeps it, because it was always there. The content we published stays on your site. Where your forms feed a lead sheet, the sheet stays where it is.

Weigh this against an agency retainer or a hire on mechanism: who does the work, what you can see while they do it, and what happens to the data when they stop. The agency comparison and the in-house comparison walk through both.

The Settings view: brand voice and tone, target keywords, target accounts, a cadence card for content, outbound and email, and a list of channels enabled.
Who does what

Your team at the gate, or ours.

WorkSelf-supervised, your team at the gateManaged
Prospect sendsLeave the review-first queue when a person releases them or on the schedule set for the engagement; each send logged with the draft, the mailbox and the timeRetainer: our team owns the queue and the switch; each send logged the same way
ContentYour team approves, or sets auto-publishRetainer: our team runs the cadence and the approvals
Google Ads searchOn all tiers, managed by our team; our changes sit in the history the watch readsSame record; what Command adds, the outbound engine, ad creatives and your full marketing team, always on, runs alongside it
Strategy and planYours, with the screen to read fromRetainer: strategy and optimization from our team, scoped with you
Requests from the screenTo your TruLata team, loggedSame door, same log
Daily watchesAds change watch 7:05am ET; lead watch 7:20am ET on an instance whose forms feed the sheetSame watches; our own changes sorted as ours and kept in the record
PriceStarter is $400 a month, Launch $650, Growth $1,200, and Command is scoped per engagementCommand scoped per engagement; the managed strategy retainer scoped with you
Nobody is exempt from the record

Every change our team makes to your account is in your account, under our login, open to you in your own console for as long as Google keeps the history.

FAQ

Questions, answered.

Is Command the same as the managed strategy retainer?

No. Command is a tier, scoped per engagement: the Command Center, full analytics, leads, search visibility, the AI visibility program, managed Google Ads search, the assistant and briefings, support tickets, the content engine, Meta ads, the outbound engine, ad creatives and your full marketing team, always on, with the seats your tier carries: three on Starter, three on Launch, ten on Growth and unlimited on Command. The retainer is an add-on on any tier, scoped with you, that puts strategy, optimization and the approvals on our side.

Can I see what your team changed in my ads account?

Yes, in your own Google Ads console. Every change we make to your campaigns is in the account's change history under our login, and the daily watch reads that history at 7:05am Eastern. Who has access is read separately, from the account's user list, because Google's change events do not log it.

Why is there no price for Command on the site?

Because it is scoped per engagement, with you. You get one flat monthly figure, month to month, with nothing metered.

Do you send email or spend money on your own when you manage the account?

Spend, no. Budget and bid strategy changes are made by a person on every engagement, and they sit in your account's change history with who made them. Prospect emails leave from a review-first queue; a person releases them, or the queue releases on the schedule set for the engagement, and every send is logged with the draft, the mailbox and the time. On a managed engagement our team owns that queue.

Can I add the retainer to Starter?

Yes. It sits on top of any tier. Whatever your tier carries stays the same; the judgment moves to our team. Which tier carries the outbound engine and which carries the content engine is on <a href="/product/pricing">the pricing page</a>.

What happens if I drop the retainer or leave Command?

You stop at a month boundary. Approvals return to your team, you revoke our manager access in your own console, the change history stays in your account and the published content stays on your site.

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.