What do you like best about Attio?
- Flexible data model — instead of being locked into rigid "Contacts/Companies/Deals" objects, you define custom objects, attributes, and relationships. It behaves more like a relational database with a CRM UI on top, so you can model your actual business (e.g., investors, partners, properties) rather than bending it into a sales-only schema.
- Automatic enrichment & email/calendar sync — it builds records automatically from your inbox and calendar, and enriches company/people data (funding, headcount, social, etc.) without manual entry. This is the single biggest day-to-day time saver for most teams.
- Real-time, collaborative, fast UI — spreadsheet-like views with filtering/grouping, plus a snappy interface that feels closer to Notion/Linear than legacy CRMs.
- Powerful API & webhooks — well-documented REST API, making it a good fit when you want to programmatically read/write records or wire it into automations (relevant if you're integrating it into agents or tooling).
- Workflows/automation — built-in automation builder for routing, notifications, and record updates without external tools. Review collected by and hosted on G2.com.
What do you dislike about Attio?
- Pricing scales aggressively — the per-seat cost climbs fast, and the genuinely useful features (enrichment credits, automations, more API throughput) sit behind higher tiers. For a small team it's fine; for a larger org it gets expensive relative to the value over a cheaper CRM.
- The flexibility cuts both ways — because it's data-model-first, you have to design your CRM before it's useful. There's no opinionated "just works" sales pipeline out of the box like HubSpot/Pipedrive. Teams that want to start selling on day one find the blank-canvas setup a burden.
- Reporting/dashboards are weak — analytics, forecasting, and reporting are noticeably thinner than mature CRMs. If you need real sales forecasting or rich BI-style dashboards, you'll be exporting to another tool.
- Smaller ecosystem — fewer native integrations and a smaller marketplace than Salesforce/HubSpot. You lean on the API and Zapier-style glue more often, which means more engineering effort.
- API rough edges — it's good and modern, but rate limits are tight on lower tiers, some objects/attributes are awkward to write through the API, and pagination/bulk operations can be fiddly for large syncs. Relevant if you're driving it from an agent.
- Still maturing — it's a younger product, so you hit occasional gaps (permissions granularity, mobile experience, edge-case automation logic) that the incumbents solved years ago. Roadmap-dependent.
- No real offline/strong audit story — governance, audit logs, and fine-grained role-based access are lighter than enterprise buyers expect. Review collected by and hosted on G2.com.