Inspect a fixed six-company CRM evidence panel, four reconfirmed records and two unresolved sources or scopes. A dated baseline, not a CRM market-share estimate.
Dated evidence review ·
Q4 2026 pilot: one observation on October 15, not a completed-quarter total or a recurring publication commitment. Next editorial review due . This edition records what was checked on the review date; it does not promise current contract status. If the review is overdue, use the linked primary sources to recheck before acting.
A fixed six-company evidence panel
All six CRM company records in the retained 2026-09-12 evidence batch. Membership follows that historical batch regardless of this recheck’s outcome; later customer-directory additions are excluded.
One named company or explicitly bounded business unit, keyed by recorded domain. Casio means UK and Ireland; Spotify means the advertising workflow.
6 fixed entities
All remain in the denominator.
4 reconfirmed records
Original CRM scope supported by the checked story.
2 unresolved records
Source or scope gaps; not confirmed losses.
Reconfirmed source coverage divided by all six entities. This is not CRM market share.
Provider
Reconfirmed / panel
Share of fixed panel
Salesforce
2 / 6
33.3%
HubSpot
1 / 6
16.7%
Pipedrive
1 / 6
16.7%
A convenience panel selected for earlier published customer stories. It overrepresents public references, is not randomized or representative, and cannot estimate CRM market share, active contracts or adoption rates. Only the originally recorded provider and scope is rechecked; other providers are not exhaustively searched.
Every panel member, including unresolved records. Original observations: September 12, 2026; recheck: October 15, 2026.
Entity / original provider
Original scope
October recheck
Source timing
Siemenssiemens.com · Salesforce
Sales Cloud and customer-facing sales processes
UnresolvedThe replacement story describes Agentforce lead qualification, Commerce Cloud and Data 360. It does not re-establish the original Sales Cloud claim. No discontinuation is inferred.Check original source ↗
Published: Not statedAdoption: Not established
Spotifyspotify.com · Salesforce
Spotify Advertising: advertiser data and sales pipeline
ReconfirmedThe retained customer story supports the originally recorded CRM scope; continued contract status is not independently verified.Check original source ↗
Published: Not statedAdoption: Not established
Schneider Electricse.com · Salesforce
Global sales team CRM
ReconfirmedThe retained customer story supports the originally recorded CRM scope; continued contract status is not independently verified.Check original source ↗
Published: 2024-10-15Adoption: Not established
Casio UK and Irelandcasio.co.uk · HubSpot
UK and Ireland sales and marketing CRM
ReconfirmedThe retained customer story supports the originally recorded CRM scope; continued contract status is not independently verified.Check original source ↗
Published: Not statedAdoption: Not established
Avison Youngavisonyoung.com · HubSpot
Global customer relationship management
UnresolvedThe story URL redirects to HubSpot’s general case-study index. Prior evidence is preserved; current CRM use is unresolved, not removed.Check original source ↗
Published: Not statedAdoption: Not established
Cascade Energycascadeenergy.com · Pipedrive
Customer, sales, and operational data
ReconfirmedThe retained customer story supports the originally recorded CRM scope; continued contract status is not independently verified.Check original source ↗
Published: Not statedAdoption: 2018 (publisher-reported year)
The metric measures whether each previously recorded CRM relationship remains supported by its original public source at this recheck. It does not establish current production use. A reconfirmed record is counted once per company and provider; unresolved records remain in the six-entity denominator. Other provider relationships have not been exhaustively searched.
Why this is not CRM market share
The panel comes from an earlier convenience collection of vendor stories. Selection already depended on public disclosure, and the providers and industries were not randomly sampled. These figures cannot be generalized to CRM customers, revenue, licenses or software installations. There is no weighting or population estimate.
A repeatable next observation
For a follow-up, revisit these same six original URLs and entity scopes, retain each response and redirect, and classify reconfirmed, source unavailable or scope unresolved. Do not replace missing members with easier-to-find customers. Preserve old evidence and report missingness separately from additions or removals.
There is only one baseline under this method. The older source batch is the panel membership record, not a comparable prior-quarter observation. No quarterly trend or change rate is published. A new panel member or source-replacement policy requires a separately versioned method and a bridge table before comparing periods.
Quarterly maintenance without a publication promise
The next editorial checkpoint is January 15, 2027. A follow-up is optional until a sustainable collection process is established. If a quarterly series is promised later, every promised quarter needs a complete source audit, fixed denominator and coverage notes. This October 15 baseline remains a historical edition and is corrected only with a visible correction note.
A public job board supports an ATS observation. A subprocessor disclosure identifies a provider that may process data for particular services. A vendor customer story describes a published relationship. These sources have different scopes and are labeled separately.
Counts cover the records on these pages, not the whole market. No observation in our covered sources does not mean a company does not use a vendor. Source recency and unresolved conflicts affect confidence; observations do not establish spend, renewal timing, or customer churn.