Your marketing campaigns won’t work if sales don’t use the CRM

Why won’t marketing campaigns work if sales don’t use the CRM?

Because a campaign is only as good as the history behind it. And if sales don’t log anything, there is no history.

When reps skip the CRM, you lose the timeline — the actual sequence of how a stranger became a deal, or a partnership. Who reached out first. What they asked for. What stalled it. What finally moved it. Without that, you’re not personalizing. You’re guessing with a nicer template.

A spot-on campaign needs to know where someone sits in a story. Empty records don’t tell stories.

What can you do in B2B when the deal history is thin?

More than you’d think. B2B is harder here — longer cycles, more people on the buying side, fewer deals to learn from — but it’s not impossible.

Even a partial logged history gives you a view of the likely scenarios, the recurring needs, and the persona types worth approaching. Ten logged deals beat zero. You start to see that the ones that closed all had a champion in finance, or all opened with the same complaint. That’s enough to aim a campaign at.

But it only works if the history exists. Which brings us to where it goes instead.

Where do the touchpoints go when reps live in WhatsApp and Telegram?

Nowhere you can see.

Plenty of reps run their real relationships over WhatsApp, Telegram, and phone calls — from personal devices, on personal accounts. None of it lands in the CRM. And what isn’t logged may as well not exist.

So you can’t count the number of touchpoints it took to close. You can’t work out the cost per interaction, the average cost of a deal, or the true sales-cycle length. Worst of all, you can’t tell a repeatable pattern from a lucky one-off — and repeating what works is the entire point of measuring.

You end up with a pipeline number and no idea how it got there.

How do you get reps to actually use the CRM?

You make it accessible, and you make it worth being in. Nagging doesn’t work. Nobody logs a call to make a manager feel better.

Two things move it. First, a workshop — not a demo, a working session on how this team uses the CRM and what for. What each field means. What to log and what to skip. Reps walk away from systems that don’t match how they actually sell.

Second, automations that take the admin off their plate, so the time goes to the customer instead of data entry. A CRM that fills itself in is one people stop avoiding. Both are the day job in marketing operations.

Custom objects in HubSpot for BDRs, sales, and customer success

The reason reps work around a CRM is usually that it doesn’t fit their work. Everything gets crammed onto the Deal. Custom objects fix that — purpose-built record types for each team.

A few that earn their keep. Sales: a Subscriptions or Licenses object tied to a company, tracking seats, usage, and renewal dates separately from the sales deal. BDRs: a Partners or Channel object, so a distributor sourcing a deal doesn’t get confused with the end customer, and territory attribution stays clean. Customer Success: an Onboarding object auto-created the moment a deal hits Closed-Won, with its own milestones, success criteria, and CSM owner. The handoff happens without anyone chasing it.

One catch. Custom objects are an Enterprise feature on HubSpot — you need at least one Enterprise hub, and an Enterprise portal can hold up to ten of them, a thousand properties each. Which is HubSpot’s way of saying the feature you need is one tier above the one you bought. They can be built in settings or provisioned through the Custom Objects API, which starts to matter once automation is filling them.

Custom fields that reps will actually fill in

If Enterprise isn’t on the table, custom fields are. Properties work on every paid tier — up to a thousand per object on Starter and above — and they’re the accessible lever for most teams.

The trick is fields that surface meaning, not more boxes. Next step as text. Deal risk as a Low/Med/High dropdown, never free text. Compelling event. Budget confirmed as a checkbox. Decision date as a date, so you can watch it drift from the close date.

Field type is the whole game. Dropdowns and checkboxes can trigger automation and survive a report filter. Free text gives you twenty spellings of the same answer and breaks every report. And “last meaningful touch” should be a date your automation sets on real engagement — not HubSpot’s Last Activity Date, which fires on any event at all.

HubSpot workflows vs Make.com and n8n

Two ways to strip the admin out.

Native workflows live inside HubSpot and depend on your tier. The Workflows tool needs Professional or Enterprise — Starter doesn’t have it. Professional caps out around three hundred workflows; Enterprise raises that to around a thousand and adds cross-object automation, which is what lets a workflow read and write those custom objects. Custom-code actions — the ones that call an enrichment API and write the result back — need Data Hub (HubSpot’s operations tier) at Professional or higher.

External automation with Make.com and n8n doesn’t care about your tier. It sits outside HubSpot and pushes data in through the API. Pull a company name off a signup, enrich it, normalize it, write it to the right field — automatically, from whatever source you’ve got. It’s how the deal record fills without the rep touching it. We build both, and choose based on what the portal already pays for. The services lay out how the pieces fit.

None of this makes a rep log a WhatsApp message. But a CRM that fills itself in, matches how people sell, and asks for the one field that matters — that one they’ll use. The invisible pipeline is a choice. Usually the tool’s, not the rep’s.