Choosing a technology partner is difficult for a simple reason: the weaknesses in the relationship often become obvious only after the contract is signed.
Sales processes show suppliers at their best. Presentations are polished and senior specialists appear in meetings. The harder question is what working together will look like six months later, when there is an incident or a deadline is slipping.
No selection process can remove that uncertainty completely, but there are warning signs worth noticing before committing.
1. Every answer is yes
A prospective partner that agrees with everything can feel easy to work with. It can also be a problem.
Organisations usually bring in external expertise because they want knowledge they do not have internally or additional experience around a difficult piece of work. That expertise has limited value if the supplier is unwilling to challenge assumptions.
A good partner should be able to explain when a proposed approach creates unnecessary risk, cost or complexity. That does not mean turning every meeting into an argument. It means being prepared to say, with evidence, that there may be a better route.
If every request is immediately described as straightforward, it is worth asking whether the supplier is listening critically or simply trying to win the work.
2. The experts disappear after the sales process
Most buyers have encountered some version of this problem.
The people involved before signature are impressive. They understand the technology, ask intelligent questions and seem to grasp the business quickly. Once the project begins, an entirely different team appears.
There is nothing unusual about sales specialists handing work to delivery teams. The issue is whether the buyer has had enough opportunity to assess the people who will actually deliver the service.
Ask who will be responsible day to day, what their experience is and how much of their time is allocated. If those questions are difficult to answer before the contract is signed, they are unlikely to become easier afterwards.
3. Recommendations arrive before discovery
Technology firms build expertise by solving similar problems repeatedly, so it is reasonable for them to have preferred approaches.
It is less reassuring when they recommend a detailed solution before understanding the environment.
Good discovery can uncover application dependencies, security constraints, licensing issues, internal skills and business processes that materially change the right answer. A proposal produced without that context may be based more on what the supplier prefers to sell than what the organisation needs.
Early conversations should therefore contain plenty of questions. A partner that spends more time explaining its solution than understanding the problem may have started in the wrong place.
4. Credentials are used as a substitute for evidence
Certifications, vendor relationships and formal designations can all provide useful signals of capability. They should not end the evaluation.
Buyers still need to understand whether the supplier has delivered comparable work and whether the relevant experience exists within the team assigned to them.
This is particularly important in large technology ecosystems where the same vendor name can cover cloud infrastructure, security, data, productivity software and business applications. Being capable in one area does not automatically imply equal depth in another.
For example, organisations comparing Microsoft partners should look at the specific areas in which each partner has proven expertise, rather than treating a broad vendor relationship as proof that every specialism is covered.
5. Nobody can explain what happens when things go wrong
Happy-path delivery is easy to describe. The more revealing conversation is about failure.
What happens if a migration overruns? How are serious incidents escalated? Who makes decisions when the original plan no longer works? How quickly can senior technical expertise be brought into a problem?
A mature partner should have clear answers because difficult situations are part of technology delivery.
Vague escalation arrangements can leave clients navigating account managers and support queues at exactly the moment they need decisive technical ownership.
6. The proposal depends on vague outcomes
Terms such as transformation, optimisation and innovation appear frequently in technology proposals. They sound positive but can hide a lack of measurable objectives.
Both sides should understand what success means.
For a project, that might involve migration milestones, performance requirements or adoption targets. For an ongoing service, it could include response expectations, security improvements or reductions in recurring incidents.
Not everything valuable can be reduced to a metric, but a relationship without clear outcomes becomes difficult to evaluate. The supplier can point to completed activity while the customer wonders why nothing feels better.
7. The contract makes change unnecessarily difficult
Technology requirements rarely remain static for the full length of a commercial agreement.
The organisation may acquire another business, adopt new software, change its security model or bring some capabilities back in-house. A useful partnership needs enough flexibility to respond.
That does not mean contracts should have no commitments. Suppliers need commercial predictability too. But buyers should understand how services can be changed, how pricing responds and what happens if the relationship eventually ends.
Exit arrangements deserve particular attention. Access to documentation, configurations, data and operational knowledge should not become a negotiation after the decision to move supplier has already been made.
A good partner should become easier to work with over time
The best technology relationships accumulate useful context.
The supplier learns the environment, understands the organisation’s appetite for risk and knows which internal teams need to be involved in particular decisions. The customer, in turn, learns where the partner is strongest and when to involve it.
That familiarity can make delivery faster and better, but only when the foundations are sound.
Technical credentials matter. So do commercial terms. Yet the less tangible behaviours often determine whether a partnership becomes valuable: curiosity, transparency, willingness to challenge, clear ownership and the ability to deal sensibly with problems.
Those qualities are harder to fit into a procurement scorecard. They are also worth looking for before the polished presentations end and the real work begins.