Open one page and know what your marketing did, without asking anyone for a report.

How fresh are the numbers when I open it?

Last night's numbers first, then today's. The page renders a snapshot baked at 12:01am Central before any request returns, so the first screen is always full. It then asks our service for the live payload, which a warm service answers from cache in about 100 milliseconds. If that snapshot is older than five minutes, a pull of your sources starts behind the request. Ten people opening at 9am cause one pull, not ten.

The fresh numbers swap in when they land. The page then checks every 3 seconds for the new snapshot, swaps it in and puts you back on the view you were reading at the same scroll position. It waits while a panel is open or you are typing.

Read the stamp before you read a number. Beside the page title a stamp gives the time of the last pull. Hover it and it says one of two things: pulled live when you opened the page, or live refresh unreachable, showing the last saved snapshot. The age of the data is always on the screen.

Press Refresh and every connected source is pulled again. A pull takes 2 seconds to a little over 3 minutes depending on how many sources you have, so the page polls until the stamp moves, then reloads. A slow pull, an unreachable service and a five minute timeout all end the same way: a reloaded page whose stamp says how old what you are reading is. The button has no error state.

What runs on its own, and what stays with a person?

Scheduled work runs whether anyone is at a desk. Prospects are sourced weekly to your target profile on Command; enrichment finds a deliverable address or routes the prospect to a contact form. Content moves through research, draft and publish on your cadence on Launch, Growth and Command. Each topic passes a demand gate before a word is written: real search volume above a floor and below a head-term ceiling, and a live top ten not already owned by major publishers. A topic is written on demonstrated demand, and one that fails the gate is rejected. Each piece cites current sources, is filed as a Google Doc in your Drive and carries a generated featured image. The ads change watch reads every Ads account mapped to a client at 7:05am Eastern. On an instance whose forms feed a lead sheet, a lead watch built for that instance compares the sheet with Ads and GA4 at 7:20am Eastern.

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 shown, and not-interested or bounced addresses are suppressed from further sends. Named accounts are always reviewed by a person. Budget and bid changes in ad accounts are made within the limits set for your engagement and land in your account's own change history. Approval on content is a setting you choose.

Your requests take the same path. Ask for a website change, a content topic, a keyword target, a category or a targeting change from inside the screen. The request is logged, opened as a ticket with a number and sent to your team, and the confirmation on your screen carries that number. An email to [email protected] opens a ticket the same way. The Support view lists every ticket with when it was opened, where it came from, its subject and its status, and our replies sit under it. The engine's writes to your ad accounts and your site go through their APIs and land in each account's own change history, and the ticket carries the reply when your change is done.

How soon do I see my own numbers, and what should I check in the demo?

Access comes first: the four manager invitations, the CRM link, the website and its forms, and your login working. Then comes the first pull, which fills the Overview with your numbers, plus the answer-engine baseline across ChatGPT, Gemini, Claude and Grok, the keyword set for the search view, and the ads watch starting on your account. A blank answer from an engine is a measurement error and leaves the denominator, so your score reflects answers rather than outages. After that come the content cadence, the first ads reports and the email flows. Views arrive as their sources connect, and every number on them is yours.

Your login is a single-use link from login.trulata.com, sent to the email on your seat, with a chooser if you hold more than one seat. A single-use sign-in link confirms who you are; our seat list decides what you may open. The Team view shows seats used of plan seats, and you invite by email as Member or Admin. Remove a seat and the revocation takes effect within 30 seconds. Every instance passes a preflight before every deploy, and one of its checks is that no other client's name appears anywhere in your files.

Before you sign, open demo.trulata.com. It opens in any browser, with your name and email in front of it. It runs the same engine code every client runs, on a fictional company, with every number illustrative. Check four things. Click a headline metric and confirm it opens with its value, its change and its window. Open a workstream from the Overview grid and confirm the view names its source. Open Support and see how a request is listed: ticket number, when it was opened, where it came from, subject and status. Note that the Refresh button lives on your instance, where live sources sit behind it; the demo runs on fixed numbers and leaves it out. Then ask us which of your sources will be live and which will lag. The answer is per source, and we put it in writing.