A spreadsheet charges no license. It charges the hours of whoever builds, checks and fixes it every month — and that is the bill Nimbos replaces.
From R$9.00 per licence/month, minimum R$90.00 · parameters set per company, proposal and project
It is free, already installed, everyone knows how to use it, and it accepts any format you invent this afternoon. For a small team in a simple month it does the job — and swapping a spreadsheet for a system too early is paying to lose flexibility. What this page compares is what happens when the month stops being simple: collective agreements, hour banks, margin per contract, and an invoice that has to match what was approved.
| Capability | Planilha | Nimbos |
|---|---|---|
| Overtime | It calculates whatever the formula says. The agreement's bands, the weekend and holiday uplifts and the night-work window have to be written by someone — and rewritten when the union renews the agreement. | Nimbos calculates overtime by your company's labor agreement rules: bands, weekend and holiday premiums and the night premium, all configurable — the defaults of a real agreement come ready to adjust. |
| Hour bank | The balance exists as long as someone maintains it: cycle, weekday and non-working-day factors and caps become columns, and what rolls into the next cycle is a copy between tabs. | Nimbos keeps the hour bank under the collective labor agreement: configurable cycle, factors for working and non-working days, night premium and balance caps — the balance turns into time off and rolls into the next cycle. |
| Time clock | Reconciling the clock against what was logged is a third spreadsheet, built from lookups across two exports — and it goes stale the moment someone fixes a punch at the source. | Nimbos checks, day by day, whether clock-ins and logged hours match: who clocked in without logging hours, who logged hours without clocking in, and where the sources diverge — without demanding hours on holidays, during vacation, or for the day that hasn't closed yet. |
| Margin per contract | Cost per hour and price per role live in cells. When the rate changes, the spreadsheet recalculates the whole month — including what was already invoiced. That is what makes March's margin change in July. | Nimbos shows each contract's margin throughout the month — hourly cost and price per role, negotiated contract by contract. On invoicing, it stamps the price and cost used: renegotiating later does not touch an already invoiced month. Cost is visible only to those with permission to see it. |
| Month-end close | Nothing locks. Closing is an agreement not to touch it any more, and the file called “final_v3_reviewed” exists because someone did. | Nimbos requires approval per project before closing: any recorded approval locks the month for editing. Once closed, the month freezes the quantity and the clause in force — renegotiating later does not move a closed month. First you define how much of the hours becomes billing, then you close, only then you invoice — and it is on invoicing that the price and cost get stamped. |
| Invoicing | The invoice breakdown is typed again, from what the spreadsheet added up — and typing is where an error gets in without leaving a trace. | Nimbos calculates the invoice amount and line items from the closed month. In Barueri-SP, it also builds the submission file in the city hall's layout — sending it remains a separate step. |
| Bringing the history | There is no API to connect to: what exists is the file, and the file is exactly what Nimbos reads. | Nimbos reads your spreadsheet file. You say which column is what — the mapping is saved for next time — and before writing anything Nimbos shows what it UNDERSTOOD: the period, the total hours, who it does not recognise and what it will replace. The spreadsheet does not have to change format to fit. |
| Where the data lives | Wherever the file is: the maintainer's computer, the email attachment, the shared folder. There are no permissions inside the file — whoever opens it sees everything in it, cost included. | Nimbos hosts the data in Brazil, each company isolated from the others in the database, and each person sees only what concerns them. |
| Price | No license cost. It costs the hours of whoever maintains it, and those hours almost never show up in any report. | From R$9.00 per licence/month, with a R$90.00 minimum invoice; without commitment, R$20.00 per licence/month, cancel anytime. Every module is included in the price. |
This is the only comparison on the site WITHOUT an official source, and the reason is that none exists: a spreadsheet is nobody's product, with no features page and no pricing page. So its column claims nothing about third-party software — it describes the WORK the approach demands, with no number nobody measured.
A spreadsheet charges no license, and that point is hers. Nimbos starts at R$9.00 per license/month, with a minimum invoice of R$90.00 — and what it replaces is not the file, it is the work of keeping it.
The price is per seat, not per login: it counts every person whose hours exist in Nimbos, including those who never sign in. If someone imports the hours of ten others, that is eleven seats — the importer's and the ten imported.
There is no figure on the other side because there is no price list to quote. What the spreadsheet costs at your company is a sum only you have: how many hours a month, from whom, and what that person's hour is worth.
There is no API to connect to, and none is needed: Nimbos reads the file. Upload the spreadsheet, map the columns once, and check the preview before writing — the period, the total hours, who it does not recognise and what it will replace. The history keeps counting.
The market matrix compares six tools in one table, with the official source for each of them.
Message us on WhatsApp. Bring a month you already closed in the spreadsheet and compare it with what Nimbos closes from the same file.
Sales channel. If your company already uses Nimbos, support goes through your administrator.