"We Need to See Results From Phase One First" — The Expansion Objection

The stall that sounds like a plan

You ask for the expansion. The champion doesn't push back on price. He doesn't tell you the product is broken. He doesn't say no. He says:

"Look, we're happy. But we need to see results from phase one before we take this to the committee."

And because it sounds like the most reasonable sentence a buyer has ever said to you, you write it down, you thank him, and you set a follow-up for next quarter. That follow-up will produce the same sentence. So will the one after it.

I have watched this specific stall eat two full quarters on accounts that were never actually at risk. The product worked. The renewal was safe. The expansion just sat there, parked behind a phrase nobody had ever defined out loud. That's what makes it dangerous. A hard no gets escalated. A pricing objection gets a discount approval. "We need to see results first" gets a calendar invite and a slow death.

The reason it works on us is that it borrows the language of good practice. Of course you should prove value before you expand. Of course a buyer should want evidence. Every customer success playbook ever written says land, prove, expand. So when a customer says it back to you, your own methodology tells you to sit down.

Here's the thing though. In almost every case I've seen, the sentence is not a plan. It's a placeholder. And the entire job of customer expansion objection handling at this moment is to find out what's sitting behind the placeholder before you agree to anything.

Three things "results" can mean, and they need different work

When someone tells you they need to see results from phase one, they mean one of three things. You cannot respond until you know which one. The responses are not interchangeable and using the wrong one will cost you the relationship, not just the deal.

One: there is a real, agreed metric and a real date

This is the good version. Somebody signed off on phase one against a number. Ticket deflection, days to fill, documentation time per encounter, whatever the thing is. There is a review scheduled. There is an executive who will look at a slide.

If this is what's happening, your customer is not stalling you. They're telling you the truth about how their company buys. The mistake here is treating it as an objection and pushing. You don't push. You get inside the measurement.

You can usually tell within two questions. Ask what the number is and when it gets reviewed, and if they answer both instantly and specifically, it's real. "We committed to cutting average handle time and Priya presents to the ops council in the second week of the quarter" is real. That person has the slide in their head.

Two: it's political cover

This is the most common one and the hardest to see, because it uses identical words.

Here, "results" means: I don't currently have the political capital to ask for more money, and saying that out loud to a vendor is humiliating, so I'm going to attribute the delay to your product's performance instead of my standing in the building.

Maybe their budget got reallocated. Maybe the executive who sponsored phase one left. Maybe there's a reorg nobody has announced. Maybe your champion asked for something else last month and got told no, and he is not going back to that well.

The tell is vagueness in the wrong direction. They can talk fluently about how happy they are with the product but go soft the moment you ask who reviews the outcome and when. Fluent on satisfaction, foggy on process. That gap is where the politics live.

Three: nobody has actually logged in since March

The third version is the one that should scare you, and it's the one your own dashboards should have caught before the call.

Phase one didn't fail. Phase one never started. Three seats got provisioned, two people did the onboarding, one of them changed roles, and the workflow quietly reverted to the spreadsheet it was supposed to replace. Your champion knows. He's embarrassed. He is not going to open a conversation with "we never rolled it out," so he says "we need to see results," which is technically true in the most literal possible sense.

If this is the situation and you respond with an expansion play, you will burn the account. Not lose the deal — burn the account. You'll look like a vendor who either doesn't know or doesn't care that nobody's using the thing they already bought.

How to diagnose it in one call, without interrogating anyone

You need three pieces of information and you need to get them without sounding like you're auditing the customer.

The first is the number. Not "how's it going," which invites a polite lie. Ask what specifically gets measured:

"Totally fair. When your team looks at phase one and decides whether it worked — what's the actual thing they're looking at? Is it the ticket volume, or is it something else?"

The second is the calendar. Reviews have owners and dates:

"And who's in the room when that gets reviewed? Is that a formal QBR or more of a hallway thing?"

The third is usage, and you should never ask for it. You should already know. Pull the login data, the seat activation, the feature adoption, whatever you have, before you get on the call. If your usage data says fourteen active users and the customer bought forty seats, you are in diagnosis three regardless of what anyone tells you on the call.

The reason to lead with the number rather than the usage is dignity. If you open with "I noticed nobody's logged in," your champion has to defend himself in the first sixty seconds. If you open with the metric, he will very often walk himself into the truth. I've had champions answer that first question with a long pause and then, "honestly, we haven't been measuring it, because we haven't really got it in front of the team yet." That pause is worth more than any discovery framework. Shut up and let it happen.

Selling inside AWS taught me that the fastest way to find out what's really blocking a deal is to ask a question the customer can answer with a fact rather than a feeling. Feelings get you "we're happy." Facts get you the org chart.

Response one: the outcome-definition play

This is the highest-value response and it's the one to reach for when diagnosis one is true, or when you can't yet tell diagnosis one from diagnosis two.

The move is simple: you accept the condition and then you make the condition specific, dated, and written down.

An undefined condition is a trap because it can never be satisfied. "Results" is a mood. There is no evidence you can produce that definitively closes it, which means the customer can renew that stall indefinitely without ever feeling like they're stalling. A defined condition is a commitment. It converts the objection into a milestone you can both work toward, and it hands you a legitimate reason to come back on a specific date.

Here's roughly how I say it:

"Makes complete sense — I wouldn't expand either without knowing phase one landed. Can I suggest something? Let's write down right now what 'landed' looks like. If we hit a fifteen-minute reduction in documentation time per clinician by the end of March, is that the bar? Or is the bar something else?"

Then the part most reps skip:

"And if we hit it — what happens next? Does that go straight to the committee, or is there another step I should know about?"

That second question is the whole play. It smokes out diagnosis two. If the answer is "yeah, if we hit that I'd take it to Priya," you have a real path. If the answer wanders — "well, it depends on where we are with budget" — you've just learned that results were never the actual gate. Budget was. Now you can work the real problem.

Then you paper it. Not a contract. An email:

"Quick recap so I don't chase you unnecessarily: success for phase one is X by March 31. If we're there, you'll take the phase two scope to the ops council in April. I'll send you the measurement pull on the 25th so you have it before that meeting. If any of that's wrong, tell me now and I'll fix it."

That email does three jobs. It gives them a chance to correct you, which they usually will and which is where the real information lives. It gives you a reason to build the evidence rather than wait for it. And it means that in April, if the number was hit and the meeting didn't happen, the conversation is about their commitment rather than your persistence. Those are very different conversations to have.

Response two: the adjacent-team play

Sometimes phase one genuinely is the gate for that buying group, and there is nothing you can do to move it up. Fine. Go sideways.

The insight is that "phase one results" is only a dependency for the team phase one was run in. It is often not a dependency for a different team with a different budget and a different problem. Expansion doesn't have to mean more of the same thing to the same people. It can mean the same thing to a group your champion has never mentioned.

When I'm selling into a staffing firm and the perm desk is waiting on placement data before it expands, the contract desk has a completely separate P&L and a completely separate problem — which is why the redeployment conversation with staffing customers so often opens a door that the original buyer can't. Same in freight, where a brokerage's carrier sales team and its customer service team frequently sit under different leaders with different numbers, and the check-in that turns into a 3PL expansion is usually the one that stopped trying to move the original stakeholder.

The ask sounds like this:

"Understood — let's let phase one run. Separate question. When we scoped this originally you mentioned the carrier sales team has the same problem with a completely different queue. Is that still true? Because if their budget's separate, there's no reason they should be waiting on your results."

Two cautions. First, ask your champion for the introduction rather than going around him. Going around him to another team is how you turn a supporter into an enemy, and the account remembers that longer than you do. Second, be honest about what the adjacent team gets. If the other group's use case is genuinely weaker, don't sell it. You'll create a second phase one that also fails and now you have two stalls.

Response three: the sequenced-commitment play

This one is for the accounts where the relationship is strong, the outcome is likely, and the only real problem is timing. You paper the expansion now and activate it on the milestone.

The structure: phase two is signed, priced at today's terms, with a start date triggered by either the agreed metric or a fixed calendar date, whichever comes first. Nobody pays for anything they aren't using. The customer gets pricing certainty and the option to walk if the metric misses. You get the deal off the pipeline treadmill.

"Here's an idea that might make this easier for both of us. What if we sign phase two now at this quarter's pricing, but nothing activates and nothing bills until you've hit the number we just talked about? If phase one doesn't land, you don't pay and we both go back to the drawing board. If it does, your team isn't spending six weeks in procurement to get started."

The reason this works is procurement, and you should say so out loud. In most enterprises, the paperwork cycle is a genuine cost and your champion knows it. You're not asking him to commit money on faith. You're asking him to front-load the administrative pain so the value doesn't slip another quarter.

Where this fails: if your champion's actual problem is political cover, a contingent contract is still a contract, and he still has to walk it through legal, which is exactly the exposure he was avoiding. If he flinches at signature, you've confirmed diagnosis two. Go back to response one and find out who really controls the money.

The honest option: stop selling for six weeks

Now the version nobody wants to run, which is the correct answer more often than the other three combined.

If your usage data says the product isn't being used, there is no expansion play. There is only an adoption problem wearing an expansion problem's clothes. Every minute you spend trying to sell phase two into an unadopted phase one is a minute you spend making yourself look like a vendor who can't read the room.

So say it. Out loud. First:

"Can I be straight with you? I pulled the usage before this call and I don't think phase one has had a fair shot. You've got forty seats provisioned and fourteen people in the product regularly. That's on us as much as you. I don't want to talk about phase two today. I want to spend the next six weeks getting the team you already paid for actually using this, and then we can have an honest conversation about whether more of it makes sense."

Three things happen when you say that. Your champion exhales, because you just took the thing he was embarrassed about and made it a shared problem. You become the only vendor in his portfolio who told him something inconvenient. And you get a legitimate, welcome reason to be in the account weekly for six weeks, which is more access than any expansion pitch would have bought you.

The part that scares reps is the quarter. You just talked yourself out of a forecasted deal. Two things about that. One, it was never going to close this quarter — you were forecasting a stall, and your manager would rather know now. Two, the fix is to be specific about what replaces it. Don't just pull the deal. Pull the deal and put a dated adoption plan next to it, with named users, a training date, and a check-in on the calendar. Forecast the expansion for the following quarter with a real trigger behind it. That's not a lost quarter, that's a cleaned-up pipeline, and in my experience the second conversation closes faster and bigger than the one you walked away from.

The same logic applies in environments where the buyer is genuinely underwater and every new tool is a threat — the reason the SOC expansion conversation works at all is that it starts from what the team can absorb rather than what you'd like to sell.

What I'd do with this on Monday

Pull your expansion pipeline. Find every deal where the note says something like "waiting on phase one results." For each one, write down three things: the specific metric, the specific date it gets reviewed, and current usage against seats sold. If you can't fill in all three from what you already know, that deal is not a deal. It's a hope with a close date attached.

Then pick the one worth the most money and run the diagnosis call this week.

The reason most reps don't handle this well isn't that they don't know the plays. It's that the diagnosis call is uncomfortable and they've never said the words out loud before, so the first time they try it is live, on the account that matters. That's the wrong place to learn. It's why we built DrillCall — so you can run the awkward version of the conversation against an AI buyer who stalls you the same way your real customer will, ten times, before it counts. Run the healthcare version too if that's your patch; the ambient documentation upsell has its own particular flavour of this stall and it's worth rehearsing separately.

And whatever else you do, stop writing "waiting on results" in the CRM. Write the number. Write the date. Write the name of the person who reviews it. If you can't, you already know what you're dealing with.