Your software vendor announces a price increase. Your account manager explains that a new subscription package offers greater value. A product demonstration promises capabilities that appear to address your challenges. Yet after the conversation, you still have questions: What is actually changing? What will it cost? Does this recommendation fit our needs?
These are reasonable questions. Answering them requires a clear connection between the vendor’s message and your organization’s circumstances.
Having worked on both the customer and vendor sides of AECO technology, I have seen how information can change as it moves between people. I describe this as “filtered circles”—a practical way to understand how a decision becomes a message, how that message is interpreted, and what the customer ultimately hears.
How Vendor Messages Become Filtered
Imagine a vendor introducing a new licensing model. Leadership approves the direction, commercial teams establish the terms, and sales teams receive guidance on presenting the change. Your account manager then explains it to you.
Each person sees the decision through a different lens. Leadership may focus on business objectives. Product teams may emphasize capabilities. Sales teams need to explain the offering and respond to objections. Your organization needs to understand the effect on its budget, users, and existing commitments.
The information you receive may be accurate while still leaving important questions unanswered. A representative might explain what a package includes without establishing whether those capabilities are useful to your business. They may understand the announced price change but need help from another team to clarify your options.
That gap between the explanation and its practical meaning is where closer examination becomes valuable.
Bring the Conversation Back to Your Needs
When a vendor describes a change as an improvement, ask what improves for your organization.
A larger software bundle deserves a closer look if your team needs only a few of its capabilities. A lower unit price requires context if the proposal includes more licenses or a longer commitment. A promising enhancement needs clarification if your decision depends on functionality that has not yet been released.
Start with a straightforward request: “Please show us how this proposal differs from our current agreement and how those differences address our needs.”
Then examine the response through four connected considerations: people, processes, technology, and budgets. Who will use the software? How will it fit their work? What capabilities and dependencies matter? What resources will the commitment require?
This keeps the discussion focused on a business decision you can evaluate.
Ask Questions That Lead to Clear Answers
You do not need an adversarial approach to challenge a proposal. Specific questions give your representative an opportunity to provide useful information or involve someone who can.
Before approving a purchase or renewal, ask:
- What exactly changes from our current agreement?
- Can you separate price increases from changes in quantities, discounts, and packaging?
- Which capabilities are available today, and which depend on future development?
- What additional products, services, or internal effort will we need?
- Which parts of the proposal can we adjust?
- What deadlines affect our choices?
- What happens if we decline the proposed changes?
- Which commitments can you confirm in writing?
When an answer remains unclear, ask for a supporting document, a relevant demonstration, or a specific example. If a question falls outside your representative’s responsibilities, establish who will answer it and when.
Turn the Discussion Into a Decision Record
A productive meeting should leave you with more than a positive impression. Summarize what has been confirmed, what remains uncertain, and which information is still needed.
Keep demonstrated capabilities separate from verbal descriptions and future plans. Record assumptions about costs, quantities, training, and implementation responsibilities. Where a commitment is essential to your decision, ask how it will appear in the proposal or agreement.
Share your summary with the vendor and invite corrections. This gives both parties an opportunity to address misunderstandings before you commit.
Evaluate the Relationship as Well as the Proposal
The way a vendor responds to reasonable scrutiny tells you something useful about the relationship.
Do answers become more specific as the discussion progresses? Are the appropriate specialists available? Does someone take responsibility for unresolved questions? Are promised follow-up actions completed?
A representative will not always have an immediate answer. What matters is whether there is a reliable path to obtaining one.
The same accountability applies within your organization. Clear requirements, timely participation, and honest feedback help vendors respond meaningfully. Better communication requires both parties to understand the decision being made.
Look Beyond the Message
“Filtered circles” is a reminder to examine how information reaches you and what may still be missing. An incomplete explanation does not automatically indicate bad intent. It does mean you may need more evidence before making a commitment.
Your goal is to reach a decision you can explain: what you are buying, why it fits, what it will cost, and which risks or uncertainties you are accepting.
At AECO Ensights, we help architecture, engineering, construction, and infrastructure organizations bring that clarity to software decisions. Our independent perspective helps leaders examine proposals, question assumptions, and prepare for more productive vendor conversations.
Approaching a software renewal? Our Software Renewal Review focuses on one vendor and one upcoming commitment, delivering a Renewal Decision Brief with findings, unanswered questions, and recommended next steps.