The first time a company looks at a full HR platform, the temptation is to switch everything on at once. In practice, that usually means no module gets implemented properly: people get overwhelmed, nothing gets fully adopted, and the rollout stalls halfway through.

A sensible priority order isn't about which module looks most exciting in a demo. It's about which problem is most urgent to solve at your company's current stage.

First: what's already a legal requirement

People and Time modules almost always come first, because they cover a reliable employee directory and time tracking, which has been mandatory for every company in Spain since 2019. Leave management usually follows right behind, because once you're past a handful of employees, tracking absences over WhatsApp or email stops scaling. These three modules are the foundation everything else sits on: without a reliable employee record, no performance or training module has good data to work with.

Next: what improves day-to-day management

Once the basics are covered, the next step is usually Climate — a quick two-question pulse is cheap to roll out and gives an early warning signal — and Analytics, so leadership stops requesting one-off reports and gets a single dashboard covering headcount, time, hiring and climate.

Later: what requires mature processes already in place

Talent — recruiting funnels, career paths and 360 performance reviews, training with auto-generated courses — usually gets switched on once a company already has hiring and development processes reasonably defined. Turning on performance reviews before job levels and objectives are actually clear tends to create more confusion than value: the system can support the process, but it can't invent it for you.

  • First: People, Time, Leave.
  • Next: Climate, Analytics.
  • Once the process already exists: Talent (recruiting, career, training).

There's an additional reason not to reverse this order: Analytics is only as good as the data it receives from the other modules. An executive dashboard covering headcount, time or hiring built on incomplete data — because People or Time have only been active for two months — gives a partial picture, not a broken tool. It's worth letting each module accumulate a few months of real data before leaning on its reports for major decisions. It's also worth not underestimating the cost of switching on too much at once: every new module means explaining to the whole team how to use it, and a company that launches three modules in the same month usually ends up with half-adopted versions of all three, instead of one that's properly embedded. Rolling out module by module, letting each one become a habit before adding the next, is slower on paper but much faster in practice. That's especially true for smaller teams, where the same handful of people are the ones expected to learn every new screen.

There's no universal formula — a company with high turnover might need Talent before Climate — but the underlying logic stays the same: prioritize the module that solves the problem you already have, not the one that reads best on a feature list.