Leadership Peter Micciche June 30, 2026 By Peter Micciche, CEO, Certain
TL;DR
Customer success teams should watch five event signals: how a customer behaves at events relative to time-to-value, whether their presence shows real adoption, whether the account is single-threaded, the value proof points that surface and vanish in the moment, and the shifts in attendance and questions that reveal expansion intent.
Events are the most honest feedback your customers will ever give, because they aren't choosing their responses for a QBR slide.
Customer Success teams are sitting on the richest source of customer intelligence available to them. Customer Success teams often walk away with nothing more than attendance numbers. Every event your customers attend is a live behavioral environment. Customers tell you exactly where they stand at each event. Customers reveal what is working and what is falling short at events. Customers reveal who is engaged and who has checked out at events. I've had customers rip my head off and others extol the virtues of my company. Every one of them reflected the customer's real emotions. Most signals are visible to anyone in the room who knows what to look for.
Signal 1: What does time-to-value look like at an event?
Time-to-value looks like behavior, not a milestone on a project plan. A customer who has crossed the value threshold attends sessions with purpose. A customer who has crossed the value threshold asks forward-looking questions about what comes next. A customer who has crossed the value threshold brings more people across more roles. A customer who hasn't shows up sparsely. A customer who hasn't disengages in sessions. A customer who hasn't questions basic functionality that should have been resolved months ago. The energy, or its absence, is unmistakable.
Your customers are telling you whether they've reached value every time they show up. The question is whether your CS team is paying attention. An unhappy customer exhibits dissatisfaction in ways that are visible to anyone standing in the room. Low attendance from the account is visible dissatisfaction. Disengaged body language is visible dissatisfaction. Pointed questions about basics are visible dissatisfaction. A conspicuous absence of executive participation is visible dissatisfaction. All signals tell you the customer hasn't arrived at the business outcome they expected. Signals are pulsing intensely during and around event attendance.
Events are the most honest feedback mechanism your customers will ever give you. Events are honest because customers aren't choosing their responses for a QBR slide. After every event, assess how the account showed up. Assess who attended, how customers engaged, what customers asked, and what their demeanor communicated. Track those observations alongside your quantitative health metrics. Behavioral signals at events will often tell the truth three months before the data does. This discipline turns event data into revenue intelligence. Capture the behavior first. Connect the behavior to the outcome.
Signal 2: How do events reveal real adoption?
Events reveal real adoption in ways your dashboards cannot. Adoption metrics are mostly self-reported or system-derived. Logins, feature usage, and support tickets filed are examples of adoption metrics. Those numbers tell you something about adoption. Those numbers do not tell you how the customer feels about your platform. The distinction between numbers and feelings matters at renewal. A customer who has truly adopted brings more people. A customer who has truly adopted brings people from more parts of the organization. A customer who has truly adopted brings people into deeper sessions.
You see people from operations, the business side, and leadership at events. You see these groups because the platform has become relevant across functions. The platform is relevant across functions instead of confined to a single team. Customers participate in advanced sessions when the platform is relevant. Customers share use cases with peers during roundtables when the platform is relevant. A customer who hasn't adopted sends one person. That person is usually the administrator. That person sits in the back of the beginner track. That person has nothing to share in peer conversations.
After every event, compare what the signals tell you against adoption metrics. Trust the event when event behavior differs from adoption metrics. A customer whose team shows up in force and talks openly about results has adopted. That adoption survives a champion departure or a budget review. A customer whose single attendee leaves at lunch has adoption that is more fragile than the numbers suggest.
Signal 3: Why are single-threaded accounts your highest risk?
Single-threaded accounts are your highest risk. The renewal depends entirely on one person's continued employment, enthusiasm, and influence. When a single administrator is the only person inside the customer organization who understands what your platform does, you have no coverage if they leave. Enterprise deals are won by committees. Enterprise deals are lost by committees. The same dynamic governs renewals as much as it governs new business.
Events tell you exactly how deep or how shallow your relationships run. The attendance pattern is the relationship map. A healthy, multi-threaded account sends people from multiple functions. Multiple functions include marketing operations. Multiple functions include sales leadership. Multiple functions include revops. Multiple functions may include an executive sponsor who wants to see what's new. A single-threaded account sends one person. That person is usually the administrator. That person attends every session because no one else from their organization will. When you look across a user conference and see one badge per account after account, you see a portfolio of single-threaded relationships.
The signal isn't subtle. Events offer the fastest path to fixing single-threaded accounts. Before every event, review your attendee list against your relationship map for each account. When you see a single registrant from a customer you know uses the platform across multiple functions, the relationship is narrower than it should be. At the event, find people from those accounts engaging with content relevant to their role. Make the introduction in that context. The same logic that reveals buying committees in new deals exposes relationship gaps in your installed base.
Signal 4: What proof should you capture in the moment?
The proof you should capture is candid, unprompted evidence of value. That evidence surfaces and disappears within a few days.
A department head says the product changed how her team runs quarterly planning. A director mentions a workflow that saved three days of manual work. An executive sponsor tells a peer the investment paid for itself in the first quarter. Each moment would be compelling at renewal.
QBRs that lack substantiation of value creation are missed opportunities. Events are where the best proof points appear and vanish. The problem is timing. Customers are most candid about the value they've received when they are in the event environment. Customers are candid when they are surrounded by peers. Customers are candid when they reflect in real time. Candor fades once customers return to their day-to-day. The department head who volunteered that insight on Tuesday is buried in her own priorities by Thursday. The evidence evaporates because no one was equipped to capture it.
Treat every customer event as a live evidence-gathering opportunity. Before the event, identify which accounts are approaching renewal or expansion. Brief your team on what to look for. During the event, poll and survey reactions. Note anecdotes from those accounts. After the event, consolidate those observations into a brief account-level summary quickly. Over the course of the relationship, those summaries become the basis for the QBR. Those summaries shift the renewal conversation entirely.
Signal 5: Where are expansion signals hiding?
Expansion signals are hiding in how a customer's event presence changes over time. Expansion signals are in plain sight at every event. A customer who sent one person last year and four this year, from three departments, is telling you something. A customer whose attendees migrate from introductory sessions to advanced workshops tells you something. Those customers ask about capabilities they haven't yet purchased. Their ambitions are outgrowing their contract.
The behavioral signals are often more reliable than the explicit ones. A customer rarely calls their CSM and says "we need to expand our contract." A customer sends a new executive who spends an hour at the booth asking about capabilities outside their current scope. A customer brings a colleague from a different business unit who has heard about the results. A customer mentions during a roundtable that they're planning to broaden their use of the product next year. A customer wonders how the product scales.
Establish a baseline for how each account typically engages. Baseline engagement includes how many people attend. Baseline engagement includes which functions are represented. Baseline engagement includes seniority. Baseline engagement includes session depth. When that pattern shifts, treat the shift as an expansion signal. Act on the expansion signal. Ground framing in the signals captured rather than what you are trying to sell. "Your team's engagement at the last conference was different from a year ago, with more people asking more sophisticated questions." Acting on those patterns across your full portfolio is a matter of orchestrating event signals at scale.
Frequently Asked Questions
What event signals should customer success teams watch for?
Five signals.
Customer success teams should watch how a customer behaves at events relative to time-to-value.
Customer success teams should watch whether event presence shows real adoption.
Customer success teams should watch whether the account is single-threaded.
Customer success teams should watch value proof points that surface in the moment.
Customer success teams should watch shifts in attendance and questions that reveal expansion intent before anyone articulates it.
How does an event reveal a time-to-value problem?
A customer who has reached value attends with purpose.
A customer who has reached value brings more roles.
A customer who has reached value asks forward-looking questions.
A customer who has not reached value sends few people.
A customer who has not reached value disengages in sessions.
A customer who has not reached value questions basic functionality.
Basic functionality issues surface at events.
These issues surface months before a renewal conversation forces them into the open.
Why are single-threaded accounts the highest renewal risk?
When a single administrator is the only person who understands your platform, the renewal depends entirely on that one person's employment, enthusiasm, and influence.
Event attendance is the relationship map.
One badge per account session after session is a portfolio of fragile, single-threaded relationships.
How do customer success teams spot expansion signals at events?
Establish a baseline for how each account engages.
Watch for change.
When attendance grows, new departments appear.
When questions move from operational to strategic, expansion intent appears.
The customer's ambitions are outgrowing their contract.
That shift is an expansion signal.
That shift can appear even when no one calls their CSM to say so.
The Bottom Line: The Customers Who Renew Tell the Story First
The throughline across all five signals is the one that runs through every edition of this newsletter, The Signal. The signals are already there. The question is whether your systems and your CS team are designed to see the signals.
Technology that turns unstructured event signals into structured data increasingly gives CS teams an intelligence advantage that other channels cannot match. The behavioral layer and the metrics layer have run in parallel for too long. Customers who renew and expand are not always the happiest ones. Those customers are the ones whose CS team captured the evidence. Those customers built the relationships. Those customers told the story before anyone thought to question the investment.
Peter Micciche is CEO of Certain. Certain is the leading AI-powered Event Signal Platform for enterprise B2B companies. Connect with Peter on LinkedIn or visit certain.com to learn more about transforming events into revenue engines.