CRM

Attio

UK / wider Europe Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Attio Ltd · attio.com

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Solo Seller v1.2 · The Data Protection Officer v1.0 · The Sales Ops Lead v1.0 · The RevOps Integrator v1.0 · The Migrator v1.1 · The Skeptic v1.2 · rubric v1 · evaluated 16 Sep 2026

Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The RevOps Integrator

Weighted verdict

Treats the CRM as one system in a revenue stack. Optimizes for two-way email and calendar sync, a real API with webhooks, and native connections to the tools money already flows through. Rejects closed ecosystems and integrations that are one-way imports in disguise.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The RevOps Integrator

Contact & data model

How this is scored

Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.

0 — A flat address book; no relations between people, companies and deals.

3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.

5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.

8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.

10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.

Report an error

The RevOps Integrator

The only data-model fact on record is objects-by-plan — up to 3/5/12/custom objects by tier — so custom objects are real, not cosmetic. But the evidence says nothing about field types, dedupe, merge tooling, activity history or relationships, and the object count is aggressively tier-gated; a modelable shell with no evidenced hygiene. 2

Report an error

Pipeline & forecasting

How this is scored

Whether the pipeline enforces a process and produces reporting a finance department accepts.

0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.

3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.

5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.

8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.

10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.

Report an error

The RevOps Integrator

The sole pipeline evidence is tagline — 'builds pipeline, advances deals' — with no pipelines, stage gates, required fields, forecasts or reports anywhere, and the pricing comparison itemizes credits, storage and email caps but not one pipeline capability. I cannot confirm this thing enforces a sales process at all, let alone produces reporting finance would accept. 2 1

Report an error

Automation & workflows

How this is scored

Triggers, sequences and routing that remove manual work without a consultant.

0 — No automation beyond email templates.

3 — Simple if-this-then-that on records; no multi-step sequences, no branching.

5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.

8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.

10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.

Report an error

The RevOps Integrator

The 'grows accounts around the clock' agentic claim is the only automation signal, and the one concrete feature is manual bulk email at 10–50 messages at a time — a blast, not a sequence. No triggers, branching, delays, routing or workflow builder appear anywhere in the record. 2 1

Report an error

Integrations & API

How this is scored

Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.

0 — No API, no sync; data enters by CSV and leaves never.

3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.

5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.

8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.

10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.

Report an error

The RevOps Integrator

Email and calendar sync is a real tiered feature — though one connected account per user until Pro is stingy for any real revenue team — but that is the entire integration story this sheet evidences: no API, no webhooks, no OAuth apps, no native directory. By this record the CRM talks to a mailbox and nothing else, which for me is a closed ecosystem until proven otherwise. 2

Report an error

European sovereignty

How this is scored

Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.

0 — US entity, US-default hosting, no public DPA or subprocessor list.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.

5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.

8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.

10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.

Report an error

The RevOps Integrator

The evidence records no sovereignty attributes at all — no DPA, no hosting region, no subprocessor list on any captured page. A London entity is a start, but provenance itself flags US-led funding as an unresolved control question, and with zero published posture I cannot distinguish this from US-reachable processing. 1

Report an error

Import, export & exit

How this is scored

Getting in with history intact, and out with everything — the anti-lock-in criterion.

0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.

3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.

5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.

8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.

10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.

Report an error

The RevOps Integrator

Complete silence on getting data in or out: not even CSV import or export is evidenced, and the pricing comparison lists no migration or export capability among its granular limits. The only data-volume facts are record caps (50k rising to custom), which measure the size of the trap, not the door. 2

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.

5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.

8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.

10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.

Report an error

The RevOps Integrator

The comparison table is unusually granular — seats, credits, records, storage, email caps — but no per-seat price figure appears anywhere in the record, the dual credit meter (seat credits 100→2,500, workspace credits 250→10,000) has no published overage rate, and Enterprise is custom-billed-annually. From what's captured, the real invoice is not computable. 2

Report an error

European sovereignty — proven facts

2 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Legal entity	Incorporated in GB ⚠ unverified	1/3 pts	4 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined	—	uncited Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	3 Report an error

Where this could be wrong

Evidence ages. The oldest capture behind this page is from 21 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
Weak sourcing — Legal entity. The Services Agreement names a second entity: US customers accepting terms on or after 5 November 2025 contract with Attio Inc., a Delaware corporation, so the contracting jurisdiction depends on customer location.
Weak sourcing — Subprocessors. Google Cloud Platform, Intercom and Anthropic are engaged through EU contracting entities in Dublin, but Google Cloud and Intercom are US-headquartered parents and OpenAI processes customer data via its US LLC.
AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

82 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
25 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
23 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
21 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
11 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
8 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us

Do you know more about Attio? Tell us Report an error on this page

Sources (15)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

1 Vendor homepage attio.com Checked 16 Sep 2026 +2 earlier captures: 15 Sep 2026, 21 Aug 2026 Details →
2 Vendor pricing page attio.com Checked 16 Sep 2026 Details →
3 Security / trust page trust.attio.com Checked 30 Sep 2026 Details →
4 Legal notice attio.com Checked 30 Sep 2026 Details →
5 Privacy policy — found from the homepage attio.com Checked 30 Sep 2026 Details →
6 Contact & data model — found from sitemap docs.attio.com Checked 1 Oct 2026 Details →
7 Contact & data model — found from sitemap docs.attio.com Checked 1 Oct 2026 Details →
8 Pipeline & forecasting — found from sitemap attio.com Checked 1 Oct 2026 Details →
9 Pipeline & forecasting — found from sitemap attio.com Checked 1 Oct 2026 Details →
10 Automation & workflows — found from sitemap attio.com Checked 1 Oct 2026 Details →
11 Automation & workflows — found from sitemap attio.com Checked 1 Oct 2026 Details →
12 Integrations & API — found from sitemap docs.attio.com Checked 1 Oct 2026 Details →
13 Integrations & API — found from sitemap docs.attio.com Checked 1 Oct 2026 Details →
14 Import, export & exit — found from sitemap attio.com Checked 1 Oct 2026 Details →
15 Import, export & exit — found from sitemap attio.com Checked 1 Oct 2026 Details →