Launch Readiness Criteria: What Observable Evidence Looks Like

Jen was two slides into the pre-launch review when her VP stopped her.

"Hold on. You said sales is ready. How do you know that?"

With confidence, Jen said the training had happened. Three sessions, full attendance, sign-off from every rep's manager. The VP asked again, differently this time: "If I called a rep right now and asked them to handle a pricing objection, what would I actually hear?"

Nobody in the room could answer that. The training had happened. Nobody could say, with evidence, what it had actually produced..

That's the gap this post is about. If you're new to the concept, start with our guide to launch readiness - this post goes a layer deeper, into what readiness actually looks like when you can point to it instead of just claiming it.

Readiness Theater™

Most teams don't fake readiness on purpose. They perform it, which is a different and more dangerous thing. Readiness Theater is what happens when a team checks boxes, runs reviews, and declares a launch ready based on activity instead of proof. The meeting happened. The deck got reviewed. Someone said the word "ready," and everyone in the room, relieved to move on, agreed.

The problem with Readiness Theater is that it's indistinguishable from real readiness right up until the moment it isn't. The go/no-go meeting looks identical whether the evidence underneath it is real or performed. The gap between what was claimed and what was actually true doesn't show up in that meeting. It shows up three weeks later, in the pipeline numbers, when the thing everyone agreed was ready turns out not to have been. For more on how this specific failure mode plays out in the room itself, see our piece on the readiness reality check.

The Three O's: why readiness fails as a system, not a people problem

When readiness turns out to have been theater, the instinct is to blame the people in the room. That's almost always the wrong diagnosis. The real causes are structural, and they show up the same way across nearly every organization that runs into this.

Ownership is the first. When a launch has no single owner accountable end to end, it has many partial owners instead, each one responsible for their own piece and nobody responsible for the whole. Everyone can honestly report that their part is done. Nobody can honestly report that the launch is ready, because nobody was actually positioned to know that.

Organization is the second. Readiness information tends to live in five different tools with five different statuses, and the launch team becomes the integration layer, manually reconciling what the pricing doc says against what the sales deck says against what the product team shipped. That reconciliation work is exhausting, it's easy to get wrong, and it means the "current" status anyone is looking at is really a snapshot from whenever someone last did that reconciliation by hand.

Outcomes is the third. Most launch tracking measures activity — tasks completed, assets delivered, sessions attended — because activity is easy to count. What it rarely measures is the thing the launch was for: the revenue outcome, defined before the launch begins. Without that target, there's nothing to test readiness against. A completed task tells you work happened. It doesn't tell you whether that work moves the number the launch is supposed to move.

These three are the diagnosis. What follows is how to test for it.

The evidence question

There's one question that cuts through all of this, and it's worth asking about every piece of a launch before declaring it ready: what would you observe if this were actually working?

Not "is this done." Not "did the task get completed." What would you actually observe, concretely, if the thing you're claiming were true? That question is harder to answer than a status update, and that difficulty is the point. A status update can be performed. Observable evidence can't.

Launch readiness criteria, hub by hub

Here's what that evidence question looks like applied to each part of a launch — six places where the truth about readiness either holds up under scrutiny or doesn't.

Product. The evidence of readiness here isn't that the feature shipped. It's that the product story is locked, written down, and every team member who gets asked to describe what the product does gives the same answer without checking a document first. Read more about how the Product Hub keeps that story current in the first place.

Audience. Readiness here means the ICP and buyer personas in active use are current, approved, and identical across every team touching the launch — not that a persona document exists somewhere, but that the version in a rep's hands and the version in a marketer's hands are the same version. This is exactly the governance problem the Audience Hub is built to close.

Launch. The evidence here starts before the first milestone: success metrics defined up front, so the team knows what it's trying to prove, not just what it's trying to ship. From there, readiness means every milestone has a named owner and evidence attached — something a skeptical reviewer could check without taking anyone's word for it. If a milestone's only proof is that someone changed its status, it isn't ready.

Pricing. Readiness means every person who might end up in a pricing conversation — sales, success, support — would give the same answer if asked today. Nobody is freelancing a discount because the rationale behind the number was never made clear to them.

Competitors. Readiness here means a rep can name the competitor most likely to show up in a deal and give the counter-position without opening a battlecard — and the intel behind that answer has been reviewed since the competitor last changed its pricing or messaging.

Sales Assets. This is where the other five either hold together or quietly don't. Readiness means what's in a rep's hands today — the deck, the pricing, the positioning — matches what's currently true in Product, Audience, Pricing, and Competitors, not what was true when those assets were built. This is the exact mechanic the Sales Assets Hub governs.

For the full picture of how these six pieces connect as one system, see our overview of the six Hubs.

Six questions. Not six tasks to check off — six places to ask what you'd actually observe if the answer were true, and to notice, honestly, when you can't say.

If launch readiness is something your team is actively working on, Launchible is built to make it measurable — a GTM Operating System that replaces the checklist with observable evidence at every stage.

Dave Daniels is the founder of Launchible — the GTM Operating System built to close the Launch Gap between what Product ships and what Sales can actually sell. He has spent 20+ years watching great products underperform at launch because the system around the launch wasn't built to succeed.