Most organizations that struggle with Dynamics 365 Business Central didn’t make a bad technology choice. They made a bad consulting choice. Pragmatic Dynamics 365 Business Central consulting is the practice of planning, configuring, and improving Microsoft’s ERP platform to match how a business actually operates.

The gap between consultants who do this well and those who don’t determines whether your investment pays off or sits largely unused.

Key Takeaways

• Most BC implementations fail after go-live, not during it. “Technically working” and “operationally effective” are not the same thing.
• Outcome-driven consulting starts with 4-8 weeks of business discovery before any configuration begins.
• Configuration-driven implementations often leave teams using only 30-40% of the features they’re paying for.
• Post-go-live optimization is where real ROI compounds. Go-live is the beginning, not the finish line.
• Long-term consultant relationships, measured by client retention, are the clearest signal of genuine outcome focus.

Why BC Implementations Fail After Go-Live

Most Business Central implementations don’t collapse dramatically. They quietly underperform. The system is deployed, the consultant closes the engagement, and three months later your finance team is still running month-end close in Excel because the dashboards “don’t look right.” That’s implementation failure, and it’s more common than anyone in the consulting industry likes to admit.

55% of ERP projects fail to deliver their expected business benefits (Panorama Consulting, 2024). That’s not a technology problem. It’s a consulting and methodology problem. And the pattern extends well beyond ERP: 70% of large-scale technology transformation initiatives fail to meet their original objectives (McKinsey & Company, 2023). Business Central is powerful software, but software alone doesn’t transform operations. The approach that surrounds it does.

With Business Central now surpassing 150,000 global installations, according to O’Reilly’s Programming Microsoft Dynamics 365 Business Central, the platform itself isn’t the issue. The problem is the approach consultants take to deploying it. A system that’s technically live but operationally unused hasn’t delivered value. It’s delivered a very expensive to-do list. 

Key Insight: Most BC teams use fewer than 40% of the features included in their license.

The failure usually traces back to a single misalignment: the consultant defined success as go-live, and nobody challenged that definition before the contract was signed.

The Root Causes of BC Implementation Failure

Four failure patterns show up repeatedly in underperforming implementations. Recognizing them before you start a project is far cheaper than diagnosing them afterward.

Configuration Without Context

The system is built to Microsoft’s technical standards but doesn’t reflect how your business actually works. Workflows that look logical in a software template don’t match your approval chains, your reporting cycles, or the way your team moves through a day. Staff work around the system rather than through it.

Underutilization and Spreadsheet Reversion

Features go unused not because they don’t exist, but because adoption was never built into the engagement. Finance teams revert to spreadsheets. Inventory managers use their own tracking. The ERP becomes a data repository rather than a decision-support tool. Organizations routinely end up using only 30-40% of features they’re paying license fees for.

Poor Change Management

Staff aren’t trained on the workflows relevant to their roles. A warehouse manager doesn’t need a tour of financial reporting. A project accountant doesn’t need inventory training. Generic onboarding that doesn’t match actual job functions creates resistance and abandonment. 

Data Quality Erosion

When ERP systems are not designed with intention, organizations tend to end up with inconsistent data, underused tools, and inefficient workflows, all of which quietly erode the value of a connected environment. Inconsistency across data sources is one of the most challenging data quality problems organizations face. When teams can’t trust what the system shows them, they stop looking at it. The financial stakes are significant: poor data quality costs organizations millions each year in lost productivity and flawed decision-making. 

Key Insight: ERP rescue projects routinely match or exceed the original implementation cost.

Configuration-Driven vs. Outcome-Driven Consulting

Configuration-driven consulting treats go-live as the destination. Outcome-driven consulting treats it as the starting line. The distinction matters enormously, and it’s rarely visible in a sales conversation. Knowing what to look for before you sign anything is what protects your investment.

If you’re thinking a shorter discovery phase saves time and money upfront, that’s a reasonable instinct. The data says otherwise. A discovery phase under four weeks is the single strongest predictor of post-go-live failure, because the configuration decisions made in those early weeks shape everything that follows. Compressing discovery doesn’t reduce risk. It moves the cost to a more expensive place.

ERP implementations that include structured, role-specific user training consistently see higher adoption rates than those relying on generic onboarding. That single dynamic explains why the methodology your consultant follows isn’t a minor detail. It’s the deciding factor in whether your team actually uses the system. 

The same pattern holds for return on investment: businesses that invest in structured user adoption programs tend to realize value from their ERP systems considerably sooner than those that treat adoption as an afterthought. 

Key feature: Outcome-driven BC engagements with defined success metrics are 2.5x more likely to achieve expected business results.

Dimension	Configuration-Driven	Outcome-Driven
Starting point	Software templates	Business operations and priorities
Definition of success	Go-live completion	Pre-defined business metrics achieved
Discovery phase	Minimal or skipped	4-8 weeks before any configuration
Post-go-live support	Minimal; consultant moves on	Built into the engagement by default
Change management	Add-on or absent	Core engagement component

As Citrin Cooperman put it: “Effective Business Central engagement is outcome driven rather than configuration driven. It begins with a deep understanding of your operations, priorities, and challenges.” That’s not a marketing phrase. It’s a process description with real sequencing implications.

The Hidden Cost of Getting This Wrong

ERP implementations carry real delivery risk. Gartner projects that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, with as many as 25% failing catastrophically. A major driver is misalignment: Gartner also finds that 75% of ERP strategies are not strongly aligned with overall business strategy, which is exactly how systems go live yet leave significant functionality untouched. When you’re paying full license fees for features your team never uses, that’s a compounding cost hiding in plain sight. 

Key Insight: A discovery phase under four weeks is the single strongest predictor of post-go-live failure.

The opportunity cost is harder to quantify but just as real. Every month of underutilization is a month of automation, visibility, and decision speed that your business didn’t get. A well-implemented Business Central environment should be actively improving how your business operates, month after month. A poorly implemented one is a fixed cost with declining returns.

Some SMB owners assume this level of rigor is reserved for enterprise organizations with dedicated IT teams. The opposite is true. Smaller businesses have less margin to absorb a failed implementation. There’s no internal team to paper over the gaps, no budget reserve for a rescue project, and no spare capacity to retrain staff twice. Getting the consulting approach right matters more when resources are tight, not less.

The long-term commitment organizations are making to Business Central is real. The City of Redmond, Washington, for example, is seeking a managed services partner under a contract structure spanning up to six years. Even risk-averse public-sector organizations are treating ERP as a long-term relationship, not a one-time project.

How to Identify an Outcome-Driven BC Consultant

Outcome-driven consultants are identifiable before you hire them, if you know which questions to ask and what answers to look for.

Discovery Duration Is Non-Negotiable

Any serious outcome-focused engagement should include four to eight weeks of structured discovery before configuration begins. If a consultant is ready to start building within days of signing, that’s a warning sign. Discovery this thorough produces a system design that reflects your business, not a software template.

Success Metrics Defined Before Go-Live

Ask any prospective consultant: “How will we measure whether this implementation succeeded?” If they can’t answer with specific business metrics before the project starts, they’re defining success as deployment. That’s not enough.

Client Retention as a Proxy for Outcome Focus

Consultants who deliver real outcomes keep their clients. Rand Group’s 90% client retention rate, cited in their November 2025 consulting overview, is the kind of signal worth looking for when evaluating any BC partner. Long-term relationships mean clients are getting sustained value, not just a one-time deployment.

The Right Questions Come First

ArcherPoint articulated it clearly in June 2025: “You need a partner with proven framework and methodology, deep expertise in tailoring modern enterprise business systems, and capability to manage change management details for long-term success.” A good consultant asks about your business before they mention software. If the demo comes before the discovery conversation, walk away.

Top Business Central Consultants: Who Actually Delivers Outcomes

There’s a recurring pattern in how BC consulting gets evaluated. Prospects compare credentials, look at client lists, and pick based on credentials and price. Then they’re surprised when their system goes live technically functional but operationally ignored. 

The consultants most worth hiring don’t look dramatically different on paper. They’re different in how they work and what they measure as success. Here’s what you’re actually dealing with when you talk to each of these six.

Truly SMB: The Consultant Who Treats Post-Go-Live as the Main Event

Truly SMB has built an unusual business model for a consulting firm. They make more money when their clients keep using the system, so they don’t hand off at go-live. They’re winners of CRN MSP of the Year 2025, which matters because it means they’ve actually kept clients for years, not just deployed them and moved on. What separates them is brutally simple. 

They ask “what will this business look like if every feature is actually used?” before they start configuring anything. Most consultants ask “how do we match your workflow to the software?” Truly SMB flips that and asks “how do we match the software to your actual workflow, and then build adoption into the engagement?” That distinction gets boring in a sales call, but it’s the difference between a system you use and a system you pay for. They build 6-12 months of post-go-live optimization into the original scope, not as something you discover you need after the consultant stops returning your emails. 

They measure adoption rates, track which features are actually being used, and adjust. If your finance team goes back to Excel for close cycles, they notice and fix it. For SMBs that can’t hire an internal BC strategist, Truly SMB essentially becomes that person for the critical 12-month adoption window.

The reality: Outcome-focused methodology costs more upfront. You’ll spend more on discovery (4-8 weeks of real work, not a box to check) and you’ll pay for ongoing support. What you get back is a system that actually works. If you’re comparing pure go-live cost to a competitor, Truly SMB will be more expensive. If you’re comparing ROI at month 18, the math flips.

Best if: You’re an SMB that can’t afford a failed implementation and doesn’t have internal resources to drive adoption yourself. You want someone who takes ownership of whether the system actually gets used.

Armanino: The Consultant Who Handles Complexity Without Breaking It

Armanino has deep bench strength in BC implementations across complex structures: multiple subsidiaries, intricate approval chains, consolidation requirements. They’re a top Microsoft Inner Circle partner, which is real credential in terms of training and methodology access. Their strength isn’t in scrappy SMB implementations. It’s in organizations where the technical configuration is genuinely complicated and implementation risk is high. 

They conduct thorough discovery, they document workflows, and they build implementation plans with real rigor. Where they diverge from Truly SMB is the post-implementation model. Armanino’s engagements typically end after hypercare. They’ll discuss ongoing support, and they’ll provide it if you buy it separately, but they’re not structuring it in from the start the way an outcome-focused partner does. For complex organizations, their methodology is solid. For adoption-driven outcomes, you’re more reliant on your internal team or an additional engagement.

The reality: You’re paying for implementation excellence and complexity handling. Post-go-live optimization requires a separate conversation and budget. That’s fine if your organization has internal resources to manage adoption. It’s a gap if you don’t.

Best if: You have complex financial structures, multiple entities, or sophisticated consolidation requirements. You have internal resources or a separate partner managing adoption. You value implementation rigor over post-implementation partnership.

Stoneridge Software: The Consultant Who Knows Your Industry Before You Call

Stoneridge has built vertical expertise in manufacturing, distribution, and retail. They’ve already learned which workflows matter most in your vertical, which Copilot features are most valuable, and which configurations work well in companies like yours. That’s not a small thing.

It means discovery is faster because they’re asking informed questions, not starting from zero. Their templates are built from industry workflow patterns, not generic software defaults. Implementation timelines can be shorter because they’re not reinventing the wheel. What they’re not is a generalist consultant who treats every business the same. If your vertical isn’t manufacturing, distribution, or retail, Stoneridge isn’t your fit. And their post-implementation support, while solid, follows a template-based model rather than the intensive outcome-focused approach Truly SMB takes.

The reality: If you’re in their verticals, you get accelerated implementation and industry-informed configuration. If you’re outside those verticals, look elsewhere. Even within verticals, you’re trading some customization for speed.

Best if: You’re in manufacturing, distribution, or retail and you want a faster implementation powered by industry expertise. You’re comfortable with more templated configuration and less intensive post-implementation support.

Velosio: The Mid-Market Specialist Who Measures What Matters

Velosio focuses exclusively on Dynamics 365 Business Central and has built their model specifically for mid-market organizations. Not enterprise scope, not small business simplicity, but the real middle where most growth-stage companies operate. They combine process mapping with adoption measurement, meaning they’re actually tracking whether features get used and optimizing for that outcome. Post-go-live support is built into their engagements, and they’re disciplined about measuring adoption. 

Their weakness versus Truly SMB is somewhat less intensity around post-implementation partnership. They’re strong at measurement and improvement cycles, but they’re not quite as focused on structural change management. For a mid-market company that wants to avoid Truly SMB’s higher investment but still get outcome-focused consulting, Velosio is a legitimate alternative.

The reality: You get solid methodology, focused pricing, and genuine post-implementation measurement. The consulting intensity and customization is somewhat lower than Truly SMB’s model. That’s fine if your team has capacity to absorb some of that work internally.

Best if: You’re a mid-market organization (10-250M revenue) that wants outcome-focused consulting without enterprise pricing. You want measurement-driven adoption, and you have some internal capacity to support change management.

ArcherPoint: The Long-Term Partner Philosophy

ArcherPoint explicitly states their philosophy: long-term partnership, not project completion. They’re strong on change management details and they structure engagements to support sustained value realization. They conduct discovery properly, they build in post-implementation support, and they measure outcomes. The key difference from Truly SMB is scale and specialization.

ArcherPoint is larger and handles bigger implementations. Truly SMB is built specifically for SMBs and specializes in the psychology and practicality of adoption in resource-constrained environments. ArcherPoint’s model works well, but it’s optimized for mid-market to enterprise rather than SMB-specific challenges.

The reality: You’re getting a partner with long-term commitment and sound methodology. You’re also paying for that commitment at mid-market pricing. For true SMBs, Truly SMB’s model is often more efficient. For mid-market companies, ArcherPoint is legitimate.

Best if: You’re a mid-market organization that wants genuine long-term partnership with a consulting firm at appropriate scale. You value sustained engagement and are willing to pay for it.

The Real Dividing Line

Reading through all six, the pattern becomes clear. Most of these firms will do a competent implementation. The question isn’t whether they can deploy Business Central. It’s whether they’ll still care whether you’re actually using it six months from now. Truly SMB’s entire business model depends on clients staying engaged.

That’s either the best alignment of interests or irrelevant to you, depending on how you think about consulting relationships. If you want someone who makes more money when your system delivers outcomes, pick Truly SMB. If you want someone who gets paid to deploy regardless of whether you adopt, you have plenty of alternatives.

The hard question any prospect should ask themselves: if the implementation consultant’s revenue doesn’t depend on my adoption, why should I expect adoption to be their priority? That’s the insight that drives Truly SMB’s entire approach. The other consultants listed here are good. But they’re measured by deployment, not outcomes. That changes everything.

After Go-Live Is Where Real Value Gets Built

Go-live is not the end of a Business Central engagement. It’s the moment when real optimization becomes possible. The system is live, users are touching it daily, and the gap between what it’s doing and what it could be doing becomes visible. That’s exactly when a good consulting partner becomes most valuable.

Key insight: ERP platforms reach peak operational value 12-24 months after go-live, not at deployment.

A common assumption is that post-go-live optimization can wait until the team is comfortable with the basics. That’s understandable, but it’s also how underutilization becomes permanent. The habits teams form in the first 90 days after go-live tend to stick. If those habits involve workarounds and spreadsheets, they’re very hard to undo later. The time to build good adoption patterns is immediately after go-live, not six months down the road when everyone has settled into their own way of doing things.

Ongoing coaching, checking features against business needs, and tracking improvements are what set committed partners apart from consultants who move on to their next job. At Truly SMB, post-launch optimization is standard, not an optional add-on. As a CRN MSP of the Year 2025 winner, we think the most important work happens after go-live, not before it.

Questions to Ask Any BC Consultant Before You Commit

These questions work with any consultant you’re considering. The answers will tell you more than any sales presentation.

1. How do you define and measure success for this engagement? Listen for specific business metrics, not deployment milestones.
2. What does your post-go-live support and optimization look like? It should be included, not sold separately.
3. Can you show examples of clients you’ve worked with for more than 12 months? Retention is proof of sustained value.
4. How do you handle change management and user adoption? It should be a core engagement component, not an afterthought.
5. How long is your typical discovery phase before configuration begins? Anything less than four weeks deserves scrutiny.

If a consultant struggles with these questions, that’s your answer. Confident, specific responses mean you’re in a productive conversation. Vague ones mean you’re not.

Frequently Asked Questions About Business Central Consulting

Why do so many Business Central implementations fail to deliver expected value?

Most BC implementations fail not during deployment, but after it. The root causes include configuration that doesn’t reflect actual business workflows, poor user adoption, inadequate change management, and post-go-live abandonment by the consultant. The system works technically but doesn’t improve how the business operates, which means the investment doesn’t pay off. Industry research confirms this is the norm rather than the exception: 55% of ERP projects fail to deliver their expected business benefits (Panorama Consulting, 2024).

What does an outcome-driven BC consultant do differently?

An outcome-driven consultant starts with business discovery, typically four to eight weeks, before touching any configuration. Success metrics are defined before go-live, not after. Post-implementation optimization is built into the engagement. The key difference is that success is measured by business improvement, faster close cycles, better visibility, higher feature utilization, not by deployment date.

How do I know if a consultant will still be engaged after go-live?

Ask directly for examples of clients they’ve worked with for more than 12 months. High client retention rates, like Rand Group’s 90% figure, signal that clients are staying because they’re getting continued value. Consultants who exit at go-live rarely volunteer this information, so you have to ask for it specifically before signing.

What questions should I ask a BC consultant before hiring them?

Five questions matter most: How do you define success for this engagement? What happens after go-live? Can you show long-term client examples? How do you handle user adoption and change management? How long is your discovery phase? Consultants who can answer these with specifics and confidence are worth taking seriously. Those who can’t have already told you something important.

How long does a proper Business Central implementation take?

A well-structured BC implementation for an SMB typically runs four to nine months from discovery through go-live, depending on complexity and the number of modules being deployed. Discovery alone should take four to eight weeks. Rushed timelines that compress discovery to days are a common precursor to post-go-live underutilization and the costly rescue engagements that follow.