SuiteWorld 2026: What NetSuite’s Announcements Actually Mean for New and Existing Customers

---

There was no shortage of announcements coming out of SuiteWorld 2026 in Las Vegas. AI dominated proceedings, which probably won't surprise anybody, but I think there is quite a bit worth understanding beyond the headline demonstrations.

NetSuite announced SuiteSkills, SuiteAgents, SuiteExpress, AI Workspaces, new tools for developers and further developments around Ask Oracle and NetSuite Next. There were also announcements for construction businesses, early-stage technology companies and the way AI will be consumed commercially.

Having gone through the announcements, what interests me most is the direction NetSuite is taking with ERP itself.

For years, businesses have relied on people learning how to use ERP systems. They need to understand the menus, records, transactions, workflows and reports. Even when a system is working well, getting something done generally means somebody knows which part of the application to use.

NetSuite is working towards a different approach, where users explain what they need and the software does more of the investigation, preparation and, where appropriate, execution.

Oracle describes its longer-term ambition as an Autonomous Suite, with people and AI agents working together to manage business processes.

I can see why that would appeal to businesses. I'm also conscious that ERP announcements and the reality of running a finance department are sometimes two different things.

Some capabilities announced at SuiteWorld are available now in particular markets, while others are still being developed. For UK businesses especially, understanding that distinction is important.

So rather than simply repeating the announcements, I wanted to look at what they could mean for new and existing NetSuite customers, and where I think the biggest opportunities and challenges lie.

NetSuite Next and Ask Oracle: Making ERP easier to use

NetSuite Next was introduced at SuiteWorld 2025, and this year's announcements gave us a better understanding of how Oracle sees people working with the system.

At the centre is Ask Oracle, a conversational AI assistant that allows users to search, analyse information, produce reports and navigate NetSuite using ordinary language.

For example, imagine a Finance Director asking why gross margin fell last month.

In a traditional ERP environment, somebody might run an income statement, investigate sales performance, compare costs, examine particular transactions and perhaps export data to Excel. Depending on how reporting has been configured, that could involve several people.

Ask Oracle is designed to make that investigation easier by working with the information already held in NetSuite.

What I find particularly useful about this is the potential benefit for people who don't use ERP every day.

Finance teams generally know their way around their systems. The same isn't always true for Managing Directors, operational managers or departmental heads who only need information occasionally.

Giving those users an easier way to investigate performance without learning all the mechanics of the application could make a meaningful difference.

It doesn't remove the need for proper reporting, though. I would still expect any well-run finance function to have agreed management accounts, dashboards and financial controls. Asking AI a question should complement those things, not become a substitute for them.

For existing customers, moving to NetSuite Next is intended to build on their current environment. Oracle says existing records, roles, permissions, customisations and workflows remain in place, without requiring a fresh implementation or data migration.

There is a UK availability point worth highlighting. Oracle's published 2026.2 guidance identifies the US and Canada as the initial markets for NetSuite Next and Ask Oracle, with additional countries to follow. UK customers should confirm availability directly rather than assume the functionality demonstrated at SuiteWorld is already accessible in their account.

SuiteSkills and SuiteAgents: AI that understands the work

SuiteSkills is one of the announcements I would encourage existing customers to spend some time understanding.

Oracle announced more than 45 prebuilt SuiteSkills covering areas such as financial close, cash flow, billing, inventory, fulfilment, projects, sales, customer support and workforce management.

The concept is reasonably straightforward. Rather than giving an AI tool access to information and expecting it to work everything out, SuiteSkills provide knowledge about particular NetSuite business processes and how to investigate them.

Take financial close as an example. An AI tool could read the relevant financial information, but that doesn't automatically mean it understands how to investigate a reconciliation difference, identify transactions holding up close or distinguish between a genuine financial issue and a timing difference.

SuiteSkills are intended to provide that more specific business knowledge.

There are some useful examples among the announced skills. Oracle has described capabilities for identifying potential revenue leakage, investigating overdue debt, reviewing inventory movements, assessing fulfilment performance and planning project resources.

These are activities that already consume time in finance and operations teams, often because somebody has to gather information from several places before they can even start investigating the problem.

Another interesting point is that SuiteSkills aren't restricted to Ask Oracle. They can also be used with supported external AI platforms through NetSuite's AI Connector Service. Oracle has made the skills available for download, although using them through Ask Oracle still depends on the relevant product availability.

That flexibility could become important as businesses develop their own approaches to AI. They may want to use different tools for different purposes while maintaining NetSuite as the underlying source of financial and operational information.

SuiteAgents take things further.

Where a SuiteSkill provides knowledge for a particular activity, a SuiteAgent is designed to help manage a more complete piece of work.

Oracle announced agents aimed at industries including software, product-based businesses, professional services, healthcare, construction and nonprofits.

For a software business, that could involve analysing revenue retention, billing or forecasting. A product business might use agents to investigate inventory exposure, supplier changes or margin performance.

The professional services examples are particularly interesting. Oracle demonstrated agents that can help turn statements of work into project plans, assess resource availability, identify time-entry exceptions and review project health.

Anyone running a project-based business will recognise how much time can disappear into those activities.

Construction agents are being developed to help with estimates, job budgets, payment applications and the financial implications of project changes. Healthcare and nonprofit agents address processes more specific to their sectors.

It is worth remembering that not every announced agent is available today. Some have been released in markets where NetSuite Next is available, while others remain on the roadmap.

I would also want to understand how these agents work with existing processes before allowing them to perform anything significant. Identifying a problem is one thing; changing a financial transaction or operational record is quite another.

AI Workspaces and the possibility of a different month-end

AI Workspaces bring several of these capabilities together. They are designed to allow people, agents, information and approvals to operate within the same business process.

One of the examples Oracle has focused on is Autonomous Close.

Most finance teams still treat month-end as a concentrated period of reconciliations, adjustments, checks and reporting. Some of that work cannot realistically happen until the period has ended, but plenty of problems are already sitting in the system days or weeks beforehand.

The idea behind Autonomous Close is that NetSuite can help identify and address those issues continuously rather than waiting until somebody discovers them during the close process.

This is an area where I can see a genuine business case.

If a finance team currently spends ten working days closing its accounts, reducing that to five would be far more useful than simply giving the team a new AI tool to experiment with.

The same applies to collections, revenue leakage and project profitability. Finding an issue earlier often matters more than producing a better-looking report about it afterwards.

Of course, the technology will still need to demonstrate that it can deliver those improvements consistently. A product demonstration isn't evidence that a particular customer will achieve the same result.

Reporting, dashboards and information outside NetSuite

Oracle also announced AI Portlets, which allow users to describe the analysis they want and generate dashboard components containing charts, information and potential actions.

A Finance Director might want to compare current sales with forecast assumptions, or an operational manager might want to understand which orders are creating pressure on inventory.

Today, those requests often involve configuring saved searches, reports or dashboards. AI Portlets could make that process more accessible, particularly when somebody wants to investigate something that isn't covered by their normal reporting.

I like the principle, but there is a potential problem that businesses will need to manage.

Making reporting easier doesn't automatically make the underlying information more reliable.

If sales and finance have different definitions of revenue, or three departments calculate margin differently, allowing everybody to generate their own analysis could make the disagreement even more obvious.

That isn't a reason to avoid AI. It is a reason to make sure the business has consistent definitions, properly maintained master data and confidence in its financial information.

NetSuite Analytics Warehouse is also evolving into NetSuite Data Intelligence, with announced capabilities including the Data Intelligence Agent and Deep Insights Agent. These are intended to help users investigate business information conversationally and receive more tailored insights and recommendations.

For organisations already using Analytics Warehouse, this is worth following, although customers should confirm the availability and scope of the newer capabilities.

Ask Oracle Connectors are another development on the roadmap.

NetSuite already supports connections that allow approved external AI tools to work with permitted NetSuite information. Ask Oracle Connectors are intended to extend that in the other direction, allowing Ask Oracle to work with information from supported external applications and the internet.

Consider a purchasing decision. NetSuite might hold the current inventory, outstanding orders and supplier records, while other systems contain forecasts or relevant supplier information.

Bringing that information together could make it easier to investigate whether a purchase order should be placed and what the consequences might be.

The important consideration is how that information is accessed, validated and acted upon. Access to more data is useful only if the business can trust what is being used to reach a decision.

Giving AI more responsibility means looking carefully at controls

One of the more interesting parts of the announcements concerns the tools Oracle is developing to let businesses create and manage their own agents.

SuiteAgent Studio is intended to allow organisations to configure agents, including their instructions, tools, triggers and execution roles.

SuiteFlow Agent aims to let administrators and power users create workflows using natural-language instructions. Instead of configuring every condition manually, somebody could describe the workflow they need and review the proposed configuration before it is created.

SuiteAgent Management Workspace is designed to provide oversight of agent access, permissions, activity and execution issues.

These capabilities are part of Oracle's development roadmap rather than something every NetSuite customer can deploy today, but I think the direction creates an important question for existing customers.

How confident are you in your current roles, permissions and approval processes?

NetSuite's approach is intended to respect existing access permissions and introduce appropriate controls and human approvals around agent activity. However, those controls need to be understood and configured properly.

If a business has spent ten years creating custom roles, copying permissions, changing responsibilities and adding exceptions, it might be worth reviewing that structure before introducing agents that can perform work.

The same applies to workflows and approvals. Businesses should decide which activities AI can investigate, which it can prepare and which it should be allowed to execute.

Those decisions are particularly important when financial records, supplier payments, inventory or customer information are involved.

AI may eventually perform more administrative work, but accountability for what happens in the ERP will still sit with the business.

SuiteExpress: Could ERP implementations really take days instead of months?

SuiteExpress probably generated some of the biggest headlines because Oracle has talked about reducing implementation times to weeks or potentially even days.

Anyone who has been involved in ERP implementations will appreciate why that attracts attention.

SuiteExpress combines NetSuite's product and industry knowledge with information specific to the customer. That customer information can include documents, meeting notes, spreadsheets, recordings, existing system data and configuration decisions.

The intention is for AI to assist with requirements gathering, solution mapping, data preparation, migration validation, testing and training materials.

There is also a longer-term benefit being proposed. Rather than losing much of the knowledge gathered during an implementation, the customer-specific knowledge base can continue supporting the business as its requirements change.

I can see considerable potential in this.

Traditional ERP projects involve a lot of necessary but time-consuming work preparing documents, mapping data, configuring processes, producing test scripts and creating training materials. If AI can take on a meaningful proportion of that work, it should improve efficiency.

Where I would be more cautious is the suggestion that a substantially faster implementation must also be a better implementation.

I've worked on both the customer and implementation sides of ERP, and the difficult parts aren't always the technical activities.

A business might have ten years of historical data and insist that all of it needs migrating. AI may make that migration easier, but somebody still needs to question whether bringing everything across is the right decision.

The same applies to requirements. AI might capture everything a department asks for, but some requirements are unnecessary, some contradict each other and others reflect processes that the business should probably change rather than reproduce.

Testing is another example. Generating test scripts quickly is helpful, but those tests still need to cover how the business actually operates. A perfectly executed test of the wrong process doesn't get you very far.

I would hope SuiteExpress allows consultants to spend less time on administration and repetitive configuration, and more time understanding how the customer operates, challenging requirements and making sure important decisions are taken properly.

That would be a worthwhile development for both customers and implementation partners.

I would be much less comfortable if faster implementations simply became an excuse to reduce discovery, shorten user acceptance testing or avoid difficult conversations about process design.

The shift now is to business transformation as opposed to configuration. I expect businesses to benefit from more consultants being able to spend more time on overall transformation. At C&J, we already focus on this, but with SuiteExpress we'll be able to put even more time into it when it arrives into the UK.

There is also an immediate practical limitation for the UK market. SuiteExpress is initially available to software-industry customers in the US and Canada. It is therefore something UK organisations should be aware of rather than assume they can use on an implementation starting next month.

Why SuiteExpress could matter after go-live

I also think there is a useful longer-term benefit here for existing NetSuite customers.

Consider a company that implemented its ERP several years ago. People have moved on, processes have changed and there are customisations nobody is entirely sure about.

Eventually somebody asks why a particular workflow was designed in a certain way.

The answer is that Dave knew.

Unfortunately, Dave left three years ago.

Most organisations that have operated an ERP for any length of time will recognise some version of that situation.

If SuiteExpress can retain the original business requirements, configuration decisions and reasoning behind them, that information could be extremely helpful when introducing a new subsidiary, expanding internationally or reviewing existing processes.

It could also make ongoing optimisation and support more efficient. Rather than starting discovery from scratch every time something changes, the business and its advisers would have access to a better record of how the system was designed and why.

That assumes, of course, that the knowledge remains accurate as the business changes. Capturing it initially is only part of the job.

Other announcements worth understanding

Beyond the main AI announcements, there were several developments that could affect NetSuite's position in particular markets.

QuickStart and the early-stage technology market

NetSuite QuickStart is an AI-first financial platform designed for eligible early-stage US technology businesses. It provides accounting, banking, receivables, payables, subscription management and other core financial functionality, with AI helping handle routine activity.

Oracle is offering QuickStart free to qualifying US startups within defined usage limits.

What interests me is the effect this could have on when a business first starts using Oracle technology.

Traditionally, a company might begin with relatively simple accounting software and only consider NetSuite once it has grown significantly or accumulated enough operational complexity.

QuickStart potentially allows Oracle to establish a relationship much earlier, with a route into NetSuite as the business grows.

If this approach eventually expands internationally, it could change the traditional pattern of businesses moving through several accounting systems before reaching ERP.

For the moment, though, it remains a US proposition aimed at a specific type of business.

Construction becomes a more deliberate focus

Oracle also announced NetSuite for Construction Businesses, with functionality intended to connect estimates, job budgets, costs, billing, work-in-progress and financial reporting more closely.

The planned capabilities include payment applications, change orders, retainage and progress billing, alongside AI assistance for some of those processes.

This is potentially important because construction businesses often need specialist functionality around the core accounting platform.

A housebuilder, contractor or project-based construction business has financial requirements that can be quite different from those of a straightforward trading company. Job costing, subcontractor management, progress billing and profitability at project level all matter.

The closer NetSuite can bring those processes together, the less customers may need to rely on additional software and integrations.

However, the initial release is planned for the US market. UK construction businesses should also consider local requirements, including CIS, when assessing future suitability.

Developers and administrators will need different skills

The changes announced at SuiteWorld will also affect the people who develop and maintain NetSuite.

Oracle already has the SuiteCloud Developer Assistant to support activities such as generating SuiteScript 2.1, while SuiteCloud Agent Skills give AI coding tools more knowledge about NetSuite development standards and practices.

Alongside SuiteAgent Studio and SuiteFlow Agent, these capabilities suggest that some development and administration work could become significantly quicker.

That should be positive, but I can see another risk.

NetSuite environments can already accumulate technical debt from unnecessary scripts, workflows and customisations. If generating those becomes easier, businesses may create even more functionality without properly considering whether it is needed.

The ability to build something in an afternoon isn't a particularly good justification for building it.

I expect developers and consultants will increasingly be valued for their ability to design sensible solutions, understand integrations, protect system performance and determine when standard functionality is the better option.

The technical work won't disappear, but I can see the balance of effort changing.

AI Units: Customers need to understand the commercial model

One announcement that deserves attention away from the demonstrations is how NetSuite intends to measure consumption of native AI functionality.

Oracle has introduced AI Units, which provide a way of tracking the AI processing consumed by eligible features.

Customers receive an allocation through qualifying NetSuite licences, with consumption measured against a shared account-level pool. Oracle has published allocation details and additional unit packages.

The important point is that AI consumption will need managing.

What we don't yet have is sufficiently clear commercial pricing to reliably calculate what additional AI Unit consumption will cost a particular customer. I would therefore treat that cost as TBC until Oracle provides confirmed commercial pricing.

I would also avoid making detailed return-on-investment assumptions that depend on unknown additional unit costs.

That doesn't mean businesses should avoid the functionality. It means they should approach adoption sensibly.

If AI can reduce the time required for month-end, improve collections or help a project business identify profitability problems earlier, those are outcomes worth testing.

Customers should establish how much effort a process requires today, understand the AI consumption involved and measure what improves after introducing the functionality.

I'd rather see a business getting a measurable benefit from two or three useful applications of AI than switching everything on and discovering later that nobody has properly assessed the value.

It is also worth distinguishing NetSuite's native AI Unit model from connected third-party AI services and add-on modules, as the charging and consumption arrangements may differ.

What does this mean for businesses considering NetSuite?

I don't think the fundamentals of selecting ERP have changed.

A prospective customer still needs to understand whether NetSuite can handle its financial reporting, consolidation, inventory, projects, procurement, billing, integrations and industry-specific processes.

Those requirements remain important regardless of how much AI the product contains.

What has changed is that businesses should now give more consideration to how they expect people to work with their ERP over the next few years.

I would certainly want to see demonstrations of Ask Oracle and understand which SuiteSkills or SuiteAgents might be relevant to the business.

But I would insist on a clear explanation of which capabilities are available, where they are available and what remains on Oracle's roadmap.

I wouldn't recommend choosing an ERP because of functionality that doesn't yet exist.

Roadmaps are useful for understanding where a platform is heading, but release dates, product scope and commercial arrangements can change.

A business needs to be confident that the system it purchases can support the operation it has today. Future capabilities should strengthen that decision rather than become the reason for making it.

I would also expect implementation discussions to address data quality, permissions, reporting definitions and unnecessary customisations from the outset.

Those are sensible considerations for any ERP project, but they become even more important if the business intends to use AI to investigate information or carry out activities across the system.

For example, an inventory agent will struggle if the underlying stock records are consistently inaccurate. A finance assistant cannot produce reliable margin analysis if costs are incomplete or transactions are incorrectly classified.

The quality of the existing information remains fundamental.

Existing customers could have an even bigger opportunity

For businesses already using NetSuite, I think SuiteWorld raised some particularly interesting possibilities.

Existing customers often have years of financial and operational data in the platform. They also have established processes, users and integrations.

If that information is reliable and the system is well maintained, AI could provide new ways to make use of what they already have.

The challenge is that many established ERP environments have also accumulated things they no longer need.

Customisations introduced years ago, workflows that have been amended repeatedly, reports that nobody uses, duplicate information and business processes that have gradually moved into Excel are all fairly common.

Before adopting new AI capabilities, I would want to understand whether those issues are likely to affect the results.

That doesn't necessarily mean undertaking a huge optimisation project. I would start with a small number of business processes where improvement would have an obvious benefit.

Financial close is a sensible candidate. So are collections, inventory exceptions, project profitability and management reporting.

Take the process as it operates today, establish how much time it consumes and identify the recurring problems. Then assess whether a relevant AI capability could genuinely help.

I would also review roles, permissions and approval processes before allowing agents to perform activities that could change records or create financial consequences.

Some of the announced functionality may eventually replace existing bespoke development. That could be an opportunity to simplify the environment, although businesses should assess what the native tools actually provide before removing anything.

I would be particularly interested in customers using these changes as an opportunity to review how much of their existing NetSuite investment they are really making use of.

There is no point introducing sophisticated AI to automate a workaround if the underlying process could have been simplified in the first place.

What happens to NetSuite consultants and implementation partners?

There has been plenty of discussion about AI replacing technical work, and some of the SuiteWorld announcements suggest that parts of ERP implementation and development will become more automated.

I don't see that as necessarily bad news for the consulting industry.

It does, however, raise questions about where consultants provide the most value.

Historically, a significant amount of ERP consulting effort has involved configuring systems, preparing documentation, creating reports, migrating data and building customisations.

Those activities will still require expertise and oversight, but AI could reduce the manual effort involved.

I would expect customers to increasingly question why they are paying for several days of work that technology can now help complete much more quickly.

That's a fair question.

Consultants should be able to demonstrate value through their understanding of the customer's business, the quality of their solution design, their ability to challenge requirements and the decisions they help the business make.

Knowing NetSuite inside out is important. Understanding what a Finance Director, Operations Director or Managing Director is trying to achieve is equally important.

There are also consequences when those two things don't come together.

A technically correct implementation can still leave the customer with inefficient processes, poor reporting or functionality that people struggle to use.

If AI reduces the time consultants spend producing documentation and completing repetitive tasks, I would hope more attention goes into getting those fundamentals right.

Whether that happens will depend on how implementation partners choose to use the technology.

What I would be doing now

After reviewing the SuiteWorld announcements, I wouldn't suggest that every NetSuite customer considers an AI transformation project immediately.

I would start by understanding where the business is spending time on activities that add little value, and whether the new capabilities could realistically help.

For existing customers, I would ask how well NetSuite is working today. Are people getting reliable information when they need it? Which processes still depend heavily on spreadsheets or manual investigation? Are roles, permissions and approvals properly maintained? How much bespoke functionality is still necessary?

I would then look at which new capabilities could address those issues, making sure they are actually available and suitable for the business.

For prospective customers, I would want to understand how AI changes the implementation approach, what can genuinely be delivered faster and which decisions still require proper business involvement.

I would also ask how AI consumption will be measured, what is included in the subscription and what any additional capacity will cost once the commercial position is confirmed.

For both new and existing customers, I think the most useful question is whether their implementation or support partner understands the business problem well enough to challenge the proposed solution.

That has always mattered in ERP, and I suspect it will matter even more as some of the technical work becomes easier to complete.

My view after SuiteWorld 2026

I think NetSuite is moving towards an interesting model where ERP does more of the work that currently depends on users investigating information, preparing transactions, monitoring processes and navigating the application.

Some of what Oracle demonstrated is already available in certain markets. Other capabilities will take time to reach customers, and we should expect some of the roadmap to evolve.

I am particularly interested in SuiteSkills, the development of industry-specific agents and what SuiteExpress could do for the way ERP projects are delivered. Those are areas where I can see practical benefits beyond simply making the software easier to use.

I'm also cautious about how quickly businesses will be able to adopt these changes. Good data, properly designed processes, effective controls and experienced decision-making will remain necessary.

For me, the real test over the next few years will be whether NetSuite can help businesses reduce the amount of effort involved in operating their ERP without losing control of the processes that matter.

If it can do that consistently, some of the announcements from SuiteWorld 2026 could make a substantial difference to both customers and the people who implement and support their systems.