Every time we fly back from Brazil, the same thought comes up somewhere over the Atlantic: "Okay, next time we stay longer." NEXP 2026 was no exception.
From September 23 to 25, Nimble Evolution brought its community together at the Wyndham São Paulo Ibirapuera for the Nimble Evolution Experience, or NEXP for short. It was a record year. More than 1,000 people came, and over 50 speakers took the stage across three days. According to the Nimble team, that makes NEXP the biggest event in the Atlassian ecosystem after Atlassian's own Team conference, and the largest event ever organized by an Atlassian partner. You could feel that from the booth. The hallways between sessions were busy from morning till evening.
We were there as a Platinum sponsor, with a booth, a lot of coffee and a long list of people we wanted to finally meet in person. To be honest, we missed more sessions than we'd like to admit, because the booth kept us busy. That's the good kind of problem.
What people came to talk about
The program was wide: collaboration between people and AI, corporate agility, business intelligence and automation, ITSM and ESM, DevOps and SRE. Teams from Globo, Claro, MadeiraMadeira, ZEISS, Pernambucanas, CPFL Energia, Prevent Senior and others presented real cases, and Atlassian was on site too, with Eugênio Onofre and Ana Agari from the partner team.
AI was everywhere, of course. What we liked is that the tone was calmer than a year or two ago. Fewer demos of "look what it can do," more practical questions: where does an agent actually save time, what's worth automating, and who is accountable when it gets something wrong. One session looked at Rovo working as a member of a Scrum team, which is a very down-to-earth way to frame it. Before the event, Alvaro D'Alessandro, CEO of Nimble Evolution, said he wanted people to leave with concrete references for decisions. From the conversations at our booth, that's exactly what people were looking for.
Our own view hasn't changed much, and we said it a few times over those three days: use AI where it's genuinely more efficient than the simple way, and wait where it isn't. A filter that answers "who's free next week?" in one click doesn't need a language model.
Meeting our Brazilian customers
For us, the best part was the people. Some of our Brazilian customers we had only known through support tickets and emails, so it was really nice to finally shake hands and hear how things look from their side.
We asked pretty much everyone the same simple question: how do you actually use ActivityTimeline day to day? The answers were more varied than we expected. We wrote down every request. The ones we heard more than once will go straight into our next planning discussion, because a pattern you hear from five different teams in two days is hard to ignore.
What we learned about the Brazilian market
We came to São Paulo wanting to understand one thing better: what makes work management in Brazil different from what we usually see in Europe or the US?
One answer showed up in Nimble's own product news. They presented Nimble Attune, an app that reconciles the electronic time clock (ponto eletrônico) with the hours people log against their work. Many Brazilian companies have to keep time clock records for labor compliance, and on top of that they track time in Jira for projects, billing and reporting. So the same hours get recorded twice, in two systems, and at the end of every month someone has to make them match. Nimble had this exact problem in their own company, fixed it for themselves first, and then turned it into a product.
That one sounded very familiar. Several people at our booth described the same "two sources of truth" situation with their time tracking. And once the hours finally match, the next question is usually about money: what did this project actually cost us, and did we earn anything on it? Jira can't answer that, because Jira tracks effort, not money.
That's the gap our Finances module covers. It takes the hours already logged in Jira and turns them into cost and revenue. You create a budget for a project, a few epics or a JQL filter, set cost and billing rates per person (hourly or monthly), and add the things that aren't hours, like licenses or contractor invoices, as transactions. Rates are effective-dated, so a raise in March doesn't rewrite February. From there, the Summary dashboard shows actual and forecasted spend against the budget, so you see a project heading over while you can still do something about it. If you bill clients by the hour, the Detailed Financial Report gives you every worklog with its rate applied, ready to export to Excel.
And there's more coming. Nimble announced a new event in the US and an even bigger NEXP in Brazil in 2027. If this year's crowd is any sign, someone should start looking for more chairs (we have already booked ours 😉).
Thank you
A huge thanks to Alvaro D'Alessandro and Jamale Harris for inviting us again. It's really cool to see our partnership with Nimble keep growing year after year.
Thank you to the whole Nimble team for this event. Three days in São Paulo taught us more about our Brazilian customers than a year of emails. See you at NEXP 2027, and this time we really will stay longer.
Next stop: Amsterdam for Atlassian Team ‘26 Europe. 🇳🇱
If you’re interested in a partnership or co-marketing collaboration, feel free to book a time with Yuliia Hushcha and discuss possible opportunities. See you there 👋
