Clients
Who you sell to, and on one page: their projects, their invoices, their support tickets, their open work, what they have been billed and what is still outstanding.
GRIND
GRIND
The operating system for an organisation
Clients, the work done for them, the people doing it, what you buy and what it all costs — held together rather than kept in five places that have to be reconciled by hand every month.
In daily use at the company that built it. Figures shown are demonstration data.
What it does
A client holds projects; projects hold tasks; tasks belong to people; people belong to departments. Because those links are real, a figure on the dashboard can be traced to the record that produced it.
Who you sell to, and on one page: their projects, their invoices, their support tickets, their open work, what they have been billed and what is still outstanding.
Work with an owner, a deadline and a reviewer. Nothing is "done" because somebody said so — it goes to review, and a named person signs it off.
Invoices, receipts, purchasing and the ledger in one place. Raise an invoice, issue it, take the money, and watch it land in the books without anybody re-typing it.
Twelve stages from raising a need to paying the supplier, each owned by a named party, with a three-way match between order, delivery and invoice before a shilling moves.
Employee records, contracts, leave that flows into the company diary automatically, and a self-service file each person can open for themselves.
Who you buy from, what you have spent with them, and what the company still holds as a result — including who is carrying which laptop.
Tickets from clients and staff, with a knowledge base attached, so the answer given once is the answer available next time.
Seventeen reports and the three financial statements. Export to CSV or PDF, keep a run exactly as it stood, or have one emailed on a timetable.
See it working
Not screenshots — a few seconds of each one being used, filled with demonstration data. The companies and the figures are invented; the software is not.
How it keeps count
Most of the work in a system like this is not the screens. It is making sure the number on one screen and the number on another cannot drift apart without somebody being told.
Debits equal credits or the entry is refused. Checked in code rather than trusted, because an unbalanced ledger cannot be corrected by anything except finding the entry that broke it, months later.
Each entry records the document that produced it, and the database itself refuses a second one. A retry, a double-click or a re-run cannot quietly double your revenue.
A wrong entry is fixed by posting its reverse, which is what an auditor expects to find. There is no button anywhere that removes a journal line.
Where a figure is withheld, it is left out before it reaches the browser — not hidden on the screen. A report never shows anybody more than the screens already do.
The order, the delivery and the invoice have to agree before a supplier is paid. Where they do not, paying anyway needs a separate permission and a written reason.
Procurement's stage log is append-only, enforced by the database. An amendment is recorded as an amendment; nothing is quietly edited after the fact.
Get started
Two minutes and three details. Your organisation gets its own system, built while you answer a few quick questions.
Only your name and email are required. Over 200 people? Choose Enterprise on the pricing page and we will talk first.