HubSpot Event Attribution Needs the Event Object First
HubSpot event attribution should use the event object as the source of truth and multi-select fields only for rep visibility.
Published
Updated
11 min read
Blog
Field notes from 100+ RevOps implementations.
HubSpot event attribution should use the event object as the source of truth and multi-select fields only for rep visibility.
Published
Updated
11 min read
RevOps automations need exception paths before more branches, so bad inputs stop visibly instead of corrupting downstream work.
Published
Updated
9 min read
RevOps teams should route AI models by workflow risk, not model preference, so cost, quality, permissions, and review match the job.
Published
Updated
9 min read
CRM adoption fails when the system makes daily work harder. Fix the CRM design before asking reps to sit through more training.
Published
Updated
9 min read
AI sales coaching needs call type labels before summaries, or managers get generic advice scored against the wrong sales motion.
Published
Updated
9 min read
Define the RevOps workflow before adding AI. Otherwise automation speeds up bad handoffs, fuzzy permissions, and broken CRM logic.
Published
Updated
9 min read
A lead should be a time-boxed engagement attempt, not the person. The contact persists; the lead opens, moves through a path, and closes.
Published
Updated
10 min read
A pipeline hygiene dashboard should show managers which deals need cleanup this week, not give executives another stale forecast view.
Published
Updated
8 min read
RevOps teams should automate repetitive, high-context workflows that humans can verify before they automate judgment or customer-state changes.
Published
Updated
8 min read
Use Claude Code for GTM operations when the work is structured, artifact-based, and tied to a real operating question, not vague prompting.
Published
Updated
9 min read