Know what was paid, and by whom, without opening Stripe.
The Revenue view reads your Stripe account when you open the page: what was collected in the window, what is recurring, and each recent payment with the date, the amount, what it was for and who paid. It sits in the left-hand menu right after the Overview, one click from your leads and your ad spend.
What do I see when I open the Revenue view?
Your Stripe account, read through Stripe's own API. The stat row at the top carries the totals for the window the page names: revenue collected, the number of payments, active subscriptions and the recurring figure per month. Click any stat and a panel opens with the current value, the window it covers and a source line.
Two tables sit under the stats. Recent payments lists each payment newest first with the date, the amount, what it was for and who paid; click a row and the panel shows the amount, the date and the customer. Where you sell subscriptions, a second table lists each tier with its price and how many are active now, under a Live badge, and a How this runs line beneath it says in plain words where the figures come from.
Nothing is re-keyed by a person. If Stripe knows it, the view knows it, and a refresh moves it. Press Export and the tables on the screen download as trulata-revenue.csv, exactly as displayed.
Which channel did the money come from?
The Overview answers that. A revenue-by-channel card sits beside the funnel and splits collected revenue by the recorded source of each sale, one bar per channel with its amount and its share. Click a channel and the panel shows its revenue and its share of the total.
The card appears only where the source of each sale is recorded. Where it is not, the card is not shown, and nothing is guessed into a channel. An empty card would be a guess dressed as a number, and a wrong split would send your next dollar to the wrong place.
The lead side of the same question lives on the Leads view, where each row carries the source, the landing page and the referrer captured when the form was submitted. The spend side lives on the Google Ads view, with spend, conversions and cost per conversion for each campaign. Revenue, leads and spend are three views in one menu, not three logins.
What if my business runs on a CRM or booking platform instead of Stripe?
Then the Jobs view carries your job pipeline, read live from your CRM or booking platform, and the Revenue view reads whatever you take payment through. A business that runs both sees both. The point is one screen, not one vendor: revenue is read from where it lands.
Each view appears only when its source is connected. The Revenue view is in your menu once Stripe is reading and absent until then, rather than sitting on the screen with a sample figure. Jobs appears only where your CRM or booking platform is connected, and it shows a coming-soon card until the data behind it is trustworthy.
Stripe is the payment platform the Revenue view reads today, and it reads your own account, with access you grant.
How do I get from all this to a cost per won job?
By division, with every part of it on the screen. The Google Ads view records spend, conversions and cost per conversion for each campaign. The Leads view records every form submission your site received and, with outcomes switched on for your instance, lets your team mark each one New, Contacted, Quoted, Won or Lost from a dropdown on the row. The Revenue view records what was paid. Cost per won job is spend divided by jobs won.
Take an example with round numbers. The ads view shows $2,400 spent in the window. Twelve leads on the Leads view are marked Won. Cost per won job is $200. The Revenue view shows what was collected in the same stretch, payment by payment with the customer on each, so you read the two against each other on one screen. You did not export anything or reconcile two logins to get there.
The number is only as good as the outcomes your team sets. A lead nobody has marked stays counted as a lead and stays New; nothing is assumed about it. A lead that has sat two days with no status wears a badge reading no contact marked yet, with its age in days, computed from your own record. The gap shows the week it opens, not at the end of the quarter.
What runs on its own, and what stays with a person?
The reading runs on a schedule whether anyone is at a desk. Open the page and it loads last night's snapshot first, fetches the live payload from a cache at once, and starts a pull in the background if that snapshot is older than five minutes. Press Refresh and a full pull starts, 2 seconds to a little over 3 minutes depending on how many sources you have; the page reloads when the stamp moves and never shows an error. Every night at 12:01am Central one job rebakes the fallback snapshot for every client, and a failed pull leaves yesterday's page up rather than shipping an empty one.
The money never moves on its own. The view reads Stripe and never creates a charge, a refund or a subscription. Budget and bid changes in your ad accounts are made by a person, never by a scheduled job. The outcome on a lead is set by your staff, not inferred. What a person can write from the screen is short: a lead outcome, to the lead record; a website change request, or a content, keyword, category or targeting request, to our team, logged. None of it writes to Stripe, your ads account, your CRM or your site directly.
Two watches run each morning on the marketing that feeds this screen. At 7:05 Eastern the ads change watch reads your ad account's change history and its user list, because a change to who has access is not logged as a change event. At 7:20 Eastern, on an instance whose forms feed the lead sheet, the lead watch compares what the sheet holds against what Google Ads and GA4 counted. The watches read; any change that follows is made by a person.
How is Stripe connected, and where is the ceiling?
Our team connects Stripe from the inside during setup, with access you grant. You paste no key and install nothing; there is no wizard and no client-side sign-in. Setup takes two to four weeks and is not billed: access in week one, the first pull with your baselines in week two. The Revenue view is part of the Command Center, which is on all tiers, and it appears in your menu once the connection is reading.
Read the ceiling before you buy, because the sources set it. Stripe is live: it records a payment when it succeeds, and a refresh moves it. Your CRM, your booking platform, website leads and email statistics are live too. Google Ads and GA4 intraday figures on the same dashboard lag by hours, and Search Console runs two to three days behind. The stamp in the header says when the data was pulled; hover it and it says either that the numbers were pulled live when you opened the page or that the live refresh was unreachable and you are reading the last saved snapshot.
It does not forecast, and it holds no card data. A number on this screen is a payment that already happened, a subscription active now or the price of a tier you sell. No card number is read on any instance. If Stripe did not record it, the screen does not show it.
Check three things in the demo. The demo runs the same engine code every client instance runs, on a fictional company with illustrative numbers, and there is no form to fill. It has no Stripe account behind it, so the Revenue view is not in its menu; on your instance it is. Open the Overview, click a revenue-by-channel bar and read the panel: revenue and share. Click a headline card and confirm the window and the source line. Then press Export and open the file, because that same button on your Revenue view is how the tables leave the screen.
What the Revenue view reads.
| What | Where it comes from | How fresh |
|---|---|---|
| Payments | Stripe API | Live |
| Subscriptions and tiers | Stripe API | Live |
| Recent charges | Stripe API, newest first: date, amount, what, who | Live |
| Revenue by channel | The recorded source of each sale, on the Overview | Shown only where a source is recorded |
| Jobs | Your CRM or booking platform, where used | Live |
| Writes and card data | None; no card data read | Never |
Every figure on the Revenue view is a payment that already happened, a subscription active now or the price of a tier you sell, read from your own Stripe account, and nothing on the screen can charge, refund or change anything there.
Questions, answered.
Is the revenue number live?
Yes. Stripe records a payment when it succeeds and the view reads Stripe directly, so a refresh moves it. The stamp in the header says when the data was pulled.
Can it charge or refund anyone?
No. The view reads Stripe and never writes to it: no charge, no refund, no subscription change, and no card data is read.
Do I need Stripe?
No. Stripe is the payment platform the Revenue view reads today, and the view appears only once it is connected. Businesses whose jobs live in a CRM or booking platform get a Jobs view, read live.
How is revenue tied to a marketing channel?
Through the recorded source of each sale. The Overview splits collected revenue by that source and shows the card only where a source is recorded; nothing is guessed into a channel.
Does it forecast?
No. Every number on the screen is a payment that already happened, a subscription active now or the price of a tier you sell.
Which tier includes it?
Once Stripe is connected on your account, it is there. A view appears when its source is connected, and the pricing page lists what each tier includes.
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.