Part of the Signal Ledger site family. Structured pricing intelligence for busy buyers.

Pricing Explainer

What counts as a contact in CRM pricing?

The word contact looks simple, but vendors often mean different things when they tie pricing to stored or marketed records.

contact_limit 6 official sources

Who, How, and Why

This page should make it obvious who is responsible for it, how the conclusion was built, and why it exists.

Who

CRM Pricing Ledger Editorial Review

Source-backed pricing review

How

  • 6 official source snapshots support the examples on this page.
  • This explainer is grounded in the same normalized fields used in the vendor and comparison pages.
  • The goal is to clarify a confusing field before you trust the comparison pages built on top of it.

Why

Use this page to understand contact_limit in plain English before comparing multiple CRM vendors.

Core explanation

Read this first if you want the concept in one pass before moving into examples and comparisons.

A contact can mean a stored record, a marketable record, a billable active profile, or some narrower definition hidden in the help docs. That is why contact-based pricing feels slippery: the number itself looks comparable across vendors, but the thing being counted may not be the same. Unless the definition is normalized first, a cheap-looking contact threshold can give a very false sense of headroom.

Common mistakes

These are the misunderstandings most likely to distort a pricing comparison.

Why this matters

This is why the field deserves its own explainer instead of a footnote.

Contact definitions are one of the easiest ways a cheap-looking CRM turns into a budget problem after adoption, because the team usually discovers the real counting rules only once marketing volume or database size starts rising.

Keep exploring

Use these pages to move from definition into a real pricing decision.