Signals vs Attio

Where Attio shines

Attio is one of the best-designed CRMs of its generation, and its strengths are real. The data model is unusually flexible — custom objects, custom attributes, and workflows let a team mould the CRM to its own process rather than the reverse, which is why relationship-heavy businesses like VC and PE firms, agencies, and PLG startups gravitate to it. Its native email and calendar sync is genuinely good: connect Gmail or Google Calendar (Microsoft 365 and Outlook are supported too) and Attio auto-populates fields like "Last interaction" and "Next calendar event," while maintaining a per-contact activity tab that is the closest CRM analog to a timeline. It is fast, modern, and pleasant to use in a category not known for either. Pricing is public and self-serve, starting free for up to three seats, so a small team can adopt it without a sales conversation. If your core need is a flexible system of record for relationships and deals — somewhere to run pipeline, shape custom objects around your workflow, and keep contact context current — Attio is a strong, well-built choice, and its email and calendar sync means that context is not purely manual.

Where Signals is different

Attio's activity tab is the closest a CRM comes to a timeline, but the boundary is clear: it is manually browsed CRM activity, not a cross-platform engine for "who needs a reply?" and "who is at risk?" You open a contact and read its history; Signals inverts that by computing the answers across your whole customer base and showing the timeline as evidence. The sharpest difference is billing. Attio's Stripe support comes through its official Stripe Invoicing app — invoice creation, sync, and webhook-driven invoice status on records — which is invoicing-centric, not aggregation of MRR, subscriptions, and payment history the way Signals treats Stripe. And on churn, no native health or risk score was found in Attio at all, whereas that is the question Signals exists to answer. There are practical sync edges in Attio too — private calendar events do not sync, shared inboxes are unsupported, and Microsoft 365 syncs only Inbox and Sent folders. Signals is not competing to be a better CRM; it is a read-only layer that turns activity from Stripe, Gmail, and Calendar into direct answers, rather than a place you maintain and then read through by hand.

Cost in practice

Attio's pricing is public, which keeps this honest. It is free for up to three seats, then Plus is $29 per user per month billed annually (or $36 month-to-month), and Pro is $69 per user per month annually (or $86 monthly), with Enterprise quoted custom — all as of July 2026. The model is a hybrid: per-seat tiers layered with usage-based credits, both seat credits and workspace credits for AI and automation actions, and extra workspace credits sell as add-ons from $70 to $475 a month. The headline coincidence is worth naming — Attio Plus and Signals Starter both read as "$29" — but the shapes differ entirely. Attio's $29 is per user per month on an annual commitment, so a five-person team is $145 a month before any credit add-ons; that same five-person team is $99 a month on Signals Growth, whose plan covers up to ten members — a plan price, not a per-seat one. As seats grow, a per-user CRM and a plan-based timeline diverge quickly, and Attio's credit add-ons can push the real number above the sticker. Neither is expensive at small scale; the difference is that Signals charges by plan — $29 for up to two members, $99 for up to ten — rather than multiplying by every head.

A system to maintain, or an answer you just get

Every CRM, Attio included, carries an implicit tax: it is only as accurate as the records people keep current. Attio softens that tax with excellent email and calendar sync, so some context arrives automatically — but pipeline stages, deal notes, and relationship status still depend on someone updating them, and a flexible data model is flexible precisely because you configure and tend it. That is the right trade for a team whose job is running deals and relationships. It is the wrong trade for a founder who just wants to know, this morning, which customers have gone quiet and whose payment failed. Signals asks you to maintain nothing. It has no pipeline stages to advance and no custom objects to model; it reads Stripe, Gmail, and Google Calendar and states the conclusion. The two can coexist happily — Attio as the system of record your team shapes and updates, Signals as the read-only answer layer that never needs tending. But if you do not yet have a relationship or sales motion that justifies maintaining a CRM, Signals gives you the customer visibility without the upkeep, and leaves the CRM decision for when your process actually needs one.

Switching to Signals

Connecting Signals means granting read-only OAuth to Stripe, Gmail, and Google Calendar; your history backfills on its own, and nothing you do touches or migrates your Attio workspace. Because Signals only reads and Attio remains your CRM, the two run side by side with no conflict — Signals never writes a record or moves a deal. Keep Attio for what it does best: pipeline, custom objects, and the relationship data your team maintains. Add Signals when you want churn and reply signals computed across your billing, inbox, and calendar without opening and reading each contact by hand.

Frequently asked questions