// Guides

Guides for revenue teams

These are the questions we get asked in sales calls, usually before anyone has said the word CRM: why deals go quiet, which commits are really at risk, why reps skip the update, how to keep a pipeline review to half an hour. Each guide gives the answer in its first paragraph, then the reasoning and a worked example you can check against your own numbers. Tools come last. We spent around a decade at HubSpot building the systems these questions are about, so some of this is what we'd do differently now.

Pipeline and forecasting

• Why do deals go quiet, and how do you catch it before the quarter ends?

  Deals go quiet because the buyer's priority changed and nobody on your side noticed in time. Measure days since the last inbound reply on every open deal, compare it against stage age, and review the outliers weekly.

• Which deals are at risk this quarter, and how do you know before the forecast call?

  A deal is at risk when the buyer's behavior stopped matching its stage. Check activity, relationship, and timing signals on every committed deal; a commit failing two of the three is not a commit.

• How do you run a weekly pipeline review in 30 minutes?

  Prepare the changes since last week before the meeting, discuss only the deals that moved or stalled, and let every deal discussed leave with a next step and a date. The meeting is for decisions; the reading happens before it.

• Why do follow-ups slip after sales calls, and how do you stop it?

  Follow-ups slip after sales calls because the work gets deferred to a moment that never arrives: the notes sit in a meeting recorder, no next-step date is set, the draft never gets started, and the rep is already in the next call.

Adoption and data entry

• Why don't sales reps update the CRM, and what actually fixes it?

  Reps skip the update because it gives them nothing back. Process fixes raise compliance a little; the fix that lasts is capturing the activity automatically and asking the rep only for judgment.

• How do you stop logging CRM activity by hand?

  You stop logging activity by hand when the CRM reads the mailbox, the calendar, and a recorder on every call, and writes emails, meetings, and calls to the right record itself. Keep three fields for humans and review the exceptions weekly.

Getting started and switching

• When should a startup get a CRM?

  Get a CRM the first time a second person needs to know what happened with a customer, or the first time you forget a follow-up you promised. Not at incorporation, and not at a headcount.

• What actually transfers when you leave HubSpot?

  Contacts, companies, deals, tickets, tasks, and calls export from HubSpot as CSV with their properties and associated record IDs, and they import cleanly. Activity history takes work, and workflows, sequences, and templates do not leave at all.

• What does a CRM security review ask for, and how do you get through it in a week?

  A CRM security review asks for eight things: a SOC 2 report under NDA, the OAuth scopes the email and calendar connection requests, a subprocessor list, where data is stored, retention and deletion terms, SSO and SAML support, the permissions model, and what the AI does with customer data.

How these guides are written

Every guide starts with the answer, so you can stop after one paragraph if that's all you needed. The rest is the reasoning: what causes the problem, the signals to watch, a method you can run this week, and a worked example. The numbers in the examples are illustrations, and we say so; your pipeline will produce different ones. Tools come last, as a short list of things to ask any vendor. Where a guide names Ahoy it's because the question is one we built the product around, and we say that once rather than on every page.

More are on the way: migration and renewals, security reviews, follow-up, and what a CRM needs when two companies merge. If there's a question you want answered, write to us and we'll probably write it.

Keep reading: What is an AI-native CRM? · Leaving HubSpot? · Free sales tools · Compare the field