Context: You've just presented a 3-year Azure architecture to a VP of Finance. The architecture includes Azure SQL Hyperscale and Azure Kubernetes Service.
Objection: "I ran the numbers. This costs $2.8M over three years. Our current data center costs $800K a year. That's $2.4M over three years. You're 16% more expensive. Why would we do this?"
Hidden root concern: The TCO comparison is incomplete: the legacy column is missing facilities, FTE labor, hardware refresh, and DR costs. But the VP doesn't know that. They feel ambushed by the number.
Context: A project sponsor tells you they want to proceed, but their CFO has blocked the purchase because the spend doesn't fit the current fiscal year's capital budget.
Objection: "The CFO said we can't approve a capital commitment of this size until Q1 next year. The budget cycle doesn't support it."
Hidden root concern: CapEx/OpEx structure. Azure consumption can often be structured as OpEx through Microsoft's enterprise agreements, but the sponsor doesn't know to ask for that.
Context: First meeting with a new customer. Midway through your architecture overview, the CTO interrupts.
Objection: "We went through a 'cloud transformation' three years ago with a Big 4 consulting firm. We spent $4M and ended up back on-prem. Why would this be any different?"
Hidden root concern: The prior failure was a governance and adoption failure, not a technical one. The CTO is scared of repeating the pattern, not of the technology itself.
Context: VP of Engineering, late in the sales cycle. Everything has gone well. Now:
Objection: "I need to see this working in a customer environment similar to ours before I sign off. Do you have a reference I can actually talk to, not a case study?"
Hidden root concern: Legitimate request, but also a stall mechanism. The VP needs permission from a peer to proceed.
Context: Two weeks after what seemed like a successful final architecture review, you get an email from your sponsor:
Objection: "I need to bring our Head of Procurement in before we can finalize anything. They have some concerns about the contract structure and I can't move without their sign-off."
Hidden root concern: Procurement is a Shadow Stakeholder who was never engaged (M01 gap). They have legitimate concerns: probably about contract terms, not technology.
Context: A customer who has been enthusiastic for three months suddenly gets quiet. When you follow up, you get:
Objection: "We've had some internal reorganization and I think we need to let the dust settle before we commit to something this significant. Let's reconnect in Q3."
Hidden root concern: The sponsor's authority or priority has changed. The reorg has shifted the power dynamics. "Q3" with no trigger is a polite way of saying "we don't know."