To shortlist a NetSuite partner in the US, start with eight to ten names, cut them with a few knock-out tests tied to your scope, ask the survivors for the same written evidence and score a working session against fixed weights. Three partners should reach the proposal stage. Fewer leaves you without a real comparison. More turns the SOW review into a second job.
The trap is shortlisting on signals that cost a partner nothing: a polished sales demo, a badge on the website, a familiar client logo or the lowest rough estimate. None of them tells you who will set up your sales tax, sign off your revenue schedules or answer a ticket at 5 PM Pacific. The shortlist is the cheapest place to test those things, before three firms spend weeks on proposals and the conversation turns to price.
Partners can only be compared if they respond to the same facts. Before you contact anyone, write one page that covers your legal entities, the states where you collect sales tax, revenue streams and how they are recognized, the systems NetSuite must connect to, your audit position and your target go-live window.
Keep it factual, not aspirational. "We collect sales tax in 19 states through a tax engine" is useful. "We want a modern finance platform" is not. If you have not documented the footprint yet, our NetSuite US implementation requirements checklist covers entities, tax, payments, payroll and recordkeeping in more detail.
Add two or three scenarios that would hurt most if they went wrong. For a distributor that might be a drop-ship order into a state where you only recently registered. For a software company it might be a multi-year contract with a mid-term upgrade. You will reuse these scenarios later.
Aim for eight to ten names. Take a few from Oracle's partner listings and from your NetSuite account executive, then add firms recommended by peers in your industry, your outside accountants and any integration vendors you already use. One source tends to produce firms that look alike.
A partner listing shows a commercial relationship with Oracle. It does not show who will work on your account or what they have delivered for a company like yours. Treat every source as a lead, not a recommendation.
Check one conflict early. If your external auditor's firm also implements NetSuite, ask your audit partner whether independence rules allow it to do the work. For public companies and those preparing for an IPO, the rules generally stop an audit firm from designing or implementing financial information systems for an audit client. It is better to find that out before the firm is on your shortlist.
Knock-out tests are pass or fail. They exist to save time, so keep them few and tied to the brief. A short email and a 30-minute call are usually enough to apply them.
Economic nexus rules mean many US companies collect tax in states where they have no office, so the sales tax test is not a formality. Our guide to NetSuite sales tax and US nexus explains what that work involves. If you face an external audit of internal controls, the control evidence described in SOX controls in NetSuite for pre-IPO companies gives you a concrete thing to ask for.
Use the rough range only as a pass or fail. A range is not a quote, and scoring it at this stage rewards the firm that guessed lowest. NetSuite implementation cost in the US shows what a complete USD budget should include when the real proposals arrive.
Send the five or six firms that pass a short written request with a deadline. Ask for the CVs of the proposed lead and two core consultants, one sample deliverable with client details removed (a design document, a test script or a cutover plan), their standard change request form and a list of three references that match your footprint.
Then read what comes back for specifics. A cutover plan with named tasks, owners and rollback points shows how the firm works. A capability deck does not. A firm that sends marketing material instead of the requested items has answered the question in a different way.
Invite the remaining firms to a 90-minute working session, not a sales demo. Give each the same scenario from your brief and the same small data set a week ahead, and ask the proposed lead to run it. A sales engineer can attend, but cannot be the presenter.
Score what you see, not what you are told. Did the lead ask about your tax engine, your nexus states and your approval rules before showing a screen? Did they show the exception, such as a partial shipment or a credit after the period closed, or only the clean path? Our NetSuite demo script checklist explains how to write scenarios that expose the difference.
Ask to speak with the controller or the system owner at each reference, not only the executive sponsor. Choose companies that went live at least six months ago, operate in several states and run a similar mix of order types or revenue streams.
Ask what changed between the SOW and go-live, how the partner handled the first sales tax filing after cutover and who answered the phone in the first month. Ask whether the people named in the proposal were the people who did the work. Write the answers down in the same template for every firm.
This example is hypothetical and simplified. A Columbus, Ohio, industrial distributor with $60 million in revenue, two legal entities, sales tax collection in 19 states and a warehouse in Nevada is moving from QuickBooks Enterprise to NetSuite.
Its long list has ten firms. Four fail the knock-out tests: two cannot name a solution lead, one has no tax engine work to show and one offers no support after 2 PM Pacific. Of the six that receive the evidence request, two send capability decks, which leaves four firms for working sessions.
The steering group scores each firm from 1 to 5 against six weighted criteria. Weighted points are the weight multiplied by the score divided by five, so each firm can earn up to 100.
Partner B scores 83, Partner A 81 and Partner C 75. Partner D scores 56, mainly because it named only a sales architect for delivery, and drops out. A two-point gap built from 1-to-5 ratings is within the margin of judgment, so the group treats A and B as level. C ran the best session but proposed a lead who had joined two months earlier. C stays on the list on one condition: it must confirm a lead with comparable delivery before the SOW request goes out.
The scores do not pick the winner. They tell each conversation where to focus: tax evidence with B, support coverage with A and team depth with C.
Ask each of the three for its standard master services agreement now, before the proposals. Problems found here take weeks to resolve if you wait until a preferred partner is chosen and everyone wants to start.
Have counsel review the limitation of liability, who owns the custom scripts and workflows written for you, the key-person clause, subcontractor approval, insurance certificates such as professional liability and cyber, data access and termination assistance. A partner that will not name its key people in the contract is telling you how firm those names are.
Send the three firms the same request: your brief, the scenarios, your data volumes, a draft acceptance approach and a fixed response date. Ask each to price the same scope so the proposals can be compared line by line. The questions in NetSuite partner questions to ask before signing the SOW then do the detailed work.
Tell the firms that dropped out, and tell them why in a sentence. You may need them later, and a clear reason costs you nothing.
A CuriousRubik NetSuite implementation review can help US finance and operations teams turn their scope into a brief, run the knock-out tests and score working sessions before any SOW is signed. See our NetSuite work in the United States for more.
Three is usually right. Two gives you a weak comparison and little negotiating room. Four or more means reading proposals that differ in format more than in substance.
No. Most delivery is remote, with on-site visits for design workshops, testing and go-live. What matters more is a named team, support hours that overlap your business day and travel costs written into the proposal.
Not as a score. Use a rough range as a pass or fail to remove firms that are far outside budget. Compare real prices only once all three firms have priced the same scope.
Yes, if you are reviewing the relationship rather than leaving it. Put them through the same tests as the other firms. If you have already decided to move, our guide to switching NetSuite partners in the US covers access, code and handover first.
Mostly. The knock-out tests change with the country. Our guides to choosing a NetSuite partner in Singapore and a NetSuite partner in Australia cover the local tax and support tests.
A practical evidence checklist for the delivery team, comparable work, reference calls, escalation and contract questions.