Cross-department workflows: how to automate processes that span 3+ teams

The invisible problem: processes that "fall between departments"

Automating individual processes is relatively straightforward. A form that sends data to your CRM. An invoice that generates automatically on order confirmation. But what about processes that cross 3-4 departments, each with their own systems, rules, and deadlines?

Consider a typical B2B client onboarding process:

1. Sales closes the deal in the CRM

2. Legal reviews and countersigns the contract in DocuSign

3. Finance creates the client account in the ERP and issues the advance invoice

4. Operations assigns a project manager and sets up the project in the PM tool

5. Support creates the client's platform account and sends credentials

In theory, this takes 2 days. In practice? 7-12 days. Why? Because each step depends on the previous one, no one has visibility on the overall status, and the "baton pass" happens through emails, Teams messages, and "go tap Andrei from ops on the shoulder."

The hidden cost: A 2024 McKinsey study found that 20-30% of employee time is lost on cross-departmental coordination — not productive work, but questions like "has step X been done?", "who needs to approve this?", "where's the document?"

What the problem looks like in real numbers

Take a distribution company with 50 employees:

• Order processing (sales → logistics → invoicing): 45 minutes manual, 20 of which are "handoff" time — transferring information between departments
• New supplier onboarding (procurement → legal → finance → IT): 5-day average, 3 of which are waiting for inter-team transfers
• Monthly reporting (operations → finance → management): 2 days compiling data from 4 different systems

If you process 30 orders daily, those 20 minutes of handoff per order mean 10 hours lost every day. At an average cost of 25 EUR/hour, that's 5,500 EUR/month spent copying data and waiting for confirmations.

Step 1: Map your cross-department processes

Before automating, you need to see what you have. Not in someone's head, but on paper (or screen).

Practical exercise (takes 2-3 hours):

1. Gather one person from each involved department

2. Choose a specific process (e.g., from order received to delivery completed)

3. Each person writes on sticky notes what they receive, what they do, and who they pass it to

4. Stick them on a wall (or a Miro board), connected with arrows

5. Mark in red: where time is lost, where errors occur, where information gets duplicated

What you'll discover (almost guaranteed):

• The same data gets entered manually into 2-3 different systems
• There are "dead zones" — moments when no one is monitoring the process
• Approvals get stuck because the approver doesn't know they have something pending
• Information gets lost in transit (email wasn't sent, attachment was missing)

At NEXVA SYSTEM, when we run this exercise with clients, we find an average of 3-5 loss points per process — places where automation can completely eliminate waiting time.

Step 2: Choose high-impact intervention points

Don't automate everything at once. Look for three types of "junctions" with the highest impact:

Automated handoffs

When department A finishes, department B automatically receives the task with all necessary data. Not via email, but directly in their system.

Example: Signed contract in DocuSign → automatically creates an invoicing task in the ERP with pre-filled client data + Slack notification to the finance team. Time saved: 1-2 days of waiting per contract.

Approvals with automatic escalation

The approval request reaches the right person directly, with full context, and if not processed within X hours, escalates automatically.

Example: Purchase request over 2,000 EUR → auto-approved by team lead if under 5,000 EUR, escalated to CFO if above. Not approved within 24 hours → automatic reminder. Not approved within 48 hours → notification to hierarchical manager. Average approval time reduction: from 4 days to 8 hours.

Centralized status tracking

A dashboard or notification system showing where each process stands, without calling anyone.

Example: Has the client signed the contract? Process is at step 3 of 5. Has the ERP been updated? Yes, 2 hours ago. Who's responsible for the next step? Maria from operations, deadline tomorrow at 2 PM.

Step 3: Implement incrementally, not Big Bang

The biggest mistake I see: "Let's automate the entire flow from scratch." The project takes 6 months, costs a fortune, and by the time it's done, the process has already changed.

The approach that works:

1. Month 1: Automate the handoffs (connecting existing systems via API). Typical cost: 2,000-4,000 EUR. Immediate impact.

2. Month 2: Add automated approvals and notifications. Cost: 1,500-3,000 EUR. Reduces bottlenecks.

3. Month 3: Build the status dashboard. Cost: 2,000-5,000 EUR. Provides complete visibility.

4. Month 4+: Optimize based on real data — see where things still get stuck, where frequent exceptions occur.

Typical total cost: 7,000-15,000 EUR for a fully automated cross-department process. ROI typically appears by month 2-3.

The tech stack: what works in practice

For companies with 20-200 employees, the combination that covers 80% of needs:

• Workflow orchestration: n8n (self-hosted, free) or Temporal.io (for complex processes with state management)
• Notifications: Slack/Teams API + automated email
• Approvals: Simple custom forms or integration with existing systems
• Status dashboard: Metabase or Retool connected to a central database
• Connectors: Direct APIs to ERP, CRM (HubSpot, Salesforce), DocuSign, invoicing platforms

You don't need an enterprise BPM platform (Camunda, Bizagi) unless you have 500+ employees and regulated processes. For most mid-sized companies, a combination of n8n + Metabase + custom API connectors is sufficient and costs under 100 EUR/month in infrastructure.

Where to start

1. Pick one cross-department process that consumes the most time

2. Map it with the exercise above (2-3 hour investment)

3. Identify the top 3 loss points from the resulting map

4. Automate the first handoff — the simplest one with visible impact

5. Measure: time before vs. after, errors before vs. after

If you have processes that "fall between departments" and want a concrete evaluation of what to automate first, book a free consultation. We'll analyze the flow together, identify bottlenecks, and estimate automation cost and impact — without proposing oversized solutions.