Skip to main content

Kanban Pipeline View

The Kanban pipeline view presents your entire client portfolio as a visual board with columns for each pipeline stage. It is the fastest way to get an overview of your business development progress, move companies between stages, and identify where your pipeline needs attention. The visual format makes patterns and bottlenecks immediately apparent in a way that a list view cannot.

What the Kanban View Shows

Pipeline Statistics Cards

At the top of the Kanban view, a row of statistics cards gives you an instant numerical overview of your pipeline:
CardIconColorShows
ProspectUsersGrayTotal number of companies at Prospect stage
ContactedPhoneBlueTotal number of companies at Contacted stage
MeetingCalendarPurpleTotal number of companies at Meeting stage
WonTrophyGreenTotal number of Won (active client) companies
LostX CircleRedTotal number of Lost deals

Search and View Toggle

Below the statistics cards, a search bar lets you filter companies by name across all columns. Next to the search bar, a toggle button lets you switch between the Kanban board view and a list view of your pipeline.

Board Columns

The board is organized into columns, one for each pipeline stage:
ColumnColorContents
ProspectGrayCompanies you have identified but not yet contacted
ContactedBlueCompanies where you have made initial outreach
MeetingPurpleCompanies where you have had or scheduled a meeting
WonGreenActive clients — deals that are closed
LostRedDeals that did not close
Each column header displays the stage name and a count badge showing how many companies are at that stage. The columns are arranged left to right following the natural progression of the sales pipeline — from initial discovery (left) to final outcome (right).

Company Cards

Each company in the Kanban view is represented as a card. These cards provide a compact summary of key information:
  • Company name — The primary identifier, displayed prominently
  • Favorite star — A star icon to mark the company as a favorite
  • Industry — The company’s sector for quick context
  • Employee count — The size of the company
  • Active job count — Number of open positions
  • New jobs badge — A badge showing the count of new jobs since your last visit (when applicable)
  • Contact count — How many contacts are on file for this company
  • Location — The company’s headquarters location
  • Last activity — Timestamp of the most recent activity on this company
  • Last viewed — When you last visited this company’s detail page
  • Loss reason — For companies in the Lost column, the reason the deal was lost is displayed
Cards are designed to be scannable — you should be able to evaluate your entire pipeline at a glance without clicking into individual company pages. The most important information is visible on every card.
When scanning your Kanban board, pay attention to the column heights. A much taller Prospect column compared to Contacted means you have a bottleneck at the outreach stage. Balanced column heights (with natural funnel narrowing) indicate a healthy pipeline flow.

Drag and Drop

The Kanban board supports drag-and-drop interaction for moving companies between stages:
1

Grab a Company Card

Click and hold on a company card to start dragging it. The card will visually lift and follow your cursor.
2

Drag to the Target Column

Move the card to the column representing the new pipeline stage. Valid target columns will highlight to show they can accept the drop. Invalid target columns remain unchanged, making it clear which moves are allowed.
3

Drop to Update

Release the card in the target column. The company’s status updates immediately, the client_status_changed_at timestamp is recorded, and an activity record is created in the company’s activity timeline. The update is saved and visible to all team members.
Drag-and-drop respects the same transition rules as the status pipeline. You cannot drop a card into a column that represents an invalid status transition. For example, you cannot drag a company from Won directly to Meeting, or from Meeting back to Prospect. See Status Pipeline for the full transition rules.

Valid Drag Targets

From ColumnCan Drop In
ProspectContacted, Meeting, Won, Lost
ContactedProspect, Meeting, Won, Lost
MeetingContacted, Won, Lost
WonLost
LostProspect

Drop Zone Indicators

When dragging a card, valid target columns show a visual indicator (like a highlighted border or a “Drop here” message). Invalid target columns do not show this indicator, making it immediately clear which moves are allowed and which are not. This prevents accidental invalid transitions and makes the interface intuitive to use.
If you need to add context when changing a status (like a loss reason for Moving to Lost), the drag-and-drop may prompt you for additional information after the drop. Status changes to Lost require a loss reason, which the system will request after you complete the drag.

Kanban View vs. List View

Recruitier offers two ways to view your client pipeline: the Kanban board and a traditional list view. You can switch between them using the toggle button next to the search bar. Each has its strengths:

Kanban Board

Best for:
  • Getting a visual overview of your entire pipeline distribution
  • Quickly assessing how many companies are at each stage
  • Moving companies between stages with drag-and-drop
  • Weekly pipeline review meetings and team stand-ups
  • Identifying bottlenecks and pipeline imbalances at a glance
  • Quick pipeline health checks (2-minute daily review)
Trade-offs:
  • Less detail per company than a list row
  • Columns with many items require scrolling
  • Limited sorting and filtering options within columns

List View

Best for:
  • Detailed information about each company in a tabular format
  • Sorting and filtering companies by specific criteria
  • Working through a specific stage methodically (e.g., follow-up calls)
  • Exporting or reviewing data in a structured format
  • Finding specific companies quickly by searching or filtering
  • Viewing all company metadata at once
Trade-offs:
  • No visual overview of stage distribution
  • Requires reading each row individually to assess the pipeline
  • Status changes require opening each company detail page
Use both views for different purposes. Start your week with the Kanban board for a strategic overview, then switch to the list view when you need to work through a specific batch of companies (like following up on all Contacted companies that have been waiting more than a week).

When to Use the Kanban View

The Kanban view is most valuable in these situations:

Weekly Pipeline Review

Set aside time each week to review your Kanban board. In one glance, you can:
  • See how many companies are at each stage — is the funnel balanced?
  • Identify if your pipeline is top-heavy (too many Prospects, not enough further along)
  • Spot companies that may need attention (e.g., companies that have been in Contacted for too long)
  • Move companies whose status has changed since your last review
  • Assess whether you need to add more Prospects from Client Discovery

Team Stand-ups

If you work in an agency team, the Kanban board is an excellent tool for brief stand-up meetings. Walk through each column and discuss:
  • Which companies are new Prospects this week?
  • Who is following up with Contacted companies? Any responses?
  • What meetings are scheduled or completed?
  • Any recent Wins to celebrate? Lessons from Losses?
The visual board makes these conversations efficient because everyone can see the same picture simultaneously.

Pipeline Health Assessment

A healthy BD pipeline typically has a funnel shape:
  • Many Prospects — You are consistently adding new potential clients through Client Discovery
  • Fewer Contacted — You have reached out to a subset of prospects and are waiting for responses
  • Even fewer Meeting — A portion of contacted companies have progressed to real conversations
  • Fewest Won — The natural conversion rate from meeting to active client
If your Kanban board shows an inverted shape (more companies at later stages than earlier stages), you need to increase your prospecting activity. If you see a bulge at Contacted (many more than at either Prospect or Meeting), your outreach approach may need refinement.
Use the column counts as a quick health check:
  • Empty Prospect column: You need to do more discovery immediately.
  • Contacted much larger than Meeting: Your outreach messages may need improvement.
  • Many Meetings but few Wins: Your pitch or qualification criteria might need adjustment.
  • Growing Lost column: Review loss reasons for patterns you can address.

Visualizing Your BD Pipeline at a Glance

The Kanban board answers several critical questions instantly:
QuestionWhere to Look
”How many active prospects do I have?”Prospect column count
”Who am I waiting to hear back from?”Contacted column
”What meetings do I have coming up?”Meeting column
”How many active clients do I have?”Won column
”What is my win rate?”Won count vs. Lost count
”Where is my pipeline bottleneck?”Which column has disproportionately many companies
”Is my pipeline growing or shrinking?”Compare to last week’s review

Handling Columns with Many Items

When a column has many companies (common for Prospect and Contacted stages), the cards stack vertically within the column and you can scroll to see all of them. The column header always shows the total count, so you know how many items are in the column even without scrolling through all of them. For very active pipelines, consider:
  • Aggressively moving or removing companies — If a Prospect has been sitting for months without outreach, it should either be contacted or moved to Lost. Stale Prospects create noise.
  • Using the list view for detailed work — When you need to work through 30 Contacted companies systematically, the list view with sorting by date may be more efficient.
  • Prioritizing within columns — While the Kanban board does not offer sorting within columns, the order in which cards appear helps you scan. Use the list view to identify your highest-priority items, then return to the Kanban for the overview.

Empty Columns

An empty column in the Kanban board shows a message indicating that no companies are at that stage. This is normal for certain columns at certain times:
  • Empty Meeting — If you are just starting BD, you may not have any meetings yet. This is a signal to focus on converting Contacted companies through better outreach.
  • Empty Won — Early in your BD process, you will not have Won clients yet. This is expected and motivating — every company in your pipeline is a potential first Win.
  • Empty Lost — If you have been doing BD for a while and have no Lost companies, you may be either very successful or not recording losses honestly. Some loss is natural and expected.
An empty Prospect column is a warning sign. If you have no new prospects in the pipeline, your future pipeline will dry up as current companies move to Won or Lost. Always maintain a healthy flow of new Prospects through regular Client Discovery sessions. Think of the Prospect column as your pipeline’s fuel tank — when it is empty, you are running on fumes.

Best Practices for Kanban Pipeline Management

Daily Quick Check (2 minutes)

Spend two minutes at the start of each day glancing at your Kanban board:
  • Any new items in any column from colleague activity?
  • Any companies that need immediate attention today?
  • What is your BD focus for the day?

Weekly Review Ritual (15-30 minutes)

Once a week, spend 15-30 minutes doing a thorough pipeline review:
  1. Start from the right (Won/Lost) and move left
  2. Review each Won client — any upsell or additional placement opportunities?
  3. Review Meetings — are follow-ups needed? Any upcoming meetings to prepare for?
  4. Review Contacted — who needs a follow-up? Who should be moved to Lost after prolonged silence?
  5. Review Prospects — who is ready for outreach? Who should be removed as no longer relevant?
  6. End by checking if you need new Prospects (go to Client Discovery and run your saved searches)

Keep It Clean

A Kanban board only works if it accurately reflects reality. Remove or archive companies that are no longer relevant. Update statuses promptly after every interaction. Add notes when you have context. The board should be a living, accurate representation of your pipeline at all times. An inaccurate board is worse than no board — it gives you false confidence about your pipeline health.
The Kanban board and list view share the same underlying data. Moving a company in the Kanban board is identical to changing its status from the detail page or list view — the change is reflected everywhere immediately. There is no synchronization delay between views.

Advanced

How the Kanban View Works Under the Hood

The Kanban view queries Company records (your personal/agency tracked companies) and groups them by the client_status field. Each column represents one status value:
  • Prospect column: WHERE client_status = 'prospect'
  • Contacted column: WHERE client_status = 'contacted'
  • Meeting column: WHERE client_status = 'meeting'
  • Won column: WHERE client_status = 'won'
  • Lost column: WHERE client_status = 'lost' (often hidden by default or shown separately)
Each Company record is joined with its linked GlobalCompany to populate the card with company name, industry, employee count, and job metrics.

Drag-and-Drop Status Changes

When you drag a card between columns, the frontend:
  1. Validates the transition against the allowed transition map
  2. Sends a status change request to the API
  3. The API validates the transition again (server-side validation)
  4. Creates a ClientCompanyActivity record with the status change
  5. Updates the client_status and client_status_changed_at fields
  6. Returns the updated Company record
  7. The frontend moves the card to the new column
If the status change to Lost requires a loss reason, the frontend prompts for it before sending the request. This ensures all Lost transitions have recorded reasons.

Connection to Other Features

  • Status Pipeline: The Kanban board is a visual representation of the same pipeline that the status selector on the company detail page manages. All transition rules apply identically.
  • Activity Timeline: Every drag-and-drop status change creates the same ClientCompanyActivity record as a status change made through the detail page. The timeline makes no distinction between the two.
  • Company Detail Page: Clicking a card in the Kanban view navigates to the full company detail page.
  • List View: The Kanban and list views share the same Company data. Switching between them shows the same pipeline from different perspectives.
  • Client Search: The “saved” indicator in search results reflects whether a Company record exists, regardless of which view you use to manage the pipeline.

Power User Tips

  • Use the Kanban for weekly strategy, list for daily execution: The Kanban gives you the big picture of where your pipeline stands. The list view lets you efficiently work through a batch of follow-ups.
  • Pay attention to column ratios: A healthy pipeline for most recruiters has roughly a 5:3:1 ratio (Prospect:Contacted:Meeting). If your ratio is severely off, adjust your activities accordingly.
  • Screenshot your board weekly: Taking a screenshot of your Kanban board each week gives you a simple visual history of pipeline evolution. You can see growth, contraction, and conversion patterns over time.
  • Move Lost companies quickly: Do not let the Contacted column become a graveyard of unresponsive companies. If you have sent 3+ follow-ups without response over 2-3 weeks, move to Lost. This keeps your active pipeline realistic and your metrics meaningful.
  • The Won column is not the end: Companies in Won still deserve regular attention. Check in on Won clients monthly. Their hiring needs evolve, and maintaining the relationship leads to repeat business and referrals.

Business Logic Rules

  • The Kanban board displays only non-deleted Company records for the current user/agency.
  • Drag-and-drop enforces the same transition validation as the status change API.
  • Moving to Lost requires a loss reason (prompted after the drop).
  • Column counts update immediately on status changes.
  • All status changes are logged as ClientCompanyActivity records.
  • The board shares data with the list view — changes in one are reflected in the other.