Skip to main content
The Relationship Pipeline (/pipelines/relationship) is designed for the long game. Unlike business pipelines that track a specific transaction, this pipeline tracks where you are in your relationship with a person — from first contact all the way to loyal past client and referral source.

​
Why it exists

Real estate is a relationship business. Most deals don’t happen on first contact — they happen 3 months, 6 months, or 2 years later when a contact is finally ready to buy or sell. The Relationship Pipeline keeps every contact visible and moving forward, even when there’s no active transaction.

​
Default stages

Org admins can rename and reorder these stages in Organization → Settings → Pipelines.

​
How contacts move through it

Unlike business pipelines, contacts in the Relationship Pipeline don’t always move linearly. A lead might jump from “Contacted” back to “New Lead” if they go cold, or skip several stages if they respond immediately and book a meeting. You can move contacts by:
  1. Dragging the card on the kanban board
  2. Clicking the stage selector on the Person Detail page
  3. Workflow automation — e.g., automatically moving to “Engaged” after a contact replies to an email

​
Who appears in this pipeline

Every contact in your database is automatically enrolled in the Relationship Pipeline when created. You don’t need to manually add them — they start at “New Lead” and you move them as the relationship develops.

​
Using the Relationship Pipeline effectively

  • Sunday sweep — Once a week, scan your “Contacted” and “Engaged” columns and follow up with anyone who’s been there too long
  • Celebrate wins — Moving someone to “Past Client” or “Referral Source” is a milestone. Log a note about what made the relationship successful
  • Winnie’s suggestions — The AI Suggestions tab on the People page surfaces contacts in the Relationship Pipeline who are overdue for follow-up based on your typical cadence
  • Follow-ups hub — Open the Follow-ups hub (or the Follow-ups panel on your dashboard) to triage everyone with a due or overdue nextFollowUpDate in one place, with hot-lead and overdue signals, filters, and bulk Snooze/Mark done