# CRM outcome data vs contact lists | SourceX

Canonical: https://refer.sourcex.si/guides/crm-outcome-data-vs-contact-lists
Last updated: 2026-11-04

The CRM records that show decisions and outcomes are stage changes with dates, loss and win reasons, approvals, close dates and amounts, and case resolutions. Contact records (names, emails, phone numbers, titles) only show who the business talked to. In Salesforce terms, OpportunityHistory and OpportunityFieldHistory hold the decision trail; in HubSpot, the deal stage and the Closed lost reason property do. A partner can ask whether those tiers exist, and for how many years, without opening a single record.

## Which CRM records show decisions and outcomes rather than contact details?

Records that change because someone decided something. A contact field changes when a person moves jobs; a stage field changes when a seller, manager or customer makes a call. That difference is what separates a contact list from operational evidence.

The live SourceX page on [selling a customer list](/questions/can-you-sell-a-customer-list) explains why SourceX steers owners away from lists of people. This page answers the next question an introducer hears: "So what in our CRM is not a list?" The answer is a schema, not a file.

## The sample schema: four tiers in one CRM

The fields below are standard objects and properties documented by Salesforce and HubSpot. The tier labels are SourceX's way of sorting them for a discovery conversation.

| Tier | What it records | Salesforce example | HubSpot example | Licensing relevance |
|---|---|---|---|---|
| Contact | Who the business knows | Contact name, email, phone | Contact properties | Not the asset; SourceX steers away from it |
| Activity | What people did, in order | Logged tasks and events on a deal | Logged calls, emails, meetings | Context for a decision |
| Decision | Who changed what, and when | OpportunityHistory stage changes; OpportunityFieldHistory where field tracking was on | Deal stage; Closed lost reason | Core of the record chain |
| Outcome | How it ended | Closed opportunity with amount and close date | Is closed lost; close date set on closing | The label that makes the chain evaluable |

Salesforce describes the Opportunity object as a sale or pending deal, OpportunityHistory as its stage history, and OpportunityFieldHistory as the history of changes to field values. HubSpot documents a default Closed lost reason property, an automatically set Is closed lost flag, and a close date that is set when a deal moves into a closed-won or closed-lost stage. Checked 2026-10-18.

### One deal traced through the tiers (Illustrative)

A fictional 160-person commercial HVAC contractor runs bids through its CRM. One bid, written as metadata only, with no customer named:

| Date | Tier | Change recorded | Who changed it |
|---|---|---|---|
| 2025-03-04 | Activity | Site survey logged against the bid | Estimator |
| 2025-03-11 | Decision | Stage moved from Qualified to Proposal | Estimator |
| 2025-03-19 | Decision | Amount revised down after value engineering | Sales manager |
| 2025-04-02 | Activity | Follow-up call logged | Account lead |
| 2025-04-15 | Decision | Stage moved to Negotiation | Account lead |
| 2025-05-06 | Outcome | Closed lost; reason recorded as "lost on lead time" | Account lead |

Strip the contact tier away and the chain is still complete: what was proposed, how it changed, who changed it and why it ended. That is the shape an AI buyer studying sales or estimating decisions would care about, and the same shape appears in QA work, as in [examples with an expected outcome](/guides/how-to-identify-quality-assurance-examples-with-an-expected-outcome), and in field operations, as in [construction punch list records](/data-types/construction-punch-list-process).

### The questions that test each tier

- **Activity:** were tasks and calls logged against deals consistently, or only by some teams?
- **Decision:** was field history tracking turned on, and since when? Is a loss or win reason required at closing, or optional?
- **Outcome:** do closed records carry an amount and a close date for most years?
- **Contact:** how much of the CRM is only this tier? A CRM that is 95% contacts and 5% deals is mostly a list.

## Does the company qualify, and who decides?

A full schema helps, but eligibility comes first:

- **Size and history:** at least 50 full-time employees at peak, contractors excluded, with documented operating history. Several years of closed deals matter more than a large contact count.
- **Ownership:** sales and service records are usually the company's own; data bought from list vendors usually is not, and vendor terms may restrict it.
- **Rights and privacy:** what customers were told, what contracts say about confidentiality, and which privacy laws apply. Counsel answers these.
- **Authority:** the CRM administrator knows the schema; the CEO, CFO or head of revenue decides whether to discuss licensing.
- **Geography:** Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

RevOps consultants who already work inside client CRMs will find the project-level prompts in the [Salesforce consultants guide](/guides/how-crm-and-revops-consultants-spot-referral-opportunities-during-salesforce-projects). Screening detail is on [who qualifies](/who-qualifies).

## Limits and unanswered questions

- **Field names vary.** Custom objects, renamed stages and add-on apps change the schema. The tiers still apply; the field names in the table may not.
- **Tracking is not retroactive.** If field history tracking started in 2022, decisions before then may survive only as final values. Retention of that history is its own question: see [Salesforce field history tracking retention](/questions/salesforce-field-history-tracking-retention).
- **No value is implied.** A clean decision tier makes a company easier to review; it does not establish SourceX's current data needs or a price.
- **Compensation stays separate.** What SourceX pays the company for licensed data is agreed with the company. The partner's referral reward is paid separately by SourceX and is never deducted from the company's payout.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If an owner can confirm years of stage history and outcome fields rather than a contact export, introduce the executive who can authorize the discussion: [register](/register), check [who qualifies](/who-qualifies), and read the [terms](/terms). More partner playbooks are in [guides](/guides).

## Sources

- https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_opportunity.htm
- https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_opportunityhistory.htm
- https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_opportunityfieldhistory.htm
- https://knowledge.hubspot.com/properties/hubspots-default-deal-properties
- https://refer.sourcex.si/terms
