Is It Time to Look for a New Technology Partner?

Quick Summary

There are four reasons worth watching for: costs that keep creeping up, the people doing your work changing after you signed, being the last to find out about things that affect you, and a partner who never seems to have enough time for you. None of these on their own mean something has gone wrong. What matters is whether they’ve become the normal way things happen, not just something that happened once.

If it’s worth doing anything about, the first step is figuring out what kind of partner you actually need, not just swapping in a replacement for the one you have.

Has working with your technology partner started to feel like something you have to manage, rather than something you can rely on? If so, it’s worth paying attention to. Four reasons tend to show up: costs that keep growing, the people on your project changing, being kept in the dark about things that matter, and a partner who’s stretched too thin to help when you need them. None of these mean you’ve done anything wrong.

You Haven’t Done Anything Wrong

That’s worth saying at the start, because most people asking themselves this question are quietly wondering if they missed something.

Sometimes a partnership that starts out well simply stops keeping up. It’s rarely down to bad intentions, usually it just drifts. And it happens so gradually that you adjust without really noticing: you get used to slower replies, you start building extra room into your budget for the “surprise” that turns up every quarter, you quietly start handling things yourself instead of asking. None of it feels like a crisis while it’s happening. It just becomes the way things are.

Here are four things worth checking against your own experience, not as accusations, just as things worth being honest about.

Sign 1: Has Your Budget Kept Moving?

You were given a figure. Then the work began, and the figure didn’t hold. Sometimes there’s a fair reason for that: discovery work can turn up things nobody could reasonably have known about in advance, and a scope change with a clear explanation attached is a normal part of any Microsoft Dynamics 365 implementation project.

What’s worth watching for is different: it’s when “one more thing’s come up” stops being occasional and becomes how every single project with this partner goes. You find yourself padding your own budget before a project has even started, not because anyone told you to, but because you’ve learned to expect it.

Worth asking yourself: Looking back at your last two scope changes, were they things nobody could have predicted, or things a proper discovery process should have picked up the first time round?

Sign 2: Did Your Team Change After You Signed?

During the sales process, you met sharp, experienced people. They asked good questions, seemed to understand your business, and gave you real confidence in your decision. Then the actual work began, and the faces were different, sometimes more junior, sometimes less familiar with your setup than the people you thought you’d hired.

This isn’t automatically a problem. Businesses staff their projects in plenty of legitimate ways, and skilled people do excellent work without ever sitting in on a sales call. But it’s worth naming clearly, because it’s something a lot of people quietly notice and rarely mention out loud, partly because it can feel awkward to bring up. It isn’t. Continuity genuinely matters, particularly for something as specific to your business as your ERP system.

Worth asking yourself: Are the people actually doing your implementation work the same people, or at least the same calibre of people you met at the start?

Sign 3: Are You the Last to Know?

A good Microsoft partner tells you what’s coming before you have to ask. If you’ve more than once learned about something that directly affects your business, a Microsoft change, an end-of-support date, a feature that would have saved your team real time, from somewhere other than your own partner, that’s worth paying attention to.

Here’s a real example rather than a made-up one. Microsoft first announced Dynamics GP’s end of support in 2024 and later confirmed the specific date of 31 December 2029 in a follow-up update. That’s a couple of years of public notice by now, and yet businesses running Dynamics GP still regularly find out the actual timeline for the first time from a new partner, not from the one already supporting their system. Some of that responsibility sits with partners who should have raised it and didn’t. Some of it, fairly, sits with all of us for not always keeping track of what our own suppliers are saying publicly. Both can be true at once, and it’s worth being honest about which one actually applies to your situation.

Worth asking yourself: When something changes that affects your setup, do you usually hear about it from your partner first, or do you find out on your own?

Sign 4: Is Your Partner Stretched Too Thin?

Not every capacity problem comes from bad intentions. Plenty of smaller firms are genuinely good at what they do and simply don’t have enough people to keep up as your needs grow, or as several of their clients grow at once. That’s not a character flaw, it’s a mismatch between what you need now and what made sense when you first signed on, and mismatches like that are worth naming honestly rather than working around indefinitely.

This one can be the hardest to spot, because it usually shows up as a string of individually reasonable delays rather than one obvious failure. A slower reply here. A “let me check and get back to you” there. Each one seems fine on its own. It’s the pattern that actually matters.

Worth asking yourself: If you needed something urgently next week, do you know exactly who at this partner would handle it and whether they’d genuinely have the time?

Is This Normal Friction, or a Real Pattern?

It helps to separate ordinary bumps in the road from an actual signal.

None of the items in the left-hand column mean, on their own, that anything is genuinely wrong. The right-hand column, especially if more than one applies at once, is what’s actually worth acting on.

What to Do If You Recognise These Signs

Noticing one of these doesn’t mean the relationship is broken. Most partnerships go through a rough patch or two. The real question isn’t whether you’ve ever experienced one of these signs, it’s whether more than one of them has quietly become the norm rather than the exception.

If that sounds like where you are, the next step isn’t panic, it’s getting clearer on what to actually look for instead. It’s worth understanding the real difference between a reseller, a managed services provider, and a genuine trusted advisor, since knowing which one you need shapes everything else about your next move: Choosing a Technology Partner: VAR, MSP, or Trusted Advisor.

If you’re evaluating a partner for a specific move, such as a GP-to-Business-Central migration, there’s a detailed guide for exactly that: How to Evaluate a Microsoft Dynamics Partner: 10 Questions You Must Ask. And if what you’re actually after is an ongoing support relationship rather than a one-off project, here’s what to ask instead: Tips for Choosing Your Managed Services Partner.

Frequently Asked Questions

How do I know if my technology partner relationship is actually a problem, or just a rough patch?
A single bad month usually isn’t a real signal. A pattern is. If you can point to more than one of the four signs above happening repeatedly rather than once, it’s worth taking seriously.

Is it normal for project scope to change at all?
Yes, some scope change is normal, even healthy, as a project reveals more about your actual environment. What’s worth watching is whether changes consistently come with a clear explanation, or simply turn up as bigger invoices with no real context.

What if the issue is on our end, not the partner’s?
That happens too, and it’s worth being honest about. These patterns aren’t about assigning blame. They’re meant to help you tell the difference between a relationship that needs an honest conversation and one that genuinely needs to end.

Should we switch partners the first time we notice one of these signs?
Not necessarily. Most of these are worth raising directly with your current partner first. How they respond to that conversation often tells you more than the original issue did.

How disruptive is it to actually switch technology partners?
It depends on the kind of relationship you’re switching. An ongoing support relationship is usually a lighter change than an active, in-progress project. Either way, a genuinely good new partner should start with an honest look at where things actually stand, not a sales pitch.

How Nevas Technologies Can Help

If any of this sounds familiar, an honest second opinion is worth more than another sales conversation. Nevas Technologies has spent over 20 years supporting businesses running Microsoft Dynamics environments, with more than 200 clients and a team of certified Microsoft Dynamics consultants who start every new relationship with a genuine assessment of where things stand, not a pitch.

Schedule a free consultation with our Microsoft Dynamics team to talk through your current partner relationship, or get a custom quote if you’re ready to explore a change.