The spreadsheet everyone asks for is the wrong tool
Every NetSuite versus Fusion Cloud engagement I have worked on starts the same way. Someone in finance builds a spreadsheet with forty rows down the side, one for every module and sub-feature they can think of, and two columns across the top. Approval workflows, check. Multi-currency, check. Fixed assets, check. By the time the sheet is full, both columns are green in almost every row, because both products handle nearly everything a finance team asks of a general ledger.
That spreadsheet then goes to a steering committee as the basis for a decision, and it cannot actually make one. I have watched a committee stare at a nearly identical scorecard for both platforms with nothing left to argue about except vendor relationship and gut feel. The comparison shows what each platform can do today, not which one still fits the company after the next acquisition, the next entity split, or the next country the business decides to sell into.
I still build the feature matrix when a client asks for one, since it catches a genuine gap that would rule a platform out on its own. I stopped letting it drive the recommendation. The question that actually decides this rarely appears on the spreadsheet, and it rarely comes up until I ask for it directly.
Ask what the org chart looks like in three years
The question I ask early in every one of these engagements is simple. Does the company expect to be substantially the same legal entity in three years, or does it expect to be several. Not headcount growth within the current structure. A different count of subsidiaries, a different set of countries with statutory books, a different consolidation story for the board.
A single legal entity with one or two straightforward subsidiaries has a consolidation problem that stays simple: one chart of accounts, one close calendar, intercompany transactions rare enough to handle by hand. A company on a path to five, ten, or twenty entities through acquisition faces eliminations that touch every close, statutory reporting that differs by jurisdiction, and a consolidation engine that has to reconcile all of it on a schedule the audit committee will not move.
That structural distinction separates these two platforms far more than the module list ever will. The trouble is that it almost never makes it into the RFP, because the person writing the RFP sits in finance operations, not the boardroom where the acquisition pipeline gets discussed.
NetSuite wins when the company looks like it does today
NetSuite's real strength shows up in how fast a contained, well-scoped implementation goes when the target org structure matches the current one closely enough that nobody has to design around a hypothetical future. I have seen a single-entity distribution business with one warehouse go from kickoff to a live general ledger, order management, and inventory system in under six months, with a four-person client team and an implementation partner who had run the same playbook a dozen times before.
That speed comes from NetSuite's own opinions about how a company should be structured. Its suite level consolidation and multi-subsidiary features work well for a handful of straightforward subsidiaries with clean ownership, but push past that into layered ownership, mixed functional currencies, and elimination rules that vary by jurisdiction, and the same opinionated structure starts asking the implementation team to build around it instead of within it. The mistake is choosing NetSuite for its speed and contained cost without checking whether the company will still be that shape in three years.
Fusion earns its complexity when the entity count grows
Fusion Cloud is a heavier implementation by almost every measure I have tracked. Longer timelines, a bigger systems integrator team, a steeper learning curve for the admins who own it after go-live. Clients feel that weight in the first steering meeting, and more than one has asked me directly why they would choose the harder path.
The answer shows up the first time a client with a real multi-entity structure tries to close the books. Fusion's ledger architecture separates primary, secondary, and reporting ledgers, built for many legal entities and statutory bases, and currencies that roll up differently depending on which report gets produced. I worked with a services company that had grown through five acquisitions in four years, each with its own chart of accounts and local compliance rules, closing the books in eleven business days of manual elimination work nobody's auditor trusted. That is the case Fusion's tooling is built to shorten. An organization two acquisitions from that situation is paying for a process that still works once the chart doubles. One with no credible plan to get there is just paying for weight it does not need.
The real input is a board deck, not a headcount report
The recurring mistake is scoping this decision against the current org chart, since that is the document IT and finance operations can actually see. The acquisition pipeline, the planned entity split, the decision to carve out a division and sell it, that information sits in a board deck the systems selection team never sees. It just does not occur to the CFO that the platform decision and the growth strategy are the same conversation.
Ask for it directly, early enough to change the shortlist rather than arrive as a surprise eighteen months into a rollout. When you scope a statement of work for a platform migration, the entity and consolidation question belongs in the first discovery session, not a requirements appendix. A plan to acquire two competitors changes which platform gets shortlisted, and it changes how master data governance for customers, vendors, and the chart of accounts gets designed, so the second and third entities do not each invent their own version of the same vendor record.
I have also watched the reverse mistake, a company picking Fusion Cloud because a board member had used it somewhere running forty entities, when the company in front of us had one legal entity and no acquisition plan. It paid for consolidation depth nobody used. Overbuilding for a future that never arrives costs as much as underbuilding for one that does.
Ask reference customers what changed, not what they expected
Every shortlist process includes reference calls, and almost every call asks the same unhelpful question: are you happy with the platform. Reference customers are polite, the sales rep is usually listening in, and the honest answer gets softened before it reaches you.
Ask instead what changed organizationally in the two years after go-live, and how the platform handled it. Did they add a subsidiary, split a division, or absorb an acquisition mid-implementation that forced a scope change nobody budgeted for. The answer tells you whether the platform bent with the company or made the company wait to catch up, a far better predictor than whatever the reference customer believed on day one.
Build that same question into any vendor demo you run on your own terms. Ask the vendor to add a new legal entity mid-year, with a foreign currency and a messy intercompany transaction, and watch how much configuration it actually takes. Five minutes of that tells a consulting team more about fit than the forty-row spreadsheet did in three months.
Put the entity question on page one of the selection deck
If you are running or advising on a NetSuite versus Fusion Cloud decision this quarter, move the entity structure question to the front of the process instead of the middle. Ask finance leadership directly what the legal structure should look like in three years, and whether anyone outside the room already knows something the room does not. Then size the ERP decision to that answer, not to the org chart printed on today's intranet page.
A mismatched choice rarely shows up in the demo or the reference calls. It shows up eighteen months after go-live, when the second acquisition lands and someone on the integration team asks why nobody flagged the entity question during selection. Ask it now, while the answer can still change the shortlist instead of explaining a scope change nobody budgeted for.
