Many ServiceNow teams know the feeling: requirements keep growing, capacity doesn’t. At the same time, the platform has to stay stable, integrations can’t break and every change needs to be traceable.
That’s why the ServiceNow Brazil release puts one question front and center: How much development work can AI really take on, and how do companies stay in control of their platform?
With Build Agent and Autonomous Engineer, ServiceNow takes a clear step forward. For CIOs, IT leaders and platform owners, the question is no longer whether AI will play a role in development. It’s this: Where does it pay off first?
From requirement to delivery
Autonomous Engineer is designed to turn business requirements into a work plan with acceptance criteria. Once the plan is approved, the product handles the implementation and then runs the tests.
It requires Brazil Early Availability, the AI Workflow Factory SKU and a separate activation.
Build Agent takes a slightly different approach. Here, the developer works directly with the AI. A limited trial is installed by default on Brazil Early Availability instances. Automatic updates for the Build Agent app are also available on certain Zurich and Australia patch levels. The Otto for Creator package on top of it is managed separately.
For us, one point stands out: AI can only deliver as well as the task was described.
If you write clean work packages, define acceptance criteria and have a reliable testing process, you can benefit from these features. Without that foundation, an AI agent won’t fix the problem either.
AI Agent Studio: From experiment to real use
The redesigned AI Agent Studio brings agent configuration and testing together in one interface. A visual view shows agents, tools and how they connect.
The Agent Advisor is worth a closer look too. It analyzes instance data, suggests possible use cases and shows estimated time and cost savings.
The new interface is part of the September release and, under certain conditions, also available for Zurich and Australia. So it’s not exclusive to Brazil.
For companies, this can make getting started easier. Instead of trying to automate large processes right away, we’d start with one clearly scoped use case: pick a process, evaluate the results together with the business and measure whether work is actually being saved.
IT Service Management: Fewer hurdles for employees
IT Service Management also gets some interesting updates with Simplified IT Service Management and Employee Slate.
But new technical features are only half the story. What matters is what employees actually notice.
Do they find the right service faster? Can they submit a request more easily? And do they always understand what’s happening with their request?
That’s how the value should be measured.
A new interface isn’t automatically better. It’s better when it makes everyday work easier for the people using it.
Collaborative Work Management: Turning information into tasks
Collaborative Work Management is also more closely tied to AI.
ServiceNow Otto can create structured tasks from documents and natural language input. Larger tasks can be broken down into subtasks.
Further updates connect CWM more closely with Project Workspace and extend sprint tracking, dashboards and native lists. Which features are available depends on your CWM package.
This can be especially useful for teams where information currently gets lost between meetings, documents, emails and task lists.
But here too, what counts isn’t how fast a task gets created. It has to be complete, correctly assigned and clear to everyone involved.
When is the ServiceNow Brazil release coming?
ServiceNow has named September 24, 2026 for Brazil Early Availability.
General Availability is currently expected in November 2026. Until ServiceNow publishes a binding date, we’d treat this as a planning window, not a fixed production date.
If you’re planning an upgrade, now is the time to look at your upgrade path, the applications you use and the testing you’ll need.
In the end, the right time for your production upgrade isn’t set by ServiceNow’s calendar. It’s set by your own platform.
Six questions to answer before you upgrade
- Where is the real value?Pick two or three use cases where success can be measured.
- Which features are actually available to you?Release, patch level, plugins, product packages and licenses all have to line up.
- What needs testing before the upgrade?Custom applications, integrations and business critical processes matter most.
- Who is allowed to build and approve AI agents?Roles and responsibilities should be clear before the first production use.
- How is quality measured?Without acceptance criteria and tests, it’s hard to tell whether an agent really works reliably.
- Is the business involved?Even the best technical features won’t help much if they miss how people actually work.
What Brazil means for your platform strategy
Brazil shows very clearly where ServiceNow is heading.
AI won’t just add features on the side. It will increasingly take on tasks in development, planning and process execution itself.
That also changes the role of platform teams.
Less time on manual implementation can mean more time for architecture, governance, quality and working with the business.
Provided the foundations are in place.
That’s why we wouldn’t try to roll out as many new AI features as possible at once. We’d start with a few clearly defined use cases and measure whether they actually create value.
Which Brazil features fit your ServiceNow platform?
We help companies assess their ServiceNow platform and prioritize the next steps.
Together we look at which features match your goals, which prerequisites are already in place and where action is still needed before going live.
Start with our ServiceNow Platform Assessment.
As of October 14, 2026. Availability and prerequisites may change before General Availability.
