How to Build Custom Keap Pipelines for Sales, HR, and Projects

A default Keap pipeline is a starting point, not a system. The moment your sales cycle has more than three steps, your recruiting process involves more than one interviewer, or your project delivery spans more than one department, the generic stage structure stops matching how work actually moves. This guide shows you how to design and build role-specific Keap pipelines that reflect your real workflow — and wire automation into every stage transition so the system does the administrative lifting your team currently does by hand.

Before you open Keap and start clicking, read the Keap CRM implementation checklist for recruiting teams to understand the broader architecture this pipeline build lives inside. Also complete your Keap CRM data clean-up strategy before pipeline build — importing messy contact data into a new pipeline structure compounds every problem.

Before You Start

Rushing into the Keap interface before completing these prerequisites is the single most common reason pipeline builds require expensive rework.

  • Time required: One hour for design, two to four hours for build and testing per pipeline. Plan separately.
  • Access required: Keap admin credentials with pipeline creation rights.
  • Design artifact required: A written list of every stage, its entry criterion (what must be true for a record to enter), and its exit criterion (what action or event moves it forward). This document does not exist inside Keap — create it before you log in.
  • Data model decision required: Decide whether your pipeline will track contacts, companies, or opportunities (deals). Recruiting pipelines should track opportunities linked to contacts — not contacts directly — so one candidate can hold multiple role-level records simultaneously.
  • Custom fields confirmed: Identify every data point you need to capture at the pipeline level that doesn’t exist on the default Keap opportunity record. Build those fields before creating the pipeline. See the guide to Keap custom fields for HR and recruitment data tracking for the full field architecture.
  • Risk: Changing stage names or order after automation triggers are attached breaks those triggers silently. Get stage design locked before building automation.

Step 1 — Map the Real Workflow Before Touching Keap

Open a blank document or whiteboard. For the function you’re building the pipeline for — sales, recruiting, or project management — write every discrete action or decision point that occurs from the moment a record enters the system to the moment it closes. Group adjacent actions under one label only when the same person owns them and no external event separates them.

For a recruiting pipeline, this typically surfaces seven to ten distinct stages: Application Received, Resume Screened, Phone Screen Scheduled, Phone Screen Complete, Interview Scheduled, Interview Complete, Offer Extended, Offer Accepted, Onboarding Initiated. Each represents a real handoff or status change — not an aspirational milestone.

For a sales pipeline, stages like Discovery Call Scheduled, Needs Assessment Complete, Proposal Sent, Proposal Under Review, Contract Negotiation, Closed Won, and Closed Lost map to discrete moments where the deal’s next action owner or required input changes.

For a project pipeline, stages typically align to delivery phases: Brief Received, Scope Finalized, Kickoff Complete, In Production, Client Review, Revisions Complete, Delivered, Invoiced.

For each stage, write three things:

  1. Entry criterion: what must be true or done for a record to enter this stage.
  2. Owner: who is responsible for moving the record out of this stage.
  3. Exit trigger: what action or event signals readiness to advance.

This document becomes your build spec. Any stage that cannot answer all three questions is not ready to build.

Step 2 — Create the Pipeline and Stages in Keap

Log into Keap and navigate to CRM → Pipelines → New Pipeline. Name the pipeline with a department prefix: SALES_, HR_, OPS_. This naming convention keeps your pipeline list readable and makes automation filter logic unambiguous as you add more pipelines over time.

Add stages in the exact sequence from your design document. Do not add placeholder stages for situations you’re not sure about yet. Every stage you add must have a defined entry criterion, owner, and exit trigger from Step 1.

Stage configuration checklist for each stage:

  • Name matches the exact language from your design document — not a synonym or abbreviation.
  • Probability is set for sales pipelines (used in revenue forecasting). Set to 0% for recruiting and project pipelines where probability is not meaningful.
  • Stage color is consistent with your department’s color scheme if you use visual pipeline views.

Add your Closed Won and Closed Lost (or equivalent terminal) stages last. Every pipeline needs at least one positive terminal and one negative terminal stage so records have a defined end state.

Step 3 — Add Pipeline-Level Custom Fields

Navigate to the custom fields section for your opportunity record type. Add every field identified in your pre-work that is specific to this pipeline’s function.

For recruiting pipelines, essential custom fields include: Role Title, Hiring Manager, Interview Date (date field for each interview stage), Offer Amount, Offer Acceptance Date, Source, and Rejection Reason. These fields live on the opportunity record — not the contact record — because they are role-specific, not candidate-specific.

For sales pipelines: Deal Size, Product Line, Decision Maker Name, Proposal Sent Date, Expected Close Date, and Loss Reason are the minimum set for meaningful reporting.

For project pipelines: Project Type, Budget, Kickoff Date, Delivery Date, and Client Satisfaction Score allow you to track delivery quality alongside workflow position.

Pair this step with a review of your Keap tagging and segmentation strategy to confirm which data points belong as pipeline fields versus contact-level tags. The distinction matters for how you filter records in reports and how automation triggers fire.

Step 4 — Wire Stage-Entry Automation Triggers

This is where the pipeline becomes a system rather than a visual tracker. For every stage you created in Step 2, build at minimum one automation that fires when a record enters that stage.

Minimum automation per stage (any pipeline type):

  • Task assignment: Assign an action item to the stage owner with a due date based on your target time-in-stage. A recruiting pipeline stage of ‘Resume Screened’ should create a task for the recruiter to schedule a phone screen within 24 hours.
  • Internal notification: Send the stage owner and any relevant manager a notification that the record has advanced. This replaces manual status update meetings.
  • Date field stamp: Update a custom date field (e.g., “Date Entered Resume Screened”) with today’s date. This data point enables time-in-stage reporting — without it, you cannot measure cycle time.

Candidate- or client-facing automation (where applicable):

  • Recruiting: Automated acknowledgment emails at Application Received; calendar scheduling links at Phone Screen Scheduled and Interview Scheduled; offer documentation at Offer Extended. See the full guide to automating interview scheduling with Keap CRM for the calendar integration layer.
  • Sales: Proposal delivery automation at Proposal Sent stage; contract delivery at Contract Negotiation stage.
  • Projects: Kickoff packet delivery at Kickoff Complete; client review request at Client Review stage.

Deloitte research on intelligent automation confirms that rule-based stage transitions — deterministic triggers with defined inputs and outputs — are the highest-reliability automation category. Automate these before attempting anything more complex. McKinsey research on automation potential similarly identifies data capture, notifications, and scheduling as the highest-volume, lowest-risk targets for initial automation investment.

Step 5 — Build the Recruiting Pipeline Data Model Correctly

This step applies specifically to recruiting pipelines and is the most frequently misarchitected element in Keap HR implementations.

The correct data model: one contact record per candidate, one opportunity record per role application, linked to the same contact. A candidate who applies to three open roles has one contact record and three opportunity records — each independently tracked through the recruiting pipeline.

The incorrect model — and the one that collapses immediately in practice — is using a single pipeline stage field on the contact record to track hiring status. The moment a candidate re-enters your pipeline for a second role, or is considered for a role while another application is active, the data model has no way to represent both states simultaneously.

When building the opportunity record for each candidacy, link it to the correct contact record and populate the Role Title, Hiring Manager, and Source custom fields created in Step 3 before moving the record into the first active stage. This discipline prevents the most common cause of reporting failures: opportunity records that exist in a pipeline but are missing the fields that make them reportable.

For teams managing high candidate volume, pair this architecture with the guidance on Keap CRM ATS integration for recruiting workflow automation to automate opportunity record creation from inbound applications rather than creating records manually.

Step 6 — Connect the Project Pipeline to Client Contact Records

Project pipelines provide the most value when each project opportunity is linked to the client company record in Keap — not just the individual contact. This linkage allows you to view all active and historical projects for a client in one place, which directly improves renewal and upsell conversations.

Configure the project pipeline so that when an opportunity advances to Kickoff Complete, an automation fires that:

  1. Creates a tagged activity on the linked company record indicating an active project is in delivery.
  2. Assigns the project lead as the record owner.
  3. Sets a task for the account manager to conduct a mid-project check-in at the halfway point between Kickoff Date and Delivery Date (calculated using custom date fields).

When the opportunity reaches the Delivered or Invoiced terminal stage, trigger a post-delivery follow-up sequence on the contact record. This is where the pipeline connects to retention — the closed project becomes the entry point for the next engagement. Pair this with the Keap CRM onboarding automation guide for the client-side equivalent of what the project pipeline does internally.

Step 7 — Run a Five-Record Test Before Going Live

Before moving any real data into a new pipeline, create five test opportunity records and manually advance each one through every stage. For each stage transition, confirm:

  • The stage-entry automation fired (task created, notification sent, date field stamped).
  • The correct team member received the task and notification.
  • The date field was populated with today’s date, not a blank.
  • Any candidate- or client-facing email triggered correctly and displayed the right merge fields.
  • The record’s custom fields are visible and editable from the pipeline view.

Test both the standard path (record advances stage by stage to a positive terminal) and exception paths: a record skipped from stage two directly to a terminal Closed Lost stage, and a record moved backward one stage. Both scenarios should not break automation logic or create duplicate tasks.

Document any failures with the stage name and the specific trigger that did not fire. Fix before going live. Errors caught in testing cost minutes. Errors caught in production corrupt records, generate duplicate outreach, and undermine team trust in the system.

Parseur’s research on manual data entry shows that organizations relying on manual processes lose significant productivity to error correction and rework. A tested pipeline eliminates the most preventable category of those errors at the point of record creation.

How to Know It Worked

A correctly built and adopted Keap pipeline produces four measurable signals within the first 30 days of live operation:

  1. No records in a default or catch-all stage. Every active record has a defined stage with a clear next action. If you see records accumulating in your first stage without advancing, the stage-entry task is either not being created or not being assigned to the right owner.
  2. Tasks are being completed, not accumulating. Pull a task completion report filtered to pipeline-generated tasks. A healthy pipeline produces tasks that close within the target window. A pile of overdue unassigned tasks signals a trigger misconfiguration or an ownership definition problem.
  3. Time-in-stage data is populating. Your custom date fields should show data for every record that has passed through each stage. If date fields are blank, the stamp automation did not fire — identify which stage and fix the trigger.
  4. Cycle time is visible and declining. By day 30, you should be able to report average time-in-stage for each pipeline stage. This data is the foundation for the reporting work covered in the guide to custom Keap CRM dashboards for recruiting KPIs.

Common Mistakes and How to Fix Them

Mistake: Stages defined during the build, not before it

You end up with stages that overlap in meaning, owners who aren’t sure which stage is theirs, and automation triggers built on ambiguous entry criteria. Fix: Stop the build. Return to Step 1. Define entry criterion, owner, and exit trigger for every stage before resuming.

Mistake: One pipeline used for multiple distinct functions

A single pipeline trying to serve both sales and account management creates stage naming collisions and makes reporting by function impossible. Fix: Each function gets its own pipeline. Use department-prefix naming. Contacts can exist across multiple pipelines without duplication.

Mistake: Stage-entry automations built without a date stamp trigger

You have a working pipeline with tasks and notifications but no way to report on cycle time. Fix: Add a date field update action to every existing stage-entry automation. This is a retroactive fix that can be added without disrupting live records.

Mistake: Candidate status tracked on the contact record instead of the opportunity record

Works for one active candidacy per contact. Breaks immediately when a candidate applies to a second role. Fix: Migrate to the correct data model — opportunity records per role, linked to the contact — before the contact database grows large enough to make migration painful.

Mistake: No terminal stages defined

Records that don’t close pile up in the last active stage and inflate pipeline counts. Fix: Add a Closed Won and at least one Closed Lost (or equivalent) terminal stage to every pipeline. Wire a loss-reason field update to every move into a Closed Lost stage so you capture why deals, candidates, or projects failed.

Custom Keap pipelines are the operational backbone that every automation layer above them depends on. SHRM research on hiring costs confirms that process failures in recruiting translate directly into measurable financial loss — a pipeline that loses candidates between stages or fails to trigger follow-up is not a minor inconvenience. Harvard Business Review research on automation confirms that structured, rule-based process automation delivers the most consistent and measurable return before more sophisticated tooling is introduced. Build the pipeline correctly first. Everything else — integrations, AI-assisted scoring, advanced reporting — performs better inside a sound structure than on top of a broken one.

For the full implementation context that this pipeline build sits inside, return to the Keap CRM implementation checklist for recruiting teams.