Why proposals die when they start with ROI
To access the full content, click here.
A proposal can be technically flawless and still die before the technical discussion begins. In the three brains model used in this content, that happens when the message starts with the rational cortex while threat and belonging filters are still unresolved.
The problem with starting with ROI
ROI, savings, and timelines matter, but they enter late in the decision architecture. If the decision maker still reads the proposal as a threat to status, control, or reputation, a spreadsheet does not remove the block.
Sequence changes perception
Start by framing the opportunity around survival, control, or security. Then add enough social validation to reduce the fear of being wrong alone. Only after that should the rational proof arrive.
How to apply it in your next proposal
Review your opening sentence before you open the deck. Does it speak to a spreadsheet or to the problem threatening the decision maker? Then check social context and only after that deliver the technical proof.
Deepening the decision-maker read
The most important point in Why proposals die when they start with ROI is turning an abstract idea into an operational read. In a real conversation, decision-makers rarely state directly what they are trying to protect. They may ask for more data while actually worrying about risk, exposure, loss of control, or their ability to defend the decision in front of others.
Use the framework as an attention map. Instinctive, social, and rational signals can appear at the same time. The goal is not to label a person, but to notice which concern is dominating the moment and adjust the order of the message.
The useful question is not “which brain is this person?”. It is “what does this person need to feel, validate, and prove before moving forward?”.
How to apply it in practice
Before answering an objection, identify the layer where it is likely originating. A financial objection may hide fear of losing control. A technical objection may be a socially acceptable way to avoid exposure. When you identify the likely origin, the response becomes shorter, more specific, and more coherent.
Diagnostic questions
What does the decision-maker seem to be protecting right now?
What personal, operational, or reputational risk sits behind the question?
What social proof would reduce the fear of being wrong alone?
What concrete evidence turns perceived safety into technical justification?
What next step allows progress without sharply increasing perceived risk?
Message sequence
Open with the dominant concern, using language close to the decision-maker’s reality.
Show that the choice is defensible in their professional and social context.
Only then present numbers, ROI, timeline, architecture, or technical evidence.
Close with a simple, clear next step that is reversible when possible.
This discipline improves the pitch because it reduces information overload. Instead of dumping arguments, you organize the conversation in the order the decision-maker can process and defend it.
Comments