Your numbers on one screen in two to four weeks, and nothing invented to fill a gap.
Send four manager invitations and our team connects the rest with access you grant. By week two you open your own numbers. By week four the engines run on a schedule whether anyone is at a desk.
How do my accounts get connected, and what do I hand over?
Send four manager invitations and week one is mostly done. Add our Google account as a manager on your Analytics property, your Search Console site, your Google Ads account and your Business Profile listing. Each invitation takes a few minutes in your own console, and you can revoke any of them there whenever you choose. We never hold your passwords.
Our team connects the rest from the inside with access you grant: your CRM, Stripe, your booking platform, your email platform and your website's forms. There is no wizard, no API key to paste and no consent screen to click through. Your instance is created from the canonical engine by one command and passes a preflight before anyone opens it: the engine files match the canonical, the Access gate is in place, the redirect is a 302, the fallback snapshot is present, and nothing from any other account appears in your files.
By the end of the week your login works. Sign in with a single-use magic link from login.trulata.com; there is no password to manage. Open the Integrations view and read the state of every source: Connected where the link is live, Connect where an invitation is still waiting. Invite your team from the Team view by email, as Member or Admin, and the view shows seats used against plan seats. Seats are three on Starter, three on Launch, ten on Growth and unlimited on Command. A removed seat stops working within 30 seconds.
What we need from you: the four invitations, and a written note of which accounts are which.
When do I see my own numbers?
Week two. Open the Overview and the first live pull has filled it from the accounts connected in week one: the headline cards at the top, the pipeline funnel and revenue by channel below them, and a grid of every workstream with its status. Click any card and it opens with the number, the change and the window. The header stamp reads the time of the last pull, and the Refresh button beside it starts a new one.
Baselines are taken this week so that later movement means something. Your question set is written with you, worded the way a buyer types it, and put to ChatGPT, Gemini, Claude and Grok through each engine's own API. A blank answer is recorded as a measurement error and leaves the denominator; it is never scored as a miss. The first run reads baseline and carries its date. The keyword set for the search view is agreed the same week. Its positions are Search Console average positions, and Search Console runs two to three days behind, so the first search numbers you read are two to three days old. Keyword search volumes come from Google's keyword planner through our Ads access.
The Google Ads change watch starts on your Ads account. Every morning at 7:05 Eastern it reads the account's change history, separates our own writes and routine noise from material changes made by anyone else, and reads the account's user list directly, because a change to who can see your account never logs as a change event. On Command, the target profile is set this week and the first sourced list is ready for your review.
What we need from you: the questions your customers ask, in their words. On Command, the trades or areas you want prospects from, and an hour to read the first list.
When does the work start running?
Weeks three and four. On Launch, Growth and Command, the content cadence is set and the first piece moves through the pipeline: queued, researching, writing, draft, then approved and posted, with your approval if you want one. Topics pass a demand gate on real search volume and on how occupied the results already are, and the dedupe reads the titles already published on your site. Each piece is filed as a Google Doc in your Drive with a featured image generated for it. Auto-publish is a setting on your instance.
The ads watch has been reading your account every morning since week two, and a material finding is reported the same morning. Across the accounts we watch, a 29-day window held 337 change events; 291 were our own writes and 21 were material. The watch is built to find those 21. It exists because of a real case: a Google auto-applied recommendation flipped an AI-driven setting on across three search campaigns in one second under a staff login, ran 26 days, and took impressions to roughly five times and cost up 65 percent week over week with conversions flat.
Where your website's forms feed the lead sheet, the lead watch starts: every morning at 7:20 Eastern it runs five checks across the sheet, Analytics and Ads, named loader, blind, ads blind, stalled and silent. Its real case: a tag change silently stopped every conversion for six weeks, 21 real leads landed while Ads reported zero, and the owner paused the campaign that carried every counted lead and cut its budget 90 percent. Email flows are confirmed running where you send through your email platform. Program goals are set on the Overview, in a card titled what we hold ourselves to, so the target sits next to what happened.
By the end of week four every view whose source is connected is on your screen with your numbers in it. A source that is not connected shows Connect in the Integrations view, and the view that needs it stays off the screen. The Jobs view appears only where your CRM or booking platform runs your jobs, and it shows a coming-soon card until its data is trustworthy.
What do I have to keep doing after setup?
Nothing. The scheduled work runs whether anyone is at a desk. The page pulls live when you open it, and a pull runs behind the request when the snapshot is older than five minutes. The fallback snapshot bakes at 12:01am Central every night. The ads watch reads at 7:05am Eastern, the lead watch at 7:20am Eastern where it applies. Prospects are sourced weekly on Command, and content moves on your cadence on Launch, Growth and Command.
The judged work stays with a person. 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. Replies are classified, and not-interested and bounced addresses are suppressed. Budget and bid changes in your ad accounts are made by a person, never by a scheduled job.
Ask for changes from the screen. Set an outcome on a lead and it writes to the lead record. Request a website change, a content topic, a keyword, a category or a targeting change and it goes to your team, logged. Nothing on the screen writes to your Ads account, your CRM, your site or your Business Profile directly.
Know the ceiling before you open it. Your CRM, Stripe, your booking platform, website leads and email stats are live. Google Ads and Analytics intraday numbers lag by hours. Search Console runs two to three days behind. Your email inbox, your calendar and customer card data are never connected. A phone lead counts only when your CRM records it. If a night's pull fails, the previous page stays up rather than an empty one, and the header stamp says how old the data is.
What does setup cost?
Nothing beyond your first month. Setup takes two to four weeks and is not billed. You pay the first month, and setup on your own accounts starts. Starter is $400 a month, Launch $650, Growth $1,200, and Command is scoped per engagement. Every tier is month to month, and nothing is metered. An annual commitment takes twenty to twenty-five percent off the monthly. Command carries no number on the site. A managed strategy retainer is an add-on on any tier, scoped with you.
Leaving is the same shape as arriving. Revoke our manager access in your own consoles, and the Google Docs the content engine filed in your Drive stay yours.
What should I check in the demo before I sign?
Open demo.trulata.com. There is no form. The company is fictional and every number is illustrative, but the engine code is the same code your instance will run, so the screen you see is the screen you get.
Open the Integrations view and read how a source is labelled: Connected where the link is live, Connect where it is not. That is what your own week one looks like as invitations land. Open the Overview and find the data stamp in the header; on your instance it reads the time of the last pull, and the Refresh button beside it starts a new one. A pull takes from two seconds to a little over three minutes, and every path through Refresh ends in a reloaded page, never an error.
Then check three things about your own accounts against the ceiling above. Which of your sources are live and which lag. Whether your jobs run on a CRM or booking platform we connect today, because that decides whether a Jobs view appears. Whether your website's forms feed the lead sheet, because the lead watch runs only where they do. Write to us with the answers.
Setup, week by week.
| What | Where it comes from | How fresh |
|---|---|---|
| Week 1 | Access and connections; instance created from the canonical engine and preflighted | You: four manager invitations |
| Week 2 | First live pull; answer-engine baseline; keyword set; ads change watch on; target profile on Command | You: your customers' questions; one list review where it applies |
| Weeks 3 to 4 | Content cadence and first piece on Launch, Growth and Command; ads findings; lead watch; email flows; program goals | You: approvals if you want them |
| After | Live pull on open; nightly bake 12:01am CT; ads watch 7:05am ET; lead watch 7:20am ET; weekly sourcing on Command | You: open the screen |
| Ceiling | CRM, Stripe, booking platform, leads and email stats live; Ads and Analytics lag hours; Search Console 2 to 3 days | Stated on the header stamp |
A source that is not connected shows Connect in your Integrations view and its view stays off the screen; nothing on your instance is ever filled with an illustrative number to make setup look finished.
Questions, answered.
How long does setup take?
Two to four weeks. Access in week one, the first live pull and the baselines in week two, the engines running by week four. It is not billed.
What do I have to do?
Send four manager invitations from your Google consoles, confirm in writing which accounts are which, and give us the questions your customers ask. On Command, name the trades or areas you want prospects from and read the first list.
Can I see my numbers before setup is finished?
Yes. The first live pull in week two fills the Overview, and each view appears as its source connects. The header stamp says when the data was pulled.
What if a connection cannot be made?
That source shows Connect in the Integrations view, the view that needs it stays off the screen, and everything else works. Nothing is filled with a sample.
Is there a wizard or a form to fill?
No. You send the manager invitations; our team makes every other connection from the inside with access you grant. There is no API key to paste and no consent screen to click.
Do I hand over any passwords?
No. Every Google connection is a manager invitation you can revoke in your own console, and the rest are made by our team with access you grant. Your email inbox, your calendar and customer card data are never connected.
Is there a setup fee?
No. You pay the first month and setup starts. Nothing else is billed for the two to four weeks, and every tier is month to month with nothing metered.
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.