LabKick Plan
Projects, tasks, owners, and due dates for lab work. They sit on the same record as the notebook, protocols, and inventory.
Top features
- Projects tied to the science
A project is not a separate spreadsheet. It links to notebook entries, protocols, constructs, and inventory the work actually uses.
- Tasks with real owners
Assign a person, a due date, and the experiment or protocol the task is about. Status is visible without a status meeting.
- Boards and lists
Kanban or list views for the same work. Filter by person, project, or what is blocked.
- Milestones that mean something
Mark the clone verified, the protein purified, or the figure locked. Milestones point at records, not vibes.
- Dependencies without theater
Task B waits on task A when the science requires it. Blockers show up before the deadline does.
- One seat, same permissions
Plan uses the same lab and org scopes as the rest of LabKick. No second login for project tracking.
Everything in Plan
- Projects and workspaces
- Tasks with owners and due dates
- Kanban and list views
- Milestones linked to lab records
- Task dependencies and blockers
- Comments on tasks
- Links to notebook entries
- Links to protocols and runs
- Links to constructs and entities
- Filters by person, project, or status
- Lab and org permission scopes
- Notifications for assignments and due dates
- Search across projects and tasks
What changes
- Project management stops living in a tool that cannot see the experiment. The task and the notebook entry are neighbors.
- Who owns the next step is public inside the lab, so work does not stall in a private chat thread.
- Milestones point at scientific records. Done means the clone is verified, not that a checkbox got clicked.
Run it on your own data.
Plan is not sold on its own. One price gets you all ten tools, and the trial turns every one of them on.
No card to start · One login covers all ten tools · Cancel anytime