How to Improve Your Next Launch (3 Questions to Ask First)
There's something about the first launch planning call.
You're not in it yet. No open cart panic. No "why aren't people clicking." Just two people looking at what's coming and thinking about what's possible.
I genuinely love that moment.
Recently I got on one of those calls with a client I've worked with before. She launches this offer once a year. Knows her numbers. Does the work. After her last launch she did something most people skip entirely... she sat down and wrote it all up. Detailed Google doc. Everything she'd noticed, everything she'd learned.
I saw it. It was really good.
So we got on our first planning call for the new launch and I was expecting us to open that doc.
We didn't.
What came up instead was new ads. New emails. A fresh look at the sales page. The doc just kind of... didn't make it into the room.
And honestly? I get it. That first call has energy. It feels forward-facing. Going back to the last launch feels like going the wrong direction (even when it isn't).
The debrief isn't enough
Here's what I've seen happen over and over again (and what I had to gently pump the brakes on in that call): the debrief captures what happened. The diagnosis (the part that actually tells you what it means for next time) quietly gets skipped.
And then the next launch kicks off from scratch anyway. Just with better creative.
Sound familiar?
Most repeat launchers do the debrief. They write it up, note what worked, flag what didn't. But the debrief is a record, not a roadmap. It tells you what happened. It doesn't tell you what to build on.
That's a different document. And most people never make it.
Here's what to do instead
Before you touch a single thing for your next launch, ask yourself these three questions. They won't take long. But they will change what you do next.
1. Where did momentum start to slow down?
Not "why didn't people buy" — that's too big and too vague. Get specific. Look at your open rates, your click rates, your sales page traffic. Find the moment where the numbers shifted. That's your starting point.
2. What were people doing (or stopping doing) at that moment?
This is where most debriefs stop. They find the drop and call it the problem. But the drop is a symptom, not a cause. So look at the behavior. Were people opening emails but not clicking? Clicking but not staying on the sales page? Getting to checkout and not finishing? What people did (or stopped doing) at that moment tells you something specific.
3. What changed right before that happened?
This is the question that actually leads somewhere.
Here's an example of what I mean.
A client's launch was humming along. Strong pre-launch engagement, good open rates, people showing up. Then cart opened and something shifted. Opens stayed decent but the momentum just... stopped.
When we looked at the sequence, the answer was in question 3. What changed right before the drop? Cart opened and people saw the bonuses for the first time.
That was the thread. Not the sales page copy. Not the price. Not the email sequence. The bonuses landed flat and the momentum stopped right there.
Most people looking at that launch from the outside would have rewritten the sales page or adjusted the price for next time. Both of those would have been the wrong fix.
The diagnosis pointed somewhere specific. And specific is where change actually happens.
The difference between a debrief and a diagnosis
A debrief tells you what happened. A diagnosis tells you where to look (and consequently, what to leave alone).
Your last launch is full of signals like this. Most of them are still sitting in your data, waiting to be read.
Before your next planning call, block time for a diagnosis session. Go back to the last launch (not to rehash it, but to actually read it) and let it guide what you finalize for the next one.
That's the step that helps you build on your last launch instead of just running it again with a new coat of paint.
Not sure where your launch actually leaked?
Start with the Launch Leak Scan, it’s a short diagnostic that helps you identify which specific leak caused your last launch to underperform and tells you exactly where to look first.

