AI can read your data, but it can’t read the room.
When businesses start exploring NetSuite, the conversation often turns to AI quickly these days. Automated data mapping. AI-assisted configuration. Smart migration tools that analyse your existing setup and suggest how to rebuild it in a new system. It all sounds impressive - and a lot of it is.
We use AI tools internally, and they sometimes have a supporting role in our implementations. We think that's the right call, and we'll explain why. But we also see what happens when technology is allowed to lead a project… and that's a more complicated story.
Before we get into it… We should caveat that this article is focused on companies that are comfortable with the use of AI. We know there are many businesses out there that, based on policies or security requirements, do not wish to use AI throughout their implementation. You have every right to request that AI tools not be used in your implementation, and this is where the expertise of the people in the company really comes into play.
Where AI genuinely adds value
We aren’t here to dismiss the technology. AI-assisted tools have made meaningful improvements to the mechanics of ERP implementation.
Data cleansing and migration - the unglamorous but essential job of sorting through years of accumulated records and preparing them for a new system - is faster and more accurate with AI assistance. Configuration suggestions based on industry and company type give projects a better starting point. Documentation that would have taken days to draft comes together in hours.
These are real efficiencies, and they benefit our clients directly. And while it’s important to note that an experienced consultant has to quality check this output, it still leads to shorter timelines, fewer manual errors, and potentially lower project costs. When we use AI tools well, they free our consultants to spend more time on the work that actually requires their expertise.
The difference between the mechanical work and the expert work is the one that matters.
What the data doesn't tell you
Here's something we see repeatedly across implementations: the detail that makes or breaks a project is rarely in the data.
It's in the conversation with the Finance Director where, twenty minutes in, they mention almost as an aside that three of their largest clients have billing arrangements that were negotiated years ago and never formally documented. Not in the CRM. Not in any contract. Existing entirely in the institutional memory of people who may or may not still be with the business.
No AI tool flags that. No automated analysis surfaces it as a risk. It only comes to light because an experienced consultant knows to ask - because they've been in enough implementations to understand that the gap between how a business says it operates and how it actually operates is precisely where projects go wrong.
If that particular detail had been missed, the business would have been issuing incorrect invoices to its most valuable clients from day one of go-live. The financial impact would have been significant. The relationship damage would have been worse.
The technology didn't catch it. The conversation did.
The questions that don't appear in a requirements document
This is something we talk about a lot internally: the difference between requirements gathering and genuine discovery.
Requirements gathering is a process. You document what the business does, map it to system functionality, and configure accordingly. AI tools are increasingly capable of supporting that process — identifying gaps, suggesting solutions, and validating outputs.
Discovery is something different. It's the skill of understanding not just what a business documents, but what it knows without documenting. The processes that have never been written down because everyone has always done them that way. The exceptions that have become the rule. The informal arrangements that sit outside the official version of how things work.
An experienced consultant knows that the official version is a starting point, not the whole picture. They ask different questions. They listen differently. They notice the hesitation before an answer, the qualification that almost got left out, the thing that someone nearly didn't mention.
That's not something you can automate. It's a skill that comes from having done this many times, in many different businesses, and having learned - sometimes the hard way - where the gaps tend to be.
What this means when you're choosing an implementation partner
When evaluating NetSuite implementation partners, the key question to ask isn't whether they utilise AI tools. Most do, and that's not a bad thing. The question is who is leading the project - and what they bring beyond the technology.
Look for partners who invest real time in discovery before they touch the system. Who asks about the things that aren't in your documentation., who treat your business as genuinely unique rather than a configuration template to be populated.
The tools accelerate the work. The expertise shapes it. Both matter - but they're not interchangeable, and they don't play the same role.
We've seen what happens when an implementation is driven primarily by technology with insufficient human oversight. The system goes live on time. The data may have migrated cleanly. But then, gradually, the cracks appear in processes that don't quite fit, in workarounds that creep in, in the slowly dawning realisation that the system was built on an incomplete understanding of the business it was meant to serve.
Getting it right the first time costs less. In time, in money, and in the goodwill of the people who have to use the system every day.
At 3EN Group, we're the UK & Ireland's largest NetSuite specialist team. We use AI where it adds genuine value to our delivery — and we put experienced consultants at the centre of every project, because that's where the real work happens.