For revenue marketing leaders at B2B SaaS companies whose stack has outgrown any one person's head.
When a number moves, is it real — or is it your tracking?
Steward watches your stack and shows you whether the move was real, with the evidence you need to defend the call.
No email required. Your read comes back immediately.
An animated preview of the opening of the investigation follows. The full investigation transcript is below.
A reconstruction of a real Steward investigation from a live deployment. Names, numbers, and details changed.
Built and run by the FunnelEnvy team. A decade of enterprise funnel work for:
Read the full investigation
That question, answered on a real stack, as it happened, in Slack.
Every fix to your tracking creates a new thing to track. The hard part isn't noticing something moved; it's proving which system moved it.
A reconstruction of a real Steward investigation from a live deployment. Names, numbers, and details changed.
A number moved. It was not demand. It was a consent setting over-blocking tags. Six days, one thread.
1Most days, this is the whole experience: open Slack, see you’re good, move on.
✅ Daily demo-request read: all good.
Marketo: 24 fills (normal range 20–29). GA4 capture: 64% of Marketo, inside the expected band (55–70%).
Nothing needs you today.
2It doesn’t say “something moved.” It says which system disagrees, and which side to suspect.
🚨 Variance flag: GA4 demo capture fell out of band.
Yesterday: Marketo 25 fills, normal. GA4 capture: 34% against the 55–70% band.
Marketo is steady, so this reads as a measurement-side gap, not a demand move. Digging into when it started. 🧵
3It correlates what it can see, then asks for the one thing it can’t.
This isn’t a smooth slide. Capture held near 63%, stepped down to ~35% between Tuesday and Wednesday, and has been flat since. Something shipped, so I checked.
A GTM container version published Wednesday: the nav release. I diffed it against Tuesday’s version. Nothing in it touches the demo tags.
The shape points somewhere else. All three client-side legs fell together, in proportion. A single broken firing path pulls one leg down and leaves the rest whole. These moved in lockstep, while Marketo held on the server side. That’s the signature of a consent gate, not a broken tag.
Your consent manager is the one system I can’t read. Did a consent setting change Wednesday too?
4One question, one answer. Steward keeps it.
Yes: auto-blocking switched on sitewide Wednesday, same window as the nav release.
That’s it, then. The auto-blocker is supposed to hold tags until a visitor consents.
Best-evidenced cause: an over-block. It’s holding them for visitors who did consent, too.
Your “missing” demos aren’t missing people; they’re being dropped after the form is filled.
5Your team makes the call and defends it with evidence. Steward never publishes changes.
So demo volume didn’t actually drop?
Demand looks intact: Marketo fills never left their normal range. The drop is measurement: the auto-blocker is over-blocking, holding tags for visitors who already consented.
Fix that setting and GA4 capture should come back into your 55–70% band. The consent manager itself is doing its job; keep it.
OK. We fix the over-block and keep the stricter consent setup. Shipping it this week.
6Every fix creates a new thing to track. The watching doesn’t stop when the ticket closes.
Friday read: thank-you-page leg down, datalayer leg whole. This one is not consent.
Diverging legs point at a specific firing path, and it lines up with Thursday’s site release. Flagging for the web team.
Zero GA4 demos today against 3 Marketo fills. At that volume a zero is within normal Sunday noise, not a new anomaly. No action.
Your over-block fix landed: capture back inside the 55–70% band.
Marketo 26 fills, GA4 capture 62%: a normal day again. Back to the daily read; nothing needs you today.
Watch. Investigate. Brief your team. You make the call.
Steward runs in your Slack, reads across your stack, and does the digging your team is doing by hand, so when a number moves, you know if it's real before anyone asks you to explain it.
Skip the questions and book the working session. 30 minutes, straight to a calendar. It costs nothing.
Already deployed and delivering value.
Steward runs live today, internally and with clients, watching real stacks in the team's own Slack.
Teams don't just read its reports; they assign it work in their channel.
Its first daily roll-up caught two systems disagreeing: the same check the team had been running by hand every morning.
The fix didn't settle the stack. Every time, it called the difference between a real break and normal noise, without crying wolf.
Who runs it
Built and run by the team at FunnelEnvy, who have spent a decade doing this work by hand for enterprise revenue teams. Steward does the watching now. The people who designed it still read every finding.
The same methodology has run inside FunnelEnvy programs for VMware, Box, Gong, ServiceNow, and Zoom.
How it works
A teammate in your Slack, not another tool to learn.
It says which system disagrees.
It watches volume and conversion by channel, period-over-period and year-over-year. When a number falls out of band, it names which system moved and which side to suspect, before the drop reaches the number you're goaled on.
It keeps the context only your team has.
Tag edits, campaign changes, config pushes, consent updates. Steward reads the change logs your team already keeps, asks about the ones it can't explain, and remembers the answer.
It follows the affected leads to opportunity.
When something looks off, it cohorts the affected leads and follows them through to opportunity, so you can say what the move actually touched, with the evidence attached.
Steward never publishes changes. When a fix is needed, we build it in a workspace, your team reviews and ships it.
- It shows its work. Every conclusion names the systems it compared and the change it lines up with, so your team can check it instead of taking it on faith.
Objections
The objections we hear most.
"We just hired a marketing ops manager."
Steward extends your ops team's reach: it does the daily manual watching and reconciliation so they can run initiatives instead of spreadsheets.
"How is this different from our monitoring?"
Your tools detect. Steward diagnoses the cause across GA4, your MAP, your CRM, and your tag manager, then drafts what to do about it. The alert is table stakes; the why is the product.
"What if the AI breaks something?"
It can't publish. It investigates, explains, and proposes. Your team makes every change. It removes the human from the busywork, not from the decision.
Want that answered on your own stack?
Three questions, no email, and your read comes back immediately. If it points at something real, the next step is a working session. That's where we scope the diagnostic.
The worst version of this is the break that runs silent for a month.
Get your read
Three questions. No email required.
Answer three questions about how your team watches its stack.
- Your read, now. What we see in your answers, in your terms.
- A working session, if you want one. 30 minutes with us. You bring one to three questions ("is our MQL drop real?", "why don't GA4 and Salesforce agree?") and we work out what answering them takes. The session costs nothing.
- The diagnostic, if it's warranted. We investigate your actual systems, scoped on that call. Read-only access, or exports and a screen-share for a first pass. Findings with the evidence attached, about a week from access.