Job search
Mesh Review for Job-Search Networking: The Former Clay CRM, Contact Limits, and Trial Terms
Current official Mesh sources and two completed fictional contact-inventory and purchasing decisions, with explicit trial and data-access boundaries.
Mesh, the personal relationship manager formerly called Clay, can help a job seeker organize people they already know, remember context and plan follow-ups. Its usefulness depends on the network you bring and the routine you maintain. It is not a job board, a guarantee of introductions or evidence that someone wants to hear from you.
The main buying questions are how many contacts you need accessible, which accounts you are comfortable connecting, and what happens after the trial. Use recent roles on LandOffer.ai to identify target companies separately; a relationship manager can support the people side of that search without establishing that a contact has hiring authority.

Confirm that you are reviewing the former Clay personal CRM
Mesh's March 25, 2026 announcement says Clay became Mesh, with a new home at me.sh and existing accounts, contacts and login carrying over. This review concerns that product. It does not concern the separate Clay data-enrichment platform, whose data credits and prospecting plans should not be used to explain Mesh's contact allowance.
We checked official pricing, subscription, trial, privacy and export documentation on October 20, 2026. Native public browser checks included the pricing page's monthly and annual displays, full terms and privacy guidance. We did not create an account, start a trial, import contacts, connect email or social accounts, grant permissions, send outreach or test enrichment accuracy.
The cases below use fictional contact inventories and purchasing assumptions. They document planning decisions; we did not observe Mesh deduplication, reminder delivery or networking outcomes. Public product descriptions are attributed to the provider rather than presented as hands-on findings.
What Mesh would add to a job-search routine
The pricing page lists search and groups, reconnect prompts, reminders, birthday notifications and contact updates among Personal's core features. Those features address remembering and organizing relationships. They do not establish whether an imported person is relevant to a specific vacancy or whether a suggested reconnect is appropriate.
For a job search, a useful record might contain how you know someone, the last professional topic you discussed, an appropriate next step and a date to review it. Keep your own notes factual. “Met at an accessibility workshop” is different from “will refer me,” and a new employer listed on a profile does not mean the person can speak for that employer's hiring team.
Decide which problem you are solving before connecting everything. If you forget context across several sources and maintain many relationships, a unified view may be useful. If you only need to track a small set of conversations, a simple existing note or calendar routine may already cover the immediate need. We did not measure either workflow's time savings.
Separate the contact allowance from your priority list
Mesh's subscription guide says Personal provides access to 1,000 contacts and Pro provides unlimited contacts. The pricing page places custom spreadsheet and CSV imports in Pro. Forty networking priorities do not establish that a larger connected network fits the Personal allowance.
Estimate the full source inventory before relying on the free allowance. The same person may appear in several sources, but a planning estimate is not proof of how the product will resolve identities. The reviewed pages do not fully specify every counting, overflow or downgrade behavior. Do not promise that unwanted contacts will automatically be excluded, that duplicates will always merge correctly, or that a particular thousand records will remain accessible.
If the service's actual contact count differs from your estimate, investigate that difference before changing your plan or removing records. A filter or group may organize people without changing the underlying allowance. We did not inspect an account to establish those behaviors.
Worked inventory audit: a small outreach list inside a larger network
Consider fictional backend engineer Sam. Sam wants to review forty existing professional relationships during a job search. Their assumed source inventory contains 850 people from one source and 420 from another, with 230 identities known to appear in both. No real address book or account was read for this exercise.
| Fictional inventory item | Calculation or assumption | Completed planning consequence |
|---|---|---|
| First source | 850 people | Record the full source size, not only the forty priorities |
| Second source | 420 people | Do not assume it is entirely additional or entirely duplicate |
| Known overlap | 230 people | Estimated union is 850 + 420 − 230 = 1,040 |
| Immediate networking priorities | 40 people | A work list, not evidence that Mesh would count only forty contacts |
| Personal allowance | 1,000 contacts in the public plan | Estimated union exceeds it by forty, before any product-specific counting uncertainty |
Sam's completed decision is to postpone connecting both sources. They first need to determine the permitted source scope, the service's count and the actual downgrade behavior. They do not assume a group of forty makes the entire 1,040-person network fit the free plan, and they do not delete relationships merely to make an estimate look smaller.
The first useful networking record is also bounded. For fictional former teammate Maya, Sam writes: “Worked together on the internal deployment tool; last discussed rollback ownership. Review whether a short professional check-in would be appropriate.” Sam removes “ask Maya for a guaranteed referral,” because no such offer exists in the assumed facts.
The audit identifies both the capacity question and the reason for a professional check-in. A larger allowance addresses capacity; each proposed message still needs a relevant professional reason. No message, import or reminder was actually created here.
Read trial and renewal wording before entering a card
The pricing FAQ describes a fourteen-day Pro trial, a required card and an option to downgrade to Personal. Its wording suggests no charge unless you keep Pro. However, the Terms of Use explicitly say the trial converts to the then-current subscription price unless canceled forty-eight hours in advance. The terms also describe automatic renewal for paid subscriptions.
Do not rely on an assumption that doing nothing ends the trial. Review the exact offer, billing channel, renewal amount and cancellation deadline before enrolling. We did not enter checkout, observe a trial confirmation or determine the time zone used for any actual deadline.
The public pricing selector showed Pro at $20 per month on monthly billing. The subscription guide lists $120 per year, equivalent to $10 per month, for annual billing. That equivalent monthly figure is not a promise of a $10 month-to-month charge. The page's annual Team display also differs from its monthly display; a solo job seeker should not compare a team seat with an individual plan as if they were identical purchases.
An ongoing subscription, a downgrade to Personal, an account deletion and a refund request are separate actions. Do not treat one as proof that the others occurred. If you later subscribe, retain the selected billing period, renewal amount and confirmed cancellation or downgrade state.

Worked purchasing decision: two paid periods or a year
Sam now considers a hypothetical short job-search project. Assume they have established a need for Pro and are budgeting for two paid monthly periods after any trial. These are arithmetic assumptions, not a forecast of Sam's search duration or an account invoice.
At the documented $20 monthly rate, two paid periods cost $40 before any applicable taxes or changes. An annual plan at $120 commits three times that amount at purchase. Six $20 monthly payments equal $120; that comparison does not mean an annual subscription is automatically better, because commitment, flexibility and future need still differ.
Sam chooses the two-period budget rather than the annual purchase for this hypothetical project. The reason is uncertainty about continued use, not a claim that $40 will produce a job or that all billing channels have identical terms. If the selected offer or price changes, this decision must be recalculated from that offer.
Before any trial, Sam's written decision record is: confirm the exact trial end and time zone; plan the keep-or-downgrade decision earlier than the forty-eight-hour cancellation boundary; record the billing channel; and verify the resulting plan state. This is a completed precommitment plan, not a cancellation we performed.
Sam also identifies a stop condition: if the useful workflow cannot be evaluated without connecting a source they are not authorized or comfortable sharing, they will not proceed merely to use the remaining trial days. A free trial changes the initial price, not the data decision.
Cancellation and refunds need separate review
Mesh's cancellation guide describes cancellation taking effect at the next billing date rather than ending a paid period midway. It directs App Store subscribers to cancel auto-renewal through Apple. Check the channel that actually bills you instead of assuming a web setting controls every purchase.
The refund policy says fees are nonrefundable under the terms but describes a limited exception for payments in the last seven days when there has been no account activity during that time. It excludes periods with activity and directs App Store refunds to Apple. This is not a general seven-day satisfaction guarantee for an actively used trial conversion.
We made no cancellation or refund request. If you choose to subscribe, review the then-current policy and keep the confirmation that applies to your account. A request or an email reminder alone does not establish a completed downgrade, refund approval or stopped renewal.
Review connected data and what an export preserves
The privacy documentation describes different data scopes by integration: calendar context, email headers rather than message bodies, and messaging-interaction statistics rather than message text. It describes AI features as opt-in and says processing may use Mesh infrastructure and third-party partners. These are vendor statements, not traffic or isolation tests we performed.
Read the requested permissions for the exact integration before connecting it. A work account may contain information you cannot transfer to a personal relationship tool. Avoid recording private interview details or sensitive facts about other people simply because a notes field is available. We did not grant any integration, messaging or disk access.
Mesh's export guide says CSV export includes what you put into the service, while some added information is excluded because it is licensed. Team exports are limited to the primary account holder or an administrator. Do not assume an export reproduces every enriched field or every connected-account history.
For a job seeker, the relevant test is whether your essential relationship context remains understandable and portable under the actual plan and permissions. Keep that assessment separate from a promise of complete backup, provider-data deletion or automatic reconstruction in another tool.
Decide whether Mesh solves your actual networking problem
Mesh is worth evaluating when relationship context and follow-up organization are the missing pieces, provided its account connections, contact allowance and billing terms fit your needs. It is less compelling when a small existing routine already covers the work or when the required data access is inappropriate.
Use recent roles on LandOffer.ai for role discovery, then choose a relationship routine that fits your actual network and follow-up needs. Check the full network estimate, the selected subscription and the early trial decision point before making an authorized purchase or connection.

