Kanban Board and Tasks in a CRM: Running Projects by Stage, Deadline and Owner Without a Separate System
Management6 min read
How to manage tasks and projects in a CRM: work stages, deadlines for each stage, responsible people, a kanban board and ready-made industry process templates.

Many companies keep clients in a CRM but the work for them in a separate task manager or in chats.
As a result, the manager can't see what stage an order is at, who's holding it up and why deadlines were missed.
Let's look at how to set up tasks and projects right inside the CRM, so the client, the deal and the work on it are all in one place.
One-minute plan
- List the steps of a typical order from request to payment.
- Set a deadline and a responsible person for each step.
- Build a kanban board: one column = one process step.
- After a week, see which column cards pile up in — that's your bottleneck.
What a kanban board is
A kanban board is a way of showing work in columns. Each column is a stage; each card is an order or an assignment. Cards move from left to right as work progresses.
The possible statuses on a kanban board depend on the process. For a renovation, for example: "Measurement", "Estimate", "Contract", "Works", "Handover", "Payment".
The kanban method originated in the Toyota Production System as a way to manage the flow of work "just in time". In 2010, David Anderson described its use for office and knowledge work in his book "Kanban", and since then kanban boards have become the standard for sales, service and development teams.
The stages of a task-process aren't hard-coded: you add, remove, change and rename them and save the set of stages as a template. You can create several templates — one for each service.
How to build a kanban board in 10 minutes
- Describe the process. Take your last completed order and list the steps it went through.
- Create the columns. One step, one column. 4–7 columns are usually enough.
- Add cards. Each current order is one card in the right column.
- Assign owners and deadlines to each card.
- Agree on the rules: who moves cards and when, and what "done" means.
Limiting work in progress
The main rule of kanban is to limit the amount of work in each column. If the "Estimate" column already holds five orders, a new one isn't taken on until space frees up. That way problems become visible immediately: the team doesn't pile up dozens of started tasks, but finishes them.
| Column | Limit | What to do when exceeded |
|---|---|---|
| Measurement | 6 | Redistribute site visits |
| Estimate | 5 | Bring in a second estimator |
| Works | 4 crews | Push back the start of new projects |
Online kanban board: separate tool or CRM
| Separate tool | Kanban in the CRM | |
|---|---|---|
| Link to the client and conversations | No — you have to search another system | The card is linked to the client |
| Money and invoices | Separate | In the same system |
| Data entry | Duplicated | Once |
| When it suits | Internal team projects | Work on client orders |
If you need the board for client work — orders, services, deals — it's more convenient to keep it in the CRM. For internal projects without clients, a separate free online kanban board will do.
Task or project
| Simple task | Task-project | |
|---|---|---|
| Example | Call the client back | Apartment renovation, tour preparation, course of treatment |
| Steps | None | Several named steps |
| Deadlines | One | An overall deadline and one for each step |
| Responsible people | One | A person or group for each step |
| Step back | Not needed | Can go back to the previous step |
Process examples by industry
| Industry | Process steps |
|---|---|
| Real estate | Request → Matching → Viewing → Reservation → Deal |
| Clinic | Booking → Appointment → Treatment → Follow-up visit |
| Construction and renovation | Measurement → Estimate → Contract → Works → Handover |
| Education | Request → Trial lesson → Contract → Training |
| Travel | Enquiry → Selection → Booking → Documents → Trip |
Why a separate task manager is often unnecessary
- Work gets separated from the client — you have to look for the conversation elsewhere.
- Deadlines and money live separately — it's unclear whether a stage has been paid for.
- Employees duplicate data in two systems.

How it works in Mestra
- A project inside a task: the client and the product or service are linked to it, and the work goes in stages.
- Named steps, an overall deadline and a deadline for each step.
- A responsible person at every stage — one employee or a group; notes can be added to stages, and the task can be sent back to the previous stage.
- Kanban board with stage columns.
- Ready-made industry process templates — choose your industry and everything is already set up.
- Permissions — each person sees their own work, the manager sees the whole board.
More on roles in our article roles and permissions in a CRM.
Related reading: task timeline.
FAQ
Does Mestra have a kanban board?
Yes. You can view work as a board with columns for the process stages.
Can different stages have different owners?
Yes. Each stage has its own responsible person or group of employees, with its own deadline.
Is there a Gantt chart?
No. For most service companies, stages, deadlines and a kanban board are enough. If you need a Gantt chart for complex construction projects, you can keep it in a separate tool.
Do stages have to be set up from scratch?
No. Mestra has ready-made industry templates that you can adapt to your needs.
Bottom line
When stages, deadlines and assignments live in the same system as clients, the manager sees all the work at once and notices delays before the client does.
In Mestra, any task can become a project with stages, deadlines and responsible people, and the kanban board shows the picture in a second.


