Why IT Suppliers Give Conflicting Advice

Conflicting advice from IT suppliers can leave business leaders facing an expensive decision without a clear way to judge which recommendation is right. Your software developer wants to rebuild a system. Your managed IT provider recommends replacing the infrastructure. Another consultant believes you should move to a new platform entirely.

Each supplier sounds confident. Each presents a reasonable argument. Yet their recommendations involve different costs, risks and consequences for your business.

The solution is not necessarily to find out which supplier is the better technical expert. It is to establish which recommendation best addresses your business needs, based on evidence rather than opinion.

Takeaways

  • Conflicting supplier recommendations do not automatically mean someone is wrong.
  • Define the business problem before evaluating technical solutions.
  • Compare recommendations using consistent evidence, costs, risks and assumptions.
  • Keep technology investment decisions accountable to the business.
  • Use independent advice for difficult decisions and ongoing leadership where gaps persist.

Table Of Content

Why Competent Suppliers May Disagree

Two experienced technology suppliers can examine the same situation and reach different conclusions. That does not automatically mean either is incompetent or deliberately misleading you.

Technology decisions rarely have only one correct answer. Different approaches can solve the same problem, but they may involve very different costs, risks and compromises.

There are several reasons suppliers reach conflicting conclusions.

Different Areas of Expertise

A software developer might see a performance problem and recommend changing the application. An infrastructure provider might see the same symptoms and recommend upgrading the servers.

Both recommendations could improve performance. Neither necessarily identifies the underlying cause.

Each supplier naturally approaches the problem through their own expertise. This is useful when addressing specialist technical issues, but can be limiting when the problem extends beyond their area of responsibility.

Different Commercial Interests

Technology suppliers are businesses with their own commercial models.

A software development company earns revenue from development. A cloud provider benefits from infrastructure consumption. A software vendor sells licences or subscriptions.

This does not mean their recommendations are dishonest. However, commercial interests can influence which solutions a supplier considers, how alternatives are presented and what work they propose undertaking.

A good recommendation should remain defensible even when the supplier’s commercial interests are removed from the discussion.

Different Assumptions

Two recommendations may be based on different assumptions about your business.

One supplier might assume transaction volumes will double. Another might assume existing demand will remain relatively stable.

One could be designing for maximum availability, while another is prioritising lower operating costs.

Until those assumptions are made explicit, comparing the recommendations is difficult.

Different Views of the Problem

Sometimes the disagreement exists because nobody has clearly defined the problem.

A business experiencing slow customer service might receive recommendations for a new CRM, upgraded infrastructure or custom software development.

But what if the real issue is an inefficient approval process?

Technology could help, but replacing systems might be an expensive way to avoid addressing how people work.

My approach is always to put people before technology. I want to understand the business, its customers and the people doing the work before deciding what technology should change.

Business executives comparing conflicting technology supplier recommendations during a meeting.
Comparing Technology Supplier Advice

When Disagreement Becomes a Business Risk

Disagreement between suppliers is not necessarily a problem. Constructive technical debate can expose weaknesses, challenge assumptions and lead to better decisions.

The risk begins when the disagreement prevents the business from making informed decisions.

You might recognise some of these situations:

  • Investment decisions keep being delayed. Each supplier challenges the other’s proposal, and nobody can establish a clear way forward.
  • Costs increase without clarity. Additional assessments, meetings and proposed changes consume money without resolving the underlying issue.
  • Accountability becomes unclear. Suppliers point to one another when systems fail or projects run late.
  • Business leaders become the technical referees. The CEO or Managing Director is expected to choose between technical approaches they cannot reasonably assess.
  • Important risks remain unresolved. Security, business continuity, data ownership or support responsibilities fall between suppliers.

The commercial consequences can extend well beyond the technology itself.

Employees may spend more time working around unreliable systems. Customers may experience delays. New products might be held back while management waits for technical decisions.

The business may also commit to a solution that creates new dependencies or becomes expensive to maintain.

The objective should not be to eliminate disagreement. It should be to make disagreement productive and reach a decision the business can justify.

Start With the Business Decision

Before asking which supplier is correct, establish what decision the business actually needs to make.

I would begin with five questions:

  1. What business problem are we trying to solve?
  2. What evidence shows the problem exists?
  3. What outcome do we need?
  4. What constraints must the solution respect?
  5. What happens if we delay the decision?

These questions move the discussion away from competing technical solutions and towards business outcomes.

For example, consider a business where employees spend hours manually transferring customer information between systems.

One supplier recommends replacing the CRM. Another proposes developing a custom integration.

The business problem is not necessarily that the CRM is outdated or that an integration is missing.

The problem is that employees are spending time on avoidable manual work, introducing errors and delaying customer service.

A useful outcome might be to reduce manual data entry, improve information accuracy and make customer records available when needed.

Once that outcome is agreed, it becomes easier to evaluate competing recommendations.

Define What Success Looks Like

A recommendation should explain how the proposed change will improve the business.

Depending on the problem, that might involve:

  • Reducing processing time or avoidable manual work.
  • Improving system reliability and availability.
  • Reducing operational or security risks.
  • Improving customer service.
  • Supporting additional transactions or business growth.
  • Making systems easier to maintain and support.

The measures do not always need to be financial, but they should be specific enough to evaluate.

If a supplier cannot explain how its recommendation contributes to the intended outcome, the proposal may not yet be ready for approval.

This is where a clear Technology Strategy helps connect individual technology decisions to wider business priorities.

Ask Suppliers for Comparable Evidence

When suppliers disagree, I would avoid asking each one to produce a longer presentation defending its position.

Instead, request the same information from every supplier.

This creates a consistent basis for evaluating the recommendations.

Clarify the Problem Being Solved

Ask each supplier to describe the underlying problem in plain English.

What evidence supports its diagnosis? Has the supplier examined the system directly, reviewed logs, interviewed users or relied on information supplied by someone else?

It is important to distinguish between a confirmed problem and a suspected cause.

For example, a slow application does not automatically prove the server is undersized. Performance could be affected by inefficient database queries, background processing, network conditions or application design.

The investigation should establish which factors are contributing to the problem before recommending substantial investment.

Identify the Assumptions

Every recommendation relies on assumptions.

Ask suppliers to identify those assumptions and explain what would change their recommendation.

These might include expected growth, transaction volumes, integration requirements, staffing capacity, current system limitations or the availability of support.

An assumption should not quietly become an accepted fact simply because it appears in a polished proposal.

Request Costs and Dependencies

A useful recommendation needs to explain more than its initial implementation price.

Ask for:

  • Initial implementation and migration costs.
  • Ongoing software, infrastructure and support costs.
  • Internal staff time and operational disruption.
  • Dependencies on particular suppliers, products or individuals.
  • Training, testing and documentation requirements.
  • Future upgrades and maintenance.
  • The likely cost and complexity of changing direction later.

The Australian Government’s business case guidance provides a useful decision-making principle: define the problem, examine alternative options, and assess costs, benefits and risks over the investment’s life.

Although that guidance is written for government investments, the underlying approach is useful for commercial technology decisions too.

Ask What Could Go Wrong

Every technology option involves some risk.

A supplier should be able to explain the most important risks associated with its recommendation, how those risks would be managed and what would happen if the proposal did not deliver the expected outcome.

I would also ask what happens if the business chooses not to proceed.

Doing nothing is not necessarily free. Existing inefficiencies, operational risks and maintenance costs may continue.

However, leaving the current arrangements in place temporarily can sometimes be preferable to making a poorly informed investment.

Compare Options on More Than Price

Once the recommendations are supported by comparable evidence, assess them against a common set of criteria.

The cheapest option is not automatically the best. Nor is the most technically sophisticated.

A practical comparison should consider:

Decision criterionWhat leadership should establish
Business valueHow does this option improve the outcome we need?
Whole-of-life costWhat will it cost to implement, operate, support and eventually replace?
Delivery riskHow likely is the solution to be delivered successfully?
Operational impactWhat disruption will employees and customers experience?
Security and continuityDoes it introduce or reduce important business risks?
DependenciesWill we become dependent on a particular supplier, platform or individual?
FlexibilityCan the solution support changing requirements?
EvidenceWhat supports the recommendation, and what remains uncertain?

The comparison does not need to become a complicated scoring exercise.

For a relatively small decision, a concise options paper may be sufficient. For a substantial technology investment, more detailed analysis may be justified.

The important point is that each option must be assessed against the same business requirements.

If suppliers use different assumptions, cost periods or definitions of success, the comparison will be misleading.

Consider Security and Supplier Risk

Security and business continuity deserve particular attention when a recommendation affects critical systems, sensitive information or supplier access.

The Australian Signals Directorate’s cyber supply chain risk management guidance recommends identifying supplier risks, establishing security expectations and monitoring supplier arrangements.

For your decision, relevant questions might include:

  • Who controls access to the systems and data?
  • Who is responsible for backups and recovery?
  • Who maintains the solution after implementation?
  • Can the business operate if the supplier becomes unavailable?
  • What information and documentation would be needed to change suppliers?

These questions should be proportionate to the systems involved. A customer-facing financial platform requires a different level of scrutiny from a low-risk internal reporting tool.

Business leader and technology adviser comparing costs, risks and benefits of technology proposals.
Evaluating Technology Recommendations

Who Owns the Final Technology Decision?

One of the most important questions is who has authority to make the decision.

Suppliers are responsible for providing professional advice within their agreed scope. Internal technology leaders may assess technical suitability. Finance may need to evaluate expenditure, while operations assesses business disruption.

But someone within the organisation must have the authority and accountability to approve the chosen approach.

The arrangement will depend on the business’s governance structure and delegated authority.

For example:

  • Technology suppliers explain their recommendations, assumptions, risks and delivery responsibilities.
  • Technical leadership evaluates feasibility, dependencies, supportability and alignment with the wider technology environment.
  • Business stakeholders confirm operational requirements and the consequences of proposed changes.
  • Finance and risk functions assess commercial exposure, affordability and relevant controls.
  • The authorised executive or board makes the appropriate investment decision within its governance arrangements.

The person approving a major technology investment should not be expected to understand every line of code or infrastructure setting.

They should, however, receive enough reliable information to understand the options, the business consequences and the risks being accepted.

This distinction between governance and management is also reflected in ISACA’s explanation of COBIT. Governance establishes direction and decision-making arrangements, while management carries out activities aligned with that direction.

A technology supplier should not effectively become the final decision-maker simply because nobody else feels comfortable challenging its recommendation.

What if Neither Supplier Is Right?

A common mistake is assuming the business must choose one of the recommendations presented.

There may be a third option. Both recommendations might contain useful elements, or further investigation could show that neither addresses the real problem.

Consider a business with an ageing customer management system.

Its software developer recommends rebuilding the application because the existing technology is difficult to maintain.

Its managed IT provider recommends moving the system to modern cloud infrastructure because the current hosting arrangement is becoming unreliable.

Both recommendations could be reasonable.

But suppose the largest business concern is inaccurate customer information and duplicated administrative work.

Rebuilding the application might improve maintainability without fixing the underlying data and process problems.

Moving the application to different infrastructure might improve reliability while preserving the same inefficient workflows.

Another option could involve improving data handling, simplifying business processes and addressing specific application weaknesses without immediately replacing everything.

The right choice depends on evidence.

Examine the Alternatives

I would ask the suppliers to consider several approaches:

Option A: Replace the application. This could address limitations in the existing software, but it may introduce migration risks, additional implementation costs and significant changes for employees.

Option B: Improve the existing infrastructure. This might address reliability or capacity problems, but would not necessarily resolve weaknesses in application design or business processes.

Option C: Make targeted improvements. This could involve changes to data flows, integrations, configuration or operational procedures. It may reduce immediate disruption, but could leave longer-term limitations unresolved.

Option D: Investigate and improve in stages. A focused assessment, followed by a limited change or pilot, could reduce uncertainty before committing to a larger investment.

These are illustrative alternatives, not recommendations for a particular business.

I would want enough evidence to understand which problems each option solves, which problems remain and what the business would be committing to.

Sometimes a staged approach provides the best balance between progress and risk.

Other times, replacing an outdated system is the right decision.

The objective is not to defend existing technology. It is to avoid spending money on the wrong solution.

How to Resolve the Disagreement

When technology suppliers are giving conflicting recommendations, I would use a structured decision process rather than allowing the disagreement to continue indefinitely.

Step 1: Establish a Decision Owner

Nominate one person responsible for coordinating the decision.

This person should have enough authority to obtain information, bring the relevant stakeholders together and escalate decisions for approval.

They do not have to be the most technically experienced person.

Step 2: Agree on the Business Problem

Document the problem, its impact, the desired outcome and any relevant constraints.

Ask the suppliers to confirm that they understand the same requirements.

If they disagree about the underlying problem, resolve that disagreement before assessing proposed solutions.

Step 3: Request Written Recommendations

Ask each supplier to provide a concise explanation of its proposed approach, supporting evidence, assumptions, expected outcomes, costs and risks.

Avoid relying solely on verbal explanations from meetings.

Written recommendations make it easier to identify genuine differences and prevent important details from being lost.

Step 4: Challenge the Assumptions

Bring the recommendations together and examine areas of disagreement.

Where a claim is uncertain, identify what evidence would confirm or challenge it.

This might require a short technical assessment, examination of operating data, a small proof of concept or further clarification from the suppliers.

Do not commission extensive investigations without first establishing what decision the additional information will support.

Step 5: Record and Communicate the Decision

Document the selected option, the reasons for choosing it, the risks being accepted, the person approving it and the actions required.

Communicate the outcome to everyone responsible for implementation.

A decision record is particularly useful when circumstances change or someone later asks why an alternative was rejected.

Keep the Supplier Relationship Constructive

Resolving a disagreement should not become an exercise in deciding which supplier has lost the argument.

Capable suppliers can disagree while still working constructively together.

I would bring the discussion back to evidence, responsibilities and agreed business outcomes.

Ask each supplier to explain the circumstances under which the other recommendation might be appropriate. This can reveal assumptions that were previously hidden.

It also helps distinguish constructive professional disagreement from an unwillingness to consider alternatives.

The Australian Government’s business.gov.au supplier guidance encourages clear communication, documented expectations and constructive resolution of supplier issues.

If relationships have become strained, a facilitated discussion can help establish facts and responsibilities.

However, persistent refusal to provide information, unclear ownership of critical systems or repeated attempts to shift responsibility should be treated as genuine governance concerns.

If delivery has already been affected, independent Project Delivery support may help clarify responsibilities and restore visibility across the work.

When to Seek an Independent Review

Not every supplier disagreement requires outside help.

If your internal technology leader can assess the evidence, clarify the trade-offs and recommend a defensible option, that may be sufficient.

An independent review becomes more useful when the decision involves significant expenditure, operational risk, specialised technical knowledge or competing commercial interests.

Examples include:

  • A supplier recommends replacing an important business system.
  • Two providers disagree about the cause of repeated failures.
  • A substantial software development proposal is difficult to validate.
  • Management cannot establish whether the recommended solution addresses the business problem.
  • The organisation is concerned about supplier dependency, security or continuity.
  • The decision has consequences beyond the technical team.

The purpose of an independent assessment is not automatically to overrule existing suppliers.

A good review should test the assumptions, examine the available evidence, identify important gaps and explain the options in terms the business can use.

Sometimes the result will support the recommendation already made by one of your suppliers.

That is still valuable. It gives management a stronger basis for proceeding.

At White Internet Consulting, an Independent Technology Review can provide a second opinion when a business needs clarity around a specific technology decision, proposed investment or risk.

When Fractional CTO Leadership Makes Sense

A single disagreement might be resolved through a meeting, a focused assessment or an independent review.

Repeated supplier disagreements can indicate a different problem.

Perhaps nobody owns the overall technology direction. Individual suppliers make recommendations within their own scope, but there is no experienced technology leader assessing how those recommendations fit together.

The CEO becomes responsible for resolving technical questions, approving competing priorities and managing technology risks alongside the rest of the business.

At that point, the problem may not be the suppliers.

It may be a gap in technology leadership.

Recognising the Warning Signs

Ongoing leadership may be worth considering when:

  • Multiple suppliers regularly disagree about priorities or responsibilities.
  • Technology investments are considered separately rather than as part of a coherent roadmap.
  • The CEO or Managing Director spends excessive time resolving technology issues.
  • Important technical decisions are repeatedly delayed because nobody has sufficient authority or expertise.
  • Suppliers control most of the organisation’s technical knowledge and recommendations.
  • No senior person consistently monitors delivery, risk, technology costs and business alignment.

A Fractional CTO can provide experienced technology leadership without requiring the business to appoint a full-time CTO.

Depending on the engagement, that leadership may involve assessing recommendations, establishing decision processes, coordinating priorities, challenging assumptions and helping executives understand the implications of proposed investments.

Importantly, a Fractional CTO does not need to replace your existing developers, IT provider or other suppliers.

The objective is to help the organisation get more value from the people and capabilities it already has.

For businesses facing recurring technology decisions, independent Fractional CTO leadership in Brisbane can provide continuity across strategy, supplier relationships, governance and delivery.

The right arrangement depends on the organisation’s complexity and leadership needs. Some businesses will need a full-time technology executive. Others may be well served by their existing team.

Senior business leaders and a technology adviser discussing technology priorities and supplier accountability.
Independent Technology Leadership

Common Mistakes That Make Disputes Worse

There are several approaches I would avoid when suppliers disagree.

Choosing the Cheapest Proposal

Price matters, but competing proposals may include different assumptions, responsibilities and levels of risk.

Compare the full commercial consequences rather than selecting the lowest initial quote.

Trusting the Most Confident Supplier

A confident presentation is not evidence that the recommendation is correct.

Look for supporting information, clear assumptions and a willingness to discuss limitations.

Allowing Suppliers to Define the Goal

A supplier should help refine requirements, but the business needs to own the intended outcome.

Otherwise, the proposed solution may reflect what the supplier is best equipped to deliver rather than what the organisation needs.

Delaying Until Everyone Agrees

Complete technical agreement is not always realistic.

Leadership needs enough evidence to make a reasonable decision, understand the uncertainty and manage the remaining risks.

Waiting indefinitely can have its own costs.

Replacing Suppliers Too Quickly

A disagreement is not proof that a supplier is performing poorly.

Changing providers may introduce transition costs, knowledge loss, contractual complications and new operational risks.

Assess performance and responsibilities separately from the technical disagreement.

Ignoring Employees and Customers

A technically sound recommendation can still fail commercially if it creates unnecessary disruption or is poorly suited to how people work.

The people affected by the decision should help define requirements and evaluate likely consequences.

Technology should support the business, not force the business to organise itself around whatever technology a supplier prefers.

Frequently Asked Questions

What if IT Suppliers Still Disagree?

When you receive conflicting advice from IT suppliers, ask each provider to document its assumptions and supporting evidence. Compare the options against your business objectives and obtain an independent assessment if important uncertainty remains.

How Do I Know Which Supplier Is Right?

Start by checking whether the suppliers are solving the same problem. Then examine the evidence, expected outcomes, costs, dependencies and risks rather than relying on confidence or technical terminology.

Can We Resolve This Internally?

Yes, if your organisation has the expertise and authority to evaluate the options. An internal technology leader, supported by business and finance stakeholders, may be able to reach a defensible decision without external assistance.

Should We Get an Independent Review?

An independent review may be worthwhile when a decision involves substantial investment, critical systems or risks that leadership cannot confidently assess. It should help clarify a defined uncertainty rather than become an unnecessary additional layer of process.

Do We Need a Fractional CTO?

Not necessarily. A one-off disagreement may need only a focused review, while repeated uncertainty across suppliers and investments may indicate the need for ongoing technology leadership.

Making the Right Technology Decision

When suppliers disagree, the business needs a clear decision process, not simply another technical opinion. Start with the outcome you want, examine the evidence and establish who is accountable for the decision.

If conflicting recommendations are delaying an investment or creating ongoing uncertainty, I can help you assess the situation and determine whether independent review or continuing technology leadership would be useful. Book a free consultation to discuss the business problem and what needs to happen next.

You do not have to become a technology expert to make a sound decision when facing conflicting advice from IT suppliers.

Share This Post

Need stronger technology leadership?

Good technology leadership gives your business clearer direction, stronger accountability and better decisions.

If your technology team lacks direction, leadership responsibilities are unclear, or you need experienced support strengthening how technology is led, take a look at my Technology Leadership service or Contact Us to start the conversation.

Iain White Technology Leadership Adviser

Strong technology leadership is about more than technical knowledge. It means setting clear direction, making sound decisions and helping people do their best work. 

Iain White has spent decades leading technology teams, supporting technology leaders and helping businesses improve how technology is managed.

He works with founders, executives, CTOs and technology managers to clarify responsibilities, strengthen decision-making and improve accountability across technology teams.

His experience spans technology strategy, software delivery, governance, cybersecurity and risk, giving him a broad view of the challenges technology leaders face.

Through White Internet Consulting, Iain helps organisations build stronger technology leadership so their teams have the clarity, support and direction they need to deliver.