Red Flags When Evaluating a NetSuite Support Partner

What Does It Mean When the Sales Team Is Not the Delivery Team?

The most common pattern in disappointing NetSuite engagements: the discovery call is handled by a senior consultant or sales person, and the actual development work is handed to a junior resource or offshore team. The client never meets the person doing the work until something goes wrong.

When evaluating a partner, ask directly: who will do the SuiteScript development on our account? Will we communicate with them directly? What is their certification level?

A partner that cannot give you a clear answer to these questions is signaling that the delivery model is staffed however the workload allows at any given time. This is common at larger firms where developer availability is pooled across accounts.

The alternative model is a smaller team where you know exactly who is working on your account and can reach them directly. That is not inherently a small-firm advantage, but it is harder to sustain at scale, so larger firms tend to use intermediary layers.

Why Is No Sandbox Testing Policy a Red Flag?

Certified SuiteScript development follows a standard workflow: write and test the script in a Sandbox account that mirrors Production, confirm the expected behavior, then deploy to Production. This is not optional for anything more complex than a trivial change.

A partner that deploys directly to Production without Sandbox testing is operating without a safety net. When something breaks in Production due to a script error, the remediation is more expensive and potentially affects live transactions.

When evaluating a partner, ask how they handle Sandbox testing. A capable partner will have a clear answer. A partner that hedges around this question or says "we usually just deploy to Production for simple changes" is telling you something.

Note that Sandbox testing requires that you maintain a Sandbox account. If your account does not have a Sandbox included, that is a conversation worth having with your NetSuite account manager before you evaluate support partners.

Why Are Response Time Promises Without a Structure a Red Flag?

Many partners advertise same-day or next-day response times in their pitch. The question worth asking is: how is that structured? Is it a best-effort statement, a contractual SLA, or a named person who is actually available?

Response time is most important when something is broken. In a production issue, a 48-hour response window is often too slow. The partner's answer to "what happens if something breaks on a Friday?" is an informative test. If the answer involves a ticket system, a queue, or an on-call rotation you cannot reach directly, the response time in practice will be slower than what is quoted.

Direct communication with the developer handling your account is a more reliable indicator of responsiveness than any SLA language in a contract.

Why Are Vague Certification Claims a Red Flag?

Oracle offers NetSuite certifications for specific technical roles: SuiteCloud Developer I, SuiteCloud Developer II, and NetSuite Administrator (now NetSuite Administrator Professional). These certifications require passing exams that cover platform fundamentals, SuiteScript APIs, and deployment practices.

Not every NetSuite consultant is certified. A partner that lists "NetSuite experts" or "certified professionals" on their website without specifying which certifications, at what level, and held by whom is making a claim that should be verified.

You can ask a partner to provide the names of certified staff and their certification levels. Oracle's certification program tracks this. If a partner cannot or will not provide specific names and certification levels, treat that claim skeptically.

Why Are Long-Term Contracts Without Exit Options a Red Flag?

Some NetSuite support firms sell 12-month or multi-year contracts with significant penalties for early termination. The justification is usually "we invest in understanding your account" or "we price for volume."

The problem with long-term contracts in technical services is that performance is hard to measure at signing. You learn a partner's actual capability over the first 60 to 90 days of working with them. A contract that locks you in for a year with no exit creates a situation where a poor-performing partner remains your partner regardless.

Month-to-month or quarterly retainer structures are a better sign. They mean the partner has to earn continued business. If a partner will not offer a shorter initial commitment, ask why. The answer reveals something about how they think about client relationships.

Why Is an Account Manager as Primary Contact a Red Flag?

In larger consulting firms, client accounts are typically managed by an account manager who owns the relationship but does not do technical work. Communication flows through them: you ask the account manager, they relay to the developer, the developer answers, the account manager translates back to you.

This creates latency in every communication cycle, increases the chance of information being lost or distorted in translation, and makes it harder to have technical conversations about complex problems. The account manager cannot answer technical questions from their own knowledge; they can only relay.

For ongoing NetSuite support, direct access to the developer doing the work is faster and produces better outcomes. It is not always available at larger firms where account management is part of the cost model.

Why Is Missing Documentation of Customizations a Red Flag?

When a new support partner takes over an account, the first thing they should do is document what is already there: the existing scripts, their deployment status, what each one does, which record types and workflows they touch, and what the account configuration looks like.

A partner that starts making changes without this review is working without context. They may modify or deploy something that conflicts with existing customization, introduce a script that fires on the same user event as an existing script without awareness of the execution order, or miss a customization that is relevant to the work they are doing.

Ask a prospective partner how they approach account onboarding. A partner with a defined process will describe what they review, what they document, and how long it takes. A partner without one will give you a vague answer about "getting familiar with the account."

Why Are Recommendations That Exceed Problem Scope a Red Flag?

A support engagement should focus on the issues at hand. A partner that consistently recommends rearchitecting the account, buying additional modules, or undertaking large projects when you came with a specific problem may be solving for revenue rather than the problem.

This is distinct from a partner who identifies a related issue during work on a specific request and proactively flags it. That is appropriate. The red flag is a pattern of scope expansion on every request: a script fix that becomes a recommendation to rebuild the entire workflow, a saved search question that becomes a pitch for a custom dashboard project.

You do not need to be suspicious of every recommendation. But a pattern of scope expansion is worth noticing. Ask partners to separate "what fixes the immediate problem" from "what we would recommend if you want to improve the broader area."

What Should You Look for in a NetSuite Support Partner?

The positive signals in a strong partner are the inverse of the above:

• Named developers with specific certification levels, who you meet before signing
• A defined Sandbox testing workflow that they follow by default
• Direct communication access to the developer, not an account manager layer
• Month-to-month or short-term initial commitment
• An account onboarding process that starts with documentation review
• A track record of diagnosing before recommending

Technical references from companies similar in size and industry are the highest-confidence signal. Ask for references, and ask references specifically how the partner handles production issues and what happens when something goes wrong.

---

SuitePacific provides post-go-live NetSuite support on a month-to-month basis. No long-term contracts, direct developer access, and Sandbox testing on all script work. If you are evaluating support partners and want to understand what working with us looks like, start with a conversation.