Here’s an uncomfortable truth about buying NetSuite: the software is the same for everyone. Every partner is implementing the same platform, on the same infrastructure, with the same features. The variable that actually determines whether your project succeeds isn’t in the license. It’s the people you hire to configure it.
That makes partner selection the single highest-leverage decision in the whole process, and yet most companies spend more time comparing license tiers than interrogating the teams bidding for the work. The proposals all look similar. The reference logos all look impressive. The sales engineers all give good demos.
So skip the demo theater and ask the questions that separate a partner who will get you live cleanly from one who will get you live eventually, over budget, with a change order attached. Here are the ten we’d want answered if we were on your side of the table.
1. Who, specifically, will work on my project?
Not “our team.” Names. The sales process is often run by senior people who won’t touch your account after the contract is signed. What you need to know is the actual project lead and the actual consultants who’ll be in your design sessions and configuring your account.
Ask to meet them before you sign. Ask how many concurrent projects they’re carrying. A lead consultant juggling six implementations gives you a sixth of their attention, and it shows in the details that matter: data validation, edge-case testing, thoughtful design choices.
2. What have you implemented in my industry, and what went wrong?
Industry experience matters more in ERP than almost anywhere else, because the hard problems are industry-specific. Revenue recognition for software subscriptions. Lot tracking and landed cost for distributors. Job costing for services firms. Kits, assemblies, and work orders for light manufacturing.
A partner with real experience in your vertical has already solved your hardest problems on someone else’s dime. But don’t stop at “yes, we’ve done it.” Ask what went wrong on those projects. Every honest implementer has war stories. A partner who claims every project was smooth either hasn’t done many or isn’t being straight with you.
3. Can I talk to two clients who went live more than a year ago?
References from the last six months tell you about the honeymoon. References from a year or more out tell you whether the account holds up: whether the design still fits, whether support stayed responsive, whether the customizations turned out to be maintainable.
When you call, ask about the moments of friction. How did the partner handle scope disagreements? What happened when something broke after go-live? Was the team that finished the project the same one that started it?
4. What’s your discovery process, and how long does it take?
Rushed discovery is the seed of nearly every implementation disaster. If a partner proposes a fixed price and a timeline after a two-hour conversation, they’re guessing, and you’ll pay for the gap between the guess and reality in change orders.
A credible NetSuite implementation methodology dedicates real time to understanding your processes before scoping the build: process walkthroughs with the people who do the work, review of your current data, a clear inventory of integrations and reporting needs. Ask how many hours of discovery the partner plans, who from your side needs to be involved, and what deliverable comes out of it.
5. How do you handle scope changes?
Scope will change. That’s not pessimism; it’s every project. What matters is the mechanism. Some partners quietly absorb small changes and flag large ones. Some treat every deviation as a billable event. Some let scope creep silently until the budget is blown and then have an awkward conversation.
Ask for the process in plain language. How is a change identified, estimated, approved, and tracked? What counts as in scope versus out? Get the answer in writing, ideally in the statement of work.
6. What’s your position on customization?
This question reveals a partner’s philosophy quickly. The concerning answers sit at both extremes: “we can build anything you want” signals a team that will happily script your legacy processes into NetSuite and bill for the privilege; “we never customize” signals a team that will leave you with painful workarounds for genuine business needs.
The answer you want is judgment. Native first, configuration second, customization when it earns its place, and a willingness to tell you no when a request will create maintenance pain later. Ask how they decide, and ask for an example where they talked a client out of something.
7. How do you approach data migration and testing?
These two phases are where projects lose the most time, and where corners get cut when timelines compress. Ask specifically: how many migration dry runs are planned? Who cleans the data, and who validates it? What does user acceptance testing look like, who writes the test scripts, and what’s the exit criteria for go-live?
Vague answers here (“we’ll work with your team on that”) mean the partner hasn’t planned it, which means you’ll be doing it unplanned, during the most stressful weeks of the project.
8. What happens after go-live?
Every partner includes some hypercare. The question is what comes next. Does the implementation team hand you to a separate support desk you’ve never met? Is post-go-live support a defined offering with response times, or an hourly afterthought? Do they offer ongoing managed services if you want continuity?
The transition from project to steady state is where a lot of accounts start to decay. Partners who have thought seriously about that transition tend to build accounts that are easier to support, because they know they’ll be the ones supporting them.
9. Do you resell licenses, and how does that affect your advice?
Many partners resell NetSuite licenses and earn margin on them. That’s normal and not disqualifying, but it’s worth understanding, because it can shape recommendations about modules and user counts. Ask directly whether the modules in the proposal are things you need on day one or things that can wait. A partner who suggests deferring a module until you’re ready for it is demonstrating that your interests come first.
10. What will you tell me that I don’t want to hear?
Save this for the end, and pay close attention to the answer. The best implementation partners are the ones willing to push back: on timelines that are too aggressive, on processes that shouldn’t survive the migration, on customizations that will cause pain, on executive sponsors who aren’t actually engaged.
A partner who tells you only what you want to hear during the sales cycle will do the same during the project, right up until the moment things go wrong. A partner who’s a little uncomfortable to talk to, because they’re honest, is usually the one you want.
Reading the Answers
You’ll notice none of these questions are about NetSuite features. That’s deliberate. Feature knowledge is table stakes for anyone bidding on your project. What you’re evaluating is judgment, honesty, process discipline, and whether the people in the room will still be around in a year.
When you’re comparing proposals, resist the pull of the lowest number. Implementation quotes vary for reasons, and the cheap ones usually get cheap in discovery, testing, and seniority, exactly the places that determine success. The right NetSuite partner will cost more than the wrong one on the proposal and dramatically less over the life of your account.
Ask all ten questions. Ask them of every partner on your shortlist. Then hire the team whose answers you believed.
About the Author
