Stop being the one who remembers. Marketing automation software that runs the routine on a schedule, while you keep the decisions.
TruLata is marketing automation software for a service business: the work that runs on a schedule whether anyone is at a desk. Open the page and it pulls live. Every night a fallback snapshot bakes. At 7:05am Eastern the ads change watch reads your account. At 7:20am Eastern the lead watch checks your sheet, where your forms feed it. Prospects are sourced weekly and content runs on your cadence, each on the tier that carries its engine. Our team connects your sources, sets the cadences, and builds the workflows between your tools that your business needs. Budget and bid changes move within the limits set for your engagement and land in your account's own change history, and every send and every request is logged.
What will the marketing automation software run without me once it is set up?
The work that used to wait for someone to remember it. The marketing automation software on the TruLata Marketing Command Center runs it on a schedule. Open the page and it pulls live numbers. At 12:01am Central it bakes a fallback snapshot. At 7:05am Eastern it reads your Google Ads change history. At 7:20am Eastern, where your forms feed it, it checks your lead sheet against Ads and GA4. Weekly, on Command, it sources prospects. On Launch, Growth and Command, it researches and drafts content on your cadence. All of it runs whether anyone is at a desk, and a budget or bid moves only within the limits set for your engagement.
The service is what our team does around that. We connect each source with access you grant during setup and set the cadence, the keyword set and the target profile with you. Where your business needs a workflow between two tools you already run, we scope it with you and build it during setup on the same pattern: the routine part runs on a schedule, the judged part waits for a person, and each send and each request is logged.
It is built for the service business where nobody on staff has marketing as their job. A territory is typical, a multi-location or national company fits the same way, and the software is sold nationally. The checks that catch a dead tag or a flipped setting run every morning on their own, and your hours go to the budget, the reply and the decision. The page for a business with no marketing team walks through that split.
Where do I see what the automations did?
On the Overview first. Every workstream sits in a grid marked Running with its latest figure, and where that view is live on your instance a click opens it. In the header, on the Marketing Command Center line above 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 this page, or live refresh unreachable, showing the last saved snapshot. Press Refresh and every path ends in a reloaded page whose stamp says how old the data is; the live data page covers the first second.
Then each automation reports into the view built for it. Where your forms feed the lead sheet, the Leads view reads that sheet newest first. The Content view counts the pieces at each pipeline stage and shows the recent pieces with their generated featured images and the Drive folders they were filed in. The Outbound view shows the review-first send queue, each prospect with its signal and an awaiting approval status, and the recent replies, classified. The Google Ads view shows spend, conversions and cost per conversion by campaign; the change watch is a finding sent to the team, not a screen. The Integrations view lists what is connected on your instance.
Read the freshness ceiling before you buy. Your CRM, Stripe, your booking platform, website leads and email statistics are live. Google Ads and GA4 intraday figures lag by hours. Search Console runs two to three days behind. Card data is never read. Your inbox and calendar sit outside the product today, Stripe is read only, and a phone lead counts when your CRM records it; a call-tracking platform you run is connected during setup like any other source with an API.
What runs on a schedule, and what stays with a person?
Scheduled work runs whether anyone is at a desk. Open the page and it renders last night's snapshot first, serves the live payload from cache, and starts a pull behind the request when that snapshot is older than five minutes. At 12:01am Central a fallback snapshot bakes for every client from one registry; a failed pull or a failed syntax check leaves the previous page up, so the page you open always has yesterday's numbers at the least.
Every morning at 7:05am Eastern the ads change watch reads your Google Ads change history and the account's user list, separates our own writes and routine noise from material changes by anyone else, and raises the material ones to the team. A setting switched on under any login, or a new address given access, is known the next morning. At 7:20am Eastern, where your forms feed the lead sheet, the lead watch runs five checks against Ads and GA4: loader, blind, ads blind, stalled and silent. The leads that landed are checked against the conversions Google counted, so a dead tag, a blind ad account or a stalled form is flagged the next day instead of at the end of the quarter. Weekly, on Command, prospects are sourced to your target profile. On Launch, Growth and Command, each topic passes a demand gate on real search volume before a word is written.
Judged work stays with a person. A budget or bid change in your ads account is made within the limits set for your engagement and lands in your account's own change history. 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. Whether a content piece publishes on its own or waits for approval is a per-client setting. From the screen, set a lead outcome and it is written to the lead record. Request a website, content, keyword, category or targeting change and it reaches your TruLata team as a numbered ticket. A request from the screen goes to your team as a logged ticket; the engine's writes to your ad accounts and your site go through their APIs and land in each account's own change history.
Can I see it before I talk to anyone?
Yes. Open the demo at demo.trulata.com. It opens without a form. It runs on a fictional company called Meridian, every number in it is illustrative, and it is the same engine code every client dashboard runs. Open the Overview and find the workstream grid, each tile marked Running. Open Outbound and read the review-first queue, each prospect awaiting approval. Open Support and see how a request is listed: ticket number, when it was opened, where it came from, subject and status.
Then read what your instance adds. The Refresh button is hidden on the demo, because the demo has no live service behind it; on your instance it sits in the top bar. The morning watches are findings sent to the team, not a screen, so ask to read one.
Which tier carries the automations?
Starter includes the Command Center, full analytics, leads, search visibility, the AI visibility program, managed Google Ads search, the assistant and briefings and support tickets. Google Ads search is managed on all tiers. The content engine runs on Launch, Growth and Command. Meta ads are managed on Growth and Command. The outbound engine runs on Command. Command adds the outbound engine, ad creatives and your full marketing team, always on, is scoped per engagement and carries no number on this site.
Seats are three on Starter, three on Launch, ten on Growth and unlimited on Command. Starter is $400 a month, Launch $650, Growth $1,200, and Command is scoped per engagement. Every published tier is month to month with nothing metered, and an annual commitment takes twenty to twenty-five percent off the monthly. The pricing page carries the same figures.
Can your team build it and run it for me?
Yes, and that is the service this page sells. The first half is building. We map the hand-offs your team does by hand, the report rebuilt every Monday, and rank them by the hours they cost. What the product already connects is on the integrations page: your Google properties by manager invitations you can revoke in your own console, and the rest linked by our team from the inside with access you grant during setup. We never hold your password. Where two tools you already run need a connector, we write it during setup. A workflow beyond that list is scoped with you, carries no number here, and is built on the pattern above: routine on a schedule, judgment with a person, every send and every request logged. AI agents covers the applied-AI side of the same pattern.
The other half is running. Command adds the outbound engine, ad creatives and your full marketing team, always on, scoped per engagement. The managed strategy retainer sits on top of any tier, scoped with you, and puts strategy, optimization and the approvals on our side: our team owns the review-first queue and its switch and runs the content cadence and its approvals. Every change our team makes in your Google Ads account lands in your account's own change history under our login, and the same 7:05am Eastern watch sorts it as ours. Neither carries a number on this site. The managed page covers both, and the pricing page carries the three published tiers.
TruLata is also a marketing services firm. The analytics service reads the same morning watches with you, paid search runs the account the ads watch reads, and content creation runs on the cadence the content engine keeps. The services hub lists the rest, and local services marketing is the hub for a trade with a territory.
What runs, and when.
| Automation | What it does | When it runs |
|---|---|---|
| Live pull | Renders last night's snapshot, serves the live payload from cache, and pulls behind the request when the snapshot is older than five minutes | When you open the page |
| Refresh button | A fresh pull of your connected accounts; every path ends in a reloaded page whose stamp says how old the data is | 2 seconds to a little over 3 minutes |
| Fallback snapshot | Nightly bake for every client from one registry; a failed pull or a failed syntax check leaves the previous page up | 12:01am Central |
| Ads change watch | Google Ads change history and user list; our own writes and routine noise separated from material changes by anyone else | Daily, 7:05am Eastern |
| Lead watch | Your lead sheet against Ads and GA4, five checks: loader, blind, ads blind, stalled, silent | Daily, 7:20am Eastern, where forms feed the sheet |
| Prospect sourcing | To your target profile; a deliverable address or a contact-form path; drafts to a review-first queue; every send logged | Weekly, on Command |
| Content | Demand gate on search volume and the result page; research citing current sources; a Google Doc in your Drive and a featured image per piece | On your cadence, on Launch, Growth and Command; auto-publish or awaiting approval |
Budget and bid changes stay within the limits set for your engagement and land in the account's change history. Card data is never read, and your inbox and calendar sit outside the product today. Stripe is read only. A phone lead counts when your CRM records it, and a call-tracking platform you run is connected during setup. A request from the screen reaches your team as a logged ticket, and the engine's writes go through each platform's API.
Questions, answered.
Is this the automation inside the Command Center, or something you build for me?
Both. The Command Center ships the scheduled work: a live pull when you open the page, a fallback snapshot at 12:01am Central, the ads change watch at 7:05am Eastern, the lead watch at 7:20am Eastern where your forms feed the sheet, weekly prospect sourcing on Command and content on your cadence on Launch, Growth and Command. The service is our team connecting your sources, setting the cadences, and scoping and building any workflow beyond that list on the same pattern.
Does anything send email or spend money on its own?
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. 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. Stripe is read only, so charges and refunds stay in your own hands.
Which tools can you connect?
Google Analytics 4, Search Console, Google Ads and Business Profile, each by a manager invitation you send from your own console and can revoke there. Your CRM, whichever you run; Stripe, read only; your booking platform; your email platform; your website through its API, WordPress, Webflow or Shopify, or a static site we host; Meta where connected; and your website forms, which append each submission to a lead sheet server-side and email your team. Our team links those from the inside with access you grant during setup, and the Integrations view on your instance carries a request button for anything else. A tool beyond that list, anything with an API, is connected during setup.
What does the ads change watch catch?
Material changes by anyone other than us, including the recommendations Google applies on its own, and any change to who can see the account. Every morning at 7:05am Eastern it reads the change history and the account's user list, sets our own writes and Google's routine churn aside, and raises what is left to the team the same day. A setting switched on under any login is known the next morning. The user list is read directly because Google's change events do not log who was granted access.
What happens when an automation fails?
The page keeps the last good numbers and says how old they are. The nightly bake refuses to deploy a failed pull or a failed syntax check and leaves the previous page up. Every path through the Refresh button ends the same way: a slow pull, an unreachable service or a timeout all end in a reloaded page whose stamp says the age of what you are reading, and the stamp's hover text says whether it is a live pull or the last saved snapshot.
Which tier includes it?
Starter includes the Command Center, full analytics, leads, search visibility, the AI visibility program, managed Google Ads search, the assistant and briefings and support tickets. The content engine runs on Launch, Growth and Command, and the outbound engine runs on Command. Command adds the outbound engine, ad creatives and your full marketing team, always on. Command, the managed strategy retainer and any custom workflow are scoped with you and carry no number on this site; the three published tiers are on <a href="/product/pricing">the pricing page</a>.
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.
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.
Start here: AI marketing platform · AI marketing software · all-in-one marketing platform · marketing automation software · marketing software for small business.
- 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
- Seen in AI answersHow often ChatGPT, Gemini, Claude and Grok name you, measured
- Every send loggedProspect emails leave from a review-first queue, and every send is logged.