//
MyNSKB · Your NetSuite knowledge base
Your NetSuite will keep changing. Your team will know why.
Your ERP will keep hanging. The reasons behind it shouldn't leave with your partner.
At go-live we hand your IT team MyNSKB: the full record of your implementation, with every requirement, decision, design, configuration and test connected to the conversation it came from. Your team learns to work with it alongside our agents during the project, so after go-live they can run, support and change NetSuite with the same context we had.
Every requirement
linked to the discussion where it was agreed
Every decision
with who approved it, when, and the options rejected
Every design
mapped to the configuration that implements it
Every test
traced to the requirement it proves
Every session
recorded, transcribed and searchable
//
Eighteen months after go-live
One question. The rule, the reason and everything it touches.
NetSuite admin, your IT team
Why is order SO-10482 stuck, and can we raise the credit threshold for dealers?
MyNSKB
The customer is on credit hold. Orders above available credit need approval before fulfillment.
Why
Agreed in the order-to-cash workshop, [date, 00:31:10], approved by your Controller
Here's everything a threshold change would touch:
01
Rule
Orders above available credit require approval
02
Configuration
Credit Approval Workflow
CreditCheck UE
script
03
Integration
Salesforce → NetSuite customer sync
04
Control
No fulfillment while on credit hold (SOX)
Approval needed: Controller owns this rule. A draft change request and test scripts are ready for review.
//
The problem after go-live
Most ERP knowledge walks out the door at go-live.
Your NetSuite keeps changing as the business does. But the reasons behind how it was built usually live in a partner's heads, scattered documents and meetings nobody can find. Every change starts with rediscovery.
Capacity goes to rediscovery
Your team balances running NetSuite with delivering change. Hours go into working out how something was built before anyone can touch it.
Intent gets diluted
Months later, it's hard to tell an approved design choice from a misunderstanding, or a workaround from a rule.
Changes collide
Separate initiatives make incompatible assumptions about shared data, integrations and release plans. Conflicts surface after the design is committed.
People move on
Admins leave, partners change, acquisitions add new systems. The next project has to reconstruct which decisions still apply and why.
//
What's inside MyNSKB
How your NetSuite actually works, not just how it's configured.
System settings tell you what is configured. They don't tell you why. MyNSKB keeps three kinds of knowledge together, so people and agents can understand a change before they make it.
01
System knowledge
The technical truth.
What is configured in your account and how it connects.
Records and fields
Forms and workflows
Scripts
Roles and permissions
Integrations
Saved searches
02
Business knowledge
The reasons behind it.
The processes, rules and decisions your implementation was built on.
Processes
Business rules
Design decisions
Rejected options
Controls
Owners
Exceptions
03
Agent context
What agents need to help safely.
The guardrails that let agents draft changes your team can trust.
Permitted actions
Dependencies
Approval paths
Guardrails
Test history
//
CONNECTED, NOT COLLECTED
One business rule, traced through everything it touches.
MyNSKB isn't a folder of documents. Each piece of knowledge is linked to the next, so when something needs to change, you can see what else moves with it.
01.
Process
Order-to-cash
02.
Rule
Over-limit orders need approval
03.
Configuration
Credit approval workflow
04.
Data
Credit limit, balance, hold
05.
Integration
CRM customer sync
06.
Control
No fulfillment on hold
07.
Owner
Controller, with CFO override
//
Onboarding your IT team
Your team learns it during the project, not after we leave.
A knowledge base like MyNSKB is only useful if your people know how to use it. Your IT team works alongside our consultants and agents throughout the implementation, so by go-live they're already fluent. Select a stage to see how.
Your IT team
Joins key workshops and gets read access to the project record as it builds.
Our consultants and agents
Capture every session; agents draft requirements, each cited to the moment it was agreed.
In MyNSKB
Requirements, decisions and the sessions behind them.
At go-live, a curated handoff. Our consultants review the record with your team, remove what's obsolete, and confirm which decisions are current before it becomes yours.
Your IT team
Reviews designs that touch integrations, security and shared data, and learns to query the record.
Our consultants and agents
Consultants make the design calls; agents link each design to its requirements and flag conflicts.
In MyNSKB
Approved designs, rejected options and their rationale.
.svg)
At go-live, a curated handoff. Our consultants review the record with your team, remove what's obsolete, and confirm which decisions are current before it becomes yours.
Your IT team
Watches agents read the account and propose configuration, then reviews proposed changes with our consultants.
Our consultants and agents
Agents propose each change; a senior consultant approves it before agents implement it.
In MyNSKB
Every configuration item mapped to its design.
At go-live, a curated handoff. Our consultants review the record with your team, remove what's obsolete, and confirm which decisions are current before it becomes yours.
Your IT team
Uses agents to draft and run test scripts for their own areas, alongside UAT.
Our consultants and agents
Agents propose a script for every requirement; consultants approve; results logged.
In MyNSKB
Tests traced to requirements, with results.
At go-live, a curated handoff. Our consultants review the record with your team, remove what's obsolete, and confirm which decisions are current before it becomes yours.
Your IT team
Takes ownership of the record in a curated handoff session.
Our consultants and agents
Consultants confirm which decisions are current and archive the rest.
In MyNSKB
A clean, current knowledge base your team owns.
At go-live, a curated handoff. Our consultants review the record with your team, remove what's obsolete, and confirm which decisions are current before it becomes yours.
Your IT team
Runs support and change with agents, under your own approvals and change control.
Our consultants and agents
Available for larger initiatives, starting from the same record.
In MyNSKB
A record that grows with every change.
At go-live, a curated handoff. Our consultants review the record with your team, remove what's obsolete, and confirm which decisions are current before it becomes yours.
*Review note: a one-time curated handoff is deliverable today. In-project IT access depends on a [low-cost client license during implementation], which is still under discussion. Hold any claim of an ongoing, live link between our record and the client's until the platform roadmap is confirmed.
//
After go-live
What your team can do with it
Support
Answer "why is it built this way?"
Ask in plain language and get the rule, the configuration and the decision behind it, with links to the session where it was agreed.
Change
See the impact before you build
Agents trace a proposed change through workflows, scripts, integrations and controls, then draft the requirement, design and test scripts for your review.
Configure
Agents prepare, your team approves
Agents read your current NetSuite configuration (records, workflows, scripts, roles) and prepare the configuration change. Nothing moves into your NetSuite account without your approval and your release process.
Onboard
Get new admins productive faster
New team members learn your NetSuite from your own decisions and runbooks, not a generic manual.
Audit
Show who decided what, and when
Change history, approvals and control evidence in one place when auditors or the board ask.
Plan
Start Phase 2 from the record
Deferred requirements, hypercare patterns and earlier decisions give your next initiative a head start instead of a blank page.
//
See it work
A change request in year two. Days, not a new discovery phase.
The request
Finance wants to raise the credit approval threshold for dealer customers before the holiday season.
Starting context
MyNSKB holds the original credit rule, the workshop where it was agreed, the approval workflow, the CreditCheck script, the CRM sync mapping and the SOX control.
What the agents did
Traced the rule to every connected configuration, flagged that the CRM sync also writes credit limits, and drafted the change request, updated design and regression test scripts, each citing its source.
What your team decided
The NetSuite admin confirmed the scope with the Controller, adjusted the sync mapping, and scheduled the release through IT change control.
What you got
A traced, tested change with a full audit trail, without re-hiring a partner to rediscover the design.
//
Governance
Your knowledge. Your rules.
Your people approve
Agents read, trace and draft. Your team approves every change, and configuration still goes through your release and change-control process.
Your record
MyNSKB is yours after go-live, with access set by your roles and permissions. Your data is never used to train AI models.
Every answer shows its source
Agents cite the requirement, decision or discussion behind every answer and every draft, so your team can check the reasoning before acting on it.
//
FAQ
Questions IT leaders ask
What exactly is MyNSKB?
Is it just a set of documents?
Does our IT team need to be involved during the implementation?
Can agents change our NetSuite on their own?
We already have an enterprise AI tool. Can we use that instead?
Is Myers-Holum still involved after go-live?
//
Agentic AI at MHI
How the rest of it fits together
Case study
Agentic ERP Delivery Model
How agents work alongside our consultants across an implementation.
Explore the modal
Case study
Mastering enterprise complexity
How a multi-national franchisor saw a working NetSuite design before any build began.
Explore more
.svg)
244 Madison Ave
Ste. 217
New York, NY 10016
info@myersholum.comCopyright 2026, Myers-Holum | Privacy Policy
.svg)
