How to Choose a CRM Partner: 7 Questions to Ask (Including the Awkward Ones)

There’s an obvious problem with a CRM partner writing about how to choose a CRM partner: we’d like you to choose us.

So let me be straight about the bias and then be useful anyway. What follows is how I’d tell a friend to evaluate any Dynamics 365 partner – including the questions I’d least enjoy being asked. If we come out well against them, good. If another partner suits you better, you’ll have found that out before signing rather than eighteen months in, which is when most people discover it.

Because the uncomfortable truth of this market is that the partner decision matters more than the platform decision. Dynamics 365 is capable software. Most failed CRM projects run on capable software. What separates the projects that work from the ones that quietly die is almost always who implemented them and what happened afterwards.

Why the partner matters more than the product

Choose the wrong CRM and you’ll know within months – the fit is wrong, the gaps are visible, you deal with it.

Choose the wrong partner and you won’t find out for a year or more. The system will be delivered, on time, exactly as specified. And it will change nothing, because nobody ever challenged whether the specification made sense. That’s the failure mode nobody warns you about: not a project that collapses, but one that succeeds on paper and delivers nothing in practice.

A good partner is not an order-taker. They’re the party in the room with the pattern recognition – the one who’s seen this go wrong before and says so.

The seven questions

1. Do they want to understand your business, or sell you a product?

Watch what happens in the first conversation. Do they ask about your culture, your customers, your competitors, your actual pain – or do they get to a demo as fast as possible?

Technology is the enabler, not the direction. A partner who reaches for the product before understanding the problem will sell you something that works perfectly and solves nothing.

What to ask: “What do you need to understand about us before you could tell us what we need?” The answer reveals whether they’ve got a process or a pitch.

2. Will they challenge you – or just agree?

This is the one that separates the good from the merely competent. You want a partner who keeps asking why.

Why does that approval step exist? Why does that data get re-keyed? Why does it work that way – because it’s right, or because it’s always been that way? A partner who takes your requirements at face value will faithfully automate your existing inefficiencies at considerable expense.

Agreement is comfortable. It’s also how you end up paying to preserve your worst habits in more expensive software.

What to ask: “Tell me about a time you told a client they were wrong.” If they can’t, either they don’t, or they won’t tell you.

3. What happens after go-live?

Go-live is where most partners’ interest ends and where your CRM’s life actually begins.

Ask about aftercare specifically, because this is where the difference between a relationship and a transaction shows. A partner invested in the long term wants the system to keep working – they’ll still be improving it in year three. A partner out for the project fee is already looking at the next deal.

The signal to look for: clients who speak well of the support they got *long after* the project finished. Anyone can be attentive during implementation.

What to ask: “Who will I be talking to in eighteen months, and what will that conversation be about?”

4. Is their experience relevant to you?

Experience isn’t fungible. A partner with a hundred implementations in retail may know very little about the constraints you operate under.

Sector experience matters not because your business is unique – it probably isn’t – but because a partner who knows your world can tell you what usually goes wrong before it does. That’s the value you’re buying: not implementation labour, but foresight.

What to ask: “Show me work you’ve done for a business like ours, and tell me what surprised you.”

5. Can they cover the whole picture?

CRM rarely stays neatly inside CRM. It touches integration, data migration, reporting, adoption, sometimes AI. A partner with a narrow specialism will hand you off, or improvise, at exactly the point the project gets difficult.

You’re looking for genuine breadth – and honesty about the edges of it. “We’d bring in a specialist for that” is a perfectly good answer. “We can do everything” usually isn’t.

What to ask: “What part of this project are you least well suited to?”*

6. Are they keeping up?

Microsoft ships change constantly, and the pace has accelerated sharply with Copilot and agentic AI. A partner running on 2019 knowledge will build you a 2019 system.

But be careful of the opposite failure too: partners who’ll sell you AI you don’t need because it’s what’s selling. The right answer to “should we add AI?” is often “not yet – fix your data first.” A partner who says that is telling you something valuable about themselves.

What to ask: “What’s changed in Dynamics 365 in the last six months that would affect us?”*

7. Can you leave?

Read the contract for the exit, not the entry.

Some partners build systems in ways that make them hard to hand over, or hold contractual rights over parts of the development. It’s not always malicious – sometimes it’s just how they work – but the effect is the same: you’re locked in, and the relationship stops being one you choose to continue.

A confident partner has no need to trap you. They expect you to stay because leaving would be a bad idea, not because it’s impossible.

What to ask: “If we wanted to part ways in two years, what exactly would we own, and how would handover work?” Watch how comfortable they are with the question.

One more signal: is their own house in order?

A quieter test, and a revealing one. A partner whose own business is chaotic – slow to respond, disorganised, opaque about their own processes – will not somehow become organised while running your project.

How they handle you during the sales process is the best available preview of how they’ll handle you as a client. It’s the only sample you get before committing. Take it seriously.

What good looks like, briefly

A CRM partner worth having will understand your business before proposing anything, challenge your assumptions rather than nodding along, care about what happens after go-live, bring relevant experience, be honest about their limits, keep current without chasing hype, and let you leave freely.

That’s a demanding list. It should be. You’re not buying software – you’re choosing who’s going to reshape how your business handles its customers.

If you’ve already chosen the wrong one

Plenty of people reading this are not choosing a first partner – they’re wondering whether to change an existing one, or picking up the pieces of an implementation that didn’t work.

That’s a recoverable position, and usually without replacing the platform. Most struggling Dynamics 365 projects are fixable: the causes are typically strategy, data and adoption rather than software. It’s worth reading [why CRM implementations fail](/posts/why-do-crm-implementations-fail-2/) before concluding you need to start again – the same mistakes tend to repeat with a new system unless the underlying causes are addressed.

Frequently asked questions

What should I look for in a CRM partner?

Look for a partner who understands your business before proposing a product, challenges your assumptions rather than accepting requirements at face value, has relevant sector experience, is committed to support after go-live, keeps current with the platform, is honest about their limits, and doesn’t lock you in contractually.

Why does industry experience matter when choosing a CRM partner?

Because a partner who knows your sector can anticipate what usually goes wrong before it does. You’re buying foresight rather than implementation labour – and foresight only comes from having seen similar businesses hit similar problems.

Is the CRM partner more important than the CRM platform?

Usually, yes. Most modern CRM platforms are capable, and most failed CRM projects run on capable software. The partner determines whether the system fits how your business actually works – which is what decides success or failure.

How do I compare Dynamics 365 partners?

Ask all of them the same seven questions above, and pay attention to who’s comfortable with the awkward ones – particularly around challenging clients, admitting limits, and contractual exit. Ask for sector-relevant references and speak to clients who finished their projects years ago, not months.

What if our CRM partner isn’t working out?

You’re not necessarily stuck. Check what your contract says about ownership and exit, then get an independent assessment of the system itself – the platform is often fine even when the relationship isn’t. Switching partners is usually cheaper and less disruptive than switching platforms.

Talk to us – or don’t

If the seven questions above are useful and you go and ask them of someone else, that’s a good outcome. A well-chosen partner makes the whole industry look better, including us.

But if you’d like to ask them of QGate, we’d welcome it – including the awkward ones. We’ve been implementing Dynamics 365 for UK businesses long enough to have opinions worth challenging, and clients who’ve stayed long enough to prove the aftercare point.

→ Learn about our CRM deployment and strategy approach or book a discovery call and put the questions to us directly.