Solanasis Docs

clay-earth-crm-research-playbook-solanasis

29 min read

Clay.earth as a Founder CRM for Solanasis

Research-grade handoff, playbook, briefing memo, and continuation artifact for another AI

  • Prepared for: Dmitri / Solanasis
  • Prepared on: 2026-03-14
  • Scope: Whether to use Clay.earth as the CRM for now; what Clay.earth is actually optimized for; current pricing and upgrade triggers; fit for founder-led sales; support for email / WhatsApp / messaging / enrichment; stronger alternatives; and a practical implementation playbook.
  • Verification note: This document re-verifies major claims against official sources where possible. Where sources conflict or are incomplete, that is stated plainly.
  • Reviewer note: No reviewer-agent capability was available in the tool environment at the time of writing. A serious self-review pass was completed and documented below.

Executive Summary

  1. [Verified] Clay.earth is primarily a personal relationship manager (PRM) / personal CRM, not a full sales CRM. Clay’s own materials distinguish a PRM from a specialized CRM with sales funnels, analytics, and more complex business workflows. Clay.earth is optimized for relationship memory, reconnect reminders, notes, network search, and context across personal + professional contacts — not for being a full pipeline-centric revenue system.
    Implication: It can be useful for a founder who wins through relationships and warm intros, but it is a poor choice as the only system of record for sales operations.
    Sources: [R1], [R2]

  2. [Verified] Clay.earth’s free plan currently supports up to 1,000 contacts. Pro is listed at 120/year (effective 49/seat/month or about $40/seat/month when paid annually; the exact current team price should be re-checked before purchase. Clay also advertises 3 months of Pro for students, educators, and 501(c)(3) organizations.
    Implication: Clay.earth is not expensive for a solo founder, but pricing documentation is not perfectly consistent.
    Sources: [R3], [R4]

  3. [Verified] Clay.earth does not import email bodies and does not import message text. For Gmail/email, Clay says it only imports metadata like recipients, subject, and date — not the message body. For WhatsApp and iMessage, Clay says it never reads or stores message text and only computes aggregate interaction statistics.
    Implication: If the requirement is “search my actual emails and message conversations to run outreach well,” Clay.earth fails a core requirement.
    Sources: [R5], [R6], [R7]

  4. [Verified] Clay.earth’s WhatsApp integration is intentionally limited. Clay says WhatsApp only exposes a small portion of recent messages, not full history, and Clay does not support connecting multiple WhatsApp accounts simultaneously.
    Implication: Clay.earth is workable for relationship awareness, but weak if WhatsApp is a primary operational sales channel.
    Sources: [R6]

  5. [Verified] Clay.earth has useful AI/automation surfaces — MCP, Zapier, Make, browser extension — but some of these come with caution signs. Clay has official MCP support and official Zapier/Make integrations, but Clay’s own docs say to treat Zapier/Make as a “beta of a beta.”
    Implication: Clay can fit an AI-native workflow, but it should not be treated as a rock-solid automation backbone without testing.
    Sources: [R8], [R9], [R10], [R11]

  6. [Verified] Clay.earth has real portability and hygiene caveats. Clay supports CSV export, but says you only get what you put into Clay and cannot export all licensed data. Clay also says “permanent delete” is effectively not durable if the source integration keeps re-syncing the same contact; archive is the safer pattern.
    Implication: Do not assume Clay.earth is a fully portable, canonical source of record for enriched contact data.
    Sources: [R12], [R13]

  7. [Assistant conclusion based on verified facts] Clay.earth should not be Solanasis’s only CRM if the near-term need is founder-led outreach management across email + WhatsApp + pipeline.
    Recommended default: Use a proper CRM as the system of record, and treat Clay.earth as an optional relationship layer later.
    Why: Clay.earth is strongest as a relationship memory OS, not a full outreach + pipeline engine.

  8. [Verified] The strongest current alternatives depend on what problem you are actually solving.

    • Attio is a stronger actual CRM core: official pricing is Free, Plus 29/mo annual, Pro 69/mo annual. It supports email/calendar sync on all plans, but account limits vary by plan. Its WhatsApp option appears in Attio’s app marketplace, but it is built by Appstronauts, not Attio itself.
      Sources: [R14], [R15], [R16], [R17], [R18]
    • folk is the best “one place for interactions” candidate among the tools reviewed here, because official docs say it can sync email content, calendar content, and WhatsApp conversation threads/content. However, the pricing pages conflict, and a major gotcha exists: on Standard, connecting WhatsApp means you cannot connect email simultaneously. Premium allows multiple synced accounts and is the realistic tier for the user’s stated use case.
      Sources: [R19], [R20], [R21], [R22], [R23], [R24]
    • HubSpot remains the conservative standard CRM, but its native WhatsApp support is not a cheap/simple answer for this use case. Official docs say native WhatsApp channel support requires a WhatsApp Business account, not a personal account, and is tied to HubSpot’s inbox/help desk features in Professional/Enterprise tiers.
      Sources: [R25], [R26], [R27], [R28], [R29]

  9. [Major corrected conclusion after re-verification] If simultaneous email + WhatsApp inside one app is a must-have right now, folk Standard is not enough. Earlier casual recommendations toward folk Standard should be treated as superseded by the verified documentation showing that Standard does not allow simultaneous email + WhatsApp sync; Premium is the relevant tier.
    Sources: [R21], [R23], [R24]

Purpose of This Document

This artifact is designed to serve four functions at once:

  1. Guide — explain what Clay.earth is and is not.
  2. Playbook — help choose and implement the right CRM stack for Solanasis.
  3. Briefing memo — summarize the best-supported findings and tradeoffs for a founder decision.
  4. Handoff document for another AI — preserve enough structure, evidence labels, assumptions, and open questions that another AI can continue the work without the original conversation.

Discussion Context

User goals

  • [User-stated] The user is evaluating Clay.earth as “our CRM for now.”
  • [User-stated] The user wants a system that can pull in emails, WhatsApp, and messages to organize an outreach process.
  • [User-stated] A major requirement is enrichment and having more useful relationship context than LinkedIn provides.
  • [User-stated] The user is a founder doing founder-led sales and wants a proper CRM in place without overbuilding too early.
  • [User-stated] The user values practical, operationally useful recommendations, not generic overviews.

Operating assumptions inferred from the discussion

  • [Tentative / inferred] Solanasis likely depends heavily on:
    • warm introductions,
    • partner/referral relationships,
    • thoughtful follow-up,
    • light-to-moderate outbound,
    • lean tooling,
    • AI-native workflows.
  • [Tentative / inferred] The ideal system likely needs to balance:
    • relationship memory,
    • multichannel communication capture,
    • lightweight pipeline management,
    • data cleanliness / portability,
    • not being too enterprise-heavy too early.

Decision question

Should Solanasis use Clay.earth as its CRM for now, or use something else? If something else, what and why?

Key Facts and Verified Findings

1) What Clay.earth actually is

  • [Verified] Clay.earth’s own materials frame it as a PRM / personal CRM / relationship management platform, explicitly differentiating it from a specialized CRM used for sales funnels, financial analytics, and more complex business tracking.
    Why it matters: This is not a minor branding distinction. It directly predicts the product’s strengths and weaknesses.
    Sources: [R1], [R2]

  • [Verified] Clay.earth emphasizes:

    • relationship search,
    • reconnect cadences,
    • reminders,
    • notes,
    • updates like job changes / news mentions,
    • auto-building a network from email, calendar, LinkedIn, WhatsApp, etc.
      Sources: [R2], [R3], [R10]

  • [Assistant-stated, now largely verified] Clay.earth is best understood as a relationship memory layer or “founder rolodex with context,” not a full GTM / pipeline operating system.
    Support level: Strongly supported by product positioning and feature set, though still a synthesis rather than a vendor quote.
    Sources: [R1], [R2], [R3]

2) Clay.earth pricing snapshot

Solo / personal use

  • [Verified] Personal plan: Free, up to 1,000 contacts.
    Sources: [R3], [R4]

  • [Verified] Pro plan:

    • $20/month if billed monthly
    • 10/month)
      Sources: [R3], [R4]

Team use

  • [Verified but conflicting across official sources]
    • Pricing page shows Team at about $40/seat/month with annual billing.
    • Help-center article says Team starts at $49/seat/month.
      Interpretation: Clay may be showing annual-discounted pricing on the marketing page and monthly pricing in help content, but this should be confirmed before buying.
      Sources: [R3], [R4]

Nonprofit / education

  • [Verified] Clay advertises 3 months of Pro for students, educators, and 501(c)(3) organizations.
    Sources: [R3]

Practical cost interpretation for Solanasis

  • [Assistant conclusion based on verified facts]
    • If Dmitri uses Clay alone as a solo founder: likely 120/year if Pro is sufficient.
    • If Clay were used as a shared workspace for multiple people, total cost rises quickly relative to its limited CRM depth.

3) What Clay.earth can and cannot do with email

  • [Verified] Clay’s Gmail integration:

    • creates contacts for people you’ve emailed,
    • displays the first and most recent email,
    • prioritizes people based on interaction patterns.
      Sources: [R5]

  • [Verified] Clay explicitly says it cannot see the body of emails and only imports metadata like To, Cc, Subject, and date.
    Sources: [R5], [R7]

  • [Verified] Clay uses email headers only according to its privacy/security documentation.
    Sources: [R7]

  • [Verified] Clay supports multiple email accounts according to its team / executive-assistant documentation.
    Sources: [R14]

Why this matters operationally

  • [Assistant conclusion based on verified facts] For outreach-heavy founder work, email body visibility matters a lot:

    • recovering context before replying,
    • seeing exact objections and commitments,
    • remembering promise dates,
    • coaching or delegating later,
    • letting an AI use actual thread context.

  • [Conclusion] Clay.earth is materially weaker than Attio and folk if the real requirement is “turn my communications into an operational memory I can act on.”

4) What Clay.earth can and cannot do with WhatsApp / messaging

  • [Verified] Clay’s WhatsApp integration:

    • creates contacts for people you’ve messaged,
    • shows messaging-related information on cards,
    • helps import contacts and interaction history into Clay.
      Sources: [R6]

  • [Verified] Clay does not import message content.
    Sources: [R6], [R7]

  • [Verified] Clay says WhatsApp only exposes a small portion of recent messages, not full history.
    Sources: [R6]

  • [Verified] Clay does not support connecting multiple WhatsApp accounts simultaneously. It offers a workaround, but only the currently connected account keeps updating automatically.
    Sources: [R6]

  • [Verified] For messaging integrations, Clay’s privacy docs say Clay computes aggregate stats such as how often you’ve texted someone, but never accesses message text.
    Sources: [R7]

Why this matters

  • [Assistant conclusion based on verified facts] If WhatsApp is a primary outreach or relationship channel, Clay.earth is useful for “who have I interacted with?” but weak for:
    • reconstructing conversations,
    • searching prior discussions,
    • sharing exact context with a teammate or AI,
    • using message content to draft better follow-ups.

5) Clay.earth collaboration, AI, and automation

Collaboration

  • [Verified] Clay’s Team plan supports adding members and collaboration in a shared workspace.
    Sources: [R4], [R14]

Browser extension

  • [Verified] Clay has a browser extension for major browsers and says it can surface contact info, notes, reminders, and auto-detect LinkedIn profiles.
    Sources: [R10]

  • [Tentative / caution] An older release note described Gmail support as “rolling out soon” for the extension. That specific note should not be read as proof of current Gmail-extension parity.
    Sources: [R10]

MCP + AI

  • [Verified] Clay has official MCP support, allowing AI assistants to search network data, view communication history, and take actions like notes/groups.
    Sources: [R8], [R9]

Zapier / Make

  • [Verified] Clay supports Zapier and Make integrations.
  • [Verified] Clay’s own docs tell users to treat these as a “beta of a beta.”
    Sources: [R11], [R9]

Why this matters

  • [Assistant conclusion based on verified facts] Clay is AI-friendly enough to matter to an AI-native founder. But it is still better treated as a relationship-data layer than as the full automation hub for revenue operations.

6) Clay.earth security, privacy, portability, and hygiene

Security / privacy

  • [Verified] Clay says it is SOC 2 certified, encrypts data in transit and at rest, and does not sell customer data.
    Sources: [R7]

  • [Verified] Clay says messaging imports are local/read-only and do not read message text.
    Sources: [R7]

  • [Verified] For some desktop messaging integrations, Clay says macOS restrictions require full disk access, though Clay says it uses read-only access for the integration.
    Sources: [R7]

Data export

  • [Verified] Clay supports exporting data to CSV.
  • [Verified] Clay says you only get what you put in and cannot export all data in all fields because some information is licensed.
    Sources: [R12]

Contact deletion / reappearance

  • [Verified] Clay says permanent deletion is not effectively durable if synced integrations keep re-importing the contact; archive is the better pattern.
    Sources: [R13]

CSV import

  • [Verified] CSV import is available to Pro and Team users.
    Sources: [R30]

Why this matters

  • [Assistant conclusion based on verified facts]
    • Clay is reasonably serious on security/privacy,
    • but it is not ideal if you need a fully portable, canonical CRM database with predictable record lifecycle semantics,
    • and the “delete vs archive” behavior is a real ops caveat.

7) User-reported feedback and weak-signal evidence

Clay.earth

  • [Weakly supported / user-reported] Reddit posts show some users like Clay for personal relationship management, while others complain about public profile generation, data accuracy, or the product feeling overkill / buggy.
    Sources: [R31], [R32]

Attio

  • [Weakly supported / user-reported] Reddit feedback on Attio is mixed:
    • some users like it as a lighter, flexible CRM core,
    • some say migration/import/customization can be frustrating,
    • others say HubSpot is more mature but heavier.
      Sources: [R33], [R34], [R35]

Interpretation

  • [Assistant conclusion, cautiously stated] User-reported feedback broadly aligns with the product positioning:
    • Clay.earth = strong relationship layer, mixed on data/public-profile optics.
    • Attio = flexible modern CRM, but can feel raw or undercooked for some workflows.
    • HubSpot = mature and broad, but heavy.
    • folk = compelling for interaction capture, but more expensive/unclear on pricing than a casual first read suggests.

8) Alternatives verified during this review

A. Attio

What is verified

  • [Verified] Pricing:

    • Free: $0
    • Plus: 29/month annual
    • Pro: 69/month annual
      Sources: [R15]

  • [Verified] Email/calendar sync is available on all plans.
    Sources: [R16]

  • [Verified] Free and Plus allow one synced account per workspace member; Pro allows two; Enterprise allows more.
    Sources: [R16]

  • [Verified] Attio can sync email and calendar history, and email bodies can remain private unless shared.
    Sources: [R16], [R17], [R18]

  • [Verified] Attio has a WhatsApp integration in its app marketplace, but the listing is built by Appstronauts, not Attio.
    Sources: [R14]

Strategic interpretation

  • [Assistant conclusion based on verified facts] Attio is a better true CRM core than Clay.earth.
  • [Tentative / caution] The WhatsApp piece in Attio needs additional validation before hard commitment because it appears to be a marketplace app rather than clearly native first-party functionality.

Best fit

  • [Assistant recommendation] Best if Solanasis wants:
    • a real CRM system of record,
    • flexible objects / lists / workflows,
    • team-visible email context,
    • cleaner long-term scaling than Clay.earth.

B. folk

What is verified

  • [Verified] folk’s pricing materials conflict:

    • pricing page currently shows lower numbers,
    • help-center pricing article shows higher numbers.
      Sources: [R19], [R20]

  • [Verified] folk can import:

    • email content
    • calendar event content
    • WhatsApp conversation threads/content
      Sources: [R22], [R21], [R23], [R24]

  • [Verified] On Standard, WhatsApp and email cannot both be connected simultaneously because Standard allows only 1 synced account per member.
    Sources: [R21]

  • [Verified] On Premium, users can connect up to 5 synced accounts per member, allowing multiple WhatsApp and email accounts simultaneously.
    Sources: [R21]

  • [Verified] Standard only shows up to 30 interactions per contact (with up to 3 years of history); Premium shows unlimited interactions / full history according to help docs.
    Sources: [R23], [R24]

  • [Verified] folk lets teams share interactions at different visibility levels, including metadata-only or full-access.
    Sources: [R24], [R23]

Strategic interpretation

  • [Assistant conclusion based on verified facts] folk is the strongest single-tool multichannel interaction CRM reviewed in this document.
  • [Important corrected conclusion] For the user’s stated requirement of both email and WhatsApp, the relevant folk tier is Premium, not Standard.

Best fit

  • [Assistant recommendation] Best if Solanasis wants:
    • one app that truly captures email + WhatsApp context,
    • easier founder follow-up behavior,
    • multichannel history that an AI or teammate can actually use,
    • and is willing to pay more than the initial casual read may suggest.

C. HubSpot

What is verified

  • [Verified] HubSpot has a free CRM with contact management, deal pipelines, tasking, meeting scheduling, templates, email tracking, and reporting basics.
    Sources: [R25]

  • [Verified but pricing presentation is inconsistent due promotions] Official HubSpot materials currently show:

    • Free: $0
    • Starter: often shown as 20/seat/month.
      Sources: [R25], [R26], [R27]

  • [Verified] HubSpot’s native WhatsApp channel support requires a WhatsApp Business account, not a personal WhatsApp account.
    Sources: [R28], [R29]

  • [Verified] Native WhatsApp channel support is tied to Marketing/Service Professional or Enterprise inbox/help desk capabilities, not the basic free CRM alone.
    Sources: [R28], [R29]

Strategic interpretation

  • [Assistant conclusion based on verified facts] HubSpot is the safest “grown-up” CRM baseline, but it is not the cleanest answer to “I want email + personal WhatsApp + enriched founder outreach context in one place on a lean budget.”

Best fit

  • [Assistant recommendation] Best if Solanasis wants:
    • a more conventional CRM,
    • a long-run standard platform,
    • basic deal tracking now,
    • and can defer or externalize the WhatsApp requirement.

Major Decisions and Conclusions

Primary conclusion

  • [Assistant conclusion based on verified facts] Do not use Clay.earth as Solanasis’s only CRM if the near-term requirement is a proper founder-led sales system that captures and operationalizes email + WhatsApp + outreach context + pipeline.

Secondary conclusion

  • [Assistant conclusion based on verified facts] Clay.earth is still useful — but in a narrower role:
    • founder relationship memory,
    • warm intro map,
    • reconnect engine,
    • note/reminder layer,
    • relationship intelligence companion.

Tool-choice conclusion

Option 1 — Best CRM core

  • [Assistant recommendation] Attio Plus / Pro as the actual CRM system of record.
    Reason: It is a real CRM, supports synced email/calendar with controllable visibility, and is better suited to pipeline truth than Clay.earth.

Option 2 — Best one-tool communications-centric choice

  • [Assistant recommendation] folk Premium if simultaneous email + WhatsApp content in one place is truly the top priority.
    Reason: Verified docs show real conversation/content capture, but only Premium cleanly supports simultaneous sync.

Option 3 — Relationship-first sidecar

  • [Assistant recommendation] Clay.earth Pro only if the main problem is remembering people and nurturing a warm network — and pair it with a real CRM rather than replacing one.

Option 4 — Conservative standard

  • [Assistant recommendation] HubSpot Free / Starter if the goal is simply “get a standard CRM in place now” and solve WhatsApp later or externally.

Reasoning, Tradeoffs, and Why It Matters

Tradeoff 1: relationship memory vs pipeline truth

  • Clay.earth strength: “Who do I know? what changed? when should I reach out? what do I know about them?”
  • Clay.earth weakness: “What stage is this opportunity in? what is forecasted? what sequence or process is active? what is the team-wide source of truth?”

Why it matters: Solanasis likely needs both. If only one tool is chosen, pipeline truth usually matters more than elegant relationship memory.

Tradeoff 2: metadata-only vs full conversation access

  • Clay.earth: email subject / recipients / message counts, no body text, no WhatsApp content.
  • folk: email content and WhatsApp thread content.
  • Attio: synced email + calendar with share controls; better than Clay on email context.

Why it matters: Founder-led sales often depends on exact details from past conversations. Losing body/message content creates expensive memory gaps.

Tradeoff 3: privacy / permissions vs usefulness

  • Clay.earth: strong privacy posture, but some integrations require desktop/full-disk style permissions and still intentionally avoid message bodies.
  • folk / Attio: more operationally useful because they can store richer interaction content, but that also increases sensitivity and governance burden.

Why it matters: Solanasis is security-oriented. Tool choice needs to reflect both operational utility and client-data hygiene.

Tradeoff 4: elegance vs operational completeness

  • Clay.earth: elegant, opinionated, likely pleasant for a founder.
  • HubSpot: complete, standard, but heavier.
  • Attio: flexible CRM core, but can feel raw to some users.
  • folk: operationally rich for interactions, but pricing and plan limits are less straightforward than they first appear.

Why it matters: Bad CRM fit kills usage. But “pleasant” is not enough if the system does not capture the information you need to sell.

Recommended Playbook / Process

Path A — If the immediate problem is “I need a real CRM now”

Recommendation: Start with Attio Plus.
Why:

  • real CRM core,
  • better email/calendar operational memory than Clay.earth,
  • cleaner scaling path,
  • more appropriate as system of record.

Use Clay.earth later only if relationship-memory friction remains high.

Path B — If the immediate problem is “I need one place for email + WhatsApp conversations”

Recommendation: Pilot folk Premium, not Standard.
Why:

  • verified simultaneous email + WhatsApp sync support,
  • verified content/thread visibility,
  • strong interaction capture.

Caveat: Reconfirm pricing at purchase time because official materials conflict.
Extra caveat: Verify data governance and whether the interaction-sharing model fits Solanasis.

Path C — If the immediate problem is “I mostly sell through warm relationships and intros”

Recommendation: Use Clay.earth Pro only as a relationship operating system paired with a basic CRM.
Pairing candidates:

  • Attio Free / Plus
  • HubSpot Free / Starter

Phase 1 — Clarify the real job-to-be-done

Write down, explicitly:

  1. Is the tool the system of record?
  2. Is the tool the relationship memory layer?
  3. Is the tool the multichannel communications archive?
  4. Is the tool the outbound/sales execution layer?

Rule: Do not let one tool silently drift into all four roles unless it has actually proven itself there.

Phase 2 — Set success criteria before migrating anything

For the chosen pilot, define pass/fail criteria:

  • Can it handle email + WhatsApp + LinkedIn-originated contacts the way Dmitri actually works?
  • Can it capture enough detail to let an AI prepare follow-ups?
  • Can it support a simple but real pipeline?
  • Can the data be exported cleanly enough if the tool is abandoned?
  • Can privacy/sharing be configured safely?
  • Is it pleasant enough that Dmitri will actually use it daily?

Phase 3 — Run a 7–14 day pilot with a subset

Use:

  • 25–50 active prospects,
  • 20–30 partner/referral relationships,
  • 10–20 legacy warm contacts.

Do not start with full import.

Test:

  • deduplication quality,
  • timeline usefulness,
  • search quality,
  • follow-up workflow,
  • data export,
  • how easily a note or task gets captured after a call/message.

Phase 4 — Build the minimum viable CRM schema

Regardless of tool, create the following minimum fields / attributes:

Core record fields

  • Person name
  • Company
  • Email(s)
  • Phone / WhatsApp number
  • Primary channel
  • Relationship owner
  • Referral source
  • Relationship type (prospect / partner / client / advisor / vendor / friend-of-firm)
  • ICP segment
  • Geography
  • Notes summary
  • Last touch date
  • Next action date
  • Current stage
  • Deal / project value range
  • Confidence / warmth score
  • Key pain / trigger
  • Compliance sensitivity / NDA / private notes flag

Suggested sales stages for Solanasis

  • New / uncategorized
  • Warm lead
  • Discovery needed
  • Discovery scheduled
  • Diagnosed / scoped
  • Proposal sent
  • Follow-up
  • Closed won
  • Closed lost
  • Long-term nurture
  • Referral source / partner only

Phase 5 — Define channel policy

This is critical.

Decide up front:

  • which email accounts sync,
  • whether personal accounts sync,
  • whether WhatsApp is personal or business,
  • who can see content vs metadata only,
  • whether sensitive threads stay private,
  • whether AI tools can access synced interaction content.

Security-minded default:
Use the smallest set of synced accounts that still makes the tool useful.

Phase 6 — Founder operating cadence

Daily (10–20 min)

  • Triage new contacts/imports
  • Log notes immediately after important calls
  • Set next action for every active opportunity
  • Move contacts into correct group/stage

Weekly (30–45 min)

  • Review pipeline by stage
  • Review “no touch in 14/30/60 days”
  • Review partner/referral relationships
  • Clean duplicates / archives
  • Export a backup snapshot if the system is early-stage and still experimental

Monthly

  • Check whether the current tool is still the right system of record
  • Review contact quality and field completeness
  • Verify that exports / backups are usable
  • Re-check pricing/plan fit

Fast recommendation matrix

ToolBest useBiggest strengthBiggest weaknessBest-fit verdict
Clay.earthRelationship memory / warm-network managementBeautiful PRM, reconnects, notes, founder contextNo email bodies, no message text, not a full sales CRMUse as sidecar, not sole CRM
AttioCRM core / structured pipelineReal CRM, synced email/calendar, scalable foundationWhatsApp depends on marketplace app; some users find it roughBest default CRM core
folk PremiumOne place for multichannel interactionsCaptures email + WhatsApp conversation contentPricing/docs conflict; Premium likely requiredBest one-tool option if comms capture is top priority
HubSpotConservative standard CRMMature, broad, standard, free entry pointNative WhatsApp not cheap/simple for this use caseGood baseline if WhatsApp can wait

Risks, Caveats, and Red Flags

Clay.earth-specific

  • [Verified] It is not a full CRM in the classic sales-ops sense. [R1], [R2]
  • [Verified] No email body import. [R5], [R7]
  • [Verified] No message text import. [R6], [R7]
  • [Verified] WhatsApp history is limited; multiple accounts unsupported simultaneously. [R6]
  • [Verified] Some automation docs explicitly say “beta of a beta.” [R9], [R11]
  • [Verified] Export does not include all licensed data. [R12]
  • [Verified] Delete semantics are weak; archive is the safe pattern. [R13]

folk-specific

  • [Verified] Pricing docs conflict. [R19], [R20]
  • [Verified] Standard plan does not support simultaneous email + WhatsApp. [R21]
  • [Verified] Standard interaction history/display limits may be constraining. [R23], [R24]

Attio-specific

  • [Verified] Free/Plus account sync limits may matter for multi-account founders. [R16]
  • [Verified] WhatsApp support appears marketplace-based, not clearly native first-party. [R14]
  • [Weakly supported / user-reported] Some users report friction with migration/setup. [R33], [R34], [R35]

HubSpot-specific

  • [Verified] Native WhatsApp requires WhatsApp Business, not personal. [R28], [R29]
  • [Verified] The cheapest plan is not sufficient for native WhatsApp channel needs. [R28], [R29]
  • [Verified] Pricing presentation varies across official pages due promotions and packaging context. [R25], [R26], [R27]

Open Questions / What Still Needs Verification

  1. Clay.earth Team pricing exact current terms

    • Official sources conflict.
    • Need current quote / checkout confirmation.

  2. folk’s exact current pricing

    • The public pricing page and help-center pricing article disagree materially.
    • Need live quote or in-app confirmation before buying.

  3. Attio WhatsApp reliability and security posture

    • The marketplace listing exists, but further validation is needed on:
      • data retention,
      • message sync depth,
      • vendor support,
      • security reviews,
      • whether it behaves well at founder scale.

  4. Whether Solanasis needs personal WhatsApp or WhatsApp Business

    • This sharply affects HubSpot viability.
    • It may also affect governance and role separation.

  5. How much of the workflow is warm-network cultivation vs structured outbound

    • If mostly warm-network, Clay.earth becomes more attractive as a sidecar.
    • If more structured outbound, a real CRM core matters more.

  6. Whether AI access to communications content is acceptable

    • Tools that store message/email bodies are more useful, but also more sensitive.

  7. Clay.earth public-profile/privacy optics

    • There are user-reported complaints about public profiles and data accuracy. This was not deeply verified here and should be checked directly before adopting the platform for a privacy-sensitive firm.

  8. Need for shared inbox / shared phone / sequence tooling

    • If this becomes important soon, CRM selection may shift again.

Suggested Next Steps

Run two short pilots in parallel:

  1. Attio Plus as the CRM-core candidate.
  2. folk Premium as the multichannel-interactions candidate.

Do not start by piloting Clay.earth as the only CRM.
If desired, pilot Clay.earth separately as a relationship sidecar after the CRM-core question is settled.

Specific pilot checklist

  • Import a controlled subset only.
  • Connect one real email account.
  • Connect the relevant WhatsApp account.
  • Create one minimal pipeline.
  • Test:
    • search,
    • note capture,
    • next-action workflow,
    • timeline usefulness,
    • AI usefulness from stored context,
    • export,
    • duplicate handling,
    • privacy/sharing controls.

Decision rule

Pick the tool that best satisfies the following in order:

  1. captures the communications context you actually need,
  2. is usable every day,
  3. preserves pipeline truth,
  4. has acceptable data-governance behavior,
  5. is affordable enough to keep.

Handoff Notes for Another AI

What another AI should know immediately

  • The user is not asking for generic CRM theory. He is evaluating a real near-term tooling decision for Solanasis.
  • The user’s stated requirement includes email + WhatsApp + messages + enrichment.
  • A key hidden discovery from re-verification is that Clay.earth is not really built to be the only CRM for this use case.
  • Another key hidden discovery is that folk Standard is not sufficient for simultaneous email + WhatsApp; Premium is the relevant tier.
  • Another key hidden discovery is that HubSpot’s native WhatsApp answer is narrower and more expensive than many people assume.
  • The strongest current recommendation is:
    • Attio if the priority is a real CRM core,
    • folk Premium if the priority is one app that actually captures multichannel interaction content,
    • Clay.earth only as a relationship layer or sidecar.

What another AI should avoid

  • Do not casually recommend Clay.earth as a full CRM without acknowledging:
    • no email bodies,
    • no message content,
    • limited WhatsApp history,
    • no simultaneous multi-WhatsApp support,
    • portability / archive caveats.
  • Do not recommend folk Standard for this use case without acknowledging the synced-account limitation.
  • Do not recommend HubSpot as the easy WhatsApp answer without clarifying the Business-account and tier requirements.

Good continuation questions for future work

  • Should Solanasis separate personal relationship memory from firm CRM data?
  • Should Dmitri use a personal WhatsApp account, a WhatsApp Business account, or both?
  • How much of outreach will remain 1:1 founder-led vs delegated to an EA, contractor, or AI agent?
  • Does the team need shared inbox, sequence automation, or proposal/workflow tracking in the same tool?

Reviewer Notes and Improvements Made

Reviewer-agent status

  • No reviewer-agent capability was available in the environment at the time of writing. I checked for available tool-space/reviewer resources and none were available.
  • A serious self-review pass was completed instead.

Major improvements made during self-review

  1. Corrected the folk recommendation.
    Earlier casual guidance that folk Standard could be the “best compromise” was not precise enough. Verified docs show Standard cannot support simultaneous email + WhatsApp sync. This document upgrades the recommendation to folk Premium when that combined requirement is non-negotiable.

  2. Tightened the Clay.earth positioning.
    The earlier answer correctly leaned against using Clay.earth as the sole CRM, but this document now grounds that more rigorously in Clay’s own PRM-vs-CRM language and integration limits.

  3. Added data-portability and record-lifecycle issues.
    Export restrictions and the delete-vs-archive behavior are important operationally and were missing from the earlier answer.

  4. Clarified HubSpot’s WhatsApp limitations.
    This document makes it explicit that native HubSpot WhatsApp support is not the cheap/simple path for a founder wanting personal-style multichannel outreach capture.

  5. Distinguished Clay.earth from Clay.com.
    These are different products serving different jobs. Confusing them can create a bad buying decision.

  6. Elevated evidence labeling.
    Important points are now explicitly tagged as Verified, User-stated, Assistant-stated but unverified, or Tentative/speculative.

Optional Appendix — Structured Summary (YAML-style)

document:
  title: "Clay.earth as a Founder CRM for Solanasis"
  prepared_on: "2026-03-14"
  confidence: "moderate to high on core findings; moderate on pricing snapshots with conflicting docs"
 
user_goal:
  stated:
    - "Evaluate Clay.earth as CRM for now"
    - "Pull in emails, WhatsApp, and messages"
    - "Organize founder outreach process"
    - "Get proper enrichment beyond LinkedIn"
  inferred:
    - "Need a lean but real CRM system"
    - "Warm-network selling matters"
    - "AI-native workflow is desirable"
 
main_findings:
  - status: verified
    point: "Clay.earth is a PRM / personal CRM, not a full sales CRM"
  - status: verified
    point: "Clay.earth free = 1000 contacts; Pro = 20 monthly / 120 annual"
  - status: verified
    point: "Clay.earth does not import email bodies"
  - status: verified
    point: "Clay.earth does not import message text"
  - status: verified
    point: "Clay.earth WhatsApp history is limited and multiple WhatsApp accounts are not supported simultaneously"
  - status: verified
    point: "Clay.earth export excludes some licensed data and archive is safer than delete"
  - status: verified
    point: "folk Standard cannot support simultaneous email + WhatsApp sync"
  - status: verified
    point: "folk Premium can support simultaneous multiple synced accounts"
  - status: verified
    point: "Attio is a stronger CRM core with synced email/calendar"
  - status: verified
    point: "HubSpot native WhatsApp requires WhatsApp Business and higher-tier inbox/help-desk support"
 
recommendation:
  primary: "Use Attio as CRM core, or folk Premium if multichannel conversation capture is the top priority"
  secondary: "Use Clay.earth only as a relationship layer/sidecar, not sole CRM"
  avoid:
    - "Using Clay.earth as only CRM for email + WhatsApp + pipeline"
    - "Choosing folk Standard for simultaneous email + WhatsApp"
    - "Assuming HubSpot solves personal WhatsApp cheaply"
 
open_questions:
  - "Exact current folk pricing"
  - "Exact current Clay.earth Team pricing"
  - "Attio WhatsApp integration reliability/security"
  - "Personal WhatsApp vs WhatsApp Business strategy"
  - "Whether Solanasis needs shared inbox/sequences soon"
 
next_actions:
  - "Pilot Attio Plus with subset"
  - "Pilot folk Premium with subset"
  - "Define required fields/stages before full import"
  - "Delay Clay.earth sidecar decision until CRM-core decision is made"

References

Clay.earth / official

folk / official

Attio / official

HubSpot / official

Clay.com (different product than Clay.earth)

User-reported / weak-signal sources

Graph View