Skip to main content
Klipy’s Pipelines view shows every active deal and updates automatically as conversations happen — no manual CRM data entry required. Unlike traditional CRMs where reps re-type updates after every touch, Klipy reads email, calls, and meetings and keeps deal context aligned with what actually occurred.

How deals are created

Automatic (conversation-driven) — When Klipy detects buying signals in an email thread or call, it can suggest creating a deal linked to that conversation. You confirm before anything is saved, so new opportunities stay tied to real evidence, not guesswork. Manual — You can create a deal from any contact or company record, or start one directly in Pipelines. Use this when you already know the opportunity exists and want to attach stakeholders and context on your terms.

What’s on each deal

Every deal carries the fields your team needs to run revenue without spreadsheet gymnastics:
  • Stage — Default paths include Prospecting, Discovery, Proposal, Negotiation, Closed Won, and Closed Lost; your admin can rename and reorder stages to match your motion.
  • Stakeholders — Contacts linked to the deal so everyone with a voice in the decision is visible in one place.
  • Last activity — Updates when new conversation is captured for anyone on the deal (see below).
  • Deal score / health — Reflects sales-framework coverage and conversation momentum so you see risk before the quarter slips.
  • Next step — Pulled from the latest meeting action items or to-dos so the path forward is explicit.
  • Linked interactions — Emails, calls, and messages related to the deal, in full context.

What updates automatically

When conversations keep moving, Klipy keeps the deal record honest:
  • Last activity — New email for a deal contact updates the timestamp without you touching the CRM.
  • Action items and next steps — After a meeting summary is generated, action items and follow-ups flow into the deal so “what we owe” stays current.
  • Framework scorecard — When criteria are satisfied in conversation (for example, budget confirmed), the deal’s framework coverage reflects it.
  • Deal health — Momentum and framework signals combine into a health read so prioritization matches reality.
Stage progression is yours to confirm. Klipy may suggest a stage change based on what was said, but it does not move deals between stages on its own — you drag, click, or approve the transition so pipeline hygiene stays under human judgment.

Pipeline views

ViewWhat you use it for
KanbanScan deals by stage and drag cards forward as you confirm progression — the fastest way to see pipeline shape at a glance.
ListSort by deal score, last activity, stage, or value when you need a ranked queue, not a board.
Deal detailOpen a single opportunity for the full story: every interaction, linked contacts, and the framework scorecard in one place.

Pipeline configuration (admins)

Workspace admins shape how Pipelines behaves for the whole team:
  • Custom stages — Rename stages and set their order under Settings → Pipelines so terminology matches how your org actually sells.
  • Multiple pipelines — Stand up separate pipelines for different motions — for example New Business, Renewals, or Partnerships — so each process gets the right stages without cluttering one generic board.

Next steps

To-dos

See how action items and tasks feed into deals and daily priorities.

Sales frameworks

Learn how deal scorecards map to methodology coverage in Klipy.
Last modified on April 5, 2026