Groupware for a company where one person does everything
Between five and thirty people is the size where the admin runs entirely on one person's memory. They handle leave, payroll input, purchasing, the office, the accountant and whatever else arrives that day — and when they take a week off, the company quietly stops processing anything. NOWORX gives that person a structure they can set up themselves, plus an AI agent in each department that does the chasing they would otherwise do by hand at seven in the evening.
If this keeps happening
One person is the system
HR, bookkeeping, purchasing and facilities all sit with the same person. Their week of leave is the company's backlog, and nobody else knows where anything is kept or which of the three folders is current. The business is one resignation away from an archaeology project.
Leave arrives by text message
Requests come in by chat, by phone and in the corridor. At the payroll cut-off the month gets reconstructed from a mix of memory and screenshots, and somebody's half-day is always disputed — usually the same somebody, and usually with the person who has the least time to argue.
Nobody owns accounts
With no IT person, joiners get access ad hoc from whoever is nearby and leavers keep it indefinitely. Six months after someone left, their mailbox and their folder access are still live, and no one can say with confidence what else they still hold.
Five tools, none of them talking to each other
A chat app, a spreadsheet, a shared folder, a paper form and the accountant's own system. The same figure gets typed three times, and which copy is correct depends on who you ask and how recently they looked.
'How much did we spend on that?'
The owner asks a simple question and the only honest way to answer is to open the bank statements and add it up. By the time the answer exists, the decision it was meant to inform has already been made without it.
How the work runs in NOWORX
Tap an app name in any step to see what it does.
- 1
Start with the thing that breaks first: leave and attendance
Leave and hours are where small companies bleed time, so this is the first thing to move and the easiest to prove. attendance-board holds who was in, who was out and why — one record instead of a chat history, so the payroll cut-off stops being a reconstruction exercise. team-calendar shows the same information as coverage, which is what a manager actually needs before approving anything: not 'can she have Friday' but 'who else is out on Friday'. Requests run through approval-dashboard on a phone, and the HR agent chases the two people who never submitted before the cut-off rather than after it.
- 2
Money in, money out, in one place
expense-insight turns spending into categories you can actually see, so the owner's question gets an answer in the meeting rather than the following week. ledger keeps the running position, and quote-docs produces priced documents from the same data instead of a template someone copies and forgets to update. tax-invoice-view keeps issued and received documents reconciled rather than scattered between an inbox and a folder. tax-calendar carries the filing and payment dates your accountant gives you as reminders that reach more than one person — because the usual failure is not ignorance of the date, it is that only one person knew it and they were away.
- 3
The agent as the admin person's second pair of hands
This is where a small company gains time it never had. The agent assigned to admin does the work that is entirely chasing and entirely necessary: reminding the three people who haven't filed expenses, summarising what needs a decision today, drafting the notice about next week's closure. daily-briefing puts the short list in front of the owner each morning — what's outstanding, what's due, what looks unusual — so a run of the business doesn't require a meeting. notice-digest means the same message reaches everyone in the same words, and task-board holds what was agreed so it doesn't depend on someone remembering. daily-report keeps a light record of what actually happened, which is what makes any of it answerable later.
- 4
Joiners and leavers, done the same way twice
Onboarding becomes a checklist that runs identically every time rather than a series of remembered favours. asset-ledger records what equipment a person was issued — laptop, phone, keys, card — which is the list nobody has on the day someone leaves. client-directory holds the external contacts a role owns, so a departure doesn't take the supplier relationship with it. contract-vault keeps employment documents, the lease and supplier agreements with their dates attached, and form-builder turns your joining paperwork into something completed once rather than printed, signed, scanned and mislaid.
- 5
Growing without redoing it all
Most small-company tools break at exactly the point the company starts working. Here the structure that suits eight people is the same structure at forty: more departments, more routes, the same records. data-browser lets you ask questions of what has accumulated instead of exporting everything to a spreadsheet. sheets stays available for the things that genuinely belong in a grid, form-builder covers new processes as they appear, and resource-usage shows where the load is actually landing before it becomes the next bottleneck.
Frequently asked questions
We have no IT person. Who sets this up?
The person who already does the admin, in an afternoon, from a browser. There are no servers to run, nothing to install on each desk, and no configuration project. Set up your departments, invite people, turn on one process, and leave the rest alone until that one is genuinely being used.
My staff aren't going to learn another tool.
They shouldn't have to learn much. For most people the whole surface is: request leave, approve something, read what changed. Those are phone-sized actions. The reliable way to fail is to launch four processes at once and keep the old channel open alongside — pick one, and close the old route so there is only one way to do it.
Do we have to migrate our old data before we start?
No, and we would advise against it. Start from today and let the record build. What you already keep in spreadsheets can stay in sheets and be referenced. Small companies that begin with a migration usually never reach the part that helps them.
Our accountant works outside the company.
Then give them a scoped view of what they need rather than emailing files back and forth. External people can be given access to a specific record set without seeing everything else in the business, and what they looked at is recorded — which is more control than a folder of attachments in an email chain ever gave you.
Is our data separated from other companies using this?
Yes — each organisation's workspace is isolated, and inside it access follows department and role. In a company of this size the practical risk is rarely an outsider; it is that everyone can see payroll because nobody ever set it up otherwise, and that a leaver's access is never actually withdrawn. Both are handled structurally here.
What if we grow, or open a second location?
The same structure carries: a second site is another unit, with its own attendance, its own day-to-day, and a consolidated view for whoever runs both. You don't rebuild, and you don't have to decide today which tool you'll be replacing in two years.
