User guide
The module reference answers “what does this app do”. This answers the other question: how do I actually do the job. Seven core apps, followed end to end, against the screens as they are — with the mistakes that are expensive to make twice.
Core workflows
The seven apps almost everybody uses, whatever else the business runs. 50 steps between them, 18 of them with the real screen beside the words.
Working through the inbox
Mail is a real mailbox, not a list of notifications about one. This is the round trip: read, answer, file, and turn the two or three messages a day that are actually work into something with an owner.
8 steps
ContactsKeeping one address book
Contacts is the shared address book — employees, customers and vendors in one place, held for the organisation rather than in each person’s own list. This is how to put something into it that the next person can also use.
7 steps
DrivePutting a file somewhere it can be found
Drive is file storage where sharing is actually enforced — fifteen separate permissions rather than one "can access files" switch. This is the path a document takes: in, shared, commented on, revised, and occasionally rescued.
8 steps · 8 screens
CalendarReading the day properly
Calendar projects meetings, tasks and events onto one grid, on the clock of whoever is reading it. This is how to read it without double-booking yourself between a meeting and a deadline.
5 steps · 1 screens
MeetRunning a meeting that leaves a record
A meeting here is a business record that happens to have a call attached — the agenda it ran to, who turned up, what was decided, and what somebody has to do now. This is the whole arc, from scheduling to the actions afterwards.
8 steps · 8 screens
TasksRunning work off one list
Tasks is the module most people touch most often: an owner, a day and a state, inside a project or standing entirely alone. This is how to keep a list that stays true for more than a fortnight.
7 steps · 1 screens
Notes & SocialWriting something down where it will be found
Notes keeps short-form writing against the work it belongs to — notebooks, sections and notes, with templates for the shapes you write over and over. This is how to write one that is still useful to somebody else next quarter.
7 steps
Why these show screens and the reference does not
The module reference deliberately describes no interface: buttons move, and a manual written against them is wrong at the next release while still sounding authoritative. These pages take that risk on purpose, because you cannot follow a job without seeing where it happens — so they are the pages most likely to go stale, and every screen on them is a capture of a running installation with real data in it rather than a mock-up. All 43 modules are covered by the reference; these seven are the ones worth walking through.
Still to be written
The workflows above are about using an app. These six are about running the business on it — the questions asked on the phone often enough to be worth writing down. They are published as they are finished rather than held back until all six are.
Before the first login
What has to be decided rather than configured: how many companies you are actually running, who owns the chart of accounts, which modules are switched on for the first month, and what the roles are called.
The first week
A day-by-day order of setup that does not have to be undone. Directory and roles, then the reference data each module needs, then the people — in that order, because every other order means re-keying.
Who gets what
Building roles out of 335 named permissions without ending up with one enormous role called "staff". The five or six roles most businesses actually need, and the ones worth splitting even when it feels pedantic.
A record end to end
Following one enquiry from the lead, through the deal and the quote, into an order that reserves stock, a delivery, an invoice, and the payment that closes it — without anybody retyping a line.
The month end
What has to be true before a period is locked: timesheets approved, claims decided, payments allocated, reconciliations closed. The checklist, and what each item protects.
When something looks wrong
The handful of symptoms that account for most support calls — stock that is promised twice, mail that never left, a payment that will not allocate — and which module to look in for each.
Need one of those now?
A walkthrough with a person covers the same ground against your own business rather than a general one, and it is free to ask for.
Book a walkthrough