Tom Ryan is most useful for explaining practical CRM integration, AI, privacy, data quality, and migration issues to marketing operations audiences.
Best for
CRM integration consultancy campaigns on Salesforce-HubSpot migrations, AI readiness, and data hygiene webinars.
Not for
Consumer short-form video, DTC skincare, or TikTok impulse purchase campaigns for 18-24 year olds.
Key takeaways
AI will not repair dirty CRM data; messy fragmented systems stay unreliable.
AI adoption also means checking privacy, data residency, and total cost.
Salesforce users may have a contract-level AI training opt-in they never turned off.
Check first: Confirm no published sponsorship route and ask for paid terms, pricing, deliverables, analytics.
Main ideas
AI cannot make a messy, fragmented CRM reliable · AI adoption also means checking privacy, residency and total cost · Test vendor announcements against what customers can actually use
Tom Ryan writes about marketing operations, especially the practical friction between Salesforce and HubSpot, and what happens when AI is layered onto CRM systems.
The posts show why readers may follow them: they connect product announcements to the less visible issues teams have to manage, from fragmented data and confusing product names to privacy settings, data residency and costs.
They also point readers toward other practitioners with specific expertise, rather than treating marketing operations as a solo conversation.
Ryan’s distinctive strength is turning CRM and AI news into concrete operational questions.
In a post about the Claude–Salesforce integration, they move beyond the launch to ask whether Claude can handle Salesforce’s separate data models and similarly named products, where customer data will go, and whether the combined costs will produce clear returns.
The conclusion is pointed: AI will not repair dirty CRM data.
A shorter post makes the same practical turn on privacy, comparing HubSpot’s reversed opt-in change with Salesforce’s contract-level permission for data to train predictive AI models, then directing readers to an opt-out resource.
Their curated list of marketing operations voices adds a community-minded counterpoint to the criticism of LinkedIn as an “AI echo chamber.”
Read together, the posts offer a useful mix of vendor scrutiny, actionable checks and attention to practitioners across the Salesforce–HubSpot landscape.
Across these LinkedIn posts, Tom Ryan tests CRM and AI claims against practical consequences: data quality, platform complexity, privacy terms and cost.
Read more
They pair skepticism about vendor announcements with concrete examples and, at times, an action readers can take.
AI cannot make a messy, fragmented CRM reliable
Ryan argues that adding an AI assistant does not solve underlying data problems; it can make them harder to spot.
Read more
Their concern is not just whether a model can answer a question, but whether it can accurately interpret data spread across different systems and product names.
In a post about Salesforce and Claude, Ryan calls the rollout “pushing all of your dirty clothes under your bed” and asks how Claude will handle Marketing Cloud, Sales Cloud and Data 360, which use different data models. They also flag confusion between similarly named Salesforce products.
AI adoption also means checking privacy, residency and total cost
Ryan treats AI integrations as operational and governance choices, not just new features.
Read more
Their posts raise questions about what customer data may be used for, where it goes, and whether the added costs and benefits make sense.
Ryan notes that Salesforce CRM users may have been opted in to training global predictive AI models through contract terms, while saying the data is anonymised and pointing readers to an opt-out route. They also raise EU data residency and the combined cost of Claude credits, Salesforce licensing and Data 360.
Test vendor announcements against what customers can actually use
Ryan questions launch framing and adoption claims, while allowing that the products may be useful.
Read more
The recurring test is whether an integration works with real data, documentation, budgets and customer needs—not just whether a vendor announces it.
Ryan calls “Claudeforce” marketing, notes that HubSpot had announced a Claude connector earlier, and questions whether Salesforce’s rollout will deliver clear ROI. At the same time, they say Claude has been useful for cleaning their own CRM and call the tools best-in-class.
Value specific expertise and useful contributions to the field
Ryan’s post recommending marketing-operations practitioners resists generic praise: each person is linked to a particular skill, contribution or style.
Read more
The list also shows an interest in expertise across Salesforce and HubSpot, and in useful comments as well as original posts.
Ryan recommends practitioners for specific areas such as Salesforce architecture, Marketing Cloud Engagement, HubSpot leadership, and knowledge of both Salesforce and HubSpot. Paul Hancock is singled out for sharp comments, not posts.
Answers the question "how does this person reason about a real product launch?" and shows the pattern of argument a reader would meet again: vendor announcement, then data model, product naming, residency, cost and contract consequences.
Read more
Tom Ryan reacts to Salesforce and Anthropic branding their Claude–Salesforce tie-up "Claudeforce", arguing the name is marketing and that the deal reads as Salesforce conceding Agentforce was not accessible enough on its own.
They note HubSpot announced a Claude connector for its CRM back in July 2025, so the integration itself is not new.
Most of the post is a list of what Ryan expects to break: data spread across Marketing Cloud, Sales Cloud and Data 360 sitting in different data models, so Claude has to reconcile them; large language models confusing similarly named Salesforce products such as Account Engagement, Engagement and Advanced/Next; EU data residency questions for companies that deliberately host in the EU, with services like Amazon Bedrock raised as a mitigation that slows things down; and the cost of stacking Claude credits on top of Salesforce licences and Data 360 credits.
Ryan calls the first phase "pushing all of your dirty clothes under your bed", predicts early announced wins followed by quiet failures, and repeats that Claude will not fix underlying data problems and may make them worse.
The post closes with a mention of a Pardot (Account Engagement) migration webinar dated 22 September and a list of Salesforce bets that did not land, including NFT Cloud, Blockchain and Quip.
For brands planning a campaign
A direct fit for a data hygiene webinar on AI-powered CRM integrations. The post argues that adding AI to a CRM won’t fix fragmented or dirty data, and offers two less obvious angles for a brand to build on: where data physically sits after an AI integration, and how credit-based AI costs stack up against existing CRM licences.
Shows the practical, check-your-settings side of Ryan's writing — the question it answers is "what should a marketing operations person actually do this week?" — and it is a good first read for someone deciding whether Ryan's advice is specific enough to act on.
Read more
Ryan agrees that HubSpot was wrong to automatically opt people into pooled-enrichment services and right to reverse course.
The post’s main point is the comparison: Salesforce CRM users were opted in to “Train global predictive AI models for use by the services and features to which you have access”, and many still haven’t turned it off.
Ryan notes that the customer data is anonymised, but the permission is written into the contract customers have already agreed to.
They point readers to the opt-out route via a help article in the comments.
The post is short and operational: one vendor correction, one less-known parallel, one action.
For brands planning a campaign
A ready-made call to action for a webinar or brief on data hygiene and AI readiness: audit contract-level AI training permissions, not just feature toggles. The HubSpot-versus-Salesforce comparison also suits a brief aimed at teams running both platforms.
Answers "what does this person value in their field?" in a compact form, and it maps the corner of marketing operations Ryan writes from, including the Salesforce-plus-HubSpot overlap that recurs in the other posts.
Read more
Ryan calls LinkedIn an AI echo chamber, then names eight marketing operations people worth following, each with a specific reason: Amnon Kruvi for Salesforce system architecture and data compliance; Andrea M.
Tarrell for founding, growing and selling a Salesforce consultancy; Mounir Nejjai for Marketing Cloud Engagement and Cezium; Sarah McDevitt for HubSpot leadership and a book on relational intelligence; Sara McNamara for being ahead of the field; Matt Pieper for Salesforce development and go-to-market engineering; Paul Hancock for sharp comments rather than posts; and Lauren Ryan for deep knowledge of both Salesforce and HubSpot.
The post ends by asking who else belongs on the list.
For brands planning a campaign
A practical starting point for assembling a webinar panel or shortlist of co-hosts, and evidence of the dual Salesforce–HubSpot expertise Ryan sees as rare and worth flagging to buyers.
Salesforce-to-HubSpot migration and AI integrations
Tom Ryan regularly migrates companies from Salesforce to HubSpot specifically for the HubSpot-Claude integration.
Read more
They note HubSpot announced a Claude connector for its CRM in July 2025, before Salesforce's Claudeforce launch. They frame Salesforce's move as a concession that Agentforce was not accessible enough and say the integration itself is not entirely new.
Compares vendor announcements with migration work and product history.
They do not treat the Salesforce-Claude launch as a first-of-its-kind integration.
For brands planning a campaign
A CRM integration consultancy can assess Tom Ryan for migration thought leadership comparing HubSpot and Salesforce AI integrations through hands-on migration experience.
Tom Ryan argues Claude will not fix underlying CRM data problems and may make them worse, likening the first phase of Claudeforce to pushing dirty clothes under the bed.
Read more
They point to data spread across Marketing Cloud, Sales Cloud, and Data 360, LLM hallucinations, and accuracy problems when models confuse Salesforce platform names.
Explains failure modes through concrete operational examples and platform architecture.
They see AI as useful for cleaning their own CRM, but not as a substitute for fixing CRM data.
For brands planning a campaign
Supports a webinar or content on data hygiene for AI-powered CRM integrations, built around the message that AI readiness depends on clean, well-modeled data.
Tom Ryan covers HubSpot's reversal on automatically opting people into pooled-enrichment services and says Salesforce CRM users were automatically opted in to train global predictive AI models.
Read more
They note the data is anonymised but already part of the contract, and provide an opt-out path.
Reads vendor policy changes and contract terms, then gives users a concrete action.
They welcome HubSpot correcting the mistake while warning that many Salesforce users remain opted in.
For brands planning a campaign
A brand can assess Tom Ryan for content on AI data governance, customer consent, and practical opt-out guidance for CRM users.
Tom Ryan raises data residency for EU companies, suggests Amazon Bedrock as a mitigation that may slow work, and questions whether ROI is clear when Claude credits sit alongside Salesforce licensing and Data 360 credits.
Read more
They describe the combination as a potential CFO challenge: budgets are finite and costs need to be predictable.
Frames vendor AI rollouts as budget, compliance, and architecture decisions.
They call the tools best-in-class while doubting the near-term ROI case.
For brands planning a campaign
A consultancy can assess Tom Ryan on the commercial and architectural tradeoffs of AI-powered CRM integrations, beyond feature announcements.
Tom Ryan reads the Claudeforce branding as marketing, calls the move 'if you can't beat them, join them,' and cites past Salesforce bets such as NFT Cloud, Quip, and repeated Agentforce references as reminders that not every bet wins.
Read more
They also note LLMs are regularly confused by Salesforce documentation.
Combines product-history skepticism with platform-specific documentation problems.
Focuses on vendor execution and adoption barriers rather than Claude's or Salesforce's underlying value.
For brands planning a campaign
A brand can assess Tom Ryan for analyst-style critique that tests vendor claims against adoption barriers and documentation realities.
Marketing-ops community curation and expert recommendations
Tom Ryan recommends a set of marketing-ops people they respect, naming Amnon Kruvi, Andrea M.
Read more
Tarrell, Mounir Nejjai, Sarah McDevitt, Sara McNamara, Matt Pieper, Paul Hancock, and Lauren Ryan, with reasons tied to Salesforce, HubSpot, AI, marketing automation, and community engagement. They ask who else to follow.
Curates peers by platform expertise and posting style, adding firsthand context where they have worked together.
The post shows Tom Ryan's willingness to promote other practitioners.
For brands planning a campaign
A brand can assess Tom Ryan for community-facing content, expert curation, or partner amplification in the marketing-ops space.
Tom Ryan's available posts name HubSpot, Salesforce, and Anthropic's Claude as platforms they work with or comment on, but do not mention a sponsorship, affiliate arrangement, investment, or named client engagement.
Read more
HubSpot is the closest thing to a working relationship: Ryan describes regularly migrating companies from Salesforce to HubSpot for the HubSpot-Claude integration and promotes a Pardot (Account Engagement) migration webinar. The remaining references are expert commentary on vendor products and decisions, not commercial relationships.
HubSpot
Mention
Ryan writes about HubSpot product decisions, including its reversal on automatically opting customers into pooled-enrichment services.
Read more
They say they regularly move companies from Salesforce to HubSpot specifically for the HubSpot-Claude integration.
They also promote a Pardot (Account Engagement) migration webinar dated 22 September through a HubSpot registration link.
Their role in the migration work and any partner or client status with HubSpot are not stated; ask for clarification before treating this as a formal working relationship.
Ryan analyses Salesforce products and strategy, questioning whether the Claude-Salesforce rollout can handle data spread across Sales Cloud, Marketing Cloud, and Data 360, and flagging data residency and credit costs.
Read more
They note that Salesforce CRM users were automatically opted in to training global predictive AI models. The posts read as customer-side critique, not a disclosed commercial tie.
Tom Ryan's LinkedIn posts focus on Salesforce and HubSpot, particularly where AI features meet CRM data quality, privacy and migration.
Read more
Start with the Claude–Salesforce post, which argues that an AI assistant does not fix fragmented platform data or confused product naming, then read the AI training opt-out post for a concrete governance action and the practitioner recommendations for the marketing-operations people they follow. The work is useful if you are weighing an AI-enabled CRM integration and want vendor framing tested against data quality, cost and residency questions rather than launch claims.
Both scrutinize Salesforce's commercial moves and ask what they cost customers.
Read more
Mansfield examines acquisition pricing and new licensing bundles; Ryan questions whether a combined Claude and Salesforce bill will pay off.
Mansfield writes from a procurement and negotiation angle, urging customers to press vendors and prepare for renewals. Ryan takes a hands-on view of migration and data hygiene, moving from a vendor announcement to its implications for CRM data, platform naming and privacy terms.
Both assess AI in enterprise software by testing readiness rather than repeating launch claims.
Read more
Votek scores companies on agent readiness and describes consulting work on agentic systems; Ryan asks whether an AI assistant can handle data spread across Salesforce products.
Votek compares scorecards across many vendors and tracks a consulting business model shifting toward software. Ryan focuses on a specific platform migration and the data problems that surface after an AI launch.
Both treat Salesforce acquisitions and AI features as architecture, not isolated products, and connect that view to implementation and integration work.
Read more
Perla argues Salesforce is assembling a complete AI operating system and frames the integration layer as an opportunity. Ryan is skeptical that an AI layer can solve fragmented CRM data, focusing on Salesforce-to-HubSpot migration, data residency and opt-out mechanics.
Tom Ryan's LinkedIn posts show a following of 12,613 and three posts published between 10 July and 31 August 2026.
Read more
That supports a reach decision: they can put a data-hygiene message in front of a self-selected LinkedIn audience in the marketing-operations and CRM-platform space at essentially no distribution cost.
The recent post mix—Salesforce's Claude integration, HubSpot's pooled-enrichment opt-in reversal, and a list of marketing-ops people worth following—is written for people who run, migrate, or buy CRM and marketing-automation systems.
The posts include no platform analytics, survey, or engagement data, so they do not show where followers are located, how senior they are, what employers or job functions they hold, or how many see any given post.
For the proposed webinar on data hygiene for AI-powered CRM integrations, the follower base is a plausible invite pool, but not proof that the right rooms will fill.
Before committing, ask for recent post analytics for comparable topics (impressions, reach, reactions, comments, click-through on links) and any audience survey or follower-demographic data covering country, seniority, industry, and job function.
If no such data exists, plan the webinar as a test with a registration target rather than an assumed attendance figure, and judge it on registrations, attendance, and pipeline from that one event.
No sponsorship program, rate card, media kit, or partnership inquiry route is published in Tom Ryan's posts.
Read more
The three LinkedIn posts contain no sponsored content, brand-partnership disclosure, or stated commercial terms.
The posts show one event-based activity: a webinar Tom Ryan hosted on Pardot (Account Engagement) migrations, promoted with an open registration link and a recording offered to people who could not attend live.
This was a self-hosted, audience-facing webinar, not a sponsorship product with stated terms.
A brand could approach them about CRM migration and data hygiene, but no package, deliverables, or pricing are specified.
Treat this as an unverified opportunity.
Before including Tom Ryan in a plan, ask whether paid placements are accepted and confirm availability, format, and terms.
Good fit for a CRM integration consultancy campaign aimed at Salesforce-HubSpot migrations and AI readiness.
Read more
Tom Ryan’s posts say they regularly migrate companies from Salesforce to HubSpot specifically for the HubSpot-Claude integration.
Their content goes beyond feature commentary to address buyer questions a consultancy needs to teach: fragmented data across Marketing Cloud, Sales Cloud and Data 360; LLM confusion over similarly named Salesforce products; EU data residency and Amazon Bedrock as a mitigation; and Claude credits stacking on Salesforce licences and Data 360 credits.
The AI training opt-in post is direct material for a data-hygiene webinar: it points to a contract-level setting many Salesforce users have not turned off and gives an opt-out action.
The Pardot migration webinar shows an existing webinar-plus-recording format for migration education.
A LinkedIn following of 12,613 supports a test invite pool, not a guaranteed attendance figure.
Ask for sponsorship terms and a rate card before planning a paid engagement or co-marketing.
Reasons: subject overlap is high; the proposed webinar topic is already present in the posts; the creator has an existing event format; and the audience is self-selected for CRM and marketing operations.
No post-level analytics or demographic information is available.
When to choose a specialist
Poor fit for a consumer short-form video campaign, such as a DTC skincare brand seeking TikTok and Instagram Reels creators to drive impulse purchases from 18-24 year olds with a guaranteed cost per acquisition.
Read more
Tom Ryan’s three posts are written LinkedIn posts about CRM migration, AI integrations, data quality, privacy opt-ins, and marketing-ops people to follow.
They contain no short-form video, consumer retail or beauty content, or visual format.
The posts give a LinkedIn follower count but no age, geography, interest, or platform composition data, so they cannot show whether the creator reaches 18-24 beauty buyers.
There is no published sponsorship format, rate card, or inquiry route; ask for the paid-product terms, pricing, and deliverables.
There is also no performance data on conversions or direct-response campaigns.
The mismatch is in topic, format, audience information, and commercial terms, not a judgement on reach.
For a B2B campaign about clean data for AI-driven CRM, the posts would be relevant; for consumer short-form sales, they are not.
A worked campaign example
Worked campaign angle for the CRM integration consultancy brief.
Angle: AI-ready CRM migration: how to move from Salesforce to HubSpot without carrying dirty data into Claude.
Format: 45-minute webinar with a live checklist and on-demand recording, hosted by Tom Ryan and a consultancy practitioner.
Audience: marketing operations, CRM owners, and RevOps leads evaluating Salesforce-HubSpot migrations or AI integrations.
Promise: walk through a pre-migration data audit covering the failure points raised in the posts: data spread across Marketing Cloud, Sales Cloud and Data 360; product-name confusion that trips LLMs; EU data residency decisions; and the cost stack of Claude credits plus Salesforce and Data 360 licensing.
Structure: (1) Why AI integrations expose data problems, using the Claudeforce example and the dirty clothes under the bed framing; (2) the contract-level settings most teams miss, including the Salesforce AI training opt-in and the HubSpot pooled-enrichment opt-in reversal; (3) a five-step migration data-hygiene checklist: inventory objects and fields, map Marketing Cloud and Account Engagement and Data 360 sources, test product-name disambiguation in prompts, document data residency and processing locations, and model AI credit and licence costs; (4) a live worked example of a Salesforce-to-HubSpot migration with a data-quality gate; (5) Q&A and next-step offer: a paid data-readiness audit or migration assessment.
Call to action: download the checklist and book a migration assessment.
Proof points: Tom Ryan’s own migration experience, the HubSpot-Claude connector timing, the Salesforce AI training opt-in issue, and the EU residency and cost questions.
Before committing, confirm whether Tom Ryan accepts paid partnerships or co-marketing, the exact deliverable and fee, post analytics for comparable LinkedIn posts, and whether the consultancy can supply the migration data and client example.
Success measures: registrations, attendance rate, checklist downloads, booked assessments, and pipeline from the webinar—not follower count alone.
Choose Adam Mansfield when the consultancy's campaign decision is about procurement leverage, renewal timing, and the cost consequences of Salesforce AI acquisitions rather than hands-on migration work.
Read more
The posts focus on Salesforce buying Listen Labs for $2B and on new Salesforce suites that bundle pricing, Slack, Tableau Next, Premier Success, and Agentforce flex credits.
They tell customers with renewals coming up to get ahead of the change and ask their rep for insight.
For a webinar aimed at finance, procurement, and vendor-management stakeholders who need to challenge AI add-on costs, Adam Mansfield is a stronger speaker than Tom Ryan.
If the consultancy wants a practical data-hygiene checklist for marketing operations teams, ask for coverage of Salesforce-HubSpot migration mechanics, HubSpot-Claude integration, Pardot or Account Engagement migration, data residency, and contract-level AI training opt-outs. This alternative shifts the session toward commercial negotiation and away from migration implementation.
Choose Max Votek when the buyer task is an executive AI-readiness assessment and the consultancy needs a framework for whether clients are architecturally ready for agents.
Read more
The posts score 22 software companies across API openness, agent-native features, data portability, real-time access, and ecosystem flexibility, placing Salesforce at 8.4, and describe consulting firms converting into software businesses with digital agents.
That gives the consultancy a strategic framing for positioning migration work within a broader agent-readiness offer.
For a C-suite or board-level webinar on where CRM migration sits in AI transformation, Max Votek is a better fit than Tom Ryan.
The material offers a broad view across vendors and consulting models, rather than a Salesforce-to-HubSpot operator perspective.
For a practical migration checklist, ask for coverage of the HubSpot-Claude connector, Pardot migration steps, marketing-ops data hygiene, and contract settings—the topics Tom Ryan's posts raise.
The tradeoff is a higher-level readiness discussion.
Choose Akhilesh Perla when the audience is enterprise architects and IT leaders and the consultancy needs to explain the integration and data-governance layer that makes AI agents safe.
Read more
The posts present Salesforce plus Informatica, MuleSoft, and Agentforce as a unified stack for data governance, metadata, and autonomous execution, and argue that Salesforce has become an AI operating system rather than only a CRM. That is a strong alternative for a technical webinar on governed agent access across CRM and back-office systems.
The content focuses on MuleSoft and Informatica architecture, rather than HubSpot migration, marketing-ops opt-outs, or the HubSpot-Claude integration at the center of Tom Ryan's brief. If the consultancy's differentiator is Salesforce-to-HubSpot migration for marketing teams, this alternative shifts the webinar toward enterprise integration architecture rather than migration data hygiene.
