We spent several months talking to sales teams before we built Zig. Not pitching. Just listening. And we kept hearing the same story, told slightly differently every time.

A VP of Sales put it best: "My reps spend more time feeding HubSpot than feeding the pipeline."

Because here’s the thing: HubSpot, Salesforce, Pipedrive… these are genuinely good products. 

They’ve transformed how companies manage relationships. But somewhere between the original promise of "organize your sales process" and today’s reality, something broke.

These systems became a second job. And nobody’s talking about it honestly enough.

‍

This Is Purely an Architecture Problem.

I’m not talking about clunky interfaces or slow load times. I’m talking about something more fundamental: the moment a system requires constant human orchestration to function, it stops being a tool and starts being a tax.

Let me show you what I mean. Here’s what a rep actually does when they work a deal in most modern CRMs:

Step 1: Find the contact (or create it from scratch)

Step 2: Update the notes with what you discussed

Step 3: Create a follow-up task

Step 4: Draft and send the email

Step 5: Log the activity (usually manually; sometimes it auto-logs,sometimes it doesn’t)

Step 6: Repeat this 20–30 times a day

That’s not selling. That’s administration.

And when administration becomes your team’s primary activity, everything downstream breaks. Your forecast accuracy, your deal velocity, your rep retention. All of it.

The pain isn’t in any single step. It’s in the accumulation. It’s death by a thousand clicks.

The Distinction Nobody’s Making: Systems of Record vs. Systems of Execution

Here’s what I think most CRM teams got fundamentally wrong.

They optimized for data storage, not data motion.

Your CRM is an incredible system of record. It stores everything: contacts, deals, activities, notes. But it’s not a system of execution. It doesn’t move deals forward. It doesn’t know that a deal has been sitting in "demo scheduled" for 8 days without motion. It can’t orchestrate what needs to happen next across email, Slack, calendar, and the actual human doing the selling.

So what happens? Your team fills that gap manually. They check the CRM, they check their email, they check their calendar, they check Slack. They create reminders for themselves. They chase context across four different tools. They repeat this ritual 20+ times a day.

And the worst part? They think this is normal. They think this is just what sales ops looks like. It’s not. It’s a design failure we’ve all accepted as the cost of doing business.

What Changed My Thinking

More configuration only works if your underlying architecture can actually handle execution. And most CRMs can’t. They weren’t built for it. They were built to be databases with nice frontends—which is valuable, but it’s not enough anymore.

The moment we realized this, everything shifted. We stopped asking "How do we make HubSpot better?" and started asking "How do we build a layer that makes any CRM actually executable?"

That question is what led us to Zig.

And it’s the question I think every sales leader should be asking right now.

How the Best Sales Teams Actually Handle Execution

Teams that win at sales execution aren’t doing anything revolutionary. They’re just ruthlessly eliminating the gap between “knowing what to do next” and “actually doing it.”

Here’s what that looks like in practice.

They treat follow-up as a system, not a skill. The best teams don’t rely on individual reps to remember follow-ups. They’ve moved follow-up into an automated layer—something that runs consistently regardless of whether your rep is having a great day or a terrible one. Every lead gets the right touch at the right time, because the system handles it. The rep stays in control of the relationship, but the motion is guaranteed.

They separate the record layer from the execution layer. This was the big unlock. The successful teams keep their CRM—HubSpot, Salesforce, whatever—as the source of truth. But they don’t ask it to do everything. The orchestration happens elsewhere: lead routing, activity logging, next-step creation, inbox coordination. All of that runs on a separate execution layer that feeds clean data back into the CRM. The CRM stays accurate. The reps stay focused. Nobody’s doing double data entry at 6pm on a Friday.

This is exactly why we designed Zig to plug into your existing CRM rather than replace it. Ripping out Salesforce isn’t the answer. Making it actually executable is

They measure motion, not just pipeline. Traditional CRM dashboards show you what’s sitting in the pipeline. The winning teams are measuring what’s moving. How many deals had activity this week? How many follow-ups went out on time versus late? Where exactly did the motion stall? And why?

When your execution layer is automated, you finally have clean enough data to actually answer these questions honestly.

They let the system work while the team sleeps. This is the one that really changed our thinking. The best-performing teams have deals progressing at 2am. Not because their reps are burning out, rather, their AI agents are sending the right follow-up, logging the activity, enriching the contact data, and queuing the next step. The rep wakes up to a clean inbox and a prioritized task list. Not 47 things to sort through before they can start actually selling.

None of this is magic. It’s architecture.

And the teams that are getting it right aren’t the ones with the biggest tech budgets or the most ops headcount. They’re the ones who stopped asking their CRM to be something it was never designed to be, and started building the execution layer it always needed.

The Ripple Effects Nobody Talks About

When your sales motion requires constant manual orchestration, the damage goes way beyond wasted time. I’m seeing three second-order effects that most leaders miss:

Your best reps leave first. Top performers didn’t get into sales to do data entry. They have options. When the admin burden gets heavy enough, they go somewhere lighter. And you’re left with the people who tolerate the friction; not the people who close the deals.

Your forecasts are built on fiction. If reps aren’t logging activities consistently (and they’re not, ‘coz the process is painful), then your pipeline data is incomplete. Which means your forecast is a guess dressed up as analysis.

Your onboarding gets slower. Every new rep has to learn the CRM’s quirks, the team’s workarounds, the unofficial rules about what to log and where. This is just training on navigating bureaucracy. Think about that for a second.

The Shift That’s Coming

I believe we’re at an inflection point. The CRM as we know it: the manually-orchestrated, configuration-heavy, admin-dependent system, is reaching its limits. Not because the products are bad, but because the paradigm is wrong.

Sales teams don’t need a better database. They need systems that actually execute. That follow up when reps forget. That log activities without being asked. That create the next step automatically. That work while your team sleeps.

Don’t replace your CRM. Rather, add an execution layer that turns your system of record into a system of action.

If your team is spending more time orchestrating their tools than actually selling, the answer isn’t better discipline or more training. The answer is a different architecture entirely.

What’s your team spending more time on: selling or administrating?

‍