Experiences with Business Central consulting: how to recognise a viable partner

Star ratings say little about suitability for your project. More telling are patterns from practice: does the senior person stay at the wheel, are conflicts of goals discussed early, is the standard defended, and does the partner sometimes say no. You recognise these patterns in conversation, not in a portal.

Why do review portals mislead?

A good review arises disproportionately often on simple projects. It says nothing about whether a partner can carry your complex or endangered transformation, because there it is not friendliness that decides but judgement under pressure. Selecting on stars alone measures the wrong thing.

There is also a selection effect: satisfied customers of simple projects are happy to review, while customers of failed large programmes usually stay silent, because the project is contractually or politically sensitive. A partner's review distribution therefore says more about their project mix than about their substance.

More telling is how a partner actually works: senior-led, with one fixed person at the wheel who stays. No junior carousel in which your process knowledge is lost at every handover point and decisions already taken get rolled up again months later.

Which practical patterns does a solid partner show?

Honesty is the test. Ask about a project that was difficult, and listen to the structure of the answer. Whoever tells only success stories has either done nothing complex or is not being honest. Four patterns are recognisable during the proposal conversation.

• They name risks before the engagement, not only during the project.
• They defend the standard against expensive special paths.
• They document decisions traceably.
• They also say what they are not the right one for.

The fourth pattern is the rarest and the most telling. A partner with a clear niche can name it, and whoever accepts every enquiry has none, only pressure to fill capacity. On the third pattern, one concrete request is worth making: ask to see an anonymised decision log from a real project. Where decisions are recorded with their reasoning and the rejected alternative, you can steer later even when people change.

How do you use references properly?

Talk to reference customers about conflicting goals and rework, not only about the outcome. The useful questions are uncomfortable: what went differently than planned, how was it decided, and who carried the extra effort? That is exactly where you see how a partner steers under pressure and who ended up paying the bill.

It is also useful to ask about staffing: who was at the wheel, was it the same person until go-live, and how often did the team change? Answers to those are verifiable; statements of satisfaction are not.

Control on your side, with Business Central as home: a solid partner keeps you in control of scope and data rather than quietly taking it over. Would you rather experience than read how we work? Walk through your most difficult processes with us in a first conversation and test the four patterns directly on us.