See the whole product before you decide. No form, no account.
demo.trulata.com is the Command Center itself, running on a fictional company called Meridian. Every view opens, every number drills down, and the screen tells you which numbers are invented.
Where is the demo, and what do I need?
A browser. Open demo.trulata.com and you land on the Overview of a running instance; nothing asks for your name first. It is the same engine file every client dashboard runs, pointed at a fictional company so it can be public. The left-hand menu is the client's menu: Overview and Leads at the top, then the channels (search, answer engines, Google Ads, content, outbound, email), then Analytics and Social, then Website, Integrations and Settings, then Account, Team, Billing and Branding.
Give it ten minutes and click everything. Headline cards, funnel stages, keyword rows, campaign rows and channel bars each open a panel with the number, its window and a note on where it came from. The fastest way to judge the product is to try to find a number that leads nowhere. If you want the guided version first, the Platform page walks the screens in order.
What in the demo is real?
The product. The views, the drill-down panels, the request flow, the menu and the layout are exactly what a client sees. The engine is one shared file that the demo runs too, so the demo cannot show you a screen the product does not have, and a change that ships to clients ships to the demo.
The request flow is real in shape. Open Website and use Request a website change, or open Settings and click Edit beside Brand voice. A box opens that says Goes straight to your TruLata team. On the demo the send is simulated and the toast says so. On your instance the same button sends the request to our team, logs it and hands you a ticket number you can quote back to us. Nothing you type there writes to your ad account, your CRM, your site or your Business Profile directly; a person makes the change.
The honesty on the screen is real too. Click a metric on the demo and the panel says the drill-down is illustrative in this sample workspace. On your instance the same panel says the number was pulled from your connected accounts. The product labels its own numbers, and the demo is where you can watch it do that.
What in the demo is invented?
Meridian. Its team, its numbers, its campaigns, its content titles, its invoices and its plan are all illustrative, there to show the shape of a screen and not to make a claim. Meridian is written as a software company, so its leads read Demo request and its conversions read Trial signup. Your instance shows your own form submissions and your own GA4 key events under the names your forms and your analytics give them.
The Integrations view is wider than a real account. The demo lists the whole catalogue with a Connect pill on every source and lets you switch the active model, so you can see what the screen does. Your instance lists only what is connected, and a view whose source is not connected does not appear. The real list of what each connection reads is on the Integrations page.
The answer-engine view shows more bars than your instance measures. Meridian's per-engine bars are sample data. On your instance the engines are ChatGPT, Gemini, Claude and Grok, each asked through its own API, and a blank answer leaves the denominator instead of counting as a miss. Google AI Overviews are measured on the search view, not here.
What should I check while I am in it?
Start with one number and follow it down. On the Overview, click the first headline card. The panel shows the value now, its change, the window and a trend line, with a note under it on where the number comes from. That panel is the unit of the whole product: a number, its window, its source. If you would trust a report built only from panels like that, you will trust the dashboard.
Open Leads. The ledger runs newest first, with the time, the name, what the person asked for and the page they were on; click a row for the full message. On your instance each row is written server-side the moment a form is submitted and emailed to your team at the same time, which is why the count keeps working on a day a tracking tag breaks.
Open Google Ads. Each campaign row carries spend, conversions and cost per conversion, and clicking it opens the bid strategy and the negatives added in the last 30 days. Open AEO / GEO for the presence score, the per-engine bars and the list of buyer questions with a rank wherever the business was cited. Open Team to see seats used against plan seats and an invite box with the roles Member and Admin. Open Branding for the logo upload, PNG, SVG or JPG up to 2 MB, and the brand colour.
Then try to break it. Look for a headline card that does not open, a panel that does not name its window, or a screen that needs a manual. If you find one, tell us which.
What can the demo not show me?
Freshness. The demo hides the Refresh button and carries no data stamp, because nothing behind it was pulled. Your instance loads last night's snapshot first, fetches the current payload from a cache the moment it opens, and runs a pull in the background when the snapshot is older than five minutes. Refresh starts a real pull against your accounts, two seconds to a little over three minutes depending on your sources, and the page reloads when the stamp moves. It never shows an error.
The ceiling is the upstream, not us. Your CRM, Stripe, your booking platform, website leads and email statistics are live. Google Ads and GA4 intraday numbers lag by hours. Search Console runs two to three days behind however often it is asked. A nightly bake at 12:01am Central writes the fallback snapshot for every client, and a failed pull leaves the previous page up rather than shipping an empty one.
The schedule. Part of the product runs on a schedule whether anyone is at a desk: prospects are sourced weekly to your target profile, the ads change watch reads your change history at 7:05am ET every day, and the content engine moves each piece from queued through research and draft to posted. Part of it stays with a person: budget and bid changes in ad accounts are made by a person, never by a scheduled job, and 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. The ads watch exists for a real day: a Google auto-applied recommendation flipped an AI-driven setting on across three search campaigns in one second under a client staff login, ran 26 days, put impressions up roughly five times and cost up 65 percent week over week, and conversions stayed flat.
The sign-in, and what is never connected. The demo is public; your instance sits behind Cloudflare Access, and you sign in with a single-use magic link from login.trulata.com, with a chooser if you hold more than one seat. Removing a seat takes effect within 30 seconds. Every Google connection is a manager invitation you can revoke in your own console, and we do not hold your passwords. No instance reads your email, your calendar or your customers' card data, and a phone call counts as a lead only when your CRM records it.
Can I see it on my own numbers?
Yes, in the first two weeks of setup. Week one is access: you add our Google account as a manager on your Analytics property, your Search Console site, your Ads account and your Business Profile, and our team connects your CRM, Stripe, your booking platform and your forms from the inside with access you grant. There is no wizard and nothing for you to paste. Week two is the first pull: your numbers fill the Overview, the answer-engine baseline is scored, the keyword set is agreed and the daily ads watch starts. That is real data on the real screen before the content cadence, ads reports and email flows start in weeks three and four. Setup takes two to four weeks and is not billed.
Nothing happens because you looked. The demo has no gate and asks for nothing. A button in the corner of the demo opens a short form: company, size, marketing spend, what to run first, timeline. Send it and a confirmation goes to the address you gave, a person reads it, and we come back with what the screen looks like on your data. If you would rather read first, the pricing page lists the published tiers and the contact page reaches a person.
The demo, in one table.
| What | Where it comes from | How fresh |
|---|---|---|
| URL | demo.trulata.com | Public, no account |
| Company | Meridian, fictional | Every number illustrative, and labelled |
| Engine | The same code every client dashboard runs | Current |
| Views | Every view, including some your account may not show | Working |
| Refresh and stamp | Hidden on the demo; on your instance a real pull, 2 seconds to a little over 3 minutes | Live when you open it |
| Follow-up | Only when you send the form in the corner | You decide |
The demo is the only place this product shows invented numbers, and the screen says so; your instance shows what your accounts contain and hides any view whose source is not connected.
Questions, answered.
Do I need to sign up to see the demo?
No. demo.trulata.com opens in any browser with no form and no account.
Is the demo the real product?
Yes. It runs the same engine file every client dashboard runs, pointed at a fictional company.
Are the numbers real?
No. Meridian and its numbers are invented to show the shape of each screen, and the drill-down panels say so.
Why is there no Refresh button in the demo?
Because nothing behind the demo is pulled. On your instance the button starts a real pull against your accounts, two seconds to a little over three minutes, and the page reloads when the stamp moves.
Can I see it on my own accounts?
Yes, in the first two weeks of setup: the first pull fills the Overview, the answer-engine baseline is scored and the ads watch starts, all on your accounts.
Will someone contact me because I opened it?
Only if you ask. The form in the corner of the demo is the ask; opening the page is not. A person reads every one you send.
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.