Skip to content

In Sankhya's new merit cycle, only 1 in 4 raise requests needs to go through the committee.

Sankhya took the merit cycle out of support spreadsheets and put approval levels and policy into the system. What falls within the rules moves forward without a committee, and 97% of the 100 managers who answered the survey said they were very satisfied.

Company context

Key facts

Empresa
Sankhya
Setor
Management software (ERP)
Sede
Uberlândia (MG)
People in the cycle
~1.300
Start of the partnership
2025
Entry point
Compensation
Merit cycle
Co-built with Compensation & Benefits, HRBPs and managers

At Sankhya, each manager proposes the raise and promotion for their own team, and the compensation policy has to be in their hands at that moment.

Sankhya is one of the leading Brazilian companies in business management solutions. Founded in 1989 and headquartered in Uberlândia (MG), it offers a complete platform that goes beyond the traditional ERP.

The partnership with Zivo began in 2025, with compensation, at a fast-growing company that already counts more than ten acquisitions. In 2026, the partnership evolved to turn Sankhya's HR into an AI-native HR. In the context of the merit cycle, Zivo mapped where policy, salary data and approval authority created inefficiencies or stalled decisions, brought recommendations and co-built the solution with the people who make the cycle happen at Sankhya, each with their own experience and perspective. The Compensation & Benefits team defined the escalation rules and the retention risk criteria, the HRBPs were decisive in the logic of the approval levels, and the managers brought the view of the people who make the requests.

Together with the Compensation & Benefits team, a Zivo People executive brought these rules into the product experience, and the retention risk indicator and the promotion escalation reached the manager's screen in a format close to the spreadsheets they already knew. The product became the infrastructure of the cycle, and the Compensation & Benefits team is the protagonist, owner of the rules and the policy, who drives the platform with Zivo alongside.

O desafio

Every request went through the committee, with no clear visibility into the policy, the approval authority levels and the team's actionable data.

  • Cycle governance

    Every request on the committee's table

    Leaders' requests went straight to the committee, with no approval authority levels. After submission, the HRBPs and the Compensation & Benefits team checked the policy by hand, with no visibility into who had already checked what, and that created rework.

  • Experience and data-driven decisions

    Team data far from the moment of decision

    In the merit cycle, the manager recognizes who performed well and, when it applies, moves the person closer to the salary range for the role and to their peers. To decide, they needed to see right away each person's position in the range, the comparison with people in the same role, the retention risk and the policy guidance, and these indicators were not on his screen. Each manager built their own support spreadsheet and then retyped the requests into the tool Sankhya had used until then.

The system we co-built

Policy is checked in the system before submission, and the committee receives only what falls outside the rule.

  1. Compensation & Benefits

    Defines and maintains the cycle rules

    Policy, rules and approval authority levels live in the system, co-built with Zivo by this team and the HRBPs for Sankhya's context.

  2. Zivo People Executive

    Brings the retention risk and the staggering into the product

    Before the screen went live, Zivo's People executive brought into the product experience, together with the Compensation & Benefits team, the retention risk indicator and the escalation rule that this team had defined. If the promotion leaves the salary below the new band and the raise would exceed the cycle cap, it comes in two installments, until the person reaches the minimum of the new band.

  3. Leader

    Requests with on-screen guidance

    The manager sees the team with the policy guidance for each person and the retention risk, sets the priority and the move, and knows before submitting whether the request is within policy.

  4. Approval levels

    Validam e ajustam

    The request goes up through two approval levels, and the second sits with the executive team. Both validate and adjust. HRBPs follow each manager through to the final decision and record notes on the request, which show up for the validator alongside the manager's justification.

  5. Committee

    Reviews only the exceptions

    What's within policy keeps skipping the committee, which receives out-of-policy requests with the history of each step at hand.

Technology we co-build

The platform from the inside, in the screens the manager uses in the cycle and on the path of each request.

The leader's spreadsheet, with the policy built in

The co-built screen closely follows the spreadsheet the manager already used (the complexity of the rules stays behind the scenes). Each person on the team appears with the policy guidance, the retention risk, the priority and the move, and the manager knows right away whether the request is within policy or an exception. The step-by-step shows up on the screen itself.

Retention risk, with the math in plain view

The screen alerts the manager when there are people at high retention risk who still have no request. The indicator adds up four signals (time since last raise, position in the range, equity with peers and performance relative to salary), and the leader sees the math behind each level: alto, moderado ou baixo.

The history of each request, step by step

Each request keeps the path from submission to announcement: the two validations, the committee's decision and the adjustments made by the approval levels. Whoever validates can open, with one click, the manager's justification and the HRBPs' note on the request. The promotion with staggering shows up highlighted, noting that, in this example, the first installment doesn't reach the minimum of the new band.

Impacto entregue

In the very first cycle, the vast majority of requests closed before reaching the committee, with high satisfaction among the 100 leaders who rated the new way of proposing.

~75%
fewer requests at the committee: of the cycle's 370 requests, fewer than 100 needed to go there. In the previous cycle, all of them went through the committee.
97%
of the 100 leaders who answered the survey said they were very satisfied with the cycle.

In the band, the effect also showed up in the first cycle: some of the people who were below the minimum reached it, some for promotions with staggered increases.

The numbers are from the September 2026 cycle.

In the survey comments, the data and the experience of use showed up side by side. One leader wrote: “The way the data was structured, as well as the information and comparisons with others in the same role were excellent in helping us. Not to mention the experience of use: easy, fast and intuitive.”

On the rules inside the screen, another wrote: “I really liked the embedded rules and the per-professional recommendations, it brings a quick guidance on whom we need to prioritize on the team and broadens leadership's view.”

On the cycle routine, a third wrote: “I normally used support spreadsheets to organize this process, but this time it wasn't necessary.”

During the cycle, Zivo followed the Compensation & Benefits team and the HRBPs closely, and what the practice showed went into the platform while the cycle was still open. Today this team runs the platform and arrives at the next cycle with it tested on a real case.

What comes next

With the merit cycle live, Sankhya and Zivo are already talking about the next journeys.

While following the cycle, Zivo mapped opportunities on other fronts and has been working with Sankhya's leadership and different teams to transform the area through a vision of HR as a product, with the employee journey at the center.

How much of your merit cycle still goes through the committee?

Zivo co-builds and helps run the AI-native HR of Brazil's most innovative companies. In 30 minutes, we get to know how your cycle runs today and what would make sense to co-create from it.

Outros casos

More success stories.