Getting started

What zeypm is

One platform for the work a team actually does — and a way of keeping it small. Every project shows only the modules it needs, so nobody wades through surfaces they never use.

The idea

Most tools of this kind grow by adding features until every project carries all of them. zeypm is complete on purpose — tasks, documents, time, bugs, roadmaps, client messages, invoicing, a knowledge base and meetings all live here — but a project only shows the parts you switch on.

So a small internal project can be a task list and nothing else, while a client engagement alongside it also has a roadmap the client can see, a message thread and invoices. Same platform, different surface area, no second tool.

How things are arranged

• An organisation is your company. It holds your people, your clients and your projects.
• Projects are flat. There is no nesting, no folders inside folders. A project is the unit of work and the unit of access.
• Access is all or nothing. You are on a project or you are not — there is no partial view of one.
• Teams group people so you can grant access to several at once, rather than a different meaning of "team" you have to maintain.
• Clients are real people who log in and see the parts of a project you have chosen to share.

Always on, and opt-in

Every project has task lists, documents and time tracking from the moment it exists. Everything else — bugs, roadmap, client messages, billing, knowledge base, meetings and the GitHub integration — is switched on per project when you want it.

Tracking time is part of every project and always has been. Only billing — rates, and turning that time into invoices — is one of the opt-in modules.

Where to go next

• The dashboard — what you see when you sign in.
• Your first project — setting one up.
• Switching modules on — the mechanism behind all of the above.

If you want the argument rather than the instructions, the overview and the module tour cover why it is built this way.