Clients
The client sits at the centre
Contacts, projects, hours, domains and agreements all attach to the client. One page with the full picture, composed from exactly the modules your organisation runs.
One record, built from your modules
The client is the hub: every other module contributes a panel to the client page, and the page never needs editing to receive one. Turn a module off and its panel disappears with it. What you see on the record is the way your agency actually works, not a fixed list handed to everyone.
- Contacts, projects and hours as soon as those modules are on
- Domains, websites and hosting as separate, linkable assets
- Subscriptions, files and future types following the same pattern
A status that sets the work in motion
Every client moves through a clear lifecycle, from first lead to archive. The status is more than a label: a transition can fire task templates, so a client moving to onboarding gets the right start checklist on its own. The intake is written down once and nobody begins from a blank page.
- Lead: still in conversation, no engagement yet
- Onboarding: won, the start checklist is running
- Active, offboarding and archived for the rest of the journey
Who knows the client, who runs it
A client has one primary contact, marked in your brand colour, plus as many further contacts as you need. On your own side you name one responsible person and the colleagues working alongside; that responsible person defaults down onto new projects and tasks under this client, overridable case by case. Invoicing carries its own email address too, because accounts payable rarely shares a mailbox with the day-to-day contact.
Never leave your work for a missing client
Every picker that points at a client, on a project, a time entry or a domain, offers "＋ add". The full create form opens in a dialog and once saved the new client is selected straight away. You never abandon a half-filled screen because a client did not exist yet.
Your own fields and a trail that stays
Missing a detail, like a client number, a segment or a region code? Under Instellingen → Eigen velden you define your own typed fields per entity, required where you want, and they appear in the form and on the record on their own. Every record ends with its activity trail: who changed what and when, with the change itself, recorded automatically and kept even after the person leaves. Who may view, create or edit clients is set finely per role under Instellingen → Rollen.
Want to know more?
The documentation describes every module in detail, from installation to permissions.