What a health check actually covers, how it's scoped and priced, and why it's a lower-commitment starting point than jumping straight into a support retainer.
Most businesses that go live on NetSuite never get a proper second look at their instance after the implementation partner leaves. Configuration drifts, workarounds pile up, integrations quietly start failing, and nobody notices until something breaks in a way that's visible. A NetSuite health check is a fixed-scope, fixed-price audit that surfaces exactly that — a prioritized, written report on what's wrong, what's risky, and what to fix first, regardless of who built the instance originally. This article covers what we actually review, what you get at the end, how it's priced, and why it's a lower-commitment starting point than jumping straight into a support retainer.
If your NetSuite instance has been live for more than a year and nobody's done a structured review of it since the original implementation wrapped up, you're not unusual — you're the norm. Implementation partners are typically paid to get you live, not to check back in eighteen months later. What happens in between is what a health check is built to find.
NetSuite doesn't break in dramatic ways. It drifts. A saved search that was fine at 10,000 records starts timing out at 200,000. A role permission set up for a contractor who left two years ago is still active. An integration token expired quietly six months ago and nobody's checked whether the nightly sync actually ran since. None of this shows up as an error message — it shows up as a slow report, a reconciliation that doesn't quite match, or a workaround someone built and never told anyone about.
The pattern is consistent enough that it's worth naming directly: the risk isn't that your original implementation was bad. It's that nobody's been responsible for the instance's health since it went live.
Our health check covers six areas, in this order:
Data quality — duplicate records, broken syncs, reporting inconsistencies that quietly undermine trust in the numbers.
Performance — slow dashboards, bloated saved searches, and script load that's degraded as data volume has grown.
Workflow & configuration — manual workarounds that exist because nobody automated them, or because the automation broke silently at some point.
Integrations — failed syncs, expired tokens, and the silent breakages that don't throw an error anyone sees.
Roles & permissions — stale user accounts, overly broad access, and the security gaps that accumulate as people join and leave.
Best-practice drift — where the instance has moved away from recommended configuration, whether through custom scripts, one-off changes, or accumulated exceptions.
Worth being direct about scope, since it's easy to conflate a health check with other things:
It's not an implementation. We don't sell those, and a health check doesn't turn into one by default.
It's not a sales pitch dressed up as an audit. The report is yours to keep and act on whether or not you engage us for anything further.
It's not open-ended. The scope and price are fixed before any work starts — no surprise billing partway through.
It's not a guarantee everything gets fixed. The health check identifies and prioritizes issues; fixing them is a separate, scoped piece of work you decide on afterward.
1. Initial consultation. A short call where we hear your pain points directly, before touching a single record. This shapes where we look first.
2. Full system pass. We work through data, workflows, integrations, roles, and customisations using a single, scoped user role — never broader access than the review requires.
3. Prioritized written report. Every finding documented and ranked by severity and effort to fix, not just listed in the order we happened to find them.
4. Playback call. We walk through the findings together rather than emailing a PDF and disappearing. This is where most of the "wait, why does that matter" questions get answered.
5. No obligation. The report is yours. Some clients move into a managed support retainer afterward; plenty just take the report and action it internally or with their existing team.
Fixed price, agreed in writing after the initial consultation — never quoted blind, and never time-and-materials for this specific engagement. The price depends on instance size, number of subsidiaries, and how many integrations are in play, which is exactly why we scope before quoting rather than publishing a flat number that wouldn't hold up across different businesses.
Three common paths, roughly in order of frequency:
Retainer for ongoing support. Most clients who've seen a prioritized list of real issues want someone to actually fix and then maintain them — this is where a managed support engagement usually starts.
Scoped fix-it project. Some clients want the top three or four findings addressed as a one-off project rather than an ongoing relationship.
Internal action. Some clients have the internal capability to act on the report themselves and just needed the outside, structured diagnosis to know where to point their own team.
All three are legitimate outcomes. We don't have a financial incentive to push you toward the first one over the other two — the health check is priced and delivered the same regardless of what you do afterward.
This is built for businesses already live on NetSuite, full stop. If you're still evaluating NetSuite or mid-implementation, this isn't the right engagement yet — come back once you're live and settled in. If you've been live for six months or six years and haven't had a structured outside review since, this is exactly the gap it's built to close.
No — a single, scoped user role for the duration of the review. We specify exactly what's needed before you grant anything.
It depends on instance size and complexity, which is why timeline is confirmed at scoping rather than quoted as a generic number upfront.
No — we don't sell implementations at all, and we have no commission structure tied to modules. The recommendation is whatever's actually right for your instance.
That happens, and it's a genuinely useful outcome — confirmation your instance is in good shape is worth knowing, not just bad news.
A structured audit of your instance with a prioritized report on what to fix first.
Learn More →Ongoing administration and release management from a consultant who knows your instance.
Learn More →Certified consultants for health checks, roadmap planning, and ongoing advisory.
Learn More →Fixed scope, fixed price, agreed before any work starts — no obligation.