Ghost Workflows: The Hidden Manual Tasks Costing UK Sales Teams Thousands of Hours

Somewhere in your company there's a spreadsheet that shouldn't exist. It was created because two systems don't talk to each other. Someone updates it every Tuesday. Nobody remembers who started it or why it became essential. But if it stopped being updated, things would break.

That's a Ghost Workflow.

Ghost Workflows are the undocumented manual tasks that drain capacity without anyone measuring them. They don't appear in process maps. They're not in anyone's job description. They survive because nobody owns them, nobody tracks them, and they sit in the cracks between systems where institutional knowledge fills the gap.

Every field sales company has them. Most have dozens. And they collectively consume thousands of hours per year that don't show up in any efficiency report.

How to spot a Ghost Workflow

Ghost Workflows share a set of characteristics that make them identifiable once you know what to look for.

They bridge a gap between systems. The most common type exists because System A and System B don't share data. Someone manually extracts data from A, reformats it, and enters it into B. Every week. Sometimes daily. The task takes 20 minutes to 2 hours and produces no value except keeping two systems in sync that should be connected.

They depend on one person's knowledge. Karen's spreadsheet. Dave's Monday report. The thing that "Sarah just knows how to do." When that person takes holiday, the task either doesn't happen (and something downstream breaks) or someone else attempts it (badly, because the process exists only in the originator's head).

They're invisible to management. Nobody reports on Ghost Workflows because they're not official processes. They don't have KPIs. They don't appear in time tracking. When someone asks the operations team what they spend their time on, these tasks get absorbed into vague categories like "admin" or "coordination" or "keeping things running."

They were supposed to be temporary. Almost every Ghost Workflow started as a quick fix. "I'll just do this manually until IT connects the systems." "Let me build a quick spreadsheet to track this." "I'll send a weekly email summarising the data." That was three years ago. The temporary fix became permanent. The IT project never happened.

They resist elimination. When someone suggests automating or removing a Ghost Workflow, the response is usually "it's more complicated than it looks" or "we tried that but it didn't work" or "it only takes 20 minutes." Each individual task feels too small to warrant a project. But collectively, they represent a significant operational drain.

The twelve friction signals

At Ell Advisory, we use twelve operational friction signals to identify Ghost Workflows during assessments. You can use them to audit your own operation.

1. System bridge spreadsheets. Any spreadsheet whose primary purpose is to move data between two systems. Count them. You'll find more than you expect.

2. Manual report compilation. Reports that are assembled by hand from multiple data sources rather than generated automatically. The Monday pipeline report that someone builds by pulling data from the CRM, the ERP, and the email inbox.

3. Duplicate data entry. The same information being entered into two or more systems manually. Customer address changes. Pricing updates. Product specifications.

4. Email-as-workflow. Processes that depend on email chains for routing and approval. "Forward this to Operations." "CC the warehouse." "Reply all to confirm." Each email is an undocumented process step with no audit trail and no guaranteed completion.

5. Meeting-as-coordination. Regular meetings whose primary purpose is to synchronise information that should flow automatically between systems. The daily stand-up that exists because production and sales can't see each other's data.

6. Knowledge hoarding. Critical process knowledge that exists only in one person's head. If you can point to a person and say "they're the only one who knows how to do that," you've found a Ghost Workflow.

7. Workaround documentation. Written instructions that describe how to work around a system's limitations. "When the ERP doesn't accept the spec code, use this alternative format." These workarounds become permanent adaptations that nobody ever resolves.

8. Reconciliation tasks. Regular tasks that exist to check whether two data sources agree. Stock reconciliation between the warehouse system and the sales system. Order reconciliation between the CRM and the ERP.

9. Follow-up reminders. Manual processes for tracking whether something happened. "Check on Tuesday whether the order was shipped." "Remind Dave to send the quote." These exist because the systems don't provide automated alerts.

10. Format conversion. Manually converting data from one format to another. CSV to Excel. PDF to structured data. Email to CRM entry. Phone notes to system records.

11. Exception handling. Manual processes that exist for handling exceptions that should be built into the system. "If the order is over £10,000, email the finance director for approval." "If the customer is on credit hold, call accounts before processing."

12. Cross-department translation. Someone who acts as an interpreter between sales language and operations language. The person who translates "the customer wants it faster" into a specific production priority change.

Counting the cost of Ghost Workflows

Let me work through a practical example.

A mid-market manufacturer with 120 employees. 12 field sales reps. 8 operations staff. Standard CRM, ERP, and a collection of spreadsheets.

During an assessment, we identified 34 Ghost Workflows. Here's a sample of the largest ones.

Weekly pipeline reconciliation: Operations manager spends 3 hours every Monday pulling data from the CRM, the ERP, and two spreadsheets to build the pipeline report for the sales meeting. 3 hours x 50 weeks = 150 hours per year.

Quote-to-order data transfer: When a quote is accepted, a sales administrator manually re-enters the line items from the quoting tool into the ERP for order processing. Average 25 minutes per order, 15 orders per week. 325 hours per year.

Customer price list maintenance: One person updates customer-specific pricing in both the CRM and the ERP. The CRM doesn't sync to the ERP for pricing. 5 hours per week. 250 hours per year.

Delivery schedule communication: Operations emails the sales team a daily delivery schedule. Reps check the email to see if any of their customers have deliveries today. 30 minutes per day for the operations person plus reading time for 12 reps. Approximately 300 hours per year total.

Complaints cross-referencing: When a customer complains, the customer service person checks three systems (CRM, ERP, and a complaints spreadsheet) to build the history. Average 45 minutes per complaint, 8 complaints per week. 300 hours per year.

Those five Ghost Workflows alone consume approximately 1,325 hours per year. At a loaded cost of £30 per hour (blending admin and management time), that's roughly £40,000 in annual cost for five tasks.

The full audit found 34 Ghost Workflows consuming approximately 4,200 hours per year. Cost: approximately £126,000.

According to McKinsey's automation research, about 30% of tasks in 60% of occupations are technically automatable today — and ghost workflows sit squarely in that band. Forrester analysis of operations teams shows that information transfer between disconnected systems accounts for the largest share of recoverable capacity. The Asana Anatomy of Work Index found knowledge workers spend 58% of their time on "work about work" rather than the work itself.

This pattern is consistent with what we've seen across clients — one manufacturer reclaimed 351,000 hours per year by addressing these inefficiencies at scale.

This is a company that would tell you their operations are "pretty efficient." And in many ways they are. The Ghost Workflows aren't visible because they've been normalised. They're just "how things work."

The Ghost Workflow audit

Here's a practical process for identifying Ghost Workflows in your company. It takes about half a day and it's worth every minute.

Step 1: Interview each department. Spend 30 minutes with each team lead. Don't ask "what are your processes?" (they'll describe the official ones). Ask: "What do you do every week that isn't in any system?" and "What would break if you took two weeks off?" and "Where do you spend time moving information from one place to another?"

Step 2: Follow the data. Pick three recent deals or orders. Trace the information from initial customer contact through to delivery. At each step, ask: is this information transfer captured in a system, or does it depend on a human manually moving it?

Step 3: Count the spreadsheets. Literally count every spreadsheet that is actively maintained in the business. For each one, ask: what two systems does this bridge? Why does it exist? How long does it take to maintain? What breaks if it stops?

Step 4: Map the dependencies. For each Ghost Workflow you identify, document: who does it, how long it takes, what it bridges, and what happens if it doesn't get done. This gives you the priority order for elimination.

Step 5: Calculate the cost. Time per week x weeks per year x loaded hourly cost. The total is almost always higher than people expect, because each individual task feels trivial. "It only takes 20 minutes" becomes 17 hours per year per task. Multiply by 30 tasks and you're at 500 hours before you've counted the big ones.

Eliminating Ghost Workflows

The elimination approach depends on the type.

System bridge spreadsheets are usually the easiest to fix. If the spreadsheet exists because System A and System B don't share data, the fix is connecting them. Modern integration platforms (Power Automate, Zapier, Make, or custom API work) can often connect systems for a few hundred to a few thousand pounds. The spreadsheet that costs £5,000 per year in maintenance time can often be replaced by a £2,000 one-time integration.

Knowledge-dependent tasks are harder because you first need to capture the knowledge before you can systematise it. Document what Karen knows. Build it into the system. Test it. Then Karen can stop doing the manual task and spend her time on something that actually uses her expertise.

Email-as-workflow tasks should be replaced with proper workflow tools. Whether that's a project management platform, an approval workflow built into your CRM or ERP, or a simple task automation tool depends on the complexity. The principle is the same: replace an untracked, unaudited email chain with a visible, measurable process.

Many Ghost Workflows exist specifically at the sales-to-ops handoff, where information dies between field and factory.

Meeting-as-coordination tasks point to a data visibility problem. If sales and operations could see each other's data in real time, the coordination meeting becomes unnecessary (or becomes a shorter, more productive discussion about exceptions rather than routine updates).

Why eliminating Ghost Workflows matters now

Ghost Workflows have existed as long as businesses have had multiple systems. So why address them now?

Because AI makes elimination dramatically easier and cheaper than it used to be.

Five years ago, connecting two systems required custom development. Today, AI-powered integration tools can map data between systems, handle format conversion, and manage exceptions automatically. The spreadsheet that bridges your CRM and ERP can be replaced by an automated pipeline that runs in the background, costs £200 per month, and never takes a holiday.

Voice-to-CRM tools eliminate the "rep's notebook to CRM" Ghost Workflow entirely. AI-powered document processing eliminates the "PDF to structured data" Ghost Workflow. Automated anomaly detection eliminates the "check the numbers every Monday" Ghost Workflow. The same logic applies to the cost of slow quoting — most quoting bottlenecks are ghost workflows in disguise. Smartsheet's automation research found that 40% of workers spend at least a quarter of their week on manual repetitive tasks. Make UK's productivity report shows UK manufacturers leave significant capacity on the table for exactly this reason.

The companies that systematically identify and eliminate their Ghost Workflows will recover thousands of hours of productive capacity. Hours that currently disappear into the invisible machinery of keeping systems in sync.

The companies that don't will keep paying for them. They'll keep wondering why their operations feel heavier than their headcount justifies. And they'll keep being outrun by competitors who spend those hours selling instead of spreadsheet-wrestling.

Start with the audit

You can't fix what you can't see. And Ghost Workflows are, by definition, invisible until someone looks for them.

The audit process described above takes half a day. The cost savings typically start within weeks. And the exercise itself is valuable beyond the numbers: it gives you a clear picture of where your operational capacity actually goes, and it often reveals improvement opportunities that go beyond individual task automation.

Every company I've audited has found at least 2,000 hours of Ghost Workflows. Most find significantly more. The question isn't whether they exist. It's how many, and what you'll do with the hours when you recover them.

Want us to find your Ghost Workflows? Our Hidden Waste Audit includes a systematic identification of Ghost Workflows across your sales and operations teams. Five minutes to start. No pitch. Just a clear picture of where the hours go.

Sources: Ell Advisory client assessments, Salesforce State of Sales 2024, SPOTIO Field Sales Report 2026, McKinsey automation research, Forrester operations research, Asana Anatomy of Work Index, Smartsheet automation report, Make UK productivity research, Gartner business operations research, IDC manufacturing analytics.

Frequently asked questions

What exactly is a Ghost Workflow? A Ghost Workflow is an undocumented manual task that exists to bridge a gap between systems, departments, or processes. It isn't in any process map, isn't tracked, and usually depends on one person's tacit knowledge. They survive because each individual task feels too small to fix.

How many Ghost Workflows does a typical company have? In our assessments of mid-market manufacturers and field sales companies, we typically find 30–40 Ghost Workflows per organisation, consuming 3,000–5,000 hours per year. Smaller companies have fewer in absolute terms but proportionally more — they're often the worst hit.

How do I find Ghost Workflows without disrupting the team? Start with a half-day audit: 30-minute interviews with each team lead, asking "what do you do every week that isn't in any system?" and "what would break if you took two weeks off?" Then count active spreadsheets. The two together surface 80% of the workload.

What's the difference between a Ghost Workflow and a normal manual task? Normal manual tasks appear in job descriptions, process maps, and time tracking. Ghost Workflows are invisible — they happen because systems don't talk, because someone built a workaround three years ago, or because institutional knowledge fills a gap. If management doesn't know it's happening, it's a ghost.

Should I automate Ghost Workflows or eliminate them? Eliminate first, automate second. Many ghost workflows exist only because two systems can't share data — connecting them removes the task entirely. Only automate the ones that genuinely need to happen but don't need a human. Automating waste just makes waste run faster.

How quickly can we recover hours after an audit? System-bridge integrations typically deliver hours back within 4–8 weeks. Voice capture and signal-based CRM updates take 6–12 weeks for a pilot. The full elimination programme for 30+ ghost workflows usually runs 6–12 months but produces ROI from week one.

Who should own the Ghost Workflow elimination programme? A senior operations leader with cross-functional authority — usually the COO or Head of Operations. The work crosses sales, ops, finance, and IT, so it can't sit inside any single function. See our guide on choosing an AI consultant if you need outside help.

Related reading

• The hidden cost of manual processes in UK manufacturing
• The sales-to-ops handoff is where margin dies
• The cost of slow quoting in manufacturing
• How one manufacturer reclaimed 351,000 hours
• Unlock hidden sales capacity in UK manufacturers
• Why AI projects fail without process redesign
• Sales capacity planning: the metric manufacturers miss

Ready to find yours? Start the Hidden Waste Audit (5 minutes, no pitch) or book a 30-minute call to walk through your top three ghost workflows live.