Situation
Your implementation partner has moved on
Go-live finished, the team rolled off, and the customizations they built are now yours to maintain. Oracle supports the platform. Nobody supports your configuration.
What tends to break first
Custom scripts
SuiteScript written for your go-live is not covered by Oracle support. When it breaks after a release, it is your problem and there is nobody with context on why it was written that way.
Workflows and approvals
Approval chains configured for the org chart at go-live quietly stop matching who actually works there.
Integrations
The connections built during implementation need monitoring, token renewal, and rework when the system at the other end changes.
Process changes
The business has moved on since go-live. NetSuite has not, because changing it needs someone who understands both the process and the configuration.
Release upgrades
Two releases a year land whether or not anyone tests them against your customizations.
Undocumented decisions
The reasoning behind how things were configured left with the project team. What remains is a system nobody can safely change.
What a fractional administrator picks up
- 01
What Oracle covers
Platform bugs, outages, and the standard product. That is genuinely useful and it is not the gap you have.
- 02
What nobody covers
Your scripts, your workflows, your integrations, your saved searches, and the process decisions baked into them. This is the gap a retainer fills.
- 03
Start with a written picture
A health assessment documents what was built, what is broken, and what is exposed at the next upgrade — which is usually the fastest way to find out how bad the gap actually is.
- 04
Then steady ownership
Release testing, integration monitoring, and a queue that gets worked, with someone accountable between the emergencies.
The assessment is the sensible first step here
Post-implementation accounts are the hardest to quote blind, because the risk is in what nobody documented. A fixed-scope assessment produces the written picture first: what exists, what is failing, and what breaks at the next release.
You keep that report whatever you decide next. If the account is in better shape than you feared, it will say so — and if it is not, you have a prioritized list rather than a vague worry.
If you start a retainer within 30 days, the assessment fee comes off your first two months.
What cover looks like
Three tiers, separated by how much of the account changes month to month. Three-month initial term, then month-to-month. Published prices, all in USD.
Essential
Roughly a day a month
A stable account that still needs an owner: users, access, searches, and the close.
- Users, roles, and access requests
- Saved searches and dashboards kept working
- Month-end close support
Response commitmentP3 / P4
Managed
RecommendedTwo to three days a month
An account that is still moving: workflows, reporting, and integrations that need watching.
- Everything in Essential
- Workflows, custom fields, and reporting built as you need them
- Integrations monitored, not just fixed after they fail
Response commitmentP2
Embedded
About a day a week
NetSuite runs the business and the account changes every month.
- Everything in Managed
- Scripted automation and integration work included
- Same-day response when the business is blocked
Response commitmentP1
No pressure
Tell me what you are dealing with
A 30-minute call. If a retainer is not the right answer for your situation, I will tell you that instead.