ERP projects gone right · NetSuite · Multi-entity · Close · 2026-01-08

Three subsidiaries, one close calendar

Multi-entity finance illustration
Infographic summary for this ERP case study

Winner stack: Oracle NetSuite · Multi-entity distribution · Texas · three legal entities

I am going to be honest: the first time I heard this project war story, Dana was mid-sentence when a beagle named Biscuit interrupted a Zoom, and somehow that set the tone for the whole cutover.

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 multi-entity distribution team in Texas · three legal entities got an ERP project over the finish line with Oracle NetSuite — 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. Jordan kept a private tracker because trust was optional.

Do not get me started on people who rename fields instead of fixing process. (I said what I said.)

Why Oracle NetSuite won

The bake-off was not subtle. Cloud financials with multi-entity teeth. Oracle NetSuite won — partner and all — because structure finally matched how the company legally existed.

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. One owner (Dana's boss could say no — process + data)
  2. A thin pilot on real orders, not sandbox fantasy land
  3. Master data hygiene before hero dashboards (FINAL_v12_REALLY.xlsx got archived)
  4. Training where work happens — floor, counter, finance

Human results:

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

A tangent, then the point

Oh — and yes, they still use Slack for gossip. ERP does not fix culture.

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

NetSuite is expensive when you daydream; rational when multi-entity is the product. Lean multi-channel: still demo Parsimony and Odoo.

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

Composite story (published 2026-01-08): patterns from multi-entity distribution 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 Oracle NetSuite →

← All case studies · ERP projects gone right · Scorecard