11
Reviewed operator scopes
controller/property scopes
← All company lists
Marketing and CRM · October 2026 research
Workbooks CRM operator and workflow research
Review 11 controller or property scopes with Workbooks CRM disclosures: seven published declarations and four historical workflows. The historical records do not establish current use; all 11 retain unknown runtime, paid status and whole-organization coverage.
Research dated 2026-10-25. Original source dates and website scope stay with the records.
Workbooks CRM research summary
11 controller/property scopes
Research dated
Contact-free research examples · CSV
Review 11 controller or property scopes with Workbooks CRM disclosures: seven published declarations and four historical workflows. The historical records do not establish current use; all 11 retain unknown runtime, paid status and whole-organization coverage.
Download the 1-row CSV preview11 controller/property scopes; seven published declarations and four historical workflows
7
Published declarations
operator scopes
4
Historical workflows
operator scopes
Source checks record when a declaration was read; they do not establish when the technology operated.
Preview the list
Research summary and contact-free examples only. Full-file commercial delivery and source reproduction rights remain unresolved.
CSV columns: name · domain · sourceClass · checkedOn · scope
1 company in the preview
These approved examples illustrate the 2026-10-25 research. They are not a representative sample of all customers.
ARC Building Solutions
www.arcbuildingsolutions.co.uk
Company privacy-policy declaration · 2026-10-24
The policy names Workbooks CRM among third parties used. Its revision date is 16 January 2026; the internal workflow, current runtime and whole-company deployment remain unknown.
Research findings
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
7 of 11
Published and historical workflows
Seven of the 11 operator scopes have published declarations; four describe historical workflows. Checking an older workflow in October 2026 does not make it current.
Payment, current runtime, whole-organization coverage and purchasing authority remain unknown.
Research 2026-10-25 · operator scopes · WhosBuilt saved-record analysis
How this list was checked
Source checks span 2026-10-24–2026-10-25. Retained observations and examples keep their original dates.
Review 11 controller or property scopes with Workbooks CRM disclosures: seven published declarations and four historical workflows. The historical records do not establish current use; all 11 retain unknown runtime, paid status and whole-organization coverage.
| Source class | Count | Scope |
|---|---|---|
| Company privacy-policy declaration | Not separately counted | 11 controller/property scopes; seven published declarations and four historical workflows |
Published and historical workflows: 11 controller/property scopes; seven published declarations and four historical workflows Source checks record when a declaration was read; they do not establish when the technology operated.
- Source checks record when a declaration was read; they do not establish when the technology operated.
- Payment, current runtime, whole-organization coverage and purchasing authority remain unknown.
- Selected public-source searches favor indexed and detailed disclosures. The counts do not estimate market share or the full customer population.
- Unknown source reuse rights remain separate from a proposal to publish original aggregate facts and minimal paraphrases. Full-file commercial reuse remains unresolved.
- Checks run on 24–25 October 2026 retain each source's original check date. Publication, policy revision, document version and workflow period have separate meanings.
- Ultimate parents remain unknown. A controller or website property is not an independent buying group.
- Shared Workbooks login endpoints, optional integrations, skills mentions and sources with unknown CRM scope are excluded.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.