You hold several client projects together at once.
One organisation per client, and underneath as many projects as that client has going on. Tasks come as a list or on a kanban board, and you set statuses and fields per project yourself. Client conversations are objects of their own, with transcript, summary and tasks derived from them.
What you get
Below it as many projects as that client has undertakings. The line between your clients runs above the projects, not through them.
List or kanban on the same data, statuses and fields defined per project. No foreign workflow to bend yourselves into.
A client conversation is an object of its own. The AI suggests tasks from it, and only when you accept one does it become a ticket.
With rights per area, so they see the state of their matter and not your internal notes about it.
What it does not do
Three limits worth knowing before you move.
- Sub-tasks go one level deep, and there are no dependencies between tasks. No "blocks", no "starts after".
- No scheduling across the project. There are due dates on individual tasks, but no bar chart that produces an end date.
- No capacity planning. Who is free when is not in Lalabase.
What people ask at this point
- How do I keep ten projects apart?
- Through one organisation per client with projects below it. Tasks always belong to exactly one project, a project to exactly one organisation, and across all of them you ask the chat instead of opening ten lists.
- What about the things shouted across the room?
- For those there are project notes and the comment history on the task. What was discussed belongs in the conversation, what needs doing belongs in the task.
- Do I have to set everything up again?
- No. From Redmine, CodebaseHQ, Jira or a spreadsheet we set your projects up by hand, so you decide on your own material.
Look at it
rather than take our word for it.
Productive in under 5 minutes. No sales loop.