+1 480 485 7373
Microsoft Teams
Why these Business Central case studies carry no client logos
Most mid-sized companies do not want their ERP project, stock problems or month-end struggles on a consultant's website. Many contracts rule it out entirely. A page of polished success stories also tends to hide what a buyer most needs to hear: what went sideways and how the team handled it.
So in place of named Business Central case studies, we describe patterns. If one of the project types below sounds like your company, say so on a call. We can then talk through comparable work in detail and, where a client has agreed, put you in touch with them directly.
Example project types in place of Business Central case studies
A distributor leaving QuickBooks
Starting problem: several people keep inventory in spreadsheets beside QuickBooks. Landed costs are guesses, and nobody trusts the stock value on the balance sheet.
- ✓The work: item and location setup, purchase and sales flows, costing method choice, opening balances and open orders moved across
- ✓Good outcome: one inventory figure that finance and the warehouse agree on, and orders picked from the system rather than from paper
A long-time Dynamics GP site facing end of support
Starting problem: GP has run the finance team for years, with add-ons and custom reports only one person understands. Microsoft has announced the end of support.
- ✓The work: map GP modules and third-party products to Business Central features, decide how much history to bring, rebuild the reports people actually use
- ✓Good outcome: a planned move on the company's own timetable instead of a rushed one, with the chart of accounts cleaned up on the way
A manufacturer running production on whiteboards
Starting problem: accounting software handles the books. Bills of materials, work orders and material planning live on whiteboards and in one planner's head.
- ✓The work: production BOMs and routings, planning parameters, shop floor output posting, and a costing approach finance signs off
- ✓Good outcome: purchasing driven by demand, finished goods costed consistently, and production status visible without a walk to the floor
A services firm billing from spreadsheets
Starting problem: time lives in one tool, expenses in another, and staff build invoices by hand. So billing runs late and nobody knows margins by project.
- ✓The work: jobs and job tasks, resource setup, time entry, work-in-progress rules and invoicing from the job
- ✓Good outcome: invoices out soon after period end and a margin report per project that managers look at every month
A stalled implementation handed over by another firm
Starting problem: go-live has slipped more than once and the budget is gone. The setup is half finished and the internal team has lost confidence.
- ✓The work: an honest review of setup, data and open promises, then a written plan for what to keep, fix or redo
- ✓Good outcome: a live system and a team that believes the numbers it produces, even if the original design had to change
How we share Business Central case detail with you
- 1
You describe your situation
On a first call we listen for which of these patterns fits, and where your business differs from it.
- 2
We talk through similar projects
A consultant explains what those engagements involved, where the risks were and what we learned. We name nobody who has not agreed.
- 3
References by permission
Once you are seriously weighing us, we ask a comparable client whether they are willing to speak with you, and connect you if they are.
- 4
You ask them anything
We do not sit in on reference calls. Ask them about delays, disagreements and support after go-live, the parts written Business Central case studies tend to skip.
Questions to put to any partner about past Business Central cases
- ✓Which project most like ours went badly, and what did you change afterwards?
- ✓Who from your side actually did the configuration and data work?
- ✓How much history did that client bring across, and do they regret the choice?
- ✓What did their first month end on the new system look like?
- ✓Which customizations did you talk them out of?
- ✓Can we speak to someone there without you on the call?
Can you share Business Central case references and results?
Why not publish named case studies?
Because most of our clients prefer to keep their systems and internal problems private. Publishing names without permission would break that trust, and chasing permission tends to produce only the flattering stories. Labeled project types stand in for Business Central case studies, so we can be honest without exposing anyone. Specific examples come out in conversation, where we can discuss the difficult parts too.
Can I speak to a past client before signing?
Yes, we arrange reference conversations on request during the sales process. We pick a client whose project resembles yours and ask whether they are willing to talk. If they agree, we introduce you and step out of the way. The call is between you and them.
Do you have results figures, like percentage savings?
We do not publish percentage claims, because firms rarely measure them the same way twice and outsiders cannot check them. What we can describe honestly is the kind of change a project aims for: faster close, trusted inventory, invoices out on time. On a call, we can discuss how a comparable client measured its own before and after. Treat any partner's headline percentages with care.
My situation does not match any of these examples. Can you still help?
Very likely, since these five patterns are common but far from the only work we do. Multi-company groups, Shopify sellers, field service teams and CRM rollouts all come through the door too. Describe your situation on a call and we will tell you plainly whether it is work we do well. If it is not, we will say that as well.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.