Is your relationship with your technology partner starting to feel like something you manage instead of something you can depend on?
TL;DR: If your technology partner relationship has started to feel like something you manage instead of something that helps you, that's worth paying attention to. Scope creep, staffing switches, silence on things that matter, and capacity gaps are the four patterns worth watching for. None of them mean you did anything wrong.
Key Takeaways
- Scope creep, staffing switches, being the last to know, and capacity gaps are the four patterns worth watching.
- None of them, on their own, mean something is broken.
- What matters is whether they're becoming the norm rather than the exception, not whether you've ever experienced one.
- The right next step is understanding what kind of partner you actually need, not just finding a replacement for the one you have.
Is It Time to Look for a New Technology Partner?
You didn't do anything wrong. That's worth saying up front, because most people who end up here are quietly wondering if they missed something.
Sometimes a partner relationship that started fine just doesn't keep pace. Not through malice, usually. Through drift. It happens gradually enough that you adjust to it before you notice you've adjusted, working around a slow response time, budgeting extra for the "surprise" that shows up every quarter, learning to just handle certain things yourself. None of that feels like a crisis in the moment. It just quietly becomes normal.
Here are four patterns worth knowing, not as accusations, but as things worth checking against your own experience.
Sign 1: Has Your Budget Kept Moving?
You got a number. Then the project started, and the number didn't hold. Maybe there was a good reason the first time. A discovery process turns up things nobody could have predicted, and a scope change that follows a clear explanation is a completely normal part of implementation work.
The pattern worth watching for is different. It's when "one more thing came up" stops being an occasional line item and starts being how every engagement with this partner goes. You start padding your own budget expectations before a project even begins, not because you've been told to, but because you've learned to.
Worth asking: Looking back at the last two changes to scope, were they things nobody could have predicted, or things a more thorough discovery process would have caught the first time?
Sign 2: Did Your Team Change After You Signed?
You met sharp, experienced people during the sales process. They asked good questions, understood your business, and gave you confidence in the decision. Then the actual work started, and the faces were different, sometimes offshore, sometimes junior, sometimes just less familiar with your environment than the people you thought you'd hired.
This isn't automatically a problem. Firms staff projects in all kinds of legitimate ways, and plenty of talented people do excellent work without ever sitting in on a sales call. But it's worth naming plainly, because it's a pattern a lot of people notice and rarely say out loud, partly because it's hard to raise without sounding petty. It isn't petty. Continuity matters, especially for something as specific as your ERP environment.
Worth asking: Are the people doing your actual implementation work the same people, or at minimum the same caliber of people, you met at the start?
Sign 3: Are You the Last to Know?
A good partner tells you what's coming before you have to ask. If you've had more than one moment of finding out about something that affects your business, a Microsoft change, an end-of-life date, a feature that would have saved your team hours, from somewhere other than your own partner, that's worth noticing.
We'll use a live, real example rather than a hypothetical one. Microsoft first announced Dynamics GP's end of support in September 2024, and confirmed the December 31, 2029 date in an update the following January. That's coming up on two years of public messaging at this point, yet we still regularly talk to GP customers hearing about the timeline for the
first time from us, not from their existing partner. Some of that responsibility sits with partners who should have raised it directly and didn't. Some of it, fairly, sits with all of us for not paying closer attention to what our own vendors have been saying publicly. Both things can be true at once, and it's worth being honest about which one actually describes your situation.
Worth asking: When something changes that affects my environment, do I hear about it from my partner first, or do I find it myself?
Sign 4: Is Your Partner Stretched Too Thin?
Not every capacity issue comes from bad intent. Plenty of smaller firms are genuinely good at what they do and just don't have the bench 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 signed on, and mismatches are worth naming honestly rather than working around indefinitely.
This one can be the hardest to spot because it often shows up as a series of individually reasonable delays rather than one clear failure. A slower response here, a "let me check on that" there. Each instance seems fine. The pattern is what matters.
Worth asking: If I needed something urgently next week, do I know, specifically, who at this partner would handle it, and whether they'd actually have the time?
Is This Normal Friction or a Real Pattern?
It helps to separate ordinary bumps from an actual signal. Here's a quick way to sort what you're experiencing.
|
Area |
Normal Friction |
Worth Watching |
|
Budget |
A single, well-explained scope change |
Scope creep has become the norm, not the exception |
|
Staffing |
One team adjustment, communicated in advance |
The people doing the work consistently aren't the people you met |
|
Communication |
You occasionally hear about a change a little late |
You're consistently the last to know, or find out on your own |
|
Capacity |
An isolated slow response during a busy stretch |
A recurring "who do I even call for this" feeling |
None of the left column, on its own, means anything is wrong. The right column, especially more than one of them at once, is what's actually worth acting on.
What to Do If You Recognize These Signs
Noticing one of these doesn't mean the relationship is broken. Most partnerships have a rough patch or two. The real question isn't whether you've ever experienced one of these, it's whether more than one has become the norm rather than the exception.
If that's where you are, the next step isn't panic, it's a clearer sense of what to look for instead. If you haven't already, it's worth understanding the difference between a reseller, a managed services provider, and a genuine trusted partner, since knowing which one you actually need shapes everything else: Choosing a Tech Partner: VAR, MSP, or Trusted Advisor.
From there, if you're evaluating a partner for a specific move, like a GP to Business Central migration, we've got a guide for that: How to Evaluate a Microsoft Dynamics Partner. If it's an ongoing support relationship you need instead of a project, here's what to ask: Tips for Choosing Your Managed Services Partner.
FAQ
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 signal. A pattern is. If you can point to more than one of the four signs above happening repeatedly rather than once, that's worth treating as real.
Is it normal for project scope to change at all?
Yes, some scope change is normal and even healthy as a project reveals more about your environment. What's worth watching is whether changes come with a clear explanation or just show up as bigger invoices.
What if the issue is our fault, not the partner's?
That happens too, and it's worth being honest about. The point of these patterns isn't to assign blame, it's to help you tell the difference between a relationship that needs a conversation and one that 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 switch technology partners?
It depends on what kind of relationship you're switching. Ongoing support is usually a lighter lift than an active project. Either way, a good next partner will start with an honest assessment of where things stand, not a sales pitch.
If any of this sounds familiar and you want an honest second opinion, let's talk.