Twelve modules. One record underneath all of them.
Each one switches on per company, and off means it is not in the nav at all — never present and refusing.
A CV has just arrived against this posting. In the product nobody presses anything — it is read within fifteen seconds. Here, you press it.
A dramatisation with fixed data — the candidate is invented. The states, the marks and the quoted evidence are the real screening panel’s. Nothing is ever auto-rejected: it orders the field, a person decides.
The record underneath everything
Two modules that nothing else works without. Set these up once and every approval, every report and every routing decision downstream reads from them.
- 01
Employees
Everybody who works here, with their documents, dates and employment details — and behind each record, a history of every change made to it and who made it. It is the one list the rest of the product agrees on.
- Every edit kept, with the person who made it and when
- Documents against the person, not in somebody's inbox
- Delete is soft and confirmed, kept for thirty days
- Bring a roster in from a spreadsheet, correcting as you go
- 02
Organization
Departments, designations and who answers to whom. This is the module that makes approvals work: set the reporting lines once and leave, timesheets and reviews all route along them without being told again.
- Change who somebody reports to once, and every approval moves with them
- An org chart built from the real lines, not drawn separately
- Departments and designations defined per company
- Notice board, holidays and the company calendar live here
The things people ask for every week
The requests that otherwise arrive as messages and get lost — each one routed to the person who can actually answer it.
- 01
Leave
Holiday calendars by the place somebody actually sits, allowances set per policy, and balances worked out from what has been taken rather than maintained by hand on a sheet that drifts.
- Balances computed, never stored — so they cannot go stale
- Holidays differ by country and by state, because they do
- Applying is never a module you have to be granted; everyone can ask
- The approval lands with the manager the org chart already named
- 02
Timesheets
Hours booked by the week or the month — whichever the company runs on — against live projects and clients, so the time somebody spent and the invoice that follows are built from the same number.
- Week or month is a company-wide decision, set once
- Booked against real projects, not free-text descriptions
- Approvals route to the same manager as everything else
- What was approved feeds what gets billed
- 03
Support
An internal desk for the things that go wrong — a laptop that will not start, a payslip that looks off, anything that is nobody's module in particular. Tickets have an owner, a state and a thread.
- Assigning a ticket and answering one are separate permissions
- Unassigned tickets are a rail of their own, so none sits unseen
- Attachments up to 25 MB, ten per ticket
- Raising a ticket needs no permission at all
Hiring, and the AI that reads for you
The part of the product most companies come for — and the only one where a model does work on your behalf, with the evidence printed so you can check it.
- 01
Jobs & Candidates
Your own careers page, postings that go public when you say so, and every application screened against that posting within fifteen seconds of arriving — ordered strongest first, graded, and quoting the line from the CV behind each requirement.
- Screened on arrival, with a sweep behind it for when a model is down
- Every requirement answered — met, partly, or not shown
- Nothing auto-rejected, ever. It orders the field; a person decides
- Around 0.2 of a rupee to read a CV, itemised on the invoice
- A board, a list and a per-candidate view — never only one way
Where the work turns into money
Clients, the work you do for them, and the pipeline of work you have not won yet.
- 01
Clients
Accounts, the agreements behind them, invoices built from hours already booked, and a clear view of what is outstanding. An issued invoice is immutable — it never changes underneath the person who received it.
- Money held in minor units, so rounding cannot drift
- Seeing accounts and handling billing are separate permissions
- An issued invoice is frozen; a correction is a new document
- Built to hold hundreds of clients without the list becoming unusable
- 02
Projects
The work itself — a drag board, milestones with real dates, and the hours booked against each piece. Employees get access to the projects they are on rather than a company-wide read of everything.
- Access is a grant per project, not a blanket permission
- Milestones use the local day, so a deadline never shifts by one
- Time booked here is the time that reaches the invoice
- Drag to move, or use the menu — a board is never the only way
- 03
Leads & Sales
Eleven stages from first contact to won, with dated entries rather than a last-updated stamp — and forms you can paste into your own website that feed the pipeline directly.
- Dated entries, so the history of a deal reads in order
- Embeddable forms that post from your own domain
- One line of script tracks which page the enquiry came from
- A lead becomes a client without being retyped
Reviews, files and the rest of it
The things a company needs a few times a year, and the things it needs every hour.
- 01
Performance
Quarterly reviews that are not pre-created and sitting empty — they begin when the window opens. Managers rate against criteria, HR signs off, and the appraisal follows from what was agreed.
- Reviewers score out of ten; the employee is shown a letter grade
- The server does not send an employee their own number
- Managers are entitled by the routing, not by a separate permission
- Nobody is asked to rate somebody the quarter does not cover
- 02
Tewo Drive
Company files in folders people actually share into, held by the company rather than by whoever happened to upload them — so a person leaving does not take a folder with them.
- Files belong to the company, not to an account
- Links are signed and expire rather than being public forever
- Uploads keep their original name, in whatever language it was in
- Four shelves: recent, shared, yours, and everything
- 03
Assets
The register of what the company owns and who is currently holding it — issued, returned, in repair, written off — with the person told by email and in the product when something is assigned to them.
- Events, not fields: the history is the record
- The employee is told when something is issued to them
- Counts across the top are the filter, not decoration
- Warranty and service dates that actually surface before they pass
- 04
Chat & Calendar
Direct messages, group threads and calls, plus the company calendar — kept beside the work rather than in a separate product nobody connects back.
- Calls are self-hosted, not handed to a third party
- Chat is never a module you have to be granted
- The calendar carries holidays, leave and company events together
- Losing your microphone does not end the call
Start with two of them. Switch the rest on when you want.
Most companies begin with the roster and leave. Nothing has to be decided today.