Skip to content
Use case

The spreadsheet works until two people need it at once

Every SMB starts on Excel and most outgrow it quietly. The tell is not the spreadsheet itself — it is the second spreadsheet, the WhatsApp group that corrects it, and the person who has to be asked which version is current.

How Klok handles it

Replace HR spreadsheets

Import What You Already Keep

Employees, salary structures and leave balances come in from your existing sheets with a preview, so you see what was read before anything saves.

One Version Of The Truth

Attendance, leave and payroll read from the same records, so there is no reconciliation between two sheets that disagree.

The Exit Stays Open

Everything exports back to CSV whenever you want. Moving in is only reasonable if moving out stays possible.

The second spreadsheet is the signal

One spreadsheet is fine. It is the second one — the corrected copy, the branch's own version, the WhatsApp group where the real balances are agreed — that tells you the arrangement has stopped working.

At that point the question is no longer whether the data is in a spreadsheet. It is which spreadsheet is true, and who decides.

What actually breaks

Concurrency, first: two people cannot safely edit the same file, so a copy is made and the copies diverge.

History, second: a spreadsheet holds the present. Overwrite a salary and last year's figure is gone, along with any ability to answer what somebody was paid in March.

And evidence, third: an attendance register maintained in a sheet, updated weekly, is not a contemporaneous record, and does not read as one.

Your sheets are the starting point

This is not a rebuild. Employees, salary structures and leave balances import from what you already keep — the sheet you have is the fastest way to populate the system, not an obstacle to it.

And the exit stays open. Everything exports back to CSV whenever you want it, so the decision to move in does not have to be a decision you can never revisit.

Run both for a month

The honest way to evaluate this is not a demo. Import your data, run Klok alongside your existing process for one cycle, and compare the two outputs. If they agree, you have learned the system works. If they disagree, you have learned something more useful.

Moving over

Your sheet is the input, not the problem

1

Import what you keep

Employees, structures and balances from your existing spreadsheets.

2

Run both for a cycle

Keep your process. Compare the two outputs at the end of the month.

3

Switch when it agrees

Move when the evidence says to, not because a trial expired.

4

Keep the exit open

Everything exports back to CSV, whenever you want, without asking.

Replace HR spreadsheets FAQs

We have years of history in Excel. Does it all come in?

Employees, salary structures and leave balances import cleanly. Historical month-by-month payroll is usually better kept as your archive than reconstructed — what matters is that the opening position is right.

What if the import is messy?

It usually is, and that is informative. Duplicate rows, inconsistent date formats and three spellings of one name are surfaced rather than absorbed, which is the first time many companies see the state of their own data.

Can we go back to spreadsheets?

Yes. Everything exports to CSV at any time, without raising a request. A vendor whose retention strategy is making that hard has told you something.

Do we have to move everything at once?

No. Most companies start with the spine — employee master, attendance, leave, payroll — and add modules when they become relevant.

What happens to the spreadsheets we already have?

They import. Bring them as they are and the mapping is part of onboarding, not homework we hand back to you.

Our spreadsheet has years of history. Do we lose it?

Import what you need for continuity and keep the archive for the statutory retention period. Migrating everything is rarely necessary and often delays go-live by months.

Who gets blamed when the spreadsheet is wrong today?

Usually nobody, because nobody can tell when it broke — which is the real argument for moving. A system records who changed what; a spreadsheet does not.

Try it on your own payroll

Fourteen days, no card, and every record exports back out if you decide against it.

Put your HR on autopilot

Free for 14 days. Invite your team, send one onboarding link, and see your first AI-drafted employee record today.