Why I Said No to Your Proposal - Its Not the Reason you Think

Last quarter, I turned down a million-dollar proposal. The supplier immediately sent a revised quote - fifteen percent lower. They still didn't understand why I said no. Price wasn't the problem. Price is almost never the problem. 

In this episode, I walk through the five real reasons proposals die on a CPO's desk: 

1. You didn't understand the problem - you pitched features before asking about organizational context 
2. You sold past the decision-maker - you tried to go around procurement, and it triggered every risk instinct I have 
3. Your proposal created risk you didn't acknowledge - no exit ramps, no data portability, no honest timeline 
4. You failed to connect to the mission - you pitched ROI when you should have pitched stewardship 
5. The proposal was a monologue, not a conversation - it felt produced, not crafted 

I also talk about what happens on our side when stakeholders hand suppliers bad specifications, and why price becomes the stated reason only after everything else has already failed. 

Whether you're a supplier refining your approach, a stakeholder wondering why procurement said no, or a CEO who wants to understand what your CPO is actually evaluating - this one's for you.

---

New episodes every Monday. 

Subscribe wherever you listen. 

Website: https://procurexcellence.com 

Email: robert@procurexcellence.com 

Topics covered: vendor proposals, procurement rejection, discovery process, risk management, mission-driven purchasing, stakeholder alignment, supplier relationships

Transcript

SPEAKER_00 0:00

Last quarter I turned down a proposal worth just over a million dollars. The supplier was well known, the product was solid, and the internal stakeholder who brought it to me was very enthusiastic, genuinely excited about what this solution could do for the organization and how it could move us forward. And I said no. Not not yet, not let's revisit this in the next fiscal year. I just said no. And the reaction I got from the stakeholder, from the supplier, from the account exec who'd been working on this deal for months, was the same reaction I almost always get. They assumed it was about price. The account executive sent a follow up email within forty eight hours, with a revised quote, fifteen percent lower, and new payment terms, with a note that said, We really want to make this work. And I remember reading that email and thinking, you still don't understand why I said no. The price wasn't the problem. The price was never the problem. If you're a supplier, an account executive or a sales leader, I need you to hear something that might be uncomfortable. The vast majority of the time a CPO says no to your proposal, price is not the primary reason. It might be what we cite in a debrief, it might be the easiest thing to point to. But underneath that, there's almost always something else going on. Something that was decided long before we got to the pricing conversation. This is episode two of the other side of the table. I'm Robert Brindle, and today I'm going to tell you the real reasons proposals die on my desk, and what you can do about it. Let me walk you through what actually kills a proposal from the buyer's side, and I want to be specific because vague advice doesn't help anyone. I'm going to give you the five things that in my experience account for the overwhelming majority of rejected proposals. You'll notice that among these five, price is not on the list. Number one, you didn't understand the problem. That is without question the most common reason I say no. And it's the one that frustrates me the most because it's the most preventable. Here's what typically happens. A supplier gets a meeting, maybe through a relationship with the stakeholder, maybe through a cold outreach that landed, maybe through an RFP response that my team issued. They walk in, and within the first five minutes, they're showing me their platform, their features, their dashboards, their integrations. They've got a polished deck, a confident presenter, and a great sales team, and the product that probably does exactly what they say it does. But here's what they haven't done. They haven't asked me what problem I'm trying to solve. They've assumed they already know, or worse, they've taken whatever the stakeholder told them in the initial conversation and treated it as if it was the full picture. And stakeholders' perspective, while valuable, is almost never the full picture. The stakeholder sees their piece of the puzzle. They know what their team needs day to day, but they may not know that we're in the middle of a broader technology consolidation. They may not know that we tried a similar solution two years ago and it failed during implementation. They may not know that there's a contract with a competing supplier that doesn't expire for another eighteen months, and unwinding it has financial implications nobody has factored in. I know all these things, and when a supplier walks in without asking about them, without doing the discovery work to understand the organizational context, not just the functional need, I know immediately that their proposal is going to miss. It doesn't matter how good the product is, if you're solving a problem I don't actually have, or solving the right problem in a way that ignores the constraints I do have. You don't bother to learn about. The answer is always going to be no. And here's another thing that makes this particularly painful. The fix is so simple. Ask better questions at the front end. Not what are your pain points? That's a sales script question. And it sounds like one. Ask me. Instead, what's the broader context around this initiative? What else is happening in the organization that might be affecting the way you evaluate this? What would happen if this didn't work? What does success look like twelve months from now? Not just when we go live, but after. Those questions tell me that you're thinking about my world, not just your sales pipeline. Now I want to be honest about something here because this isn't entirely the supplier's fault. Sometimes the organization hands you bad specifications to begin with. I see this constantly. A stakeholder writes a scope document that's either so vague it could mean almost anything, or so narrow it reads like it was reversed engineered from a product they've already chosen or provided to them by the supplier of choice. The requirements say things like must integrate with an ex with existing systems without specifying which systems, or should support enterprise scale reporting without defining what enterprise scale means to us. These aren't specifications, these are aspirations dressed up as requirements. When that happens, the supplier has a choice. They can take the specs at face value and build a proposal around their best guess at what we mean, and hope it lands, or they can push back, they can say, stop, I want to make sure I'm building this proposal around what you actually need. Can we walk through these requirements together? A few of these feel really broad, in fact so broad that I want to make sure I'm not making assumptions that lead us in the wrong direction. Almost nobody does the second thing. And I understand why. Suppliers are afraid that asking too many questions will make them look unprepared, or slow down the process, or worst of all, give the prospect a reason to go with someone else who just said yes to everything. But here's what actually happens when you accept a bad spec without challenging it. You submit a proposal that's misaligned. I reject it, and you never get a clear answer about why. The supplier who asks about who asks the clarifying questions might feel like they're slowing things down, but they're actually building the foundation for a proposal that will actually land. And to the stakeholders listening, this is on you too. If you hand a supplier a two page requirements document that you wrote in an afternoon, and then wonder why the proposals you get back don't match what you had in mind? The proposals are a mirror. They reflect the quality of what you gave the supplier to work with. Procurement can help you write better specifications, that's part of what we do, but you have to bring us in before the requirements go out, not before the proposals come back wrong. And ultimately, the specifications are owned by the business, not procurement. Number two, you sold past the decision maker. This is the one that will sync you faster than anything else. And it's the one I see the most talented salespeople get wrong. Here's the scenario. You've built a great relationship with the business stakeholder, the VP, the director, the end user who's going to be living in your platform every day. They love your product, they're ready to sign. And then procurement enters the pitcher. And suddenly there's a process. There are questions. There's a timeline that didn't match your quarter end deadline. And so you do what your instincts tell you to do. You go back to your champion inside the organization and try to get them to push it through. Maybe you escalate. Maybe your champion escalates for you. Maybe someone sends an email to my boss asking why procurement is holding this up. Let me tell you what happens next because it's the opposite of what you're hoping for. When a supplier tries to go around procurement, it triggers every risk instinct I have. It tells me that this supplier views the procurement process as an obstacle, rather than a safeguard. It tells me that they're optimizing for their closed timeline, not for my organization's best interest. And it tells me that if we have a problem with this supplier post contract, an implementation issue, a performance gap, maybe even a billing dispute, they're going to use that same playbook. Go around procurement, go around the scope to the stakeholder, escalate pressure. I've seen this pattern play out dozens of times, hundreds of times. And the suppliers who go around procurement don't just lose that deal, they lose credibility that it takes years to rebuild. Because word gets around, procurement teams talk to each other, and I have a very long memory and a very big network. The suppliers who win, though, and I mean consistently win, not only close one deal through pressure, they're the ones who treat the procurement process as something to work through, not something to work around. They engage with me directly, they ask what I need to feel confident, they provide documentation proactively, they respect the timeline, and when their champion inside the organization asks them how to speed things up, they say, Let's make sure procurement has everything they need. That answer earns more trust than any discount ever will. three, your proposal created risk that you did not acknowledge. Every proposal that crosses my desk at its core is a risk document. And I don't mean that in a cynical way, I mean literally. A proposal is asking my organization to commit resources, enter a contractual relationship, and depend on an external party for something that matters. Every one of those elements carries risk. And here's what separates a good proposal from a great one. A great proposal acknowledges the risk and addresses it head on. A good proposal pretends the risk doesn't exist. Let me give you some examples. If you're proposing a three year software contract, I'm thinking about what happens if your company gets acquired? If the product gets if the product gets sunset, if key personnel leave, if our needs change. If your proposal doesn't address any of those scenarios, if there's no exit ramp, no data portability clause, no performance guarantees, you've left me to assume the worst and I will. If you're proposing an implementation that depends on my team providing resources, subject matter experts, data, access to systems, and you haven't been explicit about what that requires, I'm going to assume the timeline is unrealistic. Because in my experience, suppliers chronically underestimate what they need from the client side. And then when the project falls behind, they point the finger back at us. If your pricing model has a low entry point, but escalates significantly in years two and three, and you haven't called that out transparently, I will find it. And when I do, the trust deficit it creates is significant. Not only because price escalation is inherently wrong, sometimes it makes sense, but because you tried to obscure it? And if you're obscuring pricing, what else are you obscuring? The best proposals I have ever received included a section sometimes literally titled Risk and Mitigations, where the supplier said, Here are the things that could go wrong. Here's how we've addressed them, and here's what we'll do if they happen anyway. That kind of transparency is so rare that it immediately elevates you above the competition. It tells me that you've done this before. It tells me that you're a partner, not just a seller. four, you failed to connect with the mission. So this one is particularly important if you're selling to a nonprofit, but it applies in every organization I have ever been in that has a purpose beyond revenue. I work at a nonprofit where the money that they spend comes from donors, from grants, from people who gave because they believe in what the organization does. When I evaluate a proposal, I'm not just asking is this a good deal? I'm asking can I justify this expenditure to the people whose resources are funding it? That's a different question, and it requires a different kind of answer. When a supplier walks in and pitches me the same way they'd pitch a Fortune five hundred company, all ROI and efficiency and competitive advantage, it tells me they haven't thought about who we are. We're not trying to beat a competitor. We're trying to serve a mission. Show me how your solution helps us do that better, how it stretches our resources further, how it helps us be better stewards of the trust people have placed in us. That framing changes everything. And even if you're selling to a for profit company, this principle still holds. Every organization has a purpose. They have a strategy, a set of priorities that go beyond the immediate purchase. If you can connect your proposal to that larger story, if you can show the CPO that you understand not just what they're buying, but what they're buying it for, you've moved from being a supplier to being a potential partner, and that's fundamentally a different conversation to have. And number five, the proposal was a monologue, not a conversation. This is the subtlest of the five, and it's one that I think the best salespeople already understand intuitively. The proposal should be a culmination of a conversation, not the beginning of one. By the time I'm reading your proposal, I should have already had multiple exchanges with you about scope, about requirements, about concerns, about constraints. The proposal should reflect what we've discussed. It should feel like a document that was built with me, not delivered to me. But most proposals don't feel that way. Most proposals feel like they were written in a vacuum, or worse, like they were written for a different client, and lightly customized with our organization's name and logo swapped in. I can tell, I've read hundreds of these. When the scope section uses generic language instead of reflecting the specific conversation we had, when the case studies are from a completely different industry with no explanation of why they're relevant, when the pricing structure doesn't map to the requirements we discussed, all of these are strong signals that this proposal was produced, not crafted. And that matters, because procurement is fundamentally about relationships, not in the golf outing gift basket sense, but in an operational sense. I need to trust that the supplier I'm recommending to my organization is going to deliver. The proposal is my first evidence of whether that trust is warranted. If you can't be bothered to tailor a proposal to what we actually discussed, why would I believe you can tailor the solution? The proposals that land on my desk and make me lean forward and look are the ones where I read the first page and I think, hey, they were listening. Those are the ones that move. They reference specific things I said. They address concerns I raised before I had to raise them again. They include creative approaches to problems we identified together. They feel like the next step in a relationship, not the first volley of a transaction. Now I know that some of you are thinking, but Robert, price does matter. I've lost deals on price. And you're right, price matters. I'm not saying that it doesn't. What I'm saying is that price is almost never the root cause of rejection. It's the surface cause. It's the easiest thing to point to in a debrief because it's quantifiable. But here's what's really happening. When I reject a proposal and cite price, what I what that often means is I couldn't justify the investment because the proposal didn't make a compelling enough case. The price felt too high because the value wasn't articulated. The risk wasn't addressed. The scope didn't align. The relationship wasn't there. If all of those other elements were strong, I would find a way to make the price work. I would restructure the deal. I'd phase the implementation, I'd negotiate terms that spread the cost. I'd do this all the time for suppliers that I believe in. Price becomes the reason when everything else has already failed. So here's what I wanted you to take away from this episode today. If you're a supplier or an account exec, before you submit your next proposal, go through this checklist. Have I truly understood the problem this organization is trying to solve? Not just the functional need, but the organizational context? Have I engaged with procurement as a partner? Not an obstacle? Have I acknowledged the risks in my proposal and explained how I'll mitigate them? Have I connected my solution to this organization's mission and priorities? And does this proposal feel like it was built from a conversation or does it feel like it was built from a template? If you can answer all five honestly, your proposal will be on the top ten percent of what crosses my desk. That's not hyperbole, the bar is that low, and the opportunity is that large. If you're a CEO, a COO, or a CFO, ask your CPO about the proposals they've rejected recently, and why? Not the surface reasons, the real reasons. You might be surprised at how much intelligence your procurement team has about the quality of the suppliers approaching your organization. That intelligence should inform you your should inform your supplier strategy, not just your purchasing decisions. If you're a stakeholder who's ever even had a proposal rejected by procurement and felt frustrated, I hear you. And I want you to know that when I say no, I'm not saying no to you. I'm saying no to a specific proposal that didn't meet the threshold of what I think this organization should commit to. Bring me in earlier next time. Let me help you shape the requirements before the supplier writes the proposal. Let me talk to the supplier during the discovery phase, so they understand the full picture. The best proposals I approve are the ones where procurement was in the room from the beginning. Not because I control the outcome, but because the supplier had better information to work with. And if you're in procurement, you know everything I just said is true. But I want you to push on something. When you say no to a proposal, are you being specific enough about why? Not in the legal cover yourself debrief, but in the honest feedback that helps a supplier come back stronger. We have an opportunity to raise the quality of what we see by being transparent about what we need. The suppliers who listen and the good ones do listen will come back with better proposals, and that's better for everyone. So that's episode two of the other side of the table. I'm Robert Brindle. Next week, we're going to talk about the meeting before the meeting, how procurement prepares before sitting down with anyone, and why the real decisions often happen before you walk in the room. I'll see you then.