A CRM that follows your process: columns, transition rules and history

Almost every CRM has a kanban. Few let the team say how the process really works: what comes after a visit, whether a proposal can go back to evaluation, which message goes out when a lead changes stage. Valerium's CRM module was built around those three questions.

Columns that look like yours

The eight stages are fixed — entry, first contact, follow-up, visit scheduled, evaluation, proposal, won and lost — because that is what keeps reports comparable across teams. The name, colour and order of each column are yours: admins rename, recolour and drag the headers right on the board. The vocabulary follows the business type and can be changed per team.

Transition rules

The workflow editor is a from × to matrix: tick what is allowed, see the text summary and the diagram. While the Enforce rules switch is off, the matrix is a draft; once on, the server refuses any move outside it — on the board, when editing the lead, and through the API. While dragging, forbidden columns already show as blocked.

A message at every step

Each stage (or each specific transition) can carry a default message. When you move a lead it shows up before confirming: record it as a note, send it on WhatsApp, skip or cancel. Marking as lost asks for the reason first. Nothing goes out without a person looking at it.

• —Updates tab: how long the lead sat in each stage, who moved it and when it returned to a stage it had visited
• —Lead detail tabs set by the business type and editable by the team
• —A won lead becomes a customer and can originate a contract, with the link recorded
• —Reports and the dashboard use the same stage names you defined

A process that only exists in the manager's head does not scale. One the system enforces does.