Field notes on HubSpot operations: what we fix, what we automate, and what we would never build again.
HubSpot stale deals come from a missing rule, not bad data. Agree on how many days without logged activity makes a deal stale, save a deals view filtered on Last activity date and an empty Next activity date, and have one owner revive or close each deal every week.
HubSpot deal risk rarely shows in the deal stage. Check open deals for a silent buyer, a passed or moving close date, a missing decision maker and no next step, then use time-in-stage reports to find where deals stall. Give one person the weekly risk review before you automate it.
HubSpot deal stages named after rep activity make forecasts, time in stage reports and AI suggestions unreliable. Heads of sales should write one buyer-based exit criterion per stage, then rename stages, require the evidence as stage properties and decide on pipeline rules. Test the definitions on two reps before trusting the reports.
HubSpot AI agents read your CRM as it is: fields, logged activity and the context you write down. Before switching one on, decide who owns it, review the data quality tools, merge duplicates, make key fields required, log emails and calls, and add your ICP. A cleaner portal pays off with or without agents.
One HubSpot contact can hold many deals, so a repeat sale never needs a second contact. Reps duplicate contacts because the process for returning buyers is unwritten. Sales and RevOps leaders should write a repeat-sale rule, settle contact ownership, check where activity history lands, then merge the existing duplicates.
A HubSpot MQL to SQL handoff breaks when nobody has written down when marketing stops and sales starts. Use the Date entered, owner and last contacted properties to see where marketing qualified leads wait, then agree one written rule, a response time and a single owner before building any routing workflow.
HubSpot credits are spent by AI agents, most email sends and workflow actions such as task creation and lead rotation. They reset monthly without rollover, and features pause when they run out unless you buy packs. Budget owners should review usage in Account & Billing, switch off unused workflows and name one owner before adding capacity.
Start a HubSpot CRM cleanup with definitions, not duplicates. Write what each lifecycle stage, deal stage and owner rule means, make the few fields your reports depend on required, and only then merge. Merges in HubSpot cannot be undone, and merged records keep the furthest lifecycle stage, so the rules must come first.
Hire a HubSpot administrator only after counting the admin hours your portal generates each week. If the work fits in a few hours or comes in bursts, a part-time or outsourced admin fits better; near a full-time load, hire. Test candidates on permissions, data model, workflows and reporting, not certificates.
A HubSpot implementation plan should list decisions, not settings: what each deal stage means, where marketing hands off to sales, what data migrates, who sees what, which questions reports answer, and who owns the portal. Assign an owner to each before setup starts, because these choices are costly to change after go-live.
