Ghost Work: The 40 Minutes Per Call Nobody Bills For

Your rep just finished a great call. The prospect is engaged. Budget is confirmed. Next steps are clear.

What happens next?

She opens Salesforce. Finds the record. Updates the deal stage. Adds notes from memory (not from the actual conversation, because the transcript hasn't loaded yet!). Switches to email. Drafts a follow-up. Tries to remember the exact objection the prospect raised about implementation timelines. Tabs back to the CRM. Realizes she forgot to log the call activity. Opens Slack. Messages the SE about a technical question that came up. Creates a task in Asana for the proposal. Checks the calendar. Sends a meeting invite for the next call.

Forty minutes gone. Zero revenue generated.

This happens after every single call. And nobody keeps tabs on it.

At Zig, we call this “ghost work”

Not because it's unimportant. But because it has no owner, no name on your org chart, no line item in your budget, and no tool in your stack that was designed to handle it end to end.

Ghost work is the 40 minutes after every sales call that nobody tracks, nobody bills for, and no tool was built to handle. It is the connective tissue between what your tools produce (a transcript, a lead list, a drafted email) and what actually moves a deal forward (a CRM that reflects reality, a follow-up that references what was actually said, a next step that's already scheduled).

Every tool in your stack does its one job and clocks out. The work that stitches those outputs into execution? That's on your rep.

Let's do the math.

A mid-market rep making roughly 6 productive calls per day spends an average of 40 minutes on post-call admin per interaction. That's 4 hours per day. Per rep. On work that generates exactly zero direct revenue.

Scale it:

• 10 reps × 10 hours/week × $38/hr loaded cost × 52 weeks = $197,600/year
• That's $197,600 your team spends annually on work that isn't selling, isn't measured, and isn't owned by any system in your stack

For context: that's more than a senior SDR. It's more than most teams spend on Gong, Salesloft, and Apollo combined. And unlike those line items, nobody has ever questioned it, because it's never appeared on a single invoice.

According to Salesforce's 2026 State of Sales report, reps spend only 28–30% of their week actually selling. That number hasn't improved in five years despite $50B+ in cumulative sales tech investment. The remaining 70% is a mix of admin, internal communication, and tool navigation. The vast majority of which falls into the ghost work category.

The post-call workflow nobody designed

Here's what a real post-call workflow looks like, timestamped. This is from an anonymized mid-market sales team running a typical stack (Salesforce + Gong + Salesloft + Apollo + Slack):

‍Eleven steps. Six tools. One human doing all of it manually.

Notice what's missing from this here? A column that says "automated" or "handled by the stack."

Every tool in this workflow does exactly one thing: Gong records and transcribes. Salesforce stores data. Salesloft sequences outbound. Apollo finds contacts. None of them were built to do what happens between their outputs. The assumption baked into every one of these products is that the gap between "deliverable generated" and "deal moved forward" is the rep's job.

It is. And that's the problem.

Why your stack was never going to fix this

The fragmented sales stack wasn't designed with execution in mind. It was designed around features.

Every tool you've purchased solves a discrete problem: call recording, lead enrichment, email sequencing, CRM storage. Each one delivers a single output and stops. The industry's implicit agreement is that the gap between tools is someone else's problem. Specifically, it's your rep's problem.

This is why adding more tools doesn't reduce admin time. It increases it. Every new tool adds another tab, another login, another place where data needs to be entered, reconciled, or transferred manually.

Salesforce's own data confirms this: sellers average 8 tools to close deals, and 42% of reps feel overwhelmed by their tools. Overwhelmed sellers are 45% less likely to hit quota. The correlation between tool count and rep productivity isn't positive. It's inverse.

The industry's response to this has been to build integrations, i.e., connectors that pass data between tools. But an integration is not execution. An integration just moves a data field from System A to System B. It doesn't draft the follow-up email. It doesn't update the deal stage based on what was said in the call. It doesn't create the next-step task with the right context. It definitely doesn't do all of those things without the rep touching anything.

Integration is plumbing. Execution is the water.

The compounding cost nobody calculates

Ghost work doesn't just waste time. It degrades data quality, which degrades forecasting, which degrades every decision your leadership team makes.

Here's the compounding effect:

Layer 1: Rep time. 4 hours/day of admin means your reps spend more time operating software than talking to prospects. Your best reps — the ones generating 81% of revenue (per Ebsta's analysis of 4.2M opportunities) — are spending nearly half their day on work that has nothing to do with the skill you hired them for.

Layer 2: Data decay. When reps update CRM manually from memory, the data degrades immediately. Notes are incomplete. Stages are updated in batches on Friday afternoon. Close dates are optimistic guesses. Your "source of truth" is actually a historical document — a snapshot of what someone remembered to log, not what's actually happening in the deal.

Layer 3: Forecast fiction. Your Monday pipeline review is built on Friday's manual entries. The forecast your CRO presents to the board is, at its foundation, a collection of human memory artifacts filtered through a UI that was last touched 72 hours ago.

Layer 4: Rep attrition. 42% of top sales reps cite administrative burden as a primary reason for leaving.

Your best people aren't underperforming. They're underwater.

And every day they spend on ghost work is a day they're calculating whether the job is worth it.

What the market got wrong

The entire $50B sales technology industry was built on a single assumption: if you help reps do admin faster, they'll sell more.

That assumption is wrong.

Faster admin is still admin. A better CRM UI is still a CRM UI that requires manual entry. A transcript that loads in 30 seconds instead of 5 minutes still requires the rep to read it, extract the relevant points, and manually incorporate them into five different systems.

The question the industry should have asked isn't "how do we make ghost work faster?" It's "how do we make ghost work not exist?"

That's a fundamentally different design problem. It's not a feature improvement. It's an architectural decision. And it's the difference between a tool that assists a rep and a system that executes the work on their behalf.

Assistance means a human still does the work, just slightly faster. Execution means the human doesn't do it at all.

No tool in the current stack was designed for execution. They were all designed for assistance. And we've spent a decade confusing the two.

The framework: Audit your own ghost work

Before you evaluate any solution, run this audit on your own team. It takes one week and will change how you think about your stack permanently.

Step 1: Shadow two reps for a full day. Not your worst reps. Your best ones. Track every post-call action, every tool switch, every manual entry. Timestamp everything. You will be shocked at what you find.

Step 2: Calculate the real cost. Take the total admin hours per rep per week. Multiply by loaded cost. Multiply by team size. Multiply by 52. That number belongs on your next QBR slide.

Step 3: Ask four questions about your stack.

1. What did Gong actually change about your win rate? (Not call volume. Win rate.)
2. What percentage of your CRM data is accurate right now — not when it was entered?
3. How many hours per rep does your stack save vs. create?
4. What breaks if you cancel any single tool tomorrow?

Most VPs have never run this calculation. Not because they don't care, but because no vendor had a reason to surface it. The business model of the fragmented stack depends on nobody asking these questions.

Step 4: Measure the gap. For every tool in your stack, identify where its output stops and the rep's manual work begins. That gap — between deliverable and execution — is your ghost work surface area. The wider the gap, the more invisible cost you're carrying.

The end of ghost work

Ghost work will not be solved by a better feature, a smarter integration, or a new point solution added to the stack. It will be solved by a system that was designed, from the architecture level, to own the entire post-call workflow. Not just one piece of it.

That means: a system that listens to the call, updates the CRM, drafts the context-aware follow-up, creates the next-step task, logs the outcome, and moves the deal forward.

Without the rep touching anything.

Without 40 minutes of invisible labor.

Without the compounding data decay that poisons your forecast every week.

Not faster ghost work. NO ghost work.

The industry spent a decade building tools around the call. Nobody built the system for what happens after.

That's the gap. And it's where your revenue lives.

‍