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 intelligence from customer events
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.
In every event, customers tell you exactly where they stand.
Customers show what is working at events.
Customers show what is falling short at events.
Customers show who is engaged at events.
Customers show who has checked out at events.
People attending events reflect 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 asks questions about 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 visible to anyone standing in the room. Low attendance from the account is a visible signal of dissatisfaction. Disengaged body language is a visible signal of dissatisfaction. Pointed questions about basics are a visible signal of dissatisfaction. A conspicuous absence of executive participation is a visible signal of dissatisfaction. All of it tells you the customer hasn't arrived at the business outcome they expected. Signals are pulsing intensely during the event.
Events are the most honest feedback mechanism your customers will ever give you. Customers are not choosing their responses for a QBR slide. After every event, assess how the account showed up. Assess who attended at the event. Assess how the account engaged at the event. Assess what the account asked at the event. Assess what the account's demeanor communicated at the event. Track those observations alongside your quantitative health metrics. Behavioral signals at events will often tell you the truth three months before the data does. This process is the discipline behind turning event data into revenue intelligence. Capture the behavior first. Connect the behavior to the outcome next.
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 are system-derived inputs.
Feature usage is system-derived input.
Support tickets filed are system-derived inputs.
Those numbers tell you something.
Those numbers do not tell you how the customer feels about your platform.
That distinction matters at renewal.
A customer who has truly adopted brings more people, from more parts of the organization, into deeper sessions.
You see people from operations at events. You see people from the business side at events. You see people from leadership at events. The platform has become relevant across functions. The platform is not confined to a single team. Those attendees participate in advanced sessions. Those attendees share use cases with peers during roundtables. A customer who hasn't adopted sends one person. Usually, the administrator attends the event on behalf of the customer. That administrator sits in the back of the beginner track. That administrator has nothing to share in peer conversations.
After every event, compare what the signals tell you against what your adoption metrics say. When adoption metrics suggest healthy adoption but event behavior tells a different story, trust the event. A customer whose team shows up in force and talks openly about results has adopted in a way that survives a champion departure or a budget review. A customer whose single attendee leaves at lunch has adoption more fragile than the numbers suggest.
Signal 3: Why are single-threaded accounts your highest risk?
Single-threaded accounts are your highest risk because 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. Attendance pattern is the relationship map. A healthy, multi-threaded account sends people from multiple functions. Marketing operations is one function present in multi-threaded accounts. Sales leadership is one function present in multi-threaded accounts. Revops is one function present in multi-threaded accounts. An executive sponsor who wants to see what's new may also attend. A single-threaded account sends one person. Usually, the administrator attends every session. The reason is that no one else from their organization will attend every session. When you look across a user conference and see one badge per account after account, you are looking at a portfolio of single-threaded relationships.
The signal is not subtle. Events also offer the fastest path to fixing it. 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, that registrant is an immediate signal. That signal indicates the relationship is narrower than it should be. At the event, find the people from those accounts engaging with content relevant to their role. At the event, make the introduction in that context. The same logic that reveals buying committees in new deals exposes the relationship gaps in your installed base.
Signal 4: What proof should you capture in the moment?
The proof you should capture is the candid, unprompted evidence of value.
The 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 customers are in the event environment. Customers are surrounded by peers during the event environment. Customers reflect in real time during the event environment. Candor fades once customers return to their day-to-day. A 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 before the event. During the event, poll and survey reactions. During the event, 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 hiding in plain sight at every event.
A customer who sent one person last year and four this year is telling you something.
That pattern spans three departments.
A customer whose attendees have migrated from introductory sessions to advanced workshops is telling you something.
Those customers ask about capabilities they haven't yet purchased.
Their ambitions are outgrowing their contract.
Behavioral signals are often more reliable than explicit ones. A customer will rarely call their CSM and say "we need to expand our contract." Instead, the customer may send a new executive. The new executive spends an hour at your booth asking about capabilities outside their current scope. The customer may bring a colleague from a different business unit. The colleague has heard about the results. The customer may mention during a roundtable that the customer is planning to broaden their use of the product next year. The customer may wonder how the product scales.
Establish a baseline for how each account typically engages. Baseline includes how many people attend. Baseline includes which functions those attendees represent. Baseline includes what seniority those attendees have. Baseline includes session depth. When that pattern shifts, treat it as an expansion signal. Act on the expansion signal. Ground the framing in the signals captured. Ground the framing in signals rather than in what you're trying to sell. Use the example framing: "Your team's engagement at the last conference was different from a year ago, with more people asking more sophisticated questions. We'd like to talk about what that means for next year." Acting on these patterns across your full portfolio is orchestrating event signals at scale.
Frequently Asked Questions
What event signals should customer success teams watch for?
Five signals: how a customer behaves at events relative to time-to-value, whether their event presence shows real adoption, whether the account is single-threaded, the value proof points that surface in the moment, and the 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, brings more roles, and asks forward-looking questions.
A customer who has not sends few people, disengages in sessions, and questions basic functionality.
The behavior surfaces a time-to-value problem months before a renewal conversation forces it 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, then watch for change.
When attendance grows, new departments appear.
Questions move from operational to strategic.
The customer's ambitions are outgrowing their contract.
That shift is an expansion signal, even when no one has called 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 them.
Technology that turns unstructured event signals into structured data is increasingly giving 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. Customers who renew and expand are the ones whose CS team captured the evidence. Customers who renew and expand are the ones whose CS team built the relationships. Customers who renew and expand are the ones whose CS team told the story before anyone thought to question the investment.
Peter Micciche is CEO of Certain, 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.