TQC establishes reliable, auditable NetSuite change management with Salto

The Quartz Corp (TQC) needed better control over changes to its NetSuite production environment. Without proper visibility and tracking, development risked introducing issues that were hard to catch and harder to undo. As part of their Continuous Improvement Program (CIP), the IT team wanted to align with a structured Dev → UAT → Prod workflow—ensuring that every change could be traced back to a business request, tested, signed off, and, if necessary, rolled back. TQC needed a way to bring structure, ensure traceability, and reduce risk—without slowing the team down. To overcome these challenges - Staria, a leading European NetSuite Solution Provider and Global Financial Services Partner, introduced TQC to Salto.

A built-in audit trail tying every change to business context

Before Salto, the IT environment was hard to govern. “I’ve got to be honest,” said Daniel Fagg, BI Manager at TQC, “probably before Salto, we were more focused on firefighting and fixing bugs reactively”. Developers could make changes in NetSuite without always aligning with a centralized process, and it wasn’t easy to know who changed what—or why. Looking to mature TQC’s change control - using Salto, the team can tie everything together across systems: “We’re trying to move towards a process where every change has a reason. That reason is captured in Jira, the change is developed in Git, and then we have that whole story through Salto.”

This transparency not only gives IT confidence but enables better oversight and future learning. “If something breaks, we can look back at who made that change and what ticket it was for,” Daniel said. “That gives us a nice audit trail that can help us investigate or avoid making the same mistake again.”

Salto plays a central role in enforcing a structured development process. Every change must start with a Jira ticket, be versioned in GitHub, and deployed via Salto—ensuring clear traceability from business request through to production. “Although it's a tool, it's an IT tool, for me it supports a culture and an approach of documenting what you do, justifying why you've done it, and that the business have also signed off on it.”

“We get a rogue deployment email… a rogue deployment means you haven’t followed this process because it hasn’t gone into production via Salto.”

This approach helps the team maintain discipline—and most importantly, gives business stakeholders confidence that every production change is grounded in real business requirements. 

Reducing the risk of downtime and disruption

Before Salto, NetSuite change deployment at TQC was inconsistent and vulnerable to human error. Testing environments weren’t always in sync, and there was no standardized way to roll back mistakes. Now, every fetch from the dev sandbox creates a safe restore point, and all changes follow a defined flow through test and validation before they’re deployed. “The business outcome is, it hopefully reduces the risk of downtime or wasted time… introducing a problem into your production environment.”

At the heart of TQC’s transformation is a focus on reducing the risk of change. “The key thing we’re trying to avoid really with Salto is introducing something that’s going to cause something to stop working—so people can’t do their job,” said Daniel. With Salto, the team can now structure and stage deployments, reducing the pressure of last-minute fixes and enabling safe, methodical rollouts. The team has confidence that changes are vetted, tested, and recoverable—protecting business continuity and minimizing user disruption.

Improving collaboration and IT visibility

As the IT team rolls out better processes, Salto is also helping foster a culture shift. “Because there’s more control and IT have got a bit more visibility, it can help planning and collaboration—that people aren’t doing things in isolation.” By surfacing what’s changing and why, Salto helps different stakeholders coordinate better and build trust across teams.

This approach is extended to TQC’s external consultants. “If we work with external consultants,” said Daniel, “our mandate will be: you will have a user in Salto, and you'll follow our development framework.”

Ultimately, Salto is a key part of TQC’s broader shift toward maturity. While Daniel notes that TQC is still early in their journey, Salto is already helping them professionalize and scale their approach. “We’re still pretty early in our journey of trying to get better at this sort of stuff. But Salto is helping us take that next step.”