Kanban CRM · Customer Cases · Follow-Up · Calls · Orders · Sales Progress

One-Line Description

A configurable Kanban-based CRM for marketers and sales users, covering customer ownership, follow-up, calls, sales-stage tracking, order visibility, reminders, and contract-progress supervision.

Core Purpose

The CRM was designed to give marketers a simple visual way to manage customer relationships from first contact through commercial progression.

The central concept was a multi-column Kanban workflow.

Kanban-Based CRM

Management could define or adjust the stages.

The system could use:

• predefined standard stages,
• custom stages,
• configurable columns.

Conceptually:

Initial Contact
      ↓
Follow-Up
      ↓
Pricing / Finalization
      ↓
Contract

The exact workflow could be adapted by management.

CRM Main Areas

Marketing / CRM
├── Customer Management
├── My Customers
├── My Orders
├── Follow-Up
├── Calls / Communications
├── Reminders
└── Contract Progress

Customer Management

The CRM tracked customer interactions.

Possible interaction events included:

• phone call,
• direct contact,
• follow-up action,
• status update,
• commercial progress.

Historical screens show interaction history and follow-up records.

My Customers

Each marketer had access to their own customer list.

This supported customer ownership and reduced ambiguity over responsibility.

My Orders

The sales user could view what had happened to an order after the initial sale activity.

The intent was to show:

• current stage,
• completed stages,
• pending work,
• status of the customer request.

This connected the CRM with downstream business processes.

Direct Calling

Where the organization used:

• PBX / telephony systems,
• tablets,
• mobile devices,

the CRM could support direct calling from the customer record.

The broader design also contemplated storing call records or recordings on organizational infrastructure when available.

Notifications & Follow-Up

The CRM supported notification-driven follow-up.

Examples:

• customer follow-up due,
• sales activity reminder,
• pending contract,
• commercial action required.

Action Recording

Sales users could register actions taken for each customer.

This creates an operational history:

Customer
  ↓
Interaction
  ↓
Action
  ↓
Next Follow-Up

Sales Pipeline Governance

Management or finance could require approval before the process moved to the next stage.

Example:

Marketing
   ↓
Commercial Progress
   ↓
Management / Finance Approval
   ↓
Finalization

This prevented sales users from bypassing required business controls.

Duplicate / Ownership Logic

The broader platform specification included the idea that customer opportunities/cases should not be duplicated unnecessarily.

A customer or sales case could be controlled so that responsibility remained clear.

Shared Opportunity Scenarios

The system concept also allowed for situations where more than one representative or marketer participated in the same commercial opportunity.

A modern V2 should support:

• shared ownership,
• percentage allocation,
• commission splitting,
• explicit approval.

CRM V2 Architecture

Recommended entities:

Customer
Lead
Opportunity
Pipeline
PipelineStage
Interaction
FollowUp
Activity
Order
Assignment

State & Event History

A robust V2 should preserve each stage change as an event rather than overwriting history.

Opportunity
  ↓
StageChanged
  ↓
FollowUpCreated
  ↓
CallLogged
  ↓
QuotationRequested

Career Evidence

• CRM design,
• Kanban workflow,
• configurable sales stages,
• customer ownership,
• activity history,
• notification-driven sales operations,
• approval checkpoints,
• customer-to-order traceability.

Suggested Slug

/projects/crm-sales-pipeline

Cover Direction

CRM & Sales Pipeline

Visual elements:

• Kanban columns,
• customer cards,
• calls,
• reminders,
• sales stages,
• approvals,
• order progress.