Customer Success Board — Manage the Customer Lifecycle

Your product ships features. Your CS team makes sure customers actually succeed with them. The Customer Success board gives your CS team the same structured, trackable workflow that your engineering team has — built for relationships and milestones instead of sprints and deployments.

Every customer account, every onboarding task, every renewal conversation — tracked, assigned, and visible across the team.


Who It's For

The Customer Success board is built for CS teams, account managers, implementation consultants, and anyone responsible for customer outcomes after the sale.

If your team manages customer onboarding, tracks health milestones, runs QBRs, or owns renewal conversations, this board was designed for your workflow.


Work Item Hierarchy

The CS board uses a three-level hierarchy: Customer → CS Task → CS Sub-task.

Customer

The top-level item represents a customer account. Each customer in your portfolio gets their own item. The customer item holds all the account-level context: phase, health, key contacts, notes, and commitment dates.

Think of the customer item as the account card — everything you need to understand where this customer stands lives here.

CS Task

CS tasks are action items for the team — the specific work required to move a customer forward. Examples:

  • Kickoff call
  • Technical integration review
  • Data migration
  • Training session
  • Executive business review
  • Renewal conversation
  • Health check

CS tasks are assigned to team members with due dates and status tracking. A customer might have 5 active tasks across multiple team members at any point.

CS Sub-task

Sub-tasks break down complex CS tasks into specific steps. Use them when a task like "Technical Integration" has multiple distinct phases that need individual tracking — for example: API credentials provisioned, test environment configured, data sync validated, sign-off received.

Sub-tasks are optional. Use them for complex tasks that benefit from step-by-step visibility.


The Customer Lifecycle: Phase Tracking

The Phase custom field tracks where each customer is in their lifecycle. Every customer moves through these phases over time:

Phase What's Happening
Onboarding New customer — getting set up, integrated, and trained
Adoption Customer is using the product; driving depth and habit formation
Growth Healthy, expanding usage; identifying expansion opportunities
Expansion Actively expanding — new seats, new modules, or new use cases
Renewal Contract renewal cycle — securing the next term

The By Phase kanban view shows all your customers as cards across these columns. You can see your entire portfolio's health at a glance and drag customers between phases as they progress.

Tip: Use the By Phase kanban view for your weekly team standup. Every CS team member can see who's in each phase, what's at risk, and who owns the next step — in under two minutes.

Customizing Phase Options

The phases listed above are the defaults on the Phase custom field. You can rename them, add new phases, change their colors, or remove ones that don't fit your lifecycle model.

How to customize: Go to Settings → Fields, find the Phase field, and edit its options. Changes apply across all boards that use this field.


Built-In Fields

Field Description
Status Where the customer or task is in the workflow
Priority Urgency — flag at-risk accounts as High or Urgent
Assignees CS team member(s) responsible for this account or task
Commitment Date Milestone or deadline — tracked with alerts for upcoming dates
Key Unique identifier (e.g., CS-14)

Default Custom Fields

These fields are pre-configured on every new Customer Success board:

Field Type Purpose
Phase Select Customer lifecycle phase: Onboarding, Adoption, Growth, Expansion, Renewal
Task Category Select Type of CS work: Integration, Training, Data Migration, Configuration, Review
Due Date Date Task deadline — used for sorting and alerts
Notes Text Free-form account notes, context, and history

Commitment Dates and Alerts

Commitment dates are how you make sure CS deadlines don't slip.

Add a commitment date to any customer item or CS task. Lifecycle OS surfaces upcoming commitment dates:

  • In the item's detail view
  • In the Upcoming Deadlines view
  • In automated alerts (when configured)

Never miss a customer milestone because it was buried in a spreadsheet.


CS Workflow: Statuses

The CS board uses a relationship-focused status workflow — no deployment stages or QA cycles:

Status Meaning
Not Started Task created but work hasn't begun
In Progress Actively working on this
Waiting on Customer Ball is in the customer's court
Waiting on Internal Blocked by something internal — ops, engineering, billing
Completed Task done
Skipped Not applicable for this customer — intentionally bypassed

Customizing Statuses

These statuses are the defaults. You can enable only the ones that match your workflow, rename them to fit your team's language, and disable the rest.

How to customize: Open your board → click the gear icon → Statuses tab. Toggle statuses on or off and reorder them within their groups.


Default Views (7)

View What It Shows
All Customers Full customer list, grouped by status
By Phase Kanban board showing customers across lifecycle phases
Onboarding Customers in the Onboarding phase with open tasks
Expansion Customers in Growth or Expansion phases
Renewal Customers in the Renewal phase — contract timing visible
My Customers Customers assigned to the current user
Task Board All CS tasks across all customers, grouped by status

These views are pre-built to cover common CS workflows. You can edit any of them, create new ones, delete ones you don't use, or duplicate a view as a starting point for something custom.

How to customize: Click the gear icon on any view to open its settings. Adjust the display mode, grouping, sorting, visible columns, and filters. Or click + New View in the sidebar to start from scratch.


No Sprint or Time Tracking

The CS board intentionally omits sprint planning and time tracking. CS work is relationship-driven and milestone-based — not hour-estimated and sprint-pointed.

If your CS team wants to track effort, custom number fields can be added for rough sizing. But for most CS workflows, the priority, phase, and commitment date fields are what matter.


Using the By Phase Kanban

The By Phase kanban view is the most valuable view for CS team leads. Each column is a lifecycle phase, and each card is a customer account.

What it lets you do at a glance:

  • See how many customers are in each phase
  • Identify accounts that have been in a phase too long
  • Spot where your team's attention is concentrated
  • Drag a customer to a new phase as they progress

This view works best when customer items are kept current — update the Phase field whenever a customer moves forward (or backward) in their journey.


Health Tracking

Use the Priority field as a proxy for account health:

  • Urgent — At-risk account. Needs immediate attention.
  • Very High — Struggling. Intervention required soon.
  • High — Behind on milestones or showing disengagement signals.
  • Mid — On track with some open questions.
  • Low / Very Low — Healthy and progressing normally.

With priority set this way, your team can filter to see all at-risk accounts in one view. Combined with commitment dates and the By Phase kanban, you have everything you need to run a CS health review.


Customizing for Your Team

The default configuration covers the most common CS workflows, but your process is your own. Every default can be changed.

To access board settings: Open your board → click the gear icon. The settings page has tabs for Views, Levels, Pipeline, Statuses, Fields, Defaults, Members, Automations, Import, Projects, and AI Agent.

Common customizations:

  • Add a Health Score field — a number field (1–10) for a formal health score → gear icon → Fields tab, or Settings → Fields
  • Add a Contract Value field — number field for ARR/MRR → gear icon → Fields tab
  • Add a Renewal Date field — date field to drive renewal pipeline views → gear icon → Fields tab
  • Add a CS Manager field — if multiple managers own different accounts → gear icon → Fields tab
  • Create a Churn Risk view — filter to Urgent/Very High priority accounts → click + New View in the sidebar
  • Add or rename phases — if your lifecycle has different stages than the defaults → Settings → Fields, find the Phase field

Related