Hundred MSHome / Blog / How to choose a NetSuite consultant
How to choose a NetSuite consultant
Stuck on this choice?Bring it to a free 30-minute call with Narek. No pitch.
Book a callChoose a NetSuite consultant by the work you need done. For a new license and a standard setup, a solution provider is the usual route. For accounting problems inside NetSuite, such as a slow close, reconciliations or a rescue after a bad implementation, pick a firm whose people close books in NetSuite themselves. Ask who will do the work, ask for proof of reconciled results, and get the scope in writing.
- Match the type of firm to the work: license and standard setup, or accounting inside a live account.
- Meet the people who will do the work before you sign.
- Ask what proof of reconciled balances you will be handed at the end.
The four kinds of NetSuite help
| Type | Good at | Watch for |
|---|---|---|
| NetSuite's own services team | Standard implementations, product knowledge | Less flexible on scope and price |
| Solution providers and resellers | Licenses plus implementation in one contract | They resell the license and earn a margin on it, so the advice is not neutral on whether to buy |
| Independent consulting firms | Fixing, optimizing, accounting inside NetSuite, rescues | Quality varies. Check who does the work. |
| Freelancers | Small, well-defined tasks | One person: no cover, no review |
We are in the third group. Hundred MS sells no licenses, and our NetSuite work is done by accountants and administrators who run month-end closes in NetSuite for clients. That shapes the advice below, so weigh it accordingly.
Start with the problem you have
- Buying NetSuite for the first time: you need license advice and an implementation team.
- Live, but the close is slow or the numbers do not tie: you need accountants who know NetSuite, more than developers.
- An implementation went wrong: you need someone who will diagnose before they quote.
- Integrations and scripts: you need developers, with an accountant checking what lands in the ledger.
Of the last three NetSuite problems in your company, how many were really accounting problems? If most were, weigh a firm's accountants more heavily than its developers.
Nine questions to ask before you sign
- Who exactly will do the work, and can we meet them before we sign?
- Have they closed books in NetSuite themselves, or only configured it?
- How many NetSuite-certified people are on the team, and will one be on our project?
- What will you hand us at the end to prove the data and balances are right?
- What is in the fixed scope, and how are changes priced?
- Can we speak to a client with a company like ours?
- What did your last difficult project teach you?
- Who supports us after go-live, and for how long?
- What would make you tell us not to do this project?
A consultant who cannot name a reason to say no will say yes to everything, including the things that should not be built. The honest ones challenge the brief before they quote it.
Warning signs
- A price before anyone has looked at your account or your data.
- The senior people sell, and you never meet the ones who will do the work.
- Customization offered for things NetSuite already does out of the box.
- No mention of reconciliation, testing or a parallel month.
- Accountants are absent from the design meetings.
What good looks like
A written scope you can understand. Named people. A test account or sandbox before anything touches live data. Balances reconciled to the cent at every handover. Your own team trained to run the system, so you are not dependent on the consultant forever. And a first month-end close done together.
On our side that means 9 NetSuite-trained people, 2 of them NetSuite-certified, a written scope and quote within two days of the first call, and the same named accountant every month.
Where this goes wrong
| The problem | What it costs you | The fix |
|---|---|---|
| You choose on the sales meeting | The people who turn up to do the work are strangers | Meet the delivery team first |
| A price arrives before anyone has seen your account | Change requests later | Ask for a written scope after a look at your data |
| Customization where standard NetSuite would do | Upgrade pain and lasting dependence on the consultant | Ask why the standard feature is not enough |
We are often called in after a first implementation, so we see which choices caused the trouble.
Sources we opened and checked for this guide:
First published 2024. Rewritten and checked in September 2026. If something here is out of date, tell us and we will fix it.
