Skip to content
GarnetOS

About

Companies outgrow their admin long before they outgrow their software.

Somewhere around twenty people, the spreadsheet stops working. Not dramatically — it just quietly becomes out of date, and nobody can say exactly when it happened or who was supposed to notice.

Why we are building it

The gap is not in the tools.

A business of forty people usually has decent software. A payroll product that works. A shared drive. A calendar. Somebody’s well-maintained spreadsheet. Each one does its job.

What none of them does is hold the company. Nothing knows that the person whose passport expires next month is the same person whose probation ends next week and whose manager left in March. That knowledge lives across four systems and one person’s memory, and the day that person is on holiday is the day it is needed.

GarnetOS is an attempt to put the company itself into software — one record, one set of permissions, one audit trail — and then to surface the work that record implies, before somebody has to go looking for it.

We have started with people, documents and compliance, because that is where the consequences of getting it wrong are most immediate and least recoverable. It is not where we intend to stop.

How we build

Five things we have decided, and keep deciding.

Say what happened, not that something happened
A notification that reads “1 item requires attention” has moved the work of finding out onto the reader. Every action in GarnetOS states the event, the reason, and what to do — because the alternative is a product people learn to ignore.
Refuse the claims we cannot support
It would be easy to put a green tick on a compliance dashboard. It would also be the most dangerous thing in the product, because somebody would stop checking. We describe the state of your records and stop there.
A record you cannot explain is a record you cannot defend
Every figure traces to what produced it, every change says who made it and why, and the audit trail is append-only at the database level rather than by convention. The question a year from now is not “what does it say” but “why does it say that”.
Build the boring thing properly
Leave accrual, pro-rating, bank holidays by nation, a leaver’s final pay period. None of it is interesting and all of it is where software quietly gets things wrong at somebody’s expense.
Ship nothing that cannot be reached
A capability with no screen is not finished, however good the API is. If it is in the product, somebody can use it.

Where we are

Early, and saying so.

GarnetOS is a young product. We have no customer logos to show you, no analyst rating, and no certifications. Everything on this website describes software that exists and runs — and where something is planned rather than built, it says so in those words.

What that buys you, if you join now, is a product being shaped around a small number of companies rather than around a market. If you have a view about how this should work, it is unusually likely to end up in the software.

Built in the UK, for UK businesses. Your data is hosted in London and does not leave the country.

Come and tell us what we have got wrong.

Half an hour with the real product. We will be straight with you about what it does not do yet.

Request a demo