Skip to content

Remote work · Projects · Team · CRM · Talent · Training · Invoicing

All of this, out of the box.
And whatever you are
missing, built for you.

From the first conversation to the paid invoice, all in one database: projects and people, CRM and talent pool, recruitment and training, invoicing, profitability and time tracking. And when something does not fit the way you work, it gets built. The code is ours, so every client ends up with their own.

The trial asks for no card and expires on its own. After that, no lock-in: the subscription renews and you cancel whenever you like. No headcount limit, and you talk to the people who build the product, not to a call centre.

  • Whatever configuration cannot reach, we build ourselves
  • Data held in the European Union
  • Support in Spanish, included
  • What margin each client leaves you, without building the spreadsheet
Hours used by project ACTUAL / PLANNED
Active
12
At the limit
3
Over
2
ERP migration620 h of 500 h
124 %
Annual audit182 h of 200 h
91 %
North refit312 h of 400 h
78 %
Client portal156 h of 300 h
52 %
Internal onboarding40 h of 120 h
33 %
Working On a break Unclosed yesterday Absence

A base, and your own on top

You start with all of this done.
Whatever is missing, we build.

No two firms work exactly alike, and a closed product forces yours to look like everybody else's. Not here: there is a large, proven base, and on top of it we build whatever you need. We write the code ourselves, so nobody else has to give permission.

What the base already does, from day one

No es una versión de entrada con lo bueno guardado para el plan de arriba. Es la plataforma entera de gestión de personas y de trabajo, y va entera: sin ediciones, sin extras y sin nada que haya que contratar aparte.

Projects, phases and tasks Time tracking Capacity and planning People, agreements and absences Documents and payslips Clients and legal entities CRM and sales pipeline Invoicing, payments and cash flow Profitability by project Recruitment and talent pool Your own careers page Training and certificates Time tracking and kiosks Tickets and support Reports, roles and audit trail REST API and bulk import

And on top of that, the configuration: the word you use for your work, your catalogues, your calendars, who approves what, and the reports you build yourself. That already settles most of the “yes, but we do it differently”.

And what is not, gets built. That simple

A screen that does not exist, a calculation using your formula, a report in the format your customer or your regulator demands, an approval flow that looks like nobody else's, an integration with the system you already run. Almost anything can be done. You tell us, and the order is always this:

  1. We check whether it is already a setting That happens far more often than you would think. If it does, you have it the same afternoon and it costs nothing.
  2. If it would help other firms, it goes into the product And then it is free or close to it. Half of what Fichaloto is today, somebody asked for first.
  3. And if it is only yours, it gets quoted The price and the timescale, in writing and before anything starts. You decide. What we do not do is promise a date before we have looked.

Whatever is built for you lives inside the same product and is maintained with it: it keeps getting the updates and the new blocks like any other account. There is no frozen copy of Fichaloto with your name on it, and no lock-in: your data comes out whole through CSV and the API whenever you want.

What is configured and what is built

New · Remote work compliance

Who works remotely, from where,
and whether it matched.

Spain’s remote working act requires the place of work to be set down in writing whenever someone works away from the office, and that ends up in a contract annex nobody ever opens again. Here each person declares it, the company approves it and the clock checks it on its own, every day, with nobody chasing anybody. And none of this replaces ordinary clocking in: every entry records whether it was on site, remote, at a client’s office or travelling. A company where nobody works remotely sees not one extra screen, and a hybrid one — which is most of them — runs both from the same place.

01

Each person declares it

On their own screen, inside Time management: street, postcode and town, written the way an address is written. No maps, no coordinates, no form anyone has to be talked through.

02

The company approves it

It lands under People, where it is approved or turned down with a reason. Until somebody looks at it, it checks nothing: were it live from minute one, changing your address on the day you clock in from somewhere else would be enough.

03

And the clock checks it

Each clock-in is compared with what was approved, and whether it matched is written down. Clocking in from another town blocks nobody: it notifies whoever runs the team, once a day, and that is all.

The team’s remote work YESTERDAY
Approved
21
Not declared
2
Out of area
1
Nerea O.Alcobendas · inside her area
8:05
Bruno G.Valladolid · inside his area
7:40
Celia N.waiting for approval
8:15
Rubén E.clocked in from another town
8:30

And what we do not do, which is the other half: what is stored is an area and a town, never anyone’s home address. An approximate point, good only for saying “it matches” or “it does not”. No continuous tracking, no screenshots and no looking at what anyone has open: the only remote working policy that ever gets signed is the one you can show the works council.

No home addresses No continuous tracking No screenshots, no keystrokes Clocking in is never blocked On site and remote, side by side

Everything in one place

Eleven things you live
in six different tools.

And that nearly always end up glued together with a spreadsheet only the person who built it understands. Here they are one database, so the numbers add up without anyone adding them up.

01 — PROJECTS AND ALLOCATIONS

The variance shows up in week 3, not on the invoice.

How much real time goes into each client, next to what you quoted. Every hour is logged to a project, every project has its hour bank and its cost, and the traffic light turns amber before the problem gets expensive.

Cost is not only hours: each person has their own hourly cost, which a specific project can override when they cost something else there, and expenses —subcontractors, licences, travel— are entered on the project itself and cut the margin exactly like hours do. And every figure opens: click the margin and you see the whole subtraction — which hours, whose, at what rate, and where each input is changed.

Hours per projectPhases and tasks VarianceCost per client Project expenses Cost per person
Client portal
52 %
ERP migration
124 %
North refit
78 %
Audit log
91 %

02 — PROJECT PLANNER

Timeline, board and calendar. And the real hours underneath.

The same project in four views, with no reloading: a list by phase, a timeline you drag with the mouse, a kanban board and a year calendar. The target date stays put when you move a bar, because comparing what was committed with what has been rescheduled is the only thing that shows the slippage.

Draggable GanttKanban Phases and milestonesHour approval

How the planner works

03 — STAFFING AND PLANNING

Know whether the project fits before you sign it.

Who is free in September, who has been overloaded since March, and which upcoming projects your current team cannot cover. With the hours you are short of put into a number, so you can decide whether to hire, subcontract or move the date.

Capacity by monthCoverage gaps Over-allocationUnassigned
Nerea A.
Iker T.
Olalla F.
Uncovered

04 — CRM AND SALES PIPELINE

Every live proposal, and whose court the ball is in.

Who is talking to whom, for how much, at what stage and what the next step is, with its date. Opportunities are not lost on price: they are lost to silence, and here what has stalled shows itself. Whatever was promised in a meeting — send a reference, confirm a lead time — is logged as a critical point with a due date and closed when it is done, not when somebody remembers.

And when they say yes, nothing is retyped: you review it on a confirmation screen — with a warning about similar clients that already exist — and the client and its project are created there and then. Dropping a card in the won column creates nobody: a drag can be a slip of the mouse.

Your own stagesNext action, with a date Critical pointsRadar Converts to client and project

How the CRM works

Contacted
86.000 €
Qualified
54.500 €
Proposal
31.200 €
Negotiation
18.400 €
Won
11.900 €
2 stalled over 3 weeks 4 waiting on the client

05 — INVOICING AND PAYMENTS

From logged hours to the invoice, without typing them in again.

From a project's details, “invoice this period” builds the draft with the billable hours already in it and you just review. Sequential series with no gaps, the document frozen on issue and chained to the one before. And the other half, the half that is usually missing: pull in the bank statement as CSV, Fichaloto suggests which transaction goes with which invoice and writes the reason beside it, and you confirm.

Sequential seriesCredit notes Bank reconciliationAged debt

How invoicing works

Not yet due
18.400 €
1 to 30 days
7.100 €
31 to 60 days
2.950 €
Over 60
1.180 €
3 transactions matched on their own 1 to check by hand

06 — PEOPLE MANAGEMENT

Each person's details in one place, not across three folders.

Details, working day, working calendar, collective agreement, time off, holiday and permissions by role. Who's in, who's out, who's back on Monday and how much holiday each person has left, without having to ask by email.

And their payslips, which stop living in your inbox: you drop in the folder of PDFs, Fichaloto matches each one to its person from the file name and tells them theirs has arrived, and every employee downloads theirs whenever they like, or a whole year as a zip for the bank. One less question every month of the kind only one person in the office can answer.

Details and working dayTime off HolidayPermissions by role Payslips as PDFBulk upload
22 active 3 on holiday 1 on time off 2 with no hourly cost 4 added this quarter
Holiday
61 %
Hours this month
92 %
August payslips
22 / 22

07 — RECRUITMENT AND TALENT POOL

From the vacancy to the payroll, without retyping a single detail.

Vacancies with their project, their site and their headcount, closing themselves once filled. A funnel with the stages you define, where whoever has been stuck for three weeks shows up without anybody reading the list. And a careers page of your own, with your name and your colour, where people apply themselves and land here with their CV attached to the record.

The thing almost no hiring tool does: when somebody accepts, they stop being a candidate and become a member of the team, with their role, their project and their allocation. From that minute they count towards capacity, they can log hours and they can clock in. And whoever did not get in is still findable two years later, with the reason they fell away written beside them.

Vacancies and headcountConfigurable funnel Searchable talent poolYour own careers page One-step onboarding

How recruitment works

312 in the talent pool English B2 · 41 people 2 stalled at screening

08 — LEARNING AND CERTIFICATES

Training rolls itself out, and proves itself with a certificate.

Your own courses, with their content and their exam, rolled out using the data already in here: to a team, to a site, to a job title, to whoever is on a project, or to the whole company. An assignment is a RULE and not a list of names, so whoever joins that group tomorrow gets it without anybody remembering, and whoever changes job title stops receiving what no longer applies.

On completion the certificate is issued automatically, with its code and its QR: whoever receives it — an auditor, a client, an insurer — checks from outside, with no account, that it is genuine. And whatever expires is reassigned on a fresh cycle without erasing the previous one. An auditor never asks whether you run training; they ask you to show who has it and since when.

Courses with an examLearning paths Assignment by groupVerifiable certificate Automatic expiry

How training works

Prevención de riesgos
23 / 25
Protección de datos
19 / 25
Bienvenida
25 / 25
Producto y procesos
12 / 25
3 expire this month 79% mandatory compliance

09 — TIME AND ATTENDANCE

People clock in here, and those hours land in the project by themselves.

One button on the dashboard: in, break and out. Every entry records whether it was on site, remote, at a client’s office or travelling, and if the company asks for it, clocking only works inside the work centre. Tablet kiosks for people who carry no work phone, schedules and shifts so you know what was owed, and “I forgot to clock” with approval, because a record everyone can edit at will is worth nothing as a record. And if people pick a project, those exact minutes land on it with nobody typing them in afterwards. And if they are on several, the clock asks which one: those hours are going to be charged somewhere, and the person who knows is the one starting work, not the one reading the margin at month end.

The record is not edited, it is appended to. Every clock-in, break, clock-out, correction and annulment is a new mark the database refuses to modify or delete, chained with a fingerprint that gives it away if one is missing or a value was changed. There is a button to check the chain, and you press it, not us: a record only its keeper can verify verifies nothing.

In, break and outOn site or remote Geofencing with a radius Kiosks with a PINSchedules and shifts Pours into the project Tamper-proof record Simplified view

And how remote work is tracked

Monday
8:05
Tuesday
7:20
Wednesday
9:40
Thursday
8:15
Friday
6:10

10 — TICKETS AND SUPPORT

What has broken and what you have been asked for, without leaving here.

Incidents and requests with the conversation right beside them, their statuses — yours, not ours — and their SLA hours by type. Every comment and every status change asks who should be emailed, with the participants already ticked: neither telling everyone every time, which ends up in a folder nobody opens, nor telling nobody, which ends up in tickets that die of silence. And because the ticket lives where the client and the project already live, you can finally answer how many hours go into looking after each of them.

Your own statusesNotify who you choose SLA by typeBoard by column

How ticketing works

11 — CONFIGURATION AND BESPOKE WORK

The same platform, in your own words and your own rules.

If your company calls them cases rather than projects, the whole application says cases. Statuses and billing types are catalogues you maintain yourself, so are working calendars and collective agreements, and who approves hours and time off is your decision, not ours. All of it from inside the application, without asking us and without anyone writing a line of code.

And where configuration stops, we start. What you buy is a proven base, not a ceiling: the code is ours, there is no vendor on the other side of the world owning the roadmap, and almost anything can be built for your case — a screen that does not exist, a calculation using your formula, a report in your format, an approval flow that looks like nobody else's, an integration with the system you already run. We look at it, we tell you what it costs and how long it takes, and we build it. What we do not do is promise it before we have looked.

Your vocabularyYour own catalogues Approval flowsReports you build yourself Bespoke developmentWe own the code

What is configured and what is built

Project Case Site Client
Statuses
4
Time off
10
Calendars
3
Roles
6
Hours · approved by the manager Time off · approved by HR

In more depth: project management, time entry, team planning, CRM and sales pipeline, invoicing and payments, billing plans, recruitment, candidate database, careers page, employee training, mandatory training compliance, time and attendance, ticketing and, by sector, architecture practices, engineering firms and consultancies.

Far more than “who clocked in when”

What you want to know
on a Monday morning.

Four questions that today cost you half a morning of phone calls and spreadsheets. Here they are four screens, with yesterday's data.

01

Who is swamped and who has room?

Each person's capacity, month by month, with a warning when someone goes past 100%. Not the project manager's hunch: committed hours against that person's real working day.

Capacity per person

02

Which project is eating the hours?

Actual against budgeted hours, project by project. The one heading for an overrun turns amber before it overruns, which is while you can still do something about it.

Hours variance

03

Does the project I am about to sign fit?

Demand from what is already committed against your current team's capacity, month by month. The hours you cannot cover come out as a number, not a hunch, and early enough to hire or move the date.

Coverage gaps

04

What does this client really cost me?

Actual hours times their cost, project by project and client by client, without waiting for month end. Sometimes the surprise is not the client who complains: it is the one who never complains and has been losing you money for two years.

Cost per client
Team capacity AVERAGE · 6 MONTHS
Capacity
94 %
Over-allocated
3
Room to spare
5
Asier D.over their working day since January
128 %
Iker T.peak in February and March
122 %
Olalla F.at the limit in June
97 %
Bruno G.room until September
71 %
Variance by project ACTUAL / PLANNED
Active
12
At the limit
3
Over
2
ERP migration620 h of 500 h
124 %
Annual audit182 h of 200 h
91 %
North refit312 h of 400 h
78 %
Client portal156 h of 300 h
52 %
Uncovered demand HOURS PER MONTH
Uncovered
418 h
Coverable
3 of 5
Profiles
2
Septemberthe team reaches 88%
62 h
Octoberthe team reaches 71%
134 h
Novemberthe team reaches 64%
158 h
Decemberthe team reaches 92%
64 h
Margin by client HOURS × COST
Clients
9
Loss-making
2
Average margin
21 %
Northern Client1,240 h logged
+34 %
Ribera Group890 h logged
+18 %
Delta Industrial1,510 h logged
+3 %
Amber Services2,060 h logged
−11%

Teams, people, projects, milestones, coverage gaps, holiday and an executive summary. Every view fits the terms you use, not the ones in someone else's catalogue.

Who opens this in the morning

The same hour,
four different jobs.

One clocked hour serves the person running projects, the person out on site, the person who has to account for a grant and the person checking whether a client is worth it. These are not four programs: it is the same record answering four questions.

A woman in a blazer smiling as she works at a laptop beside an office window.
Team at 94%

Runs projects at a consultancy

She checks workload before the Monday meeting. If someone is heading past 100% in March she sees it in February, which is while there is still time to move something.

A man in a hard hat and high-visibility vest checking a tablet on a building site.
Clock-in 07:58

Runs a building site

He clocks in from the tablet out on site, with the work centre already set. Nobody rings him from the office to ask who turned up today.

A woman in glasses going over a drawing spread across the table of a technical practice.
14 h to the case file

Engineer at a technical practice

She books her hours to the right case file the same day. When the grant paperwork comes round there is no need to reconstruct six months backwards.

A grey-haired man going through a paper file at his desk, with ring binders behind him.
Margin 31%

Runs a professional firm

He sees what each client really costs without waiting for the month-end close. Sometimes the surprise is not the one who complains: it is the one who never complains.

For the people who only clock in

And a fifth person
who wants to see none of this.

Of the thirty people who log in each morning, twenty are not there to manage anything: they clock in and leave. For them, a fourteen-item menu is not help, it is clutter. Turn on the simplified view and they see one single screen: their clock and the button. Nothing else.

It is a switch in Roles and permissions, off by default, and it only applies to people who hold the member role and no other. Underneath you get the list of those people with a tick box each: there are almost always three or four who do come in to check their monthly hours, so you untick them and they carry on seeing the whole of Fichaloto.

Nobody loses a single permission: they simply stop being shown what they never use. And you switch it off whenever you like, with the same click.

No side menu Person by person In, break and out “I forgot to clock in” In Spanish and English

Help right on the screen

And someone to ask
without leaving where you are.

The on-screen assistant is a little window that tells you what can be done on the screen in front of you and how to do it, step by step. It isn't a support chat that opens a ticket and leaves you waiting: it answers on the spot, because what it knows is written down, screen by screen.

The question people ask in front of a screen is always much the same: “how do I add someone?”, “I forgot to clock in”, “why won't it let me delete this”. The assistant answers those, with numbered steps and a warning about whatever usually goes wrong, plus a button that takes you there if it turns out to be done on another screen.

And he knows what YOU can do. If your role doesn't reach something, he won't walk you through steps that would end on a “no permission” screen: he tells you in one line who to ask. What he says comes from your own permissions, task by task.

In Spanish and English Bounded by role Everyone turns it on or off Without leaving the screen

It doesn't 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 doesn't keep what you ask it. It lives inside your installation and sends nothing to anyone.

The decision, in one table

Excel, a generic suite or Fichaloto.

No tricks: there are companies for which Excel is still the right answer, and there are requirements a large platform covers better today. This is what changes in each case.

A comparison of running things on a spreadsheet, on a generic HR suite and on Fichaloto
  Spreadsheet Generic HR suite Fichaloto
Working time records SpreadsheetCompliant if it is daily and per person, but you cannot prove it was never rewritten Generic HR suiteYes, time-stamped FichalotoBuilt in and append-only: a correction is a new entry, never a deletion
Hours per project SpreadsheetBy hand, and only if someone writes them down Generic HR suiteA separate module, almost always paid for FichalotoIn the base. With the clocking alongside to check against, if you switch time tracking on
Variance against budget SpreadsheetWhenever someone rebuilds the sheet Generic HR suiteDepends on the module you bought FichalotoIn real time, with a traffic light
Who comes free, and when SpreadsheetNo Generic HR suiteThey look backwards: where the time went, not who frees up FichalotoIn the base, and forward-looking: weeks 1 to 12 with absences already deducted
Fits your process SpreadsheetAs much as you like, and that is the problem Generic HR suiteWithin what the configuration allows FichalotoVocabulary, catalogues, calendars, permissions and approvals, and you run them yourselves
Minimum billable people Spreadsheet— Generic HR suiteCommon, and almost never published FichalotoNone
Connecting to your ERP or dashboard SpreadsheetCopy and paste on Tuesdays Generic HR suiteDepends on the vendor's connector catalogue FichalotoOpen REST API over the same entities as the screen, no third-party connector
Permissions and traceability SpreadsheetWhoever opens the file sees everything Generic HR suiteFixed, closed profiles FichalotoPer resource and action, everything audited, plus a report explaining why this person sees that
Who you call when it breaks SpreadsheetWhoever built the spreadsheet, if they still work here Generic HR suiteA ticket queue FichalotoWhoever writes the code
When it makes sense SpreadsheetFewer than 5 people and one project at a time Generic HR suiteIf what you need is payroll and recruitment, and project work isn't how you operate FichalotoTeams that work by project or by client, with no headcount limit

Permissions, audit trail and integrations

Who sees what, who did what
and what it connects to.

They are the three questions that come up when the conversation moves from “we like this” to “let's sign this”. Here they are answered before anyone has to ask.

01 — PERMISSIONS BY ROLE

Hourly cost stays hidden from anyone who shouldn't see it.

Permissions are not three fixed tiers. They are handed out resource by resource and action by action, so a role reads the way you would say it out loud: «sees their projects and their people’s tasks, approves their hours, and nothing at all on profitability». Five come built in —administrator, manager, employee and two for the API— which can be tweaked and put back the way they came, roles can be duplicated to start from one that nearly fits, one person can hold several, and their own data is always visible without configuring anything.

And there is a report that answers the question people actually ask: «why can this person see that?». Because roles stack, looking at them one by one never tells you; the report resolves the sum person by person and downloads as Excel, with the matrix, the detail and what each role grants.

ReadWriteAmend ApproveDelete Built-in roles Excel report
Projects
All
Team hours
Approve
People
Read
Costs
No
Roles can be duplicated Several roles per person

02 — AUDIT TRAIL AND GDPR

Anything that changes something leaves a record.

Every addition, correction, approval and deactivation is stored with the person, the date, the IP address and the reason. When someone in administration helps another person by acting on their behalf —without asking for their password, which is the real alternative— the log says both things: who pressed the button and on whose behalf. The data lives on servers in the European Union, encrypted in transit, and every read of someone else's data goes through the company identifier: one client's data never shows up on another client's screen.

Full audit logServers in the EU Encrypted in transitScoped by company
14:02
Hours OK
14:05
Cost
14:11
On behalf of…

03 — NATIVE REST API

It connects to what you already have, with no middleman.

Forty-seven entities in the application —clients, legal entities, people, teams, projects, phases, tasks, milestones, calendar, time off, time entries, opportunities, tickets, invoices and every catalogue— can be read and written from outside through a REST API over JSON. You get in with a key created from inside the application itself, read-only or read and write, and it can never do more than the person it belongs to: the permissions you have already configured apply to integrations too. Every write goes into the audit log with the name of the key, and the key is revoked in one click the day that programme stops being used.

And a key on its own does not get in. Both things are needed: the key, and a role on its owner that allows using the API — a box somebody has to tick on purpose. Being an administrator is not enough: the API is a different door, a program walks through it, and opening it has to be a decision rather than a side effect. If it is missing, the response says exactly what is missing and where to fix it.

JSON over HTTPSRevocable keys Read-only or read and writePer-minute limit API permission is separate
GET
/proyectos
GET
/imputaciones
PATCH
/clientes/12
ERP BI dashboard Invoicing Your own tools

04 — A RECORD THAT IS NEVER REWRITTEN

You run the check, not us.

Clocking in is one row. The break is another. Clocking out is another. Nothing is updated and nothing is deleted: a correction is a new entry pointing at the previous one, recording who signed it and when, and both remain. The hours on screen are not stored anywhere — they are calculated by reading the facts, the way an platform balance is the sum of its movements.

Every entry carries the fingerprint of that person's previous one, so if somebody emptied the table and rewrote it, the chain would not add up. And verification is not a certificate we show you: it is a button inside your own platform reporting how many entries it read, how many have altered content, and exactly where the chain breaks. A record only the vendor can check does not prove very much.

Append-onlyFingerprint chain Customer-run verificationSigned corrections
08:02
Clock in
13:10
Break
17:30
Corrected
Chain intact

Why we can do this

Our own team, our own code,
and nobody in between.

Fichaloto es una plataforma de personas, horas y proyectos, y va entera desde el primer día: gente, clientes, proyectos, imputación de horas, ausencias, capacidad, facturación, rentabilidad, informes, roles y auditoría, y con ellos el control horario, el CRM, el reclutamiento con su base de talento, la formación, el ticketing y la API. Sin ediciones, sin extras que aparecen a mitad de la venta y sin licencias de terceros: el código es nuestro, así que lo que pedís se puede hacer.

01

Configurable

The wording, the catalogues, the calendars, the permissions and who approves what. You run it yourselves, from inside the application.

02

Direct contact

When you call, you speak to someone who knows the code, not a switchboard that opens a ticket.

03

We listen

Improvement suggestions are looked at one by one. The ones that help more than one company go on the roadmap, and because we are a small team they get there soon.

04

Support

Included, in Spanish, with the person who already knows your setup.

05

Pricing

You pay for the base and the blocks you switch on. No licences you never use and no surprises for an extra seat mid-year.

06

Integrates

An open REST API over the same entities you see on screen. Your ERP and your dashboard read and write here.

Pricing

A quote,
not a price list.

No publicamos una tarifa por persona porque casi nunca es lo que os conviene: según el tamaño del equipo, sale mejor una cuota cerrada. Y la cuota no depende de cuántas casillas marquéis, porque no hay casillas: entra la plataforma entera, y lo que se ajusta es el tamaño. Nos lo contáis, os pasamos la propuesta por escrito y decidís. Catorce días de prueba antes, sin tarjeta.

Fixed monthly fee

Tailored

Agreed in view of your case: how many people will use it, what you actually need and which blocks you switch on. One fee, no tiers and no basic features held back for the plan above.

Request a quote

We reply within one working day with the proposal in writing. Before that, fourteen days to try it, no card.

Entra la plataforma entera.

  • People, teams, working agreements and hour banks
  • Absences, holidays, public holidays and work calendars
  • Clients, projects, phases, tasks and time logging
  • Capacity, coverage gaps and allocation planning
  • Invoicing, payments and profitability by project and by client
  • Reports you build yourselves, import and export
  • Roles, approval circuits and an audit trail
  • Setup, staff import and support in Spanish

Y esto, que otros cobran aparte.

  • Time tracking Clocking in from the phone, the computer and the kiosk, with a signed, untouched working-time record. Working patterns, shifts and the weekly grid.
  • Sales pipeline The opportunity funnel, from first contact to client, with its stages and its history.
  • Recruitment Vacancies, an application funnel, a talent pool searchable by skills, and a careers page of your own.
  • Learning Courses with an exam, learning paths, assignment by group, a verifiable certificate and a compliance figure.
  • Ticketing Incidents and requests with their conversation, their board and who handles them.
  • API and integrations An open REST API over the same entities you see on screen, with revocable keys.

They are switched on and off whenever you need, and the fee follows. Switching one off deletes nothing: its data stays and comes back whole the day it is contracted again. How modular works

And whatever else you need, built to order.

The base is a starting point, not a ceiling. The code is ours, so a screen that does not exist, a calculation using your formula, a report in the format your customer demands or an integration with the system you already run can all be built. We check first whether it is already a setting — it often is — and if not, you get the price and the timescale in writing.

No minimum number of people

You pay for the people who use the platform. If there are nine of you, you pay for nine.

No set-up fee

Getting started and importing your headcount are included.

No lock-in

The trial expires on its own. After that, cancel the subscription whenever you like, with no penalty.

Bespoke development

Whatever configuration cannot reach gets built, with price and timescale in writing before anything starts.

Is it right for your company?

If any of this sounds familiar.

It does not have to be all of them. Two or three is enough to notice the difference in the first month.

Part of the admin still runs on a spreadsheet only one person understands.
The working-time record lives in one place and the hours spent on each project in another.
You do not know whether a project made money until it is already over.
Someone forgets to clock out and nobody notices until the end of the month.
You have people on site, at home and in the office, and each place clocks in differently.
Holiday is requested over WhatsApp and written into a shared calendar.
When new work comes in, deciding who does it means asking around the office.
Someone asks you to account for hours per project —a grant, an audit, a client— and they have to be pieced back together.
You invoice by the hour and those hours do not come from anywhere you could show.
You have several tools that don't talk to each other.
The software you have does not fit the way you work, and changing it is not up to you.
You pay licences for features nobody ever opens.

It fits companies that work by project, by site, by case file or by client: engineering firms, consultancies, technical practices, installers, agencies, professional practices and service companies. No headcount limit: what decides the fit is how you work, not how many of you there are.

Half an hour looking at how you work is worth more than a list of features.

We show you the platform with your own data, work out how you do things and tell you straight what could be improved, automated or simplified. That half hour usually turns up two or three things you can fix the following week, whatever you use afterwards.

We listen

Missing something?
Tell us, and it goes on the roadmap.

Inside the application there is one button to tell us something is broken and another to ask for something that cannot be done today. They do not open a ticket at a switchboard: they reach the same people who write the code. We read everything and we always reply, even when the answer is no.

01

You tell us without leaving the application

Two forms with exactly the right questions: what you expected, what happened and how to repeat it for a bug; what you would like to be able to do and what problem it solves for an improvement. Whoever administers the platform decides who on your team can do it.

02

We read them one by one, and we reply

There is no form quietly feeding an inbox nobody opens. Every suggestion gets an answer saying what we decided and why: accepted with a date, accepted without a date, deferred, or turned down. A “no” with a reason is worth more than a polite silence.

03

What comes up repeatedly gets built soon

Anything that helps more than one company moves up the roadmap, and being a small team it lands in weeks rather than in next year's cycle. Half a dozen screens everybody uses today started life as one client's request.

Why this matters

3,1million
Unpaid overtime hours every week

Of the 7.2 million hours of overtime worked in Spain every week, 43% goes unpaid.

CCOO, on the INE Labour Force Survey · Q2 2026

7.500€
Maximum fine for not keeping the record

Serious infringement: from €751 to €7,500 per workplace. Falsifying the record goes up to €225,018.

LISOS arts. 7.5 and 40.1

4years
Records must be kept

Available to the workforce, to their representatives and to the Labour Inspectorate, since May 2019.

Article 34.9 of the Spanish Workers' Statute

14days
Free trial, no card

No card and no lock-in. If it turns out not to fit, the trial expires on its own and absolutely nothing happens.

Fichaloto

Frequently asked questions

What people ask us before the demo.

Answered properly, with the rule and the figure alongside. If your question isn't here, write to us and we'll add it.

To start with

What is Fichaloto?
Fichaloto es una plataforma española de recursos humanos, control horario, gestión de proyectos y planificación de equipo, pensada para empresas que trabajan por proyecto o por cliente, sin tope de plantilla. Se ficha dentro de Fichaloto —entrada, pausa y salida, con ubicación, centros de trabajo, kioscos en tablet y turnos— y en la misma pantalla están la ficha de cada persona, las horas dedicadas a cada proyecto y cliente, y la capacidad libre del equipo. Es modular: cada empresa enciende solo los bloques que usa. La desarrolla y opera NUDAYOSH, S.L., desde Madrid.
What size of company is it meant for?
How you work decides it, not how many of you there are: it fits best in companies that bill or justify their time by project or by client — consultancies, engineering firms, technical practices, installers, agencies, professional practices and service companies. There is no headcount limit, and every listing has search, filters and pagination precisely so it still reads well as the team grows. Below five people plenty of firms get by with a spreadsheet and that is fine. And if you are several hundred, write to us before you sign up: we would rather tell you up front what is solved and what would need adjusting than have you find out halfway through.
How is Fichaloto different from other HR platforms?
En cuatro cosas concretas. Primera: se configura hondo y sin tocar el código —el vocabulario de la casa, los permisos recurso a recurso y acción a acción, los catálogos, los calendarios laborales, quién aprueba qué y los informes— y esa configuración la lleváis vosotros, sin pedirnos nada. Segunda: la imputación de horas a projects, la capacidad del equipo, el CRM, el reclutamiento, la formación, el control horario, el ticketing, la API, la facturación y la rentabilidad van TODOS dentro: no hay ediciones, ni extras, ni una función guardada para el plan de arriba. Tercera: se integra con lo que ya tenéis mediante una API REST abierta —clientes, personas, projects, tareas y ausencias en los dos sentidos, y las horas imputadas de salida— sobre las mismas entidades y las mismas reglas que la pantalla, sin conectores de terceros ni intermediarios. Y cuarta: cuando llamas hablas con quien escribe el código, en castellano y sin centralita.

What the law says

Is time and attendance recording compulsory in Spain?
Yes. Since 12 May 2019, article 34.9 of the Spanish Workers' Statute, introduced by Royal Decree-Law 8/2019, requires every company to record the start and end of each person's working day, to keep those records for four years, and to keep them available to staff, their representatives and the Labour Inspectorate. The law does not impose a particular medium: paper or a spreadsheet are still valid today if the record is reliable and tamper-proof. A royal decree on digital time recording is going through the process and would tighten these requirements, but as of today it has not been published in the official gazette.
What is the penalty for not keeping time records?
Failing to keep the working-day record is a serious offence under article 7.5 of the Spanish law on labour offences and penalties (LISOS). Under article 40.1 of the same text the fine runs from €751 at the lowest grade to €7,500 at the highest, and it applies per workplace. Falsifying the record is a very serious offence, with fines from €7,501 to €225,018.
Is a spreadsheet enough for the working-time record?
Today, yes, with conditions. Article 34.9 of the Spanish Workers' Statute does not impose any particular medium: it requires the record to be daily, to capture the start and end of each person's working day, to be kept for four years and to be available to the workforce, their representatives and the labour inspectorate. A spreadsheet can meet that. The problem arrives when you have to prove it has not been touched: a file anyone can open and rewrite without leaving a trace is hard to defend before an inspection, and falsifying the record is a very serious offence. There is also a royal decree on digital time recording in progress which, if published, would tighten these requirements. In Fichaloto every mark is chained to the previous one with a fingerprint, so the series can be shown to be complete and untouched.
Do people have to clock in when working from home?
Yes. Article 14 of Spain's Law 10/2021 on remote work says explicitly that people working remotely must record their hours exactly as those who go into the office do, showing the start and the end. There is no exemption for working from home. In Fichaloto you clock in from your phone or your computer, and the account decides whether location is required and whether people can clock in away from a work site: for remote work, usually yes.
How are overtime hours kept in check?
With the same record. Article 35.5 of the Workers' Statute requires overtime to be totalled monthly and a copy of that summary given to each person; article 35.2 caps it at 80 hours a year, not counting hours compensated with time off within the following four months or those worked under force majeure. What it takes to keep them in check is comparing what was clocked against the working day each person is due, and that comes from the schedule and the collective agreement on their record. In Fichaloto the weekly grid shows the schedule on top and what was clocked underneath, day by day, so the excess shows up while it can still be compensated and not once it is already eighty.
How long do working-time records have to be kept?
Four years. Article 34.9 of the Workers' Statute says so, and throughout that time they must be available to the workforce, their legal representatives and the labour inspectorate. That is a practical reason not to keep them on loose sheets: three years on, the hard part is not having the data but finding it. In Fichaloto the record is searched and exported by person and by period, and it is not deleted when someone leaves.
What if someone refuses to clock in?
Clocking in is not optional for either side: the company is required to keep the record and the person is required to have their working day recorded. Refusing repeatedly is a breach handled through whatever disciplinary route the collective agreement sets out, but before getting there it is worth asking why: almost always the system is in the way — you have to log in to a computer someone else is using, the app asks for permissions that feel intrusive, or location fails in a unit with concrete walls. That is why Fichaloto lets people clock in from a phone, from a computer and from a tablet kiosk with a code, and location can be required or not depending on the site.
What is the difference between time recording and access control?
Time recording is the legal obligation: registering the start and end of each person's working day, every day, and keeping it. Access control is a broader idea with no regulation of its own: knowing who is on a site, usually with turnstiles, cards or fingerprints, and it normally answers a security or access need rather than an employment one. They get confused because many devices do both, but only the first is required by law and only the first has to be shown to an inspection. Fichaloto does time recording.

How clocking in works

Do people clock inside Fichaloto, or is another program needed?
Inside. There is a button on the dashboard — in, break and out — and a “Clock” screen with the whole week: what you clocked against what you owed, day by day. People clock from a phone, from a laptop, or from a tablet kiosk with a four-digit PIN if they carry no work phone. No separate app to install and no terminal to buy.
Can people clock in from their phone?
Yes, and it is the most common way. The clocking screen works in a phone browser with nothing to install: in, break, back, out, with the project the day goes to if the account asks for it. If the site has coordinates and a radius, the phone sends its location when clocking and the mark keeps the distance; if not, clocking still works. And for anyone without a company phone there is the kiosk: a tablet fixed by the entrance where each person types their code.
Can we require people to clock only from the work centre?
Yes, with the radius you choose. Every work centre has its coordinates and its radius — 100 metres for an office, 500 for a building site, where the signal is worse — and when someone clocks, the location the browser gives is compared against that radius. You can either refuse a clock-in from outside or let it through and flag it, which is what we recommend: blocking looks stricter and strands the person at a customer's office or with poor coverage, while flagging gives you the same information plus a list to review. Clocking out is never blocked. On top of that, each company in the group can tighten the rule on its own, but not loosen it. And wherever people clock, the IP and the city they clocked from are always recorded.
Can time recording cover several work centres?
Yes, and it is one of the reasons people set it up. Each site is registered with its address, its coordinates and its radius, and it can belong to the account, to a company in the group or to a client — the works, or a client office where someone is posted. Each person can have one or several. It also matters because the penalty for not keeping the record applies PER WORK CENTRE: with four sites, the same offence is multiplied by four.
Can shifts and schedules be planned?
Yes. You write named weekly patterns — “Split-shift office”, “Afternoon shift” — with two slots per day, which is how the Spanish split shift works, and put fifteen people on one in a single go. On top of that sits the weekly grid: one row per person, one column per day, and in every cell the schedule on top and what was clocked underneath, because the question is never one of the two on its own but whether they match. One day is changed by tapping its cell, without touching anyone's pattern, and next week is set up by copying this one.
What if someone forgets to clock out?
An entry with no clock-out stays open and counts as zero hours worked, which is what makes it noticeable. The next morning an email reaches whoever left it open, and whoever reviews the team's entries sees it in amber at the top of their screen. Fixing it is not something you do yourself: you ask from the “Clock” screen, saying what time you left, and someone with permission approves it; on approval the entry is actually created and signed with who did it and when. A working-time record everyone can edit at will is worth nothing as a record, and the first thing any inspection asks is who changed what.
Can the working-time record be changed afterwards?
No, and that is exactly the point. In Fichaloto the record is not edited, it is appended to. Every clock-in, break, return, clock-out, correction and annulment is a new row the database itself refuses to modify or delete. Correcting a time does not rewrite the original: it adds a mark saying which one it replaces, and both stay, with who signed it and when. Deleting a day does not delete it either: it adds an annulment, so the day stops counting but the record still shows it existed. And every mark carries the fingerprint of the previous one for that same person, chained with a secret that appears on no screen and in no export: if somebody emptied the table and rewrote it, the chain would not add up. There is a button to check it that you press, not us, and it says how many marks it read, how many are altered and how many are missing.
Do we need another tool for the legal time record?
No. El control horario de Fichaloto es completo por sí solo: entrada, pausa y salida con ubicación, centros de trabajo, kioscos en tablet, turnos y solicitudes de corrección con aprobación y firma. Los apuntes no se editan: se corrigen pidiéndolo, y cada corrección queda trazada con quién la pidió, quién la aprobó y qué decía antes. Si ya ficháis en otro sitio, no pasa nada: el fichaje se apaga desde vuestros propios ajustes y el resto de la plataforma funciona igual.

Hours, projects and money

Can I see how many hours go into each project and each client?
Yes, and it is the reason the product exists. Every logged hour is tied to a project, and every project to a client and an hours budget. If a project is picked when clocking in, the exact minutes on the clock land on it by themselves, with no rounding to the quarter hour and with nobody writing them down afterwards; and if not, clocked hours sit next to logged hours so you can see how much of what was clocked has been logged and how much has not. The project record compares real hours against estimated ones at all times and flags the deviation with a traffic light, so a project running over shows up in week three and not on next month’s invoice.
Can I tell whether my team is clocking the hours I planned?
Yes, and it is one of the reasons both things live in the same database. If you plan somebody full time on a project, you can see what they actually clocked against what was planned, per person and per week. And when clocking in, anybody on several projects picks which one those hours go to —anybody on just one has it preset— so clocked and charged stop being two separate acts with three days and a rounding error between them. What we do not do, and will not do, is log keystrokes, take screenshots or count idle time: we measure the work, not the worker.
Is a project’s cost just the team’s hours?
No, which is why both are declared. Each person has their own hourly cost, which a particular project can override when they cost something else there —a senior profile on loan, a rate agreed with that client— and separately you record the project expenses: subcontractors, licences, travel, materials. They cut the margin exactly like hours do and appear on the same screen, so the number you look at on a Tuesday is the one you will see at the bank. And every figure opens up: click the margin and you see the whole subtraction —which hours, whose, at what rate, which expenses— and where each part is changed. A metric that will not explain where it came from gets argued about in every meeting.
How do you know whether a project is profitable?
By comparing what it cost against what was charged, and that needs both halves. The cost comes from the hours logged multiplied by each person's internal hourly cost, plus any expenses booked to the project; the income, from what was quoted and what was invoiced. Fichaloto shows it by project and by client, with the gap between the hours planned and the hours actually spent, and a traffic light when consumption approaches the budget. What changes things is not the final number but when you see it: in month three of a six-month project there is still something you can do.
Can hours worked be invoiced to a client?
Yes. Approved hours logged to a project become invoice lines, with their sequential series, their VAT and withholding, their period and their PDF. Once issued an invoice cannot be changed: to correct it you issue a credit note, which is what Spanish invoicing rules require. It is then reconciled with the bank by uploading the statement, and a paid invoice marks itself when its payment matches.
How do you account for hours on a grant-funded project or an R&D tax credit?
What an auditor or a funding body asks for is the same in every case: who worked, on what day, how many hours, on which project or activity, and how that relates to that person's working-time record. The hard part is almost never having the hours: it is being able to show them squaring with the recorded working day, without one day showing nine hours logged and seven clocked. In Fichaloto both live in the same database and are seen side by side, they export by person, project and period, and the working-time record is chained and signed, so the logged hours rest on something that can be audited. Fichaloto does not file the claim for you and does not replace your adviser: it gives you the data the claim is built from.

People and their permissions

Can holiday and time off be handled in the same place?
Yes. Each person requests their days from their own screen, sees what is left of their allowance and who the request goes to; whoever approves answers from a queue, and on approval those days come off capacity in the planning views, so they stop showing as available. Absence types are a catalogue each company maintains — holiday, personal days, medical, training, whatever their collective agreement uses — each with its own rules on whether it draws down an allowance, whether it needs approval and whether it counts as a working day.
Can I decide who sees what inside the platform?
Yes, and in real detail. Permissions are not three fixed levels: they are granted resource by resource — projects, people, hours, costs, reports, audit trail — and action by action: read, write, amend, approve or delete. With that you build roles such as “project manager who sees the hours used on their own projects but not the profitability” or “administrator who logs everybody's hours but approves none”. Roles can be duplicated so you start from one that nearly fits, one person can hold several at once, and their own things — their hours, their holidays — are always visible without configuring anything.
What about people who only come in to clock in? Is there something simpler?
Yes: the simplified view. You turn it on from Roles and permissions, and anyone it applies to logs in and sees a single screen — their clock, the clock-in button, the break and “I forgot to clock in” — with no side menu and no other screen at all. It only applies to people holding the member role and no other, and on top of that you choose person by person: the same screen lists those people with a tick box each, because there are almost always three or four who do come in to check their monthly hours. Nobody loses a single permission: they simply stop being shown what they never use, and you switch it off whenever you like.
Can I log in as another person to help them?
Yes, and it sits behind its own permission rather than behind being an administrator. Whoever holds it can log in as if they were another person, see exactly what that person sees, and fix something for them without asking for their password — which is the real, and bad, alternative. Everything done inside is recorded in the audit trail under the name of whoever opened the session, not the person. And someone who does not administer the account cannot log in as someone who does: if they could, this permission would be the back door to every other one.
Can I see, person by person, exactly what permissions they have?
Yes, in a report built for it. Roles stack —somebody holding two can do the union of both— so looking at them one at a time never shows what a person can actually do. The report resolves that sum person by person, using the same code the application uses to decide on every screen, and downloads as Excel with three sheets: a matrix of people against permissions, the line-by-line detail, and what each role grants. It sits behind its own permission, because knowing what everybody can do is exactly the map somebody would want before doing something they should not.
Is there a record of who does what?
Of everything that changes something. Every creation, amendment, approval and deletion goes into the audit trail with the person, the date, the IP address and the reason where there is one. And if an administrator acts on somebody else's behalf to help them — without asking for their password, which is the real alternative — the record says both things: who pressed the button and on whose behalf. That is the difference between a log that explains what happened and one that is only good for arguing.

Getting it running

How long does it take to get Fichaloto running?
The account is created in minutes and your headcount is imported in one go. What takes time is not the setup, it is agreeing what you call things: what a project is, what a phase is, and who sees what. In a mid-sized company that is settled in one or two sessions, and from there people clock in and log hours.
Can we migrate from another clocking system or from a spreadsheet?
Yes, and it is the first thing you do. You upload the clocking history in a file — one row per day, with its in and out — and it comes in as marks, flagged as imported so they are told apart from those clocked here. Same for people, clients, projects, logged hours and calendars: fifty-six tables can be downloaded and uploaded again. Before anything is written, the screen shows what is going to happen row by row and what does not add up, so a badly built file shows up beforehand and not afterwards.
Can we try it before signing up?
Yes: fourteen days with the whole platform and no card. It is not a cut-down version, it is the complete platform, and what usually happens is that the real people come in during those days and really clock in, because a product like this is not judged on made-up data. If it does not fit in the end, there is nothing to do: the trial expires on its own.
Is it useful if we already have a payroll bureau or payroll software?
Yes, and it sits well alongside both because it does not do the same job. Fichaloto does not run payroll, does not hold contracts or employment paperwork and does not file social security returns: the only financial thing it knows about a person is their internal hourly cost, which is what a project's cost is worked out from. What it adds is the working-time record, absences and hours per project — exactly what a payroll bureau asks you for every month and you send over by hand today.

Fitting it to what you already have

Can Fichaloto be connected to our ERP or our dashboard?
Yes. Much of the platform can be read and written from outside through a REST API over JSON: clients, people, teams, projects, phases, tasks, milestones, diary, time off and catalogues. Logged hours can be listed, read and deleted. Roles, the audit trail, reports and calendars stay out of it and are managed from the application. You get in with a key created from the application itself, which can be read-only or read and write; a key can never do more than the person it belongs to, so the permissions you have already configured apply just the same to integrations. Every write through the API goes into the audit trail with the name of the key that made it, and the key is revoked in one click the day that program stops being used.
Is generating a key enough to use the API?
No, and that is deliberate. Both things are needed: the key —generated inside the application, shown once and revoked in one click— and a role on its owner that allows using the API. Being an administrator is not enough: this is the one exception to «whoever can do everything can do everything», because the API is a different door, a program walks through it rather than a person with a session, and opening it has to be a decision somebody takes rather than a consequence of holding a job title. Two built-in roles come with that permission already set —one read-only, one read and write— and if it is missing, the API response says exactly what is missing and on which screen to fix it. Once inside, a key can never do more than its owner.

Price, data and the relationship

What does time-tracking software cost for a small business?
It comes down to three things, and none of them is the vendor's logo: how many people will actually use it, whether you only need to meet your working-time obligations or also want to know what each project costs, and in how many places and how many ways people clock in. That is why the published list price of most of this market is not what anyone ends up paying: underneath it sit a minimum number of billable seats, an implementation fee, or a higher tier where the thing you actually need happens to live. Ask every vendor for the total cost of the first year divided by twelve, in writing, and compare that. Fichaloto does not publish a per-seat rate: you get a fixed quote built around your case, with implementation and kiosks inside it, no minimum headcount, no onboarding fee and no lock-in.
Is there lock-in, a set-up fee or a minimum headcount?
There is none of the three. The trial lasts 14 days, asks for no card and expires on its own: if you say nothing, nothing is charged. After that you pay for the people who actually use the platform, with no billable minimum below which you pay for people you do not have. The subscription renews on its own, as with any service of this kind, and is cancelled whenever you like with no penalty and no notice period.
Where is the data stored and how is GDPR met?
The data is hosted on servers inside the European Union and traffic is encrypted in transit. Access is separated by account and by role: every read of somebody else's data goes through the company identifier, so one client's data never appears on another's screen. If you need the hosting provider's details, the exact location and the data-processing agreement for your record of processing activities, we give it to you in writing before anything is signed.
What happens to our data if we stop using Fichaloto?
It is yours and you take it with you. Everything in the account exports from the application itself, table by table, into files any spreadsheet opens: people, clocking records, the marks of the working-time register, logged hours, projects, clients, invoices, absences and the audit history. There is nothing to request and nobody to wait for, and you do not have to still be a customer to have done it before leaving.
Can I suggest improvements and ask for changes to Fichaloto?
Yes, and from inside the application itself. The sidebar has one button to report a bug and another to suggest an improvement, with the same questions as the templates we hand out: what you expected and what happened for a bug; what you would like to be able to do and what problem it solves for an improvement. They reach the same people who write the code, not a switchboard. Whoever administers the account decides who on their team may send them, and sending asks for your password so that nobody writes in somebody else's name from an unlocked computer. We always reply, saying what we decided: accepted with a date, accepted without a date, deferred, or turned down.
What if I need something the product doesn't do today?
Se hace. Lo que compras es una base sólida y probada, no un techo: el código es nuestro, lo escribimos nosotros, y se puede desarrollar prácticamente cualquier cosa para tu caso — una pantalla que no existe, un cálculo con tu fórmula, un informe con el formato que te pide tu cliente, un circuito de aprobación que no se parece a ninguno, una integración con el programa que ya usas. No es un producto cerrado de un fabricante al otro lado del mundo: hablas con quien lo escribe. Primero mira uno de nosotros si ya se resuelve configurando, que pasa muchas veces y entonces no cuesta nada; si no, te decimos qué cuesta y en cuánto tiempo, por escrito, y tú decides. Y si además le sirve a más empresas, entra en la hoja de ruta y sale más barato o gratis. Lo único que no hacemos es prometerlo antes de haberlo mirado, ni decir que sí a algo que rompería el producto para los demás.
How do I report a bug in Fichaloto, and how long do you take to fix it?
From the “Tell us something” button in the sidebar, without leaving the application and without opening an email. The form asks for what is actually needed to fix it: what you expected, what happened, the steps to repeat it, whether it happens again and in which browser. You keep a copy in your inbox, so you can reply to us with a screenshot attached. Anything marked as blocking — meaning work has stopped — is looked at the same day; the rest is ordered by what it costs. In every case we tell you whether we managed to reproduce it, because a bug we cannot repeat is not a bug we have fixed.

Let's talk

One demo.
One conversation.

Tell us how many of you there are and how you handle hours and projects today. Out of that comes a demo in your own terms, not a catalogue's.

01You tell us how you work
02You see the platform with your own cases
03You decide, with no obligation

Rather look around on your own? Request access and try it for 14 days.
Rather pick up the phone? +34 919 98 08 56
Or email us at hola@fichaloto.com

Book a demo

We usually reply the same working day. No obligation, and nobody ringing you three times a day.