Fichaloto

Adoption

HR software nobody has to be taught to use

Half of all HR rollouts fail for reasons that have nothing to do with what the software does: they fail because people do not use it. Fichaloto was built the other way round — first make it understandable, then make it do things — and that comes down to five concrete decisions you can look at one by one.

The cost nobody puts in the budget

The quote shows the licence and the implementation days. What it does not show is what you actually pay: the four training sessions you have to run twice because people did not turn up, the colleague who quietly becomes the internal help desk, and the six months where half the company still emails their hours in because “I can never find anything in there”.

The useful question is not whether the product is powerful. It is how many times somebody is going to have to ask how something is done, and who they are going to ask.

One · An assistant that explains the screen in front of you

It is a small window at the bottom left, behind the question-mark button. You ask it in your own words: “how do I add someone”, “I forgot to clock in”, “where do I export this”. It answers with numbered steps, a warning about whatever usually goes wrong, and a button that takes you to the right screen if it turns out to be done somewhere else.

It answers on the spot and does not open a ticket: what it knows is written down, screen by screen, and it does not depend on somebody being at the other end at eight on a Tuesday evening.

  • It knows what YOU can do. Every task declares which permission it needs. If your role does not reach it, it says so in one line instead of walking you through steps that would end on a “no permission” screen.
  • It does not look at your data. Not one person, not one hour, not one client, not one invoice: it queries no table of your company's. And it does not keep what you ask it, so there is no conversation history for anyone to have to look after.
  • The company hands it out, each person decides. It is granted by role under “Roles and permissions”, and whoever has it can switch it off once they find their way around.
  • In both languages, and it understands the question in whichever language it is typed.

Two · A guided tour over your own menu

The first time someone logs in, the tour opens by itself and points out the screens one at a time on their menu — not on a video of somebody else's company. And it only shows what that person can open: if their role does not reach the audit log, the tour does not show it. You can leave whenever you like and reopen it from the question mark in the sidebar.

Three · One single screen for people who only clock in

Of thirty people logging in each morning, twenty are not there to manage anything: they clock in and leave. For them a menu with fourteen entries is not help, it is clutter. The stripped-back view leaves them their clock and their button, and nothing else.

Nobody loses a permission: they simply stop being shown what they never use. It is one switch, you can untick it person by person, and it comes off with the same click.

Four · Three clicks to anything done daily

It is a house rule and it gets checked screen by screen: from the dashboard to any routine task, three clicks. Actions live where they are needed — on the row, on the card, on the figure itself — and not three screens further in. There is a global search across people, clients, projects and tickets from anywhere, and keyboard shortcuts for the things done every day.

And there are no dead ends: an empty list offers the button to create one, an error offers the way back, and a missing permission tells you who to ask for it.

Five · A manual you can actually read

Close to two hundred pages, in English and in Spanish, with real screenshots of every screen, numbered steps, which role can do what, and the common error messages with their cause and their fix. It downloads from inside the app, and it is updated with every product change rather than six months later.

There is a separate one for whoever administers the account, written to the same standard.

What this means on rollout day

That training stops being a prerequisite and becomes a convenience. You can run one hour with whoever will administer the account and let everybody else walk in on their own: the tour shows them where things are, the assistant explains how they are done, and the people who only clock in have nothing to learn because they see nothing else.

And that the questions which do come through are the good ones — “how do we set this up for our collective agreement?” — rather than the same three that burn out whoever answers them.

Frequently asked questions

Is the assistant an AI that reads our data?

No, and that is a design decision rather than a limitation. The assistant queries no table of your company's and sends nothing outside your installation: what it knows is how Fichaloto works and what your role lets you do. That is what makes it possible to switch it on for everybody without having to explain to anyone what it takes from their data, because it takes nothing.

What if we would rather our staff did not have the assistant?

It is handed out by role, like everything else. Some places would rather their people were shown things by their manager, and it comes off with one tick box. Whoever does not have it loses nothing: the manual and the guided tour are still there.

How much training is actually needed?

One session with whoever is going to administer the account, to set up the roles, the calendars and the working-time rules, which are decisions only the company can make. For everybody else, in practice, none: they log in, take the tour, and ask what they need as they need it.

Is it available in English?

All of it: the app, the assistant, the tour, the emails, the exported reports, the legal pages and the whole manual. And each person picks their own language rather than the company picking one, so in a mixed team everybody works in theirs on the same data.

Does it work properly on a phone?

Yes, and it is tested in that order: iPhone on Safari first, then desktop, then Android. People clock in from their phone almost every time, so a clock-in screen that stutters is a badly built screen even if it works.

And if somebody still gets stuck?

There is a button to tell us from inside the app, with the questions we need in order to fix it: what you expected, what happened, and how to reproduce it. It goes to the people who write the code, not to a general inbox.

Getting started

Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.

Keep reading