Coach Kyle case study: 412 registered, 4 closes. What did repairing 20 of 57 messages do?

What was Coach Kyle sending before the launch?

Emails and texts were going out to Coach Kyle's subscribers every day with no reliable way to see which of them produced booked calls and sales.

Kyle Froonjian runs Coach Kyle Dating, and you know his position well if you send something every day, don't you, because you decide what goes out tomorrow from what went out today, so the count has to be right, and when it is not, every choice about the next send is a guess wearing the clothes of a decision.

Of the emails and texts you sent last week, how many links reported back to the place where you count sales?

Which seam was leaking?

The seam was Seam 01, Spend to Attention: sending was counted in one place and booking and buying in others, and nobody joined them.

The question that matters, which message made that sale, had no answer because sending and counting lived in different tools, and closing that gap is the work of marketing attribution reconciliation, so which of your channels do you already suspect has been carrying the others?

What did Jon Weberg repair first?

Jon Weberg repaired the 20 of 57 messages with broken tracking first, so every link in every message reported back to one place.

He reviewed 23 live automations holding 57 messages, 29 emails and 28 texts, before a single launch asset was built, and the sequence for doing that on your own account is in how to audit tracking before a launch.

How many messages were broken, and what was changed?

20 of the 57 messages had broken tracking, and the repair changed no copy, no timing and no automation logic.

Every one of those 20 looked fine from the outside until it was counted, which is the useful part for you, since a repair your audience never sees leaves the launch calendar untouched, and if 20 of 57 turned up in a business that sends every day, how many would a count of yours turn up?

What happened in the launch week?

The launch was built in one week and run live on 30 August 2026, on top of tracking that reported every message.

What did the 30 August 2026 launch produce, step by step?

The 30 August 2026 live launch produced 412 registered, 142 live, 37 applications, 30 calls booked and 4 closes at $6,800.

What did the repaired tracking reveal?

The repaired tracking showed which link each application came from, a finding that exists only because the tracking was repaired first.

35 of the 37 applications carried the tracking from the link shared in the live chat, so the live room produced almost every application, and what would your next launch decide differently if you knew which link each application came from?

How does 142 live from 412 registered compare with webinar benchmarks?

EasyWebinar's 6 May 2026 roundup, citing Univid's 2026 report, puts live attendance at 47 to 49% of registrants and high ticket creator webinars at 30 to 40%; 142 of 412 is 34.5%, inside the high ticket band.

34.5% sits below the all webinar figure and inside the band for high ticket offers like this one, and the reason you can see either fact at all is that the tracking was counted first, so with 412 registered and 4 closes at $6,800, which step between registered and closed would you fix first on your own funnel?

Where does this sit in The Thirteen Seams?

This engagement closed Seam 01, Spend to Attention, the handoff between the people who send and the people who count what it made.

It is the first of The Thirteen Seams, and every other line on a Seam Map is priced with the numbers this one produces, which is why the AI Acquisition show rate case and John Crestani's fifteen weeks both depend on a count somebody trusted.

Which of your messages reports what it made?

Your launches are the same seam: count your live emails and texts, then count the ones whose links report back to one place, and the difference is your 20 of 57.

Who in your company joins the sending numbers to the booking and buying numbers every week? Forty five minutes on your own account gives you that count, so your next launch reports every message's result before it goes out, and the decisions after it are made on numbers you trust, aren't they?