Anne Sloan works on CRM operations and process improvement, including HubSpot migrations, workflow design, automation, and AI integrations. Their posts also discuss practical UX research.
Useful for practical HubSpot CRM migration, lead and deal process design, workflow automation, and AI integration advice.
Best for
B2B SaaS teams needing HubSpot process planning, migration sequencing, and post-migration workflow refinement.
Not for
Reach-driven brand awareness or video-first sponsored campaigns for a general business audience.
Key takeaways
Filtering data too early in a HubSpot migration created downstream risks from unknown dependencies.
A single update replaced manual changes across multiple fields and records, improving consistency.
Spreadsheets, inboxes, and people's heads can show a CRM is only a record system.
Check first: Confirm deliverables, timeline, disclosure, and examples of long-form work or client outcomes.
Main ideas
A CRM migration is a process and adoption project, not just a technical one · A CRM only improves the processes that actually happen inside it · Process comes before software configuration
Anne Sloan’s posts show practical work at the intersection of CRM operations and process improvement, especially around HubSpot.
Rather than treating a migration as a software swap, they describe the work of cleaning and validating data, redesigning workflows, supporting adoption, and deciding what information teams should use consistently.
The posts also show smaller-scale automation and an AI-to-CRM integration, alongside an interest in practical UX research.
The clearest reason to follow them is their concrete account of how operational problems emerge—and how teams can rethink the process, not just the tool.
Sloan connects process advice to specific operational examples.
During a HubSpot migration, filtering data too early created downstream risks because dependencies between records, fields, and workflows were not yet understood.
In another example, a single update replaced manual changes across multiple fields and records; the benefit was not dramatic time savings per use, but greater consistency and less reliance on memory.
They also point to workarounds in spreadsheets, inboxes, and people’s heads as signs that a CRM may be functioning only as a record system.
Together, these examples show why migration work continues after launch and how small process changes can reduce errors.
A separate post about UX research adds a related principle: research should surface learning, including indications that a design is not working, rather than merely confirm a decision.
Anne Sloan's ideas center on treating CRM work as operations design rather than software administration.
Read more
Migrations are process, communication, and adoption projects; data decisions carry downstream consequences; workflows should be simplified and automated for consistency; and AI is most useful when connected to the tools and data already in use. A parallel thread from UX research, borrowed from Erika Hall, is that research should reduce risk and produce learning rather than validate a predetermined design.
A CRM migration is a process and adoption project, not just a technical one
Anne Sloan argues that a CRM migration is never only technical.
Read more
It is also a process, communication, and adoption project.
They defined phase 1 of a HubSpot migration as reaching functional parity with the previous CRM, meaning the team could do everything it could do before.
They then described the hidden work after migration: refining workflows, improving processes, identifying gaps, supporting adoption, and finding opportunities to create additional value.
Sloan's first migration lesson was that data clean-up decisions carry downstream risk.
They filtered and cleaned portions of the dataset too early, before fully understanding dependencies between records, fields, and workflows.
In hindsight, they recommend cleaning and validating the dataset as comprehensively as possible before filtering, transforming, or removing data.
They also credited Riley Popovich for onboarding support, noting that help articles and AI were not enough.
A CRM only improves the processes that actually happen inside it
Anne Sloan observed that a CRM can only improve processes that actually live inside it.
Read more
In their experience, the old CRM had become a record-keeping system while workarounds pushed client communication, preferences, and context into spreadsheets, inboxes, and people's heads.
The migration forced a larger question: what information should live in the CRM, and how should teams use it consistently?
They say the result was more standardized workflows, clearer reporting, less manual tracking, and fewer workarounds.
Sloan notes that the technology upgrade mattered, but the bigger opportunity was operational alignment. Their closing argument is that a CRM migration does not automatically fix broken processes, though it creates a rare chance to redesign them intentionally.
This sharpens the migration argument in the earlier post by naming operational alignment, not software replacement, as the main source of value.
Anne Sloan describes setting up a lead and deal process in HubSpot from scratch and emphasizes thinking through the process before configuring software.
Read more
Their working questions include what information is actually needed, what should trigger the next step, what can happen automatically, where something might fall through the cracks, and what people are being asked to do manually that they do not need to do. Process improvement, in this view, is a habit of noticing opportunities in CRM workflows, email marketing, long-maintained spreadsheets, and inherited steps followed because that is how it has always been done.
Sloan describes poking around a process everyone assumed was simple and discovering it was approximately 47 steps, with the aim of removing 40 of them.
Small process improvements can compound, even when they are not urgent
Anne Sloan argues that some of the most valuable CRM improvements are the small, invisible ones: process changes that save a few minutes, eliminate a few clicks, or reduce the chance of human error.
Read more
They say these improvements are often hard to prioritize because teams are busy with day-to-day requests, and improving a process can feel like a luxury when immediate demands compete for attention.
Sloan built an automation for a process that previously required someone to manually update multiple fields across multiple records.
Now a single update triggers everything else automatically.
The time saved on any one instance is not dramatic, but they say the process becomes faster, more consistent, and less dependent on someone remembering every step, so the benefits compound each time it runs.
They conclude that an hour spent improving a process can be worth more than an hour spent doing things the old way.
AI is most valuable when connected to existing tools and data
Anne Sloan describes MCP, the Model Context Protocol, as being like an API for AI, connecting AI tools to other platforms so they can work together.
Read more
They integrated an AI tool with their CRM and report practical effects rather than abstract potential.
After the integration, Sloan reports being better prepared for meetings, having more comprehensive follow-up, and being able to pull data quickly instead of spending time creating a report. Their takeaway is that AI's value is not only what it can do alone but what happens when it connects to tools and data already in use.
Research should reduce risk and produce learning, not validate a design
Anne Sloan discussed Erika Hall's book Just Enough Research with a UX book club and summarized its core idea as “Research Reduces Risk.”
Read more
They quote Hall's advice to identify the highest-priority questions, meaning the assumptions that carry the biggest risk.
Their main takeaway is to avoid framing the goal of UX research as validating a design, because that sets up any other result as failure.
The goal is to learn, and learning that a design is not working can save significant time and money.
Sloan obtained a certification, UX Research in Action – Practical Skills for Real-World Impact, from Maven, led by Joe Formica and Jean Coletta “Cola” Solwitz, to become more effective at collecting, analyzing, and applying user research.
The certification extends the research thread from reading and discussing method to formal skill development.
One post answers the question “what does this person actually do?”
Read more
It sets out a HubSpot migration, defines its first milestone, and lists what happens after launch. It is the clearest single entry point to Anne Sloan's work.
Anne Sloan defines phase 1 of a HubSpot migration as reaching functional parity with the previous CRM: the team can do everything it could do before.
The hidden work comes next: refining workflows, closing gaps, supporting adoption, and finding value after launch.
The post commits to a series on the challenges and lessons.
Lesson #1 is data clean-up.
The specific mistake was filtering and cleaning portions of the dataset too early, before understanding the dependencies between records, fields, and workflows.
The stated fix is to clean and validate the dataset as thoroughly as possible before filtering, transforming, or removing anything.
Sloan also names Riley Popovich for onboarding support, noting that help articles and AI were not enough.
For brands planning a campaign
Anne Sloan's posts describe hands-on HubSpot migration ownership, with a defined milestone and a stated post-launch plan. For a post-migration workflow improvement plan, the lesson about sequencing data clean-up before filtering offers a direct, checkable starting point.
Answers “can this person design a lead and deal process rather than just administer a tool?”
Read more
The post briefly demonstrates the questions they ask when building one.
The post describes a week or two spent setting up the lead and deal process in HubSpot from scratch.
The interesting part, Sloan says, was thinking through the process rather than configuring the software.
The working method is a set of questions: what information is needed, what should trigger the next step, what can happen automatically, where something might fall through the cracks, and what people are being asked to do manually that they do not need to do.
Sloan frames process improvement as a habit of noticing: in a CRM workflow, an email marketing process, a long-maintained spreadsheet, or steps everyone follows because that is how it has always been done.
The post ends with a concrete image: a process everyone assumed was simple turns out to be about 47 steps, with the aim of removing 40 of them.
For brands planning a campaign
Directly supports a lead/deal process optimization engagement. The question list works as an intake checklist for a discovery session, and the post shows an interest in process design rather than treating the work as a software task.
Answers “what is the thinking behind this person's migration approach?”
Read more
It explains why a tool upgrade alone does not fix operations and what must change alongside it.
Sloan observes that a CRM can improve only the processes that actually happen inside it.
Before the migration, the old CRM had known limitations, and people had built workarounds: information lived in spreadsheets, inboxes, and people's heads.
The CRM had become a record-keeping system rather than an operational tool, and client communication, preferences, and context were not stored consistently.
The migration prompted a bigger question: what information should live in the CRM, and how should teams use it consistently?
The listed outcomes are more standardized workflows, clearer reporting, less manual tracking, and fewer workarounds.
The technology upgrade mattered less than the operational alignment.
A migration does not fix broken processes automatically, but it creates a rare chance to redesign them deliberately.
For brands planning a campaign
A strong angle for a post-migration engagement: redesign processes during the migration window rather than repeat existing workarounds. The list of workaround symptoms—spreadsheets, inboxes, and unwritten knowledge—offers a useful diagnostic for testing a client's current state.
Answers “how does Sloan think about automation and incremental improvement?”
Read more
It includes the most concrete example of a workflow they built and why it mattered.
The post argues that valuable improvements in a CRM migration are often small and invisible: workflow changes that save a few minutes, remove a few clicks, or reduce the chance of human error.
The example is an automation that replaces a process where someone manually updated multiple fields across multiple records; now a single update triggers everything else.
Sloan is explicit that the time saved on any one instance is not dramatic.
The real gain is a faster, more consistent process that does not depend on someone remembering every step, with benefits compounding each time it runs.
The second half explains why this work is hard to prioritize: teams are busy with day-to-day requests, and improving a process can feel like a luxury.
The conclusion is that an hour spent improving a workflow can be worth more than an hour spent doing things the old way.
The challenge is recognizing when to step out of execution mode.
For brands planning a campaign
Directly relevant to workflow refinement: the post shows Sloan's criteria for choosing automation candidates—error reduction and consistency, not headline time savings—and their argument for funding that work against competing day-to-day demands. It also offers useful language for justifying a process-improvement workstream to a client.
Answers “does this person work with current AI tooling in a CRM context?”
Read more
It is a short, practical account of one integration and what it changed.
Sloan explains MCP (Model Context Protocol) as being like an API for AI, connecting AI tools to other platforms so they can work together.
They describe integrating an AI tool with their CRM and report three practical effects: better preparation for meetings, more comprehensive follow-up, and the ability to pull data quickly instead of spending time creating a report.
The takeaway is that AI's value comes not only from what it can do on its own, but also from connecting it to tools and data already in use.
For brands planning a campaign
Evidence of applied AI-in-CRM integration work, not just commentary. It fits a brief that includes connecting AI assistants to CRM data, and the reported outcomes offer measurable starting points for such a project.
Answers “where does the research side of this person's practice come from?”
Read more
It shows a habit of reading and applying methods, not just using tools.
Sloan discussed Erika Hall's “Just Enough Research” with a UX book club and summarized the book as “Research Reduces Risk.”
The quoted advice is to identify the highest-priority questions: the assumptions that carry the biggest risk.
Sloan's main takeaway is that research should not be framed as validating a design, because that makes any other result look like failure.
The goal is to learn, and learning that a design is not working can save significant time and money.
For brands planning a campaign
Secondary to a CRM operations brief, but relevant when a project includes user or stakeholder research: the post shows an existing method for framing research questions around risk rather than confirmation.
CRM migration as process, communication, and adoption work
Anne Sloan describes CRM migrations as more than technical projects: they also involve process, communication, and adoption.
Read more
They completed phase 1 of a HubSpot migration, defining it as reaching functional parity with the previous CRM. They then outlined the hidden work that follows: refining workflows, improving processes, identifying gaps, supporting adoption, and finding opportunities to create additional value.
Sloan created a step-by-step migration plan and a pre-import checklist of cleanup tasks, including identifying duplicate or incomplete records, formatting fields, and addressing inconsistent naming.
For brands planning a campaign
A B2B SaaS company planning or refining HubSpot operations can use Sloan's phased definition and hidden-work checklist to budget for adoption and process redesign alongside data transfer.
Sloan's first migration lesson: seemingly small data-cleanup decisions can have large downstream effects.
Read more
They filtered and cleaned parts of the dataset too early, before fully understanding dependencies between records, fields, and workflows. In hindsight, they say, teams should clean and validate the dataset as thoroughly as possible before filtering, transforming, or removing data.
For brands planning a campaign
For lead and deal process optimization, a brand can ask Sloan to sequence validation before filtering or remapping, reducing rework during and after a HubSpot migration.
Sloan argues that some of the most valuable CRM improvements are small, invisible process changes — saving a few minutes, eliminating clicks, or reducing the chance of human error — rather than big, visible ones.
Read more
They built an automation that triggers multiple field changes across records with a single update, replacing manual work. Each instance saves modest time, but Sloan says the process becomes faster, more consistent, and less dependent on someone remembering every step, with benefits that compound.
For brands planning a campaign
A HubSpot operations review can include an audit of repetitive manual updates, with Sloan proposing automations ranked by compounding reliability gains, not just time saved per task.
Sloan describes setting up a lead and deal process in HubSpot from scratch and emphasizes thinking through the process before configuring software.
Read more
They ask what information is actually needed, what should trigger the next step, what can happen automatically, where something might fall through the cracks, and what people are asked to do manually that they don't need to do.
Sloan looks for process improvement opportunities in everyday places — CRM workflows, email marketing, long-maintained spreadsheets, and inherited steps followed because 'that's just how we do it.' They investigate supposedly simple processes, uncover their many steps, and work to remove the unnecessary ones.
For brands planning a campaign
For lead and deal process optimization, Sloan's process-first questions can anchor a workshop or audit that maps triggers, automation candidates, and failure points before HubSpot configuration.
CRM as an operational tool, not just record-keeping
Sloan observed that a CRM can only improve the processes that actually happen inside it.
Read more
In their experience, the old CRM had become a record-keeping system, while workarounds pushed client communication, preferences, and other context into spreadsheets, inboxes, and people's heads.
The migration prompted a broader question: what information should live in the CRM, and how should teams use it consistently?
The result was more standardized workflows, clearer reporting, less manual tracking, and fewer workarounds.
Sloan says the technology upgrade mattered, but the bigger opportunity was operational alignment. A CRM migration doesn't automatically fix broken processes, but it creates a rare chance to redesign them intentionally.
For brands planning a campaign
A post-migration process refinement plan can include a 'What lives where?' decision session and a cleanup of workarounds that keep context outside HubSpot, improving reporting and handoffs.
Sloan describes MCP (Model Context Protocol) as 'like an API for AI' that connects AI tools with other platforms.
Read more
They integrated an AI tool of choice with the CRM and reported being better prepared for meetings, providing more comprehensive follow-up, and retrieving data quickly instead of spending time creating reports. Sloan's takeaway: AI's value lies not only in what it can do alone but also in what happens when it connects to existing tools and data.
For brands planning a campaign
For a HubSpot operations brief, a brand can ask Sloan to identify practical AI integration points — meeting prep, follow-up drafting, data retrieval — and assess readiness and governance before connecting tools.
Sloan discussed 'Just Enough Research' by Erika Hall with a UX book club and summarized its core idea as 'Research Reduces Risk.' They highlighted Hall's advice to identify the highest-priority questions and the assumptions carrying the biggest risk.
Read more
Their biggest takeaway: avoid framing research as validation of a design, because that makes any other result feel like failure.
The goal is to learn; discovering that a design isn't working can save time and money.
Sloan also obtained a certification, UX Research in Action - Practical Skills for Real-World Impact, from Maven, to become more effective at collecting, analyzing, and applying user research.
These UX research posts sit outside day-to-day CRM operations, but show a method Sloan may bring to CRM process decisions: prioritize risky assumptions and treat findings as learning rather than validation.
For brands planning a campaign
A CRM operations engagement can include a short discovery step where Sloan identifies the riskiest assumptions about lead and deal processes and designs small learning loops before large configuration changes.
Anne Sloan’s posts name two businesses: HubSpot, the CRM platform they use for a migration and a from-scratch lead and deal setup, and Maven, provider of a UX research course they completed.
Read more
Neither post discloses a sponsorship, affiliate arrangement, paid partnership, or investment. Ask Sloan to confirm any commercial relationships relevant to a campaign.
HubSpot
Mention
Sloan works inside HubSpot rather than for it.
Read more
They describe finishing phase 1 of a CRM migration into HubSpot, defined as reaching functional parity with the previous CRM, then moving into workflow refinement, process improvement, and adoption support.
A separate post covers setting up the lead and deal process in HubSpot from scratch, including decisions about what information to capture, what triggers the next step, and what can be automated.
The posts disclose no vendor relationship, partnership, reseller status, or payment; ask Sloan to confirm any such relationship before a campaign.
Sloan completed Maven’s course, "UX Research in Action - Practical Skills for Real-World Impact," taught by Joe Formica and Jean Coletta Solwitz.
Read more
They said it made them more effective at collecting, analyzing, and applying user research. Ask whether the course involved a sponsor, affiliate arrangement, or partnership before a campaign.
Start with Anne Sloan's posts on HubSpot lead-and-deal setup and CRM migration lessons, then follow the thread into workflow automation and MCP/AI integrations.
Read more
The UX research posts explore how teams reduce risk through learning. Readers seeking migration strategy beyond CRM can compare with Justin Emond; those working on plant-floor operations and documentation can look to Eric Ciampoli; those dealing with small-business bookkeeping and compliance can look to Grace Lee Ostiguy.
Both treat platform migrations as strategic and process decisions, not just technical builds.
Read more
Anne Sloan writes that a CRM migration is a process, communication, and adoption project, while Justin Emond writes that Shopify migrations are won or lost on decisions about what to keep, kill, or rethink.
Anne Sloan focuses on internal CRM operations, data clean-up, adoption, and lead/deal workflows. Justin Emond focuses on ecommerce replatforms, merchandising, bundling, and revenue strategy.
Both focus on operational improvement: aligning systems, simplifying processes, and making knowledge and visibility more useful on the ground.
Read more
Eric Ciampoli writes about ERP alignment, process optimization, and plant documentation; Anne Sloan writes about CRM process redesign, workflow automation, and operational alignment.
Eric Ciampoli works in manufacturing, plant-floor operations, and OPSIDIAN documentation. Anne Sloan works in CRM systems, HubSpot, AI integrations, and UX research.
Both address the cost of manual back-office tracking and the value of cleaner operational systems.
Read more
Grace Lee Ostiguy writes about bookkeeping, compliance, and financial visibility for small businesses; Anne Sloan writes about CRM data clean-up, workflow automation, and reducing manual work.
Grace Lee Ostiguy focuses on bookkeeping, tax compliance, and financial peace of mind for service businesses. Anne Sloan focuses on CRM operations, lead/deal processes, and AI-to-CRM integration.
The only measured audience figure available is Anne Sloan's LinkedIn follower count: 1,092, recorded on 8 October 2026.
Read more
That supports a small, test-scale LinkedIn engagement with people who manage CRM and process work, not a reach-driven campaign or a buy justified by verified practitioner composition.
Their posts do not say where followers are based, their job roles or seniority, or their employer type.
For a campaign aimed at HubSpot operations, audience relevance therefore rests on subject matter, not measured audience makeup.
The subject matter is consistent and specific: HubSpot lead and deal process design, post-migration workflow refinement, automation that replaces manual field updates, data clean-up, and connecting AI tools to a CRM through MCP.
That range points to a working audience of CRM administrators, operators, and process improvers rather than a general marketing following.
Ask for a recent LinkedIn audience breakdown covering geography, age, and gender, plus an audience survey or other documented results for occupation, seniority, and employer type, since platform demographic data cannot verify those attributes.
Also request recent results for comparable topics, depth, and formats; views accumulated across posts of different ages and subjects do not show that a topic or format caused the difference.
Anne Sloan's posts do not announce a partnership or sponsorship offer.
Read more
There is no media kit, rate card, sponsored-post example, affiliate arrangement, newsletter sponsorship, or official inquiry route.
The posts are first-person accounts of CRM migration, HubSpot lead-and-deal process setup, workflow automation, AI integration, and UX research; none disclose a paid brand relationship.
For a B2B SaaS buyer planning HubSpot process work, there is no packaged deliverable to budget against.
Any collaboration would start with direct contact through their LinkedIn profile, where the scope for HubSpot process work, deliverables, timeline, and disclosure terms would be agreed case by case.
Strong fit as a capability engagement rather than a reach play.
Read more
Brief
A B2B SaaS company wants to improve its HubSpot CRM operations and is assessing Anne Sloan for a plan covering lead and deal process optimization and post-migration workflow refinement.
Reasons
For a plan covering lead and deal process setup in HubSpot and post-migration workflow refinement, the posts describe the exact work. Sloan set up a lead and deal process in HubSpot from scratch and explained the questions they work through: what information is actually needed, what should trigger the next step, what can happen automatically, where something might fall through the cracks, and what people are being asked to do manually that they do not need to do. That list can be used almost unchanged as an intake-session agenda.
Sloan frames CRM migrations as process, communication, and adoption projects, not technical ones, and defines the first phase as reaching functional parity with the previous system. For a company mid-migration or just past go-live, that framing matches the brief's second half: refining workflows, closing gaps, and supporting adoption after launch.
There is a concrete, checkable lesson to build the plan around. Sloan filtered and cleaned parts of a dataset too early, before understanding dependencies between records, fields, and workflows. They now advise cleaning and validating as comprehensively as possible before filtering, transforming, or removing data. A client can test its migration plan against that sequence.
Sloan's automation criterion suits post-migration refinement. Rather than claiming large time savings, they argue that automation makes processes faster, more consistent, and less dependent on someone remembering every step, with gains that compound each time the process runs. Use that approach to rank automation candidates by error reduction and reliability, not headline minutes saved.
The operational-alignment argument gives the engagement its scope. Sloan observed that a CRM can only improve the processes that actually happen inside it, and that their own system had become a record-keeping tool while context lived in spreadsheets, inboxes, and people's heads. The fix was to decide what information should live in the CRM and how teams should use it consistently, producing more standardized workflows, clearer reporting, less manual tracking, and fewer workarounds.
Sloan connected an AI tool to their CRM through MCP and reported better meeting preparation, more comprehensive follow-up, and faster data retrieval. This is relevant if the brief extends to AI-assisted workflows; ask for evidence across platforms if that broader capability is required.
Best formats
Advisory or consulting-style engagement on migration sequencing and lead/deal process design, with a written plan as the deliverable
Co-created practical content — checklists, decision sessions, before-and-after workflow write-ups — rather than broad brand-awareness placement
A bounded discovery engagement: one process-mapping session plus a prioritized automation and clean-up list
Constraints
Fit rests on subject matter, not measured audience. The only audience figure available is a LinkedIn follower count of 1,092, recorded 8 October 2026. Treat content placement as a small, test-scale LinkedIn engagement with people who manage CRM and process work.
There is no documented media kit, rate card, sponsored-post example, or published inquiry route. Scope any collaboration through direct contact, agreeing on deliverables, timeline, and disclosure in advance.
Every post here is short-form LinkedIn text. Ask for examples of long-form reports, workshops, or client outcomes if those are required.
When to choose a specialist
Poor fit for this brief.
Read more
Brief
A brand-awareness campaign for a productivity app aimed at a general business audience, judged on reach and built around a video-first sponsored package: several short videos plus high-impression paid amplification on LinkedIn and other channels.
Reasons
The reach target cannot be supported by the available data: the only measured audience figure is 1,092 LinkedIn followers, recorded 8 October 2026. There is no reported data on geography, seniority, job role, or employer type. Ask for audience composition data before planning impressions or measuring delivered awareness.
The format does not match the posts here. All are written LinkedIn posts, with no video, audio, or visual work to demonstrate that Sloan produces the required video deliverables.
The message does not match Sloan's subject matter. Their work is about internal CRM operations — process design, data clean-up, workflow automation, integrations — not broad productivity messaging for a general business audience. A campaign that needs an accessible, wide-appeal spokesperson would work against the specificity that makes Sloan useful.
There is no packaged commercial offer to price against. With no documented media kit, rate card, or sponsored-post example, a video package with paid amplification would have to be built from scratch rather than matched to an existing product.
The campaign depends on current AI-tool coverage, but Sloan's AI evidence is a single account of one MCP integration with a CRM, not a track record across platforms.
When it would change
Revisit only if the goal shifts from reach to practitioner credibility, the deliverable stays written, and actual demographic or professional-composition data is available.
A worked campaign example
Angle
Position the engagement as a deliberate redesign inside the migration window, using the client's own processes as audit material. A migration will not fix broken processes by itself, but it creates a rare chance to redesign them on purpose. Make the first session a decision about what information should live in the CRM and how people should use it.
Buyer situation
A B2B SaaS company has just completed a HubSpot migration. The data moved, but the team has rebuilt its old workarounds: deal context sits in inboxes and side spreadsheets, several fields are updated by hand, and no one has decided what actually belongs in the CRM.
Phases
Name
1. Process interrogation
Output
A process map of the current lead and deal flow, with a list of steps that exist only because that is how they have always been done.
What
One working session using Anne Sloan's question set: what information do we actually need; what should trigger the next step; what can happen automatically; where might something fall through the cracks; what are we asking people to do manually that we do not need to?
Name
2. Data and dependency check
Output
A sequencing note showing what can be cleaned now, what must wait and which changes would ripple into automation.
What
Before further filtering or remapping, validate the imported dataset as comprehensively as possible and map dependencies between records, fields and workflows. A stated migration lesson: cleaning and filtering too early had downstream effects that were not visible at the time.
Name
3. What lives where
Output
A short placement rule set and a list of workarounds to retire, aimed at clearer reporting, less manual tracking and fewer side spreadsheets.
What
Decide which client communication, preferences and context belong in the CRM, then remove the workarounds that keep the rest outside it.
Name
4. Automation shortlist
Output
A prioritized automation list with the trigger, fields affected and the failure mode each one removes.
What
Identify repetitive manual updates and rank candidates by error reduction and consistency, not minutes saved. A single update that triggers multiple field changes compounds in value each time it runs.
Name
5. Optional AI integration review
Output
A short readiness note naming the data the assistant would need and where human review should remain.
What
If the team wants to connect an AI assistant to CRM data, assess readiness against the reported MCP use case: preparation before meetings, more complete follow-up and faster data retrieval instead of report-building.
Title
Worked campaign angle: a post-migration HubSpot operations reset
What not to promise
No packaged sponsorship deliverable or rate card exists, so commercial terms would be agreed directly before the engagement. Audience size is small and its composition is unmeasured; plan any public content alongside the work for practitioners and at test scale, not as paid reach.
Why this angle
The posts show a live HubSpot migration, a lead and deal process built from scratch, automation to replace manual field updates and a stated preference for process thinking over software configuration. Measure success by a usable process and reduced manual workload, not reach or impressions.
Choose Justin Emond instead of Anne Sloan when the migration itself is the decision point and the platform is a commerce storefront rather than a CRM.
Read more
His work is about what a replatform forces you to settle: which products or SKUs actually earn their place, which merchandising logic customers depend on, and which assumed integrations stopped mattering years ago. For a company whose HubSpot question is really a wider “what do we keep, what do we retire, what do we rethink while the window is open” question, he is the comparator who argues that migration is a strategic reset rather than a build task—the closest match to how they frame a CRM migration as a process and adoption project rather than a technical one.
Sloan's posts describe commerce replatforms, with named examples of brands moved to Shopify and reported outcomes such as a rise in average order size.
They do not cover HubSpot, lead and deal stages, or CRM administration.
For lead/deal process optimization and post-migration refinement inside HubSpot, they bring strategic framing rather than platform-level how-to; ask for HubSpot-specific process design experience.
Choose Grace Lee Ostiguy when the operational problem behind the CRM question is financial record quality rather than sales pipeline design.
Read more
Her posts are written for small service businesses dealing with surprise compliance notices, tax balances, and unreconciled books, and make the case that manual DIY tracking creates gaps that surface later as a disruption. If a company's post-migration pain is that revenue, invoice, or expense data does not reconcile—and the priority is audit-ready records, cleaner reporting, and a footing for tax planning—her subject matter is closer to the actual work than broader process advice.
The posts focus on bookkeeping and back-office compliance for small businesses, with a clear service offer and a booked call as the next step. For HubSpot pipeline stages, field design, automation triggers, and adoption—the core of lead and deal process optimization—ask for relevant CRM experience.
Choose Eric Ciampoli when the operation is a manufacturing plant and the risk is that documented procedures have fallen behind how work is actually done.
Read more
His posts describe equipment, processes, and teams changing while documentation lags, and present plant data, documentation, and knowledge being brought together so teams get better visibility and more consistent decisions.
A manufacturer asking how to keep operational knowledge current after a system change is a better match for that problem than for a HubSpot lead and deal process optimization engagement.
His framing of the gap between intended and actual process is the same failure mode they describe when a CRM holds record-keeping while the real context lives elsewhere.
The posts are industry-facing and promotional: a Manufacturing Day booth recap and a product-oriented post about a plant operations intelligence platform.
They do not cover HubSpot, CRM migration, lead management, or software adoption.
The only client outcome detail is the stated goal of better visibility and consistency; ask for evidence of results from software CRM engagements.
Anne Sloan's seven public LinkedIn posts cover a HubSpot CRM migration and the work that followed launch, a lead-and-deal process built in HubSpot from scratch, small automations, an MCP integration connecting an AI tool to a CRM, a UX research book club discussion, and a UX research course completion.
Every post is short-form written LinkedIn text.
The posts do not include publication dates, so the ideas are grouped by argument rather than strictly by date.
The account showed 1,092 LinkedIn followers as of 8 October 2026.
Anne's posts name no employer, client, or owned business; publish no sponsorship or partnership offer, media kit, or inquiry route; and include no long-form, video, or audio work.
They also include no publication dates.
The posts do not establish whether a signature book, show, business, or earlier career work exists, so this profile makes no claim about work outside them.