Most conversations about how to make a customer conference lead to real change start with the agenda: which executive opens, which customer speaks, which session runs where. Seen through Execution Intelligence™ (the gap between what organisations decide and what they actually do), that’s the wrong starting point. Whether a customer conference leads to real change, rather than just a good day, is decided almost entirely before the doors open, weeks before a single slide is finished. I work with CEOs, Chief Customer Officers, CMOs, Chief Product Officers and the heads of events who build these programs, across customer conferences, user conferences and partner summits, and the pattern holds: the ones whose conferences change something afterward did the work before the event, not after it.

What that work controls has a name: Stage Debt. Stage Debt is what an organisation owes its customers and partners the moment a conference ends: every commitment, direction and acknowledgement spoken from its stage, waiting to be seen in what actually changes afterward. I’ve written about the shape of that problem in the pillar piece on Stage Debt. This article is about the document that decides how much of it you create, built before the doors open.

Why Most Customer Conferences Are Planned from the Wrong End

Conference planning for outcomes usually gets treated as a wrap-up task: run the event, then figure out what to do about what got said. By the time anyone is thinking about conference follow-through, the keynotes are written and the claims are made. Designing a conference around what happens afterward reverses that order: start with what a customer will actually see change in their dealings with you, and work backwards to what the stage is allowed to say. Planned from the front end, a conference asks, “what do we want to tell them?” Planned from the back end, it asks, “what will they see us do, and by when?” The first produces a good day. The second produces a conference that changes something.

What Should Be Decided Before the Doors Open?

Three things need to be settled before the event, none of them in the wrap-up meeting: exactly what the main-stage sessions intend to claim, written as plain sentences rather than implied by the agenda; who inside the host will answer for each claim once the audience is watching for it; and what a customer will actually be able to see, unprompted, within 48 hours of walking out the door. That last point carries the most weight. The First 48 Hours is a simple test: a decision is only believed when something visibly stops, starts or changes in the first 48 hours after it’s made. For a customer conference, those 48 hours cannot be improvised after the event: a claim earns its place on a slide only if its 48-hour outside-in evidence is named, owned and ready before the doors open. Organisations that start planning it during the wrap-up have already missed it.

The Stage Claims Register: Every Claim, One Owner, Visible Evidence

The tool I use with host teams to do this is the Stage Claims Register: a working document the host’s executives build before the conference, listing every stage claim the main-stage sessions will make, its type, one named executive owner, the outside-in evidence the audience will see within 48 hours, and the first ordinary interaction where they will meet it. Five columns, deliberately plain, with no column for how important a claim feels internally. Claims that cannot complete all five honestly are cut or reworded before they ever reach a slide.

Building it is a private exercise: the host’s own executives sit with the draft keynote outlines, weeks out, and work through each claim together. It’s candid, sometimes uncomfortable, and it stays inside that room; none of it belongs on the conference stage itself, where the audience is there to watch what the host does afterward, not to watch it decide what’s realistic.

Commitment, Direction or Acknowledgement? Classifying What the Stage Will Say

Every claim on the Register gets sorted into one of three kinds, always in this order. Commitments are the “we will” statements: specific things the host says it will do, change or deliver, and they need outside-in evidence within 48 hours, full stop; without it, the claim isn’t a commitment yet, however it reads in the draft. Direction is the “we are heading” statements, where the host says it’s going without a specific delivery attached; it needs less evidence, since an honest statement of direction isn’t a promise. Acknowledgements are the “we heard you” statements, and they create the most Stage Debt per word, because the audience hears an unspoken commitment inside every one: “we heard you” with nothing visible behind it is a debt nobody has planned to pay.

Which Claims Should You Cut?

A claim gets cut or reworded in three situations: a commitment with no named owner willing to answer for it doesn’t go on stage as a commitment; a claim whose outside-in evidence nobody can describe in plain terms within 48 hours gets reworded into honest direction, or dropped; and an acknowledgement with no action behind it gets cut outright, because an apology with nothing visible afterward is worse than saying nothing.

Occasionally a claim reveals a problem bigger than the conference itself: if it crosses several functions and nobody inside actually owns the outcome at all, that is a separate diagnosis I’ve written about as Ownership Fog, and it needs fixing before you decide what the stage can promise.

Peter Gollwitzer’s 1999 paper on implementation intentions found that individuals who specified in advance when, where and how they’d act on a goal followed through far more reliably than those who only held the intention. That’s individual-level research, applied here by analogy: a Stage Claims Register is an organisation’s if-then plan for its own public promises. See Gollwitzer, “Implementation Intentions: Strong Effects of Simple Plans,” American Psychologist, 1999.

Who Needs to Be in the Room When You Decide?

Fewer people than most host teams expect: the chief executive, since commitments and direction usually originate there; the Chief Customer Officer or head of customer marketing, closest to what customers notice; whichever function owns a given claim, brought in only for that claim; and the head of events, not to approve content, but to notice if a cut claim slips back into a keynote draft. Nobody from outside the host belongs in that room. This is a host-only working session; partners and customers are the audience for what it produces, not participants in producing it.

The Three Claims That Were Cut

Picture a host team six weeks before its customer conference, writing every claim from every draft keynote onto a single page. There are more than they expected. For each, they ask the Register’s questions: who owns it, what will the customer see, and when. Most pass. Three do not.

A commitment to “a new way of working together” sounds significant, but nobody can describe it as something a customer would see change; it’s reworded as honest direction and stays in the keynote. An acknowledgement, “we know support has been slow,” offered because it will land well, has no change planned behind it; it’s cut, replaced by one small, real change visible to every customer the day after the event. A product commitment dated for a quarter the product team privately doubts is moved off the main stage entirely, into a more careful “not yet” (how to phrase that is a question for the keynote itself).

The conference ends up making fewer claims than the year before, and every one that remains has a name attached to it: the executives who say “we will” on stage know exactly what they’re accountable for the moment they walk off it. This is a composite drawn from the pattern I see across host teams, not a specific event or organisation.

Where This Leads

Building the Register is the first half of the work. Making sure each surviving claim actually reaches customers as something they can see is a discipline of its own, covered separately in a piece on what happens once the doors close. And how each executive phrases their claims on the day, the roadmap slide above all, is covered in a piece on the main-stage keynote itself.

I usually get involved at exactly this stage, in the private working session where the host’s executives build the Register. Sitting outside the organisation’s reporting lines tends to make that conversation more candid; it’s easier to say “we can’t actually evidence that” to someone who won’t have to defend the claim to their own boss next quarter. You can see how I typically approach this work on my page as a keynote speaker for customer conferences. If you’ve got a customer conference or partner summit ahead of you and want help building the Register before your keynote drafts are finished, let’s set up a conversation about your event.