Too few live calls
Keep collecting evidence. Do not kill a young test for being young.
FIELD REPORT 04 · DECISION INFRASTRUCTURE · B2B HIGH TICKET SALES CLIENT
For a B2B high ticket sales client, I joined paid media to live calls, revenue and cash, corrected the numbers everyone trusted, and built the decision system that tells every ad to Watch, Cut, Scale or Kill.
Mature and under target. Raise the budget in controlled steps, with the sales team's capacity in view.
Illustrative ads, target and thresholds. The rule shape is the real one: rank on trailing cost per live call, act only once there is enough live call volume.
The client sells a high ticket offer through booked sales calls and puts more than $500K a month into paid media to fill the calendar. Since March 2026 I have run lead generation on the account and built the data layer under it.
The job was to connect the complete path from spend to cash, then turn that evidence into a repeatable operating decision. Meta knew the spend. HubSpot held the contacts, the meetings, the deals and the payments. Each system answered a different part of the decision.
Bookings were too early and show blind. Closes were the true value signal, but sparse and often five to ten days late. The reporting needed one definition of performance that survived every source.
One number had to survive five systems and still arrive in time to move a budget: cost per live call.
Same four illustrative ads as the ledger above. Pick a metric, move the read day, and see which ad each one would put first.
On day 14, cost per live call puts AD A first and AD C last. That is the order the business would want.
Live calls reflect whether booked leads actually showed up and qualified, early enough to manage budget before close data matures.
Rank on trailing cost per live call. Act only when enough live call volume makes the signal meaningful.
Daily, weekly and monthly views read from the same definitions. No metric changed meaning between reports.
HubSpot's calendar behavior left a second, cancellation prefixed record for the same meeting. Both counted. Toggle the audit to see what one fix did to the show rate.
Show rate is live calls over booked meetings. Every twin added one booked meeting that could never show, so booked volume read high and the show rate read low. The pair above is a schematic; the 622 and both show rates are the audit's real figures.
The correction changed no calls. It made the show rate true.
The evergreen report excluded webinar sales by label. The rule matched one exact label, so every dated webinar variant flowed into evergreen: closes, revenue and cash.
Closes, revenue and cash from dated webinar variants, credited to evergreen. Evergreen looked better than it was.
exclude: "webinar"ONE LABELexclude: "webinar*"THE WHOLE FAMILYValidation: the cash removed from evergreen matched the full dated webinar payment total exactly, and every protected metric came out of the repair unchanged.
Maturity came before action. A young test was watched. A stale close could not protect recent inefficiency. A low show rate did not condemn a test without enough live call volume.
Map drawn with illustrative thresholds: four live calls to act, an $800 target, Kill past 1.5x. Same four ads as the ledger at the top.
Keep collecting evidence. Do not kill a young test for being young.
Reduce exposure while preserving enough volume to confirm the direction.
Increase budget in controlled steps and keep the sales capacity ceiling visible.
Stop funding a narrative the downstream outcomes no longer support.
Two weeks on the account. A health check every morning, a creative review every Friday, and a decision window that always looks back 14 days.
Check source freshness, filters and pipeline failures before anyone reads the report.
Read hooks and formats against qualified applications, live calls and revenue.
Rank meaningful volume by cost per live call, then Watch, Cut, Scale or Kill.
The motion piece compresses the architecture, the integrity audits, the decision signal and the weekly rhythm into a format built for a LinkedIn feed. The PDF has the same story in seven pages.
Both audits found errors that flattered someone: extra bookings in the calendar, extra revenue in evergreen. The fixes made the numbers true before any budget moved on them.
Figures are from my own audits of the client's reporting, March 2026 to now. Ad names, targets and thresholds in the diagrams are illustrative. Raw volumes, revenue and the client's name stay with the client.
Pick the decision metric on timing and quality together. The earliest number is usually show blind, and the truest one lands after the budget call.
Audit the joins before trusting the trend. Both errors on this account sat in the plumbing: a calendar habit and a naming rule.
Write the rule for young data first. Watch is a decision too, and it saves more tests than any other.
Happy to walk through any of these live.