ERP projects gone right · Business Central · Intercompany · SMB · 2026-07-13

Intercompany without inventing a holding-company cult

Microsoft ecosystem illustration
Infographic summary for this ERP case study

Winner stack: Dynamics 365 Business Central · Small group companies · Twin Cities

I am not an ERP romantic. I am the person who asks where the number comes from until someone gets annoyed. This project survived that habit.

Legal entities were real; the books treated them like optional suggestions. That is the unclean version. I am not polishing the scars off.

The mess (specific, slightly embarrassing)

A small group companies team in Twin Cities got an ERP project over the finish line with Dynamics 365 Business Central — not because the software was magic, but because ownership, data, and a thin pilot finally aligned.

Legal entities were real; the books treated them like optional suggestions. Close was performance art.

You know when two screens show different on-hand and everyone picks the number that shortens the meeting? Yeah. River kept a private tracker because trust was optional.

Do not get me started on we will clean master data later as a strategy. (I said what I said.)

Why Dynamics 365 Business Central won

They were already paying the Microsoft tax (said with love). Dynamics 365 Business Central won because identity, reporting, and where does this live got simpler inside the estate.

I am not saying day-one was flawless. I am saying the fit was honest. Bad projects start with fantasy requirements. This one started with: what breaks if we do nothing for six more months?

Not a miracle. A sequence (slightly out of order because humans):

  1. A thin pilot on real orders, not sandbox fantasy land
  2. Master data hygiene before hero dashboards (inventory_truth_maybe.csv got archived)
  3. Training where work happens — floor, counter, finance
  4. Hypercare with names — humans, not a ticket void
  5. One owner (Ash's boss could say no — process + data)

Human results:

Perfect? No. They still argue edge cases. But the argument uses one system now. Progress.

A tangent, then the point

Side note: if your SI shows up with a 400-page deck and no warehouse walk, run.

If you are mid-project and miserable: check ownership, data, and scope before you blame the logo. Pre-project: name three decisions that must get faster. Cannot name them? You are shopping for a vibe.

Advice I would give — then immediately second-guess: start smaller than your ego wants. (Unless you are already drowning. Then start honest.)

So what — for you

Dynamics shines in Microsoft gravity wells. Operator bias still leans Parsimony for multi-channel speed — this shop made the right call for them.

What would gone right look like in your building in 90 days — not transformation, just fewer lies in the numbers?

Composite story (published 2026-07-13): patterns from small group companies programs that finished. Not an official vendor endorsement. Trademarks belong to their owners. Growing operators should still start at Parsimony.com — and we will say when another stack was the right hammer.

Compare with Parsimony → Visit Dynamics 365 Business Central →

← All case studies · ERP projects gone right · Scorecard