Worked webinar case

This anonymised pattern comes from a recurring B2B software webinar. The example records use real question types observed in the webinar programme, with identifying details removed. The scores illustrate the rubric; they are not claimed revenue outcomes.

Context

The webinar topic was broad enough to attract curiosity, but the most useful signals appeared in operational questions:

• Can planned personnel hours for a quote later become an operational schedule?
• Can fixed employees be planned against monthly target hours and utilisation?
• Can relevant working-time rules be represented or checked?
• Can annual or recurring plans be generated?

Counting registrations alone would have hidden the difference between topic interest and an active buying problem.

Record A: operational buyer with a workflow question

Evidence:

• Account matched the target operating model: 20 Fit points.
• Role was responsible for the workflow: 10 Fit points.
• Question confirmed the use case: 10 Fit points.
• Attended at least half of the session: 15 Engagement points.
• Asked a substantive workflow question: 10 Engagement points.
• The question described a concrete operational process: 10 Intent points.

Score: Fit 40, Engagement 25, Intent 10, Total 75.

Routing: priority human sales review. The handoff used the buyer's exact quote-to-schedule question and did not replace it with “interested in AI.” A named owner still had to check existing relationship and approve the message.

Record B: engaged learner from a poor-fit account

Evidence:

• Account did not meet the defined company profile: 0 Fit points.
• Role was adjacent to the buying group: 5 Fit points was not available under the strict rubric, so no points were awarded.
• Watched most of the session and answered a poll: 20 Engagement points.
• Asked an educational question without a current company problem: 0 Intent points.

Score: Fit 0, Engagement 20, Intent 0, Total 20.

Routing: record only or permitted topic nurture. High engagement did not turn a poor-fit attendee into a sales task.

Record C: no-show who later viewed pricing

Initial evidence:

• Account matched: 20 Fit points.
• Role matched: 10 Fit points.
• Registered but did not attend: 2 Engagement points.
• No stated problem: 0 Intent points.

Initial score: 32. The next action was a replay or summary, not a sales task.

Later, a verified visit to a decision-stage pricing page added 15 Intent points. The record moved to 47, still below review. If a concrete reply or meeting request arrived, it would be re-scored or handed directly to sales. The process did not inflate the score merely because the account looked valuable.

Failure pattern

The first instinct was to treat every registrant as a lead and use the same post-event booking message. That would have:

• sent sales pressure to educational and poor-fit contacts;
• ignored the exact operational questions from the strongest records;
• treated no-show and attendance as equal;
• created conflicting follow-up for existing customers or opportunities;
• counted tasks or registrations as pipeline.

The corrected process separated lifecycle state, Fit, Engagement, and Intent. Sales received fewer records, but each handoff included the source, exact question, evidence, score components, existing relationship, and recommended next step.

Post-event learning

The question cluster also changed the GTM backlog. The repeated operational questions became candidates for product-page clarification, sales-demo scenarios, and future webinar topics. The team could learn from all questions without pretending that every questioner had become a qualified opportunity.