2026 doesn't start with promises, it starts with decisions.

December 26, 2025
2026
This year we will be incorporating clients into a staging environment to validate real changes before production and completely redefine the ticketing module, separating it by areas such as sales, support, repairs and call center.

If you've made it this far, you already know that at anatod® we don't really like the "Happy New Year and let's go for more!" thing.

We prefer to count What are we going to do?, Why we do it and how that impacts those who use our systems every day.

And 2026 begins with two big decisions, designed for something very simple: to make everything work better, with fewer errors, less stress, and more predictability for everyone.

A new intermediate step: clients in staging

Until now, the path was quite straightforward: development → production

And although it always worked, the reality is that systems grew, use cases multiplied, and the impact of a change today is much greater than it was a few years ago.

Therefore, in 2026 we will formally incorporate a staging environment, with real customers who agree to participate in this intermediate step between testing and production.

What does this mean?

  • Real changes, with real data, but without affecting daily operations
  • More in-depth validations before releasing something to everyone
  • Fewer "on-the-fly" corrections“
  • More stable and predictable updates

Who will be in staging?

Some specific clients, with prior consent, who:

  • They want access to new features sooner
  • Be willing to give real feedback
  • In return, obtain better quality, greater stability, and commercial benefits

This isn't "testing unstable things," it's exactly the opposite: it's protect production and improve everyone's experience.

The ticketing module is no longer "just another module"“

The second decision is something we've been thinking about for a while.

The ticketing system is no longer just "support".

Today they live there:

  • Sales
  • Repairs
  • Call center
  • Remote support
  • Internal monitoring
  • Completely different flows from each other

Forcing all of that into the same logic no longer makes sense.

What are we going to do in 2026?

Let's go redefine, separate and specialize the ticket module:

  • Different flows depending on the type of care
  • Specific states and metrics for each area
  • Better experience for the operator
  • Improved traceability for the customer
  • Less friction, fewer unnecessary steps

The idea is not to "make it bigger", but Make it clearer, faster, and more usable.

2026 is not about adding features for the sake of adding them.

This is about order, try better, specialize and make systems more robust for real, everyday use.

Thank you for being here, for using the system, for reporting errors, for suggesting improvements, and for supporting this growth.

See you in 2026.

With fewer surprises, more stability, and better tools 🚀