Solanasis Docs

solanasis-clay-earth-vs-clay-com-crm-enrichment-research-playbook-handoff-2026-03-18

26 min read

Solanasis Research Handoff: Clay.earth vs Clay.com for Founder CRM, Relationship Management, LinkedIn Import, and Enrichment — 2026-03-18

Executive Summary

This document converts the discussion into a research-grade handoff artifact for Solanasis.

Bottom-line conclusion

  • [Verified] Clay.earth is a personal CRM / personal relationship manager (PRM), not a full outbound GTM data-enrichment platform and not a classic sales CRM. Clay itself describes the category distinction: a PRM is focused on relationship context, reminders, and network memory, while a specialized CRM is built for leads, funnels, analytics, and sales process management.
    Sources: Clay PRM deep dive, Clay personal relationship manager page, Clay for Teams overview
  • [Verified] Clay.earth can import LinkedIn URLs via CSV, but that CSV import is a Pro/Teams feature.
    Source: CSV Import
  • [Verified] Clay.earth’s LinkedIn/browser workflow is useful for relationship context, not proven as a robust LinkedIn prospecting operations system. It can auto-detect LinkedIn profiles, add/update people, show interaction history and connection strength, and surface warm paths via Pathfinder. Public docs reviewed in this pass did not show strong evidence of native tracking for pending connection requests or a sales-stage pipeline model.
    Sources: Clay Browser Extension, Clay now in your favorite browser, Introducing Clay Pathfinder
  • [Verified] The user’s “$40/month Pro” assumption is incorrect for Clay.earth. Current official Clay.earth pricing shows:
    • Personal: free
    • Pro: 120/year ($10/month effective)
    • Team: shown on the pricing page as roughly 49/seat/month monthly or 41.58/month effective)
      Sources: Clay.earth pricing, Clay Billing, Subscription Plans
  • [Verified] Clay.earth’s Gmail and WhatsApp integrations have meaningful limits for CRM use.
    • Gmail: Clay uses email headers only; it does not read email bodies.
      Source: Security and Privacy, Gmail and Google Calendar
    • WhatsApp: Clay only gets a small portion of recent messages, not full history; it does not currently support multiple WhatsApp accounts simultaneously.
      Source: WhatsApp
  • [Verified] Clay.com is a different product entirely. It is the GTM data/workflow platform, and its pricing changed on March 11, 2026. Current official Clay.com FAQs show new plans such as Launch starting at 495/month, while some other Clay.com pages and legacy material still reference older plan names and prices.
    Sources: What features are included in the new plans?, What is changing?, When do changes take effect?, How much does it cost?
  • [Assistant-stated but unverified] For Solanasis at this stage, Clay.earth is best treated as a relationship OS / founder memory layer, not as the single source of truth for sales operations.
  • [Assistant-stated but unverified] If Solanasis wants one system that is closer to a true CRM now, Attio or folk are stronger candidates than Clay.earth; if Solanasis wants GTM enrichment/orchestration, that is Clay.com territory, not Clay.earth.
  • [Tentative / speculative] The best near-term operating model may be:
    1. use Clay.earth if the priority is mapping the founder’s existing network and follow-up memory,
    2. use a real CRM if the priority is pipeline structure, shared sales process, and outreach operations,
    3. only adopt Clay.com if/when the team is ready for outbound enrichment workflows and usage-based spend.

Purpose of This Document

This artifact is meant to serve as:

  • a guide for deciding whether to use Clay.earth now,
  • a playbook for how to use it if adopted,
  • a briefing memo for Solanasis leadership,
  • a handoff document for another AI so the work can continue without the original conversation.

This document emphasizes:

  • evidence status labeling,
  • verified vs unverified distinctions,
  • explicit correction of earlier ambiguities,
  • clear differentiation between Clay.earth and Clay.com.

Discussion Context

User goals and constraints

  • [User-stated] The user is evaluating whether Clay.earth could function as a CRM “for now.”
  • [User-stated] Major desired capabilities include:
    • pulling in and organizing email, WhatsApp, and message-derived contact context,
    • making LinkedIn-origin prospecting and outreach more manageable,
    • importing a batch of saved LinkedIn profile URLs,
    • understanding who is already in the founder’s network versus who still needs a connection request,
    • prioritizing who to reach out to,
    • using tags, custom fields, or “hacky” workarounds to fit Solanasis’s needs.
  • [User-stated] The user wants a proper CRM in place, but is founder-led, practical, cost-conscious, and willing to use an interim system if it materially improves execution.
  • [User-stated] The user specifically asked that the final artifact be clear about Clay.earth vs Clay.com.

Solanasis-specific operating context

  • [User-stated] Solanasis is a founder-led fractional CIO / CISO / CTO / COO firm targeting SMBs and nonprofits.
  • [User-stated] The user is especially interested in:
    • mapping warm relationships,
    • founder-led outreach,
    • enrichment and prioritization,
    • avoiding CRM bloat,
    • staying lean while getting operational leverage.

Key Facts and Verified Findings

1) Clay.earth and Clay.com are different products

  • [Verified] Clay.earth is a relationship management / PRM product. Clay’s own material repeatedly frames it as a “personal relationship manager,” “personal CRM,” “private version of LinkedIn that’s just your rolodex,” and “part contacts app and part CRM.”
    Sources:

  • [Verified] Clay.com is the GTM workflow / data-enrichment product. Public Clay.com materials describe plans in terms of data credits, actions, prospecting workflows, CRM syncs, HTTP APIs, web intent, and workflow automation.
    Sources:

  • [Verified] Confusing these two products will lead to bad tool-selection decisions. The user’s questions about contact import, LinkedIn network visibility, reminders, groups, and relationship context mostly fit Clay.earth. Questions about large-scale enrichment, credit pricing, APIs, provider waterfalls, and GTM workflows fit Clay.com.

Why this matters

  • [Assistant-stated but unverified] Most of the earlier confusion in the conversation comes from the market calling both products “Clay,” while they solve different layers of the stack:
    • Clay.earth = relationship memory + personal network intelligence
    • Clay.com = prospecting/enrichment/orchestration engine

2) Clay.earth current pricing and plan structure

  • [Verified] Clay.earth pricing page currently shows:

    • Personal: free
    • Pro: 120/year
    • Team: pricing page currently shows approximately $40/seat/month annualized
    • Enterprise: custom
      Source: Clay.earth pricing

  • [Verified] Clay help-center pricing docs still show Team as 499/seat/year ($41.58/month effective).
    Sources:

  • **[Verified] Clay.earth Pro is not approximately 40/month for Pro” is not supported by current official pricing. That figure is closer to annualized Team seat pricing, not solo Pro pricing.
    Sources:

  • [Verified] Clay offers a nonprofit discount for Clay.earth Pro. Clay says it sponsors three months of Pro for students, educators, and 501(c)(3) organizations.
    Source: Clay.earth pricing

Pricing interpretation

  • [Assistant-stated but unverified] For a solo founder, the practical Clay.earth price question is mostly:
    • free until the user needs more than 1,000 contacts or CSV import,
    • then likely Pro,
    • not Team unless shared-team visibility becomes essential.

3) Clay.earth can import LinkedIn URLs via CSV

What this means for the user

  • [Verified] The user can likely take a spreadsheet of saved LinkedIn profile URLs and import them into Clay.earth on Pro/Teams.
  • [Assistant-stated but unverified] This is one of the strongest reasons to pay for Pro if the founder already has a meaningful list of saved LinkedIn prospects or warm-network profiles.

4) Clay.earth’s LinkedIn and browser workflows

Important limitations

  • [Verified] I did not locate official evidence in this research pass that Clay.earth natively tracks LinkedIn pending invitations, connection-request stages, or a true sales pipeline.
  • [Assistant-stated but unverified] This suggests Clay.earth is better at relationship visibility than LinkedIn prospecting state management.
  • [Tentative / speculative] The user may need to represent statuses like “Need connect,” “Requested,” and “Connected” using Groups and note tags rather than native fields.

5) What Clay.earth seems to prioritize / rank

  • [Verified] Clay’s Gmail/Google Calendar docs say Clay prioritizes people depending on how well you know them and surfaces people you’ve recently emailed for the first time in Home.
    Source: Gmail and Google Calendar

  • [Verified] Clay’s messaging/social integrations also describe relevance ranking behavior.
    Sources:

  • [Verified] Reconnect for Groups provides daily recommendations based on cadence and recent interaction history.
    Sources:

Interpretation

  • [Verified] Clay does have prioritization behavior.
  • [Assistant-stated but unverified] But the prioritization appears to be about relationship relevance and follow-up reminders, not a classic lead-score system or multi-stage sales qualification model.

6) Gmail and email limits

  • [Verified] Clay’s Gmail connection creates contacts from people you’ve emailed and shows first and most recent email.
    Source: Gmail and Google Calendar

  • [Verified] Clay asks only for “email headers only” access; it can read recipients and subject lines, not email bodies.
    Source: Security and Privacy

  • [Verified] Clay explicitly says connected email accounts are only used to create contacts.
    Source: Security and Privacy

Why this matters

  • [Verified] Clay.earth is not a deep email archive or full email-content CRM.
  • [Assistant-stated but unverified] If the user expects “search my full email history semantically and use it as CRM context,” Clay.earth is likely too shallow.

7) WhatsApp limits

  • [Verified] Clay’s WhatsApp connection creates contacts for people you’ve messaged and shows messaging-related information on cards.
    Source: WhatsApp

  • [Verified] Clay says WhatsApp only lets it see a small portion of recent messages, not full history.
    Source: WhatsApp

  • [Verified] Clay does not currently support connecting multiple WhatsApp accounts simultaneously.
    Source: WhatsApp

  • [Verified] Clay says it does not read or import message text and only computes/stores aggregate messaging statistics.
    Source: Security and Privacy

Why this matters

  • [Verified] WhatsApp support exists, but it is not full-fidelity CRM ingestion.
  • [Assistant-stated but unverified] For founders who use both personal and work WhatsApp, this is a serious operational constraint.

8) Fields, tags, labels, notes, groups, and hackability

What is clearly supported

  • [Verified] Groups exist and can be used for organization.
    Source: Clay.earth pricing, plus group-specific docs below
  • [Verified] Reconnect cadences can be set at the Group level.
    Source: Reconnect for Groups
  • [Verified] Notes can be tagged with hashtags, and hashtags are searchable/clickable.
    Source: Infinite Timeline History, Tag Search, and more
  • [Verified] Source Labels exist for phone numbers and email addresses, including custom labels like work, personal, or user-created labels.
    Sources:
  • [Verified] Activity view can identify imports from LinkedIn and CSV and surface duplicates.
    Source: Activity

What was not clearly verified

  • [Verified that verification failed] I did not locate strong official evidence that Clay.earth supports arbitrary CRM-style custom fields in the way tools like Attio or Airtable do.
  • [Verified that verification failed] The pricing page says Pro can “import custom data from spreadsheets and CSVs,” but the public docs reviewed here do not clearly prove freeform custom field creation as a first-class feature.
    Source: Clay.earth pricing, CSV Import

Practical implication

  • [Assistant-stated but unverified] Clay.earth looks “hackable enough” through:
    • Groups,
    • note hashtags,
    • source labels,
    • reconnect cadences,
    • CSV-imported data, but not obviously like a true custom-schema CRM.

9) Export, portability, and lock-in considerations

Why this matters

  • [Verified] There is some portability, but not full portability of all enriched/licensed fields.
  • [Assistant-stated but unverified] This makes Clay.earth safer as a “working layer” than a total dead-end, but still not ideal if the user needs maximum structured-data ownership.

10) Team-only and paid enrichment nuances on Clay.earth

  • [Verified] Team includes “advanced data enrichment” according to the Clay.earth pricing page.
    Source: Clay.earth pricing

  • [Verified] Aura is available on Teams and Enterprise, with customizable refresh schedules, and is billed separately at $20 per 1,000 contacts.
    Source: Aura

  • [Verified] Aura does not currently support choosing which contacts to prioritize first; Clay says it prioritizes the oldest or missing data.
    Source: Aura

Why this matters

  • [Verified] Pro and Team are materially different.
  • [Assistant-stated but unverified] If the user is hoping Pro alone gives deep enrichment, that expectation is likely too high.

11) Security and permissions considerations

Why this matters

  • [Assistant-stated but unverified] For a security-sensitive consultancy like Solanasis, these permissions are not an automatic no-go, but they deserve a conscious review.

12) Clay.com current pricing and positioning (for contrast)

Why this matters

  • [Verified] Any recommendation involving Clay.com must be careful not to quote a single price as if the public pricing docs are perfectly synchronized.
  • [Assistant-stated but unverified] Clay.com should be evaluated as a separate tool-buy decision from Clay.earth.

13) Verified corrections to earlier discussion

This section records where earlier discussion needed tightening.

  • [Verified correction] Clay.earth Pro is not the approximately $40/month plan. That is closer to Team annualized seat pricing.
    Sources: Clay.earth pricing, Billing

  • [Verified correction] folk pricing cited earlier in the conversation was too low. Current official/help sources are higher:

  • [Verified correction] Attio pricing cited earlier remains broadly accurate in structure but required current confirmation. Current official pricing shows:

    • Free
    • Plus 29 annually
    • Pro 69 annually
      Source: Attio pricing

  • [Verified correction] HubSpot free CRM is still free, but the scope needs to be described carefully. Current official site says the free CRM includes up to two users and 1,000 contacts. HubSpot also promotes WhatsApp within its shared inbox / conversations stack, but that does not automatically mean every desired sales workflow is equally strong or simple.
    Sources:

Major Decisions and Conclusions

A. What Clay.earth is best for

  • [Verified] Relationship tracking, reminders, warm network visibility, contact import from multiple sources, LinkedIn context in-browser, Groups, notes, reconnect cadences, and personal/professional rolodex use.
  • [Assistant-stated but unverified] Best use case for Solanasis: founder network mapping, warm intros, thoughtful follow-up, partner/referral tracking, remembering context.

B. What Clay.earth is not clearly best for

  • [Verified] Deep email-content CRM, full WhatsApp history, multi-account WhatsApp support, clearly documented arbitrary custom-field CRM modeling, or verified native tracking of LinkedIn pending connection status.
  • [Assistant-stated but unverified] Therefore it is risky to treat Clay.earth as the single long-term sales CRM of record.

C. Pro value judgment

  • [Verified] Paying for Pro gets the user:
    • unlimited contacts,
    • CSV import/custom spreadsheet import,
    • priority support,
    • prioritized real-time network data refreshes,
    • invoice-based billing.
      Source: Clay.earth pricing
  • [Assistant-stated but unverified] Pro is worthwhile if the founder wants:
    • to bulk-import LinkedIn URLs,
    • to break the 1,000-contact ceiling,
    • to run a relationship-centric workflow.
  • [Assistant-stated but unverified] Pro is less worthwhile if the founder expects:
    • a classic CRM pipeline,
    • rich custom object modeling,
    • full multichannel sales execution.

D. Most likely recommendation for Solanasis

  • [Assistant-stated but unverified] If the immediate priority is “understand who I know, who I should reconnect with, and who is a warm path,” Clay.earth Pro is reasonable.
  • [Assistant-stated but unverified] If the immediate priority is “build a real CRM operating system for deal stages, team collaboration, and structured pipeline execution,” Attio or folk likely fit better than Clay.earth.
  • [Assistant-stated but unverified] If the immediate priority is “do outbound enrichment / signal-based prospecting / multi-provider data workflows,” evaluate Clay.com separately.

Reasoning, Tradeoffs, and Why It Matters

Tradeoff 1: Relationship intelligence vs CRM structure

  • [Verified] Clay.earth is natively optimized around relationship intelligence.
  • [Assistant-stated but unverified] Solanasis likely needs both:
    • short-term relationship leverage,
    • medium-term sales structure.

Why it matters: choosing Clay.earth alone may speed up founder follow-up but delay the creation of a real revenue system.

Tradeoff 2: Lightweight usability vs data model flexibility

  • [Verified] Clay.earth appears easier and more relationship-native than a traditional CRM.
  • [Verified that verification failed] Arbitrary custom field support was not clearly documented.
  • [Assistant-stated but unverified] This means the user may gain ease of use but lose modeling power.

Tradeoff 3: Convenience vs integration depth

  • [Verified] Clay.earth integrates with Gmail, LinkedIn, WhatsApp, iMessage, browser workflows, and export.
  • [Verified] Gmail access is header-only and WhatsApp history is partial.
  • [Assistant-stated but unverified] This means “integrated” does not equal “fully CRM-grade.”

Tradeoff 4: Solo founder efficiency vs team system

  • [Verified] Team unlocks shared-network features and advanced enrichment.
  • [Assistant-stated but unverified] Solo Pro is probably the only plan that makes sense immediately unless Solanasis is already sharing relationship management across staff.

Recommended Playbook / Process

Suggested setup

  1. Upgrade to Pro

  2. Import saved LinkedIn URLs

    • Create a CSV following Clay’s template.
    • Include at least: LinkedIn URL, name if available, company, title, group, note, cadence.
    • [Verified] LinkedIn URLs are acceptable identifiers; cadences supported include weekly, monthly, quarterly, yearly.
      Source: CSV Import

  3. Connect Gmail and LinkedIn first

  4. Treat WhatsApp as secondary

    • [Verified] Useful for contact creation and interaction context, but limited history and no multi-account support.
      Source: WhatsApp

  5. Use Groups as pseudo-status buckets

    • [Assistant-stated but unverified] Suggested Groups:
      • Warm Network
      • Need LinkedIn Connect
      • Requested on LinkedIn
      • Connected - No Reply
      • Connected - Engaged
      • Partner / COI
      • Prospect - RIA
      • Prospect - Nonprofit
      • Low Priority
    • [Verified basis] Groups and group-based reconnect cadences are supported.
      Source: Reconnect for Groups

  6. Use note hashtags as lightweight metadata

    • [Assistant-stated but unverified] Suggested tags:
      • #linkedin
      • #warmintro
      • #needsfollowup
      • #ria
      • #wealth
      • #nonprofit
      • #bookedcall
      • #security
      • #dr
      • #migration
    • [Verified basis] Tag search in notes is supported.
      Source: Infinite Timeline History, Tag Search, and more

  7. Use Source Labels for channel-specific hygiene

    • [Verified] Label emails and phone numbers as work/personal/custom.
      Source: Source Labels

  8. Set reconnect cadences by segment

    • [Assistant-stated but unverified] Example cadence model:
      • weekly: live conversations / active prospects
      • monthly: warm relationships
      • quarterly: longer-term partners and COIs
    • [Verified basis] Group and contact reconnect cadences are supported.
      Source: Reconnect for Groups

  9. Use Activity view after imports

    • [Verified] Activity can show new contacts imported from LinkedIn/CSV and duplicates to clean up.
      Source: Activity

  10. Export periodically

When this option is a good fit

  • [Assistant-stated but unverified]
    • founder-led outreach,
    • strong reliance on warm network and referrals,
    • no urgent need for complex pipeline reporting,
    • preference for elegant relationship memory over heavy CRM admin.

Option 2: Use a real CRM now, and treat Clay.earth as a sidecar

Attio

  • [Verified] Current Attio pricing: Free, Plus 29, Pro 69.
    Source: Attio pricing
  • [Verified] Attio has more explicit CRM modeling, custom relationship attributes, custom objects, workflows, sequences, API/webhooks, and reporting.
    Source: Attio pricing
  • [Verified] Attio has WhatsApp-related integrations in its app ecosystem, but the reviewed example is third-party rather than clearly first-party/native.
    Source: Attio WhatsApp integration app

folk

  • [Verified] Current official/help sources show roughly:
  • [Verified] folk markets LinkedIn extension, pipeline management, enrichment, email campaigns, and email/calendar/WhatsApp sync.
    Source: folk pricing
  • [Verified] folk help docs disclose message/enrichment limits on Standard and Premium.
    Source: folk help pricing plans

HubSpot

  • [Verified] HubSpot’s free CRM is free with up to 2 users and 1,000 contacts.
    Source: HubSpot CRM
  • [Verified] HubSpot’s conversations/shared inbox product markets WhatsApp support alongside other channels.
    Source: HubSpot shared inbox

Recommendation logic

  • [Assistant-stated but unverified]
    • If Solanasis needs a real CRM core now, Attio is the cleanest long-term foundation among the options reviewed.
    • If Solanasis wants a simple outreach-oriented CRM with LinkedIn and multichannel friendliness, folk looks appealing but needs a deeper workflow trial.
    • If Solanasis wants broad standardization and can tolerate more platform weight, HubSpot remains viable.

Option 3: Evaluate Clay.com separately for enrichment/orchestration

What it is for

What it is not for

  • [Verified] Clay.com is not the same product as Clay.earth’s personal CRM / rolodex experience.

Practical warning

Clay.earth core references

Clay.com references

Alternative CRM references

Risks, Caveats, and Red Flags

  • [Verified] Product confusion risk: Clay.earth and Clay.com are different products with different buying logic.
  • [Verified] Pricing inconsistency risk: Clay.earth Team pricing and Clay.com plan docs show some inconsistencies across official pages.
  • [Verified] Gmail depth risk: Clay.earth does not read email bodies.
  • [Verified] WhatsApp depth risk: Clay.earth only gets a small portion of recent WhatsApp messages and does not support multiple simultaneous WhatsApp accounts.
  • [Verified] Data-model risk: no strong public proof found for true arbitrary CRM custom fields in Clay.earth.
  • [Verified] Portability limitation: some licensed/enriched data cannot be exported.
  • [Verified] Permission/privacy risk: messaging integrations on desktop can require Full Disk Access on macOS.
  • [Assistant-stated but unverified] Founder-habit risk: a beautiful relationship tool can still fail if the founder does not define and stick to a status/tag/cadence system.
  • [Assistant-stated but unverified] Process drift risk: if Clay.earth is used as a pseudo-CRM too long, Solanasis may accumulate relationship data without building a real sales system of record.

Open Questions / What Still Needs Verification

  1. [Verified that verification failed] Does Clay.earth support true arbitrary custom fields?
    Public docs reviewed here did not clearly confirm it.

  2. [Verified that verification failed] Does Clay.earth track LinkedIn invitation states (pending, accepted, declined) natively?
    No clear official proof found in this pass.

  3. [Verified that verification failed] Does Clay.earth support a first-class multi-stage sales pipeline?
    Public docs reviewed here did not show it.

  4. [Verified that verification failed] How strong is Clay.earth’s duplicate resolution in messy real-world LinkedIn + Gmail + CSV imports?
    Activity/Duplicate support exists, but deeper operational quality was not independently tested.

  5. [Verified that verification failed] How well do Clay.earth browser workflows work day-to-day on LinkedIn at scale?
    Official docs describe features, but this artifact does not include hands-on product testing.

  6. [Tentative / speculative] Would Solanasis benefit more from running Clay.earth + Attio together, versus forcing Clay.earth to be the CRM?
    Likely yes, but that needs an ops design decision.

  7. [Verified] Clay.com pricing pages are in transition.
    Before budgeting Clay.com, verify directly with current official FAQs and ideally vendor confirmation.

Suggested Next Steps

If the goal is to test Clay.earth quickly

  1. [Assistant-stated but unverified] Run a 2-week founder test on Clay.earth Pro.
  2. [Assistant-stated but unverified] Import 100–300 saved LinkedIn URLs plus current warm-network contacts.
  3. [Assistant-stated but unverified] Create a fixed Group schema and hashtag taxonomy before import.
  4. [Assistant-stated but unverified] Connect Gmail and LinkedIn first; add WhatsApp only if the partial-history limitation is acceptable.
  5. [Assistant-stated but unverified] Measure:
    • how quickly the founder can find warm paths,
    • whether reconnect suggestions are actually useful,
    • whether LinkedIn-side context materially improves outreach execution,
    • whether the lack of native pipeline/custom fields becomes frustrating.

If the goal is to make a CRM decision instead of a PRM decision

  1. [Assistant-stated but unverified] Trial Attio and/or folk in parallel with a small but real Solanasis pipeline.
  2. [Assistant-stated but unverified] Compare on:
    • contact model flexibility,
    • LinkedIn workflow,
    • WhatsApp handling,
    • email sync depth,
    • list/pipeline views,
    • export quality,
    • AI utility,
    • cost after the free tier.

If the goal is enrichment/orchestration

  1. [Assistant-stated but unverified] Evaluate Clay.com only after the above is clear.
  2. [Verified] Use the current new-plan FAQs as the starting point; do not rely on older 349/$800 references without checking date/context.
    Sources:

Handoff Notes for Another AI

Use this section if continuing the work.

Core interpretation to preserve

  • The user is not just casually shopping for software. He wants a workable founder operating system that helps him:
    • map his real network,
    • see who is already warm,
    • manage people discovered on LinkedIn,
    • run follow-up consistently,
    • avoid CRM bloat,
    • and stay lean while building Solanasis.

Do not lose this distinction

  • Clay.earth = PRM / relationship OS / private rolodex / founder memory layer
  • Clay.com = GTM enrichment / prospecting automation / data workflows

Current likely recommendation state

  • Clay.earth is plausible only as:
    • a temporary relationship layer,
    • a founder-network mapping system,
    • a thoughtful follow-up tool.
  • Clay.earth is not yet proven in this research as:
    • the full CRM of record for Solanasis,
    • a native LinkedIn outreach-state manager,
    • a deep custom-schema CRM.

If continuing this project, next useful outputs would be

  1. a Solanasis-specific Clay.earth schema:
    • Groups
    • hashtags
    • reconnect cadences
    • import columns
    • review workflow
  2. a decision matrix comparing Clay.earth vs Attio vs folk vs HubSpot for Solanasis
  3. a weekend implementation guide for whichever tool is chosen
  4. a migration/exit plan so early contact work does not get trapped in the wrong tool

Important corrections to preserve

  • Prior conversation references to “$40 Pro” for Clay.earth were wrong.
  • Prior conversation references to folk pricing were understated and have been corrected here.
  • Any future mention of Clay pricing must explicitly specify which Clay product is being discussed.

Reviewer Notes and Improvements Made

Reviewer-agent capability was not available in this pass, so a serious self-review pass was performed.

Improvements made over the original discussion

  • Corrected the price confusion between Clay.earth Pro and Clay.earth Team.
  • Made the Clay.earth vs Clay.com distinction explicit and central.
  • Re-verified current official Clay.com pricing-transition details as of March 2026.
  • Corrected earlier alternative-tool pricing issues, especially for folk.
  • Tightened claims about HubSpot WhatsApp so they are not overstated.
  • Clearly separated:
    • verified facts,
    • user-stated goals,
    • assistant recommendations,
    • speculative interpretations.
  • Added missing implementation considerations:
    • export/lock-in,
    • permissions/privacy,
    • partial WhatsApp history,
    • missing proof for custom fields / LinkedIn pending invite tracking,
    • group/tag schema workaround.
  • Added a continuation-ready handoff section for another AI.

Known limitations of this artifact

  • No hands-on product testing was performed.
  • No vendor interviews or support confirmations were obtained.
  • The research relies on public official docs and pages available during this pass.
  • Some vendor public docs, especially Clay.com pricing, are visibly mid-transition and should be rechecked before purchase decisions.

Optional Appendix: Structured Summary (YAML-style)

title: "Solanasis Research Handoff: Clay.earth vs Clay.com for Founder CRM, Relationship Management, LinkedIn Import, and Enrichment"
date: "2026-03-18"
user_goal:
  status: "User-stated"
  summary:
    - "Find a practical CRM or interim system for Solanasis"
    - "Import LinkedIn-sourced people"
    - "Understand existing network vs not-yet-connected prospects"
    - "Use email / WhatsApp / LinkedIn context to prioritize outreach"
    - "Stay lean and founder-friendly"
 
main_findings:
  - status: "Verified"
    point: "Clay.earth is a PRM / personal CRM / relationship manager, distinct from Clay.com"
  - status: "Verified"
    point: "Clay.earth CSV import supports LinkedIn URLs and requires Pro or Teams"
  - status: "Verified"
    point: "Clay.earth Pro is not ~$40/month; that figure is closer to Team annualized seat pricing"
  - status: "Verified"
    point: "Clay.earth Gmail integration is headers-only, not full email-body access"
  - status: "Verified"
    point: "Clay.earth WhatsApp integration only gets a small portion of recent messages and does not support multiple simultaneous WhatsApp accounts"
  - status: "Verified"
    point: "Clay.com pricing changed on 2026-03-11 and public docs are in a mixed transition state"
  - status: "Verified that verification failed"
    point: "No clear public proof found for arbitrary custom fields in Clay.earth"
  - status: "Verified that verification failed"
    point: "No clear public proof found for native LinkedIn pending-invite tracking in Clay.earth"
 
recommendation_state:
  - status: "Assistant-stated but unverified"
    point: "Use Clay.earth only as a relationship OS / founder memory layer if warm-network leverage is the immediate priority"
  - status: "Assistant-stated but unverified"
    point: "Use Attio or folk instead if the immediate priority is a real CRM foundation"
  - status: "Assistant-stated but unverified"
    point: "Evaluate Clay.com separately if outbound enrichment/orchestration becomes the priority"
 
highest_priority_next_steps:
  - "Decide whether the immediate need is PRM or CRM"
  - "If testing Clay.earth, run a 2-week Pro pilot with a fixed Group + tag schema"
  - "If choosing a CRM, run a small live trial in Attio and/or folk"
  - "Do not budget Clay.com without checking the current March 2026 pricing FAQs directly"

Graph View