You did everything the process asks. You talked to finance before the meeting. You walked the head of IT through the integration. You had the sponsors nodding in the hallway. You walked into the committee with the votes lined up, and you walked out without the yes you expected. Nobody said no. Nobody said yes. You are back at your desk, replaying the room.
You email the two people who told you they were behind you. One replies with a line that tells you nothing. The other goes quiet. The decision is moving through rooms you are not in, and no one is narrating it for you.
A committee is a group of people, and people are not consistent from one week to the next. The same case that earns a yes on a Tuesday can draw a stall on a Wednesday, for reasons that never reach the minutes. Someone walked in irritated about a different fight. Someone carries a priority you were never shown. Gartner surveyed 632 business buying teams and found that 74 percent of them hit unhealthy conflict during the decision, meaning members with clashing objectives, open disagreement, or someone getting overruled from outside the room. Your committee is not the exception. The conflict was in the room before your case arrived.
A stall reflects the people in the room more than the strength of your case. They are human, and humans hesitate for reasons that never reach the work. The meeting did not close your case. It left you in the gap between submitting and deciding, and what you do in that gap decides whether the case survives.
“The same case that earns a yes on a Tuesday can draw a stall on a Wednesday, for reasons that never reach the minutes.”
Where cases die
The danger in the gap is silence that lasts. A real question surfaces in deliberation, reaches you late or through someone else, and sits unanswered while other priorities keep moving. A case in that state cools. Every week it sits without an answer, it loses a little of the momentum you built, until moving on is easier for the committee than taking it up again.
The stall usually looks reasonable from the outside. The committee points to the core conversation you have not finished, the website vendor you are still choosing, the reorg that moved three people last month, and sets your case aside to handle after the other thing settles. Later rarely comes.
The same Gartner study points at what pulls a case back out. Buying teams that reach real consensus are 2.5 times more likely to call the decision a good one. Consensus is what lets a committee act, and building it is work that keeps going after you submit. You cannot sit in every room where your case comes up. You can decide how fast a returning question gets a clear answer, and you can keep building the agreement that lets the room say yes.
Where the questions come from
You asked how to prepare for a question you did not see coming. Taken literally, you cannot do that. The exact question comes from a person having a human moment, and no one predicts that.
The kind of question is another matter. Across the institutions we work with, and across what sales teams hear from one prospect after another, the questions that come back in deliberation fall into five families. The committee asks whether it trusts your numbers. It asks whether the platform fits the systems you already run. It asks who does the work of standing it up, and when your team will have room to do it. It asks why this belongs ahead of the other initiative on the list, and why you should not wait until that other decision is settled first. It asks what the institution gets for the price.
Some families carry more heat than others. The fit question usually hides a specific fear, that the platform becomes one more system that does not connect to online banking and leaves the team maintaining it off to the side. The price question often has less to do with the fee than with the public site itself, and a reluctance to keep paying for it year after year rather than paying once. You will not know which family runs hot in your committee until a question comes back. You will know it belongs to one of the five.
A question feels unanticipated for one of two reasons. It arrives from someone you thought was already with you, or it arrives in a shape you did not rehearse. Name its family, and the surprise drains out of it. You reach for the answer you already built. Readiness is knowing the five families and staging an answer to each before the gap opens.
You can answer one of the five before anyone asks it out loud. Start there.
The number they will not trust
The numbers question is the most predictable of the five, and you can take it off the table inside the submission itself. A CFO distrusts a return that looks too large, even after their own finance team checked the inputs. A number that good reads as a number hiding something.
You discount it yourself, in the document, before the meeting. Say your model shows a return several times the threshold the institution uses for any investment. Rather than defend the big figure, you cut it to a quarter of what the model projects and show that even there it clears the bar. A committee that halves every vendor number out of habit meets a submission that already cut the number by three quarters and cleared the hurdle anyway.
That move changes the question in front of the committee. They stop weighing whether to trust your projection and start looking at a number they cannot easily argue down. You do the same work for the other four families, one staged answer at a time.
Speed is the part you control
Some of what stalls your case sits outside your reach. A key person leaves. Two institutions merge. Leadership freezes hiring. You cannot fix any of that, and spending the gap fighting it costs you the gap.
What you can control is the clock on a question. When something comes back from the committee, your answer reaches the right person the same week, short and credible, instead of a scramble that runs three weeks and lets the case cool. You win the gap on speed. Your answer is already written when the question lands, and it reaches the person who asked before the case goes cold.
When the committee wants to wait until the core decision or the website vendor is settled, you have an answer ready for that too. The goal leadership handed you does not wait for the other decision. Behavioral intelligence attaches to that goal rather than to whichever vendor wins the other slot, and the goal is still due this cycle. You build this readiness before you ever submit.
The answer you finally get may be a no. It may be a not now. It may be a we will let you know. Each of the three still leaves the work open, because the goal that sent you looking has not changed. Leadership still needs the growth. Behavioral intelligence still reaches it.
You go back to the person who hesitated. You sharpen the answer that landed soft. You bring the case again, into the next cycle if that is what it takes. The cases that get funded tend to be the ones somebody kept carrying after the room went quiet.
The work has a shape you can hold on one page. You list the five families. You write your own answer to each, in your own numbers, before you submit. You discount your return in advance. You name who stands the platform up and when. You settle why this goal comes before the other one. You carry that page into the submission and keep it open through the wait, so that when a question comes back, your answer is already sitting there.
Behavioral intelligence belongs in next year’s budget, tied to a goal the institution already committed to. Getting it there is quiet work that outlasts the meeting. You keep answering, and you keep building the agreement, until the room is ready to grant the yes it stalled on.
Ready for the questions that come back? Download the readiness map and stage your answer to each question before they land.
