7 Operations Bottlenecks That Keep 10-100 Person B2B Teams Stuck

The 7 operations bottlenecks that keep 10–100 person B2B teams stuck are: (1) manual data entry across disconnected tools, (2) tool sprawl with no integration, (3) unclear ownership where work waits for "someone," (4) single points of failure when one person holds all the knowledge, (5) broken handoffs between teams, (6) no documentation so every process is tribal knowledge, and (7) a firefighting culture that never fixes root causes. Most teams have 3–5 of these, costing €50,000–€150,000 per year. Fixing your top 3 takes 90 days and typically delivers 300–500% ROI.

Your team is working hard, but nothing seems to move faster. Projects are always late. Client onboarding takes weeks instead of days. Your team is drowning in manual work, but you can't pinpoint exactly where the time is going.

If you're running a 10-100 person B2B company, you're probably stuck in the same bottlenecks I see in 90% of operations teams. These bottlenecks are predictable and fixable.

After building operations systems from scratch at my previous business (scaling a growth agency across multiple European countries), I've seen the same 7 bottlenecks kill productivity in almost every company. The bad news: most teams don't know they're stuck in these patterns. The good news: once you identify them, you can fix them systematically.

In this guide, I'll walk you through the 7 most common operations bottlenecks I see in 10-100 person B2B teams. For each one, I'll show you how to identify it, quantify the cost, and fix it. You'll learn how to spot these patterns in your own operations and create a prioritized action plan to eliminate them.

Why These Bottlenecks Are So Common (And Why They're Fixable)

Most 10-100 person B2B companies are stuck in the same 7 bottlenecks. Not because they're doing something wrong but because these bottlenecks are natural byproducts of growth.

When you're small (1-10 people), you don't need processes. Everyone knows what to do. When you're large (500+ people), you have dedicated ops teams and systems. But in the middle (10-100 people), you're stuck: too big to wing it, too small to have dedicated ops resources.

The result? These 7 bottlenecks emerge:

1. Manual data entry across disconnected tools

2. Tool sprawl (too many tools, no integration)

3. Unclear ownership (work sits idle waiting for "someone")

4. Single points of failure (if Sarah is sick, everything stops)

5. Broken handoffs (work gets lost between teams)

6. No documentation (every process is tribal knowledge)

7. Firefighting culture (always reacting, never improving)

These bottlenecks are fixable. Most can be solved in 2-4 weeks with the right approach and fixing one bottleneck often solves multiple problems at once.

The 7 Operations Bottlenecks (And How to Fix Them)

Each bottleneck includes how to identify it, quantify the cost, and fix it.

Bottleneck 1: Manual Data Entry Across Disconnected Tools

Your team manually enters the same data into 3-5 different tools. Client information goes into your CRM, then gets re-entered into your project management tool, then gets re-entered into your invoicing system. Every handoff requires manual copy-pasting.

How to identify it:

• Ask your team: "How many times do you enter the same client data?"

• Look for: Data entry steps in your process maps

• Quantify it: Hours per week × cost per hour × 52 weeks = annual cost

Typical cost: 4-8 hours per week per person = €10,400-€20,800 per year per person. With 5 people doing this, that's €52,000-€104,000 per year wasted.

How to fix it:

1. Identify your single source of truth (one tool where data lives)

2. Set up integrations (Zapier, Make, or native integrations)

3. Automate data flow (when data enters Tool A, it auto-populates Tools B, C, D)

4. Test and refine (start with one process, prove it works, then scale)

Time to fix: 2-4 weeks

Typical ROI: 300-500% in first year (saves €10,000-€50,000/year, costs €2,000-€5,000 to set up)

Bottleneck 2: Tool Sprawl (Too Many Tools, No Integration)

You have 15-20 different tools, but they don't talk to each other. Your team uses different tools for the same task. Nobody knows which tool to use for what. You're paying for tool subscriptions you don't use.

How to identify it:

• List all your tools (CRM, project management, invoicing, email, docs, etc.)

• Ask your team: "Which tools do you use daily?"

• Look for: Duplicate functionality (3 tools that do the same thing)

• Quantify it: Unused tool costs + time wasted switching between tools

Typical cost: €500-€2,000/month in unused tools + 2-4 hours/week per person switching between tools = €15,000-€50,000 per year wasted.

Example from EverFruit:

We had 18 tools when I started. After auditing, I discovered:

• 5 tools nobody used (€400/month wasted)

• 3 tools that did the same thing (team confused about which to use)

• No integrations between tools (everything was manual)

Total cost: €4,800/year in unused tools + €20,000/year in time wasted switching between tools = €24,800/year wasted.

How to fix it:

1. Audit your tools (list everything, identify what's used)

2. Consolidate duplicate functionality (pick one tool per function)

3. Cancel unused tools (save money immediately)

4. Integrate remaining tools (Zapier, Make, or native integrations)

5. Document which tool to use for what (create a simple guide)

Time to fix: 2-3 weeks

Typical ROI: 200-400% in first year (saves €15,000-€50,000/year, costs €3,000-€8,000 to consolidate)

Bottleneck 3: Unclear Ownership (Work Sits Idle Waiting for "Someone")

Work sits idle waiting for "someone" to pick it up. Nobody knows who's responsible for what. Tasks get assigned to "the team" instead of a specific person. Projects stall because ownership is unclear.

How to identify it:

• Look for: Tasks assigned to "team" or "anyone" in your project management tool

• Ask your team: "Where does work get stuck waiting for someone?"

• Track: Time between task creation and task start (if it's >24 hours, ownership is unclear)

Typical cost: 15-25% of project time wasted on waiting/confusion = €40,000-€80,000 per year in lost capacity for a 20-person team.

Example from EverFruit:

When I mapped our project delivery process, I discovered:

• 30% of tasks had no clear owner (assigned to "team")

• Average wait time: 2-3 days before someone picked up a task

• Projects were always late because work sat idle

Annual cost: 20% of project time wasted = €60,000/year in lost capacity (could have taken on 2 more clients without hiring).

How to fix it:

1. Assign every task to a specific person (never "team" or "anyone")

2. Set up clear workflows (when Task A is done, it automatically assigns to Person B)

3. Use project management tools with ownership features (ClickUp, Asana, Monday)

4. Create RACI matrices for complex processes (who's Responsible, Accountable, Consulted, Informed)

5. Review weekly (catch tasks without owners, reassign immediately)

Time to fix: 1-2 weeks

Typical ROI: 200-300% in first year (saves €40,000-€80,000/year in recovered capacity, costs €2,000-€5,000 to set up)

Bottleneck 4: Single Points of Failure (If Sarah Is Sick, Everything Stops)

Only one person knows how to do critical tasks. If that person is sick, on vacation, or leaves, everything stops. Key processes depend on one person's knowledge.

How to identify it:

• Ask: "What happens if [key person] is out for a week?"

• Look for: Processes where only one person knows the steps

• Track: Tasks that can't be completed without a specific person

Typical cost: When the key person is out, work stops = €5,000-€20,000 per week in lost productivity. Plus risk of knowledge loss if they leave.

Example from EverFruit:
We had a single point of failure in client onboarding:

• Only one account manager knew how to set up new clients in all our tools

• When she was on vacation, client onboarding stopped for 2 weeks

• Annual cost: €10,000 in delayed revenue + risk if she left

How to fix it:

1. Document critical processes (write down how to do it)

2. Cross-train team members (teach 2-3 people how to do each critical task)

3. Create backup owners (if Person A is out, Person B can do it)

4. Automate what you can (reduce dependency on human knowledge)

5. Review quarterly (identify new single points of failure as you grow)

Time to fix: 2-4 weeks

Typical ROI: Prevents €10,000-€50,000 in lost productivity per incident, plus reduces risk of knowledge loss

Bottleneck 5: Broken Handoffs (Work Gets Lost Between Teams)

Work gets lost when it moves from one team to another. Sales hands off to delivery, but information is missing. Projects get delayed because handoffs are unclear. Nobody knows when work is "done" and ready for the next step.

How to identify it:

• Look for: Handoff points in your process maps (where work moves between people/teams)

• Ask: "Where does work get lost or delayed between teams?"

• Track: Time between handoff steps (if it's >24 hours, handoff is broken)

Typical cost: 10-20% of project time wasted on rework/miscommunication = €30,000-€60,000 per year in lost capacity for a 20-person team.

Example from EverFruit:
We had broken handoffs between sales and delivery:

• Sales would hand off a new client, but key information was missing

• Delivery team would have to go back to sales to get missing details

• Average delay: 3-5 days per client

Annual cost: 15% of onboarding time wasted = €15,000/year in delays + client frustration.

How to fix it:

1. Define clear handoff criteria (what information is required before handoff)

2. Create handoff checklists (ensure nothing is missed)

3. Use project management tools with handoff workflows (automated notifications when work is ready)

4. Set up handoff meetings (brief sync when work moves between teams)

5. Document handoff processes (write down who hands off what to whom, when)

Time to fix: 1-2 weeks

Typical ROI: 200-300% in first year (saves €30,000-€60,000/year in recovered capacity, costs €2,000-€4,000 to set up)

Bottleneck 6: No Documentation (Every Process Is Tribal Knowledge)

Every process exists only in people's heads. New team members take months to learn how things work. When someone leaves, their knowledge leaves with them. Nobody knows the "right way" to do things.

How to identify it:

• Ask new team members: "How long did it take you to learn how we do [process]?"

• Look for: Processes that aren't written down anywhere

• Track: Time spent explaining processes to new people

Typical cost: 2-4 weeks of onboarding time per new person = €2,000-€4,000 per new hire. Plus risk of knowledge loss when people leave.

Example from EverFruit:
When I started, nothing was documented:

• New account managers took 6 weeks to learn client onboarding (should take 2 weeks)

• When someone left, we lost their process knowledge

• Team spent 5-10 hours/week explaining processes to each other

Annual cost: €15,000/year in extra onboarding time + €10,000/year in lost productivity from knowledge gaps.

How to fix it:

1. Document your 3-5 core processes (start with the most critical)

2. Create simple SOPs (step-by-step guides, not novels)

3. Store documentation in accessible place (Notion, ClickUp, Google Docs)

4. Update documentation quarterly (processes change, docs should too)

5. Make documentation part of onboarding (new people read docs first, then ask questions)

Time to fix: 2-4 weeks (document 3-5 core processes)

Typical ROI: 200-400% in first year (saves €15,000-€30,000/year in onboarding time, prevents knowledge loss)

Bottleneck 7: Firefighting Culture (Always Reacting, Never Improving)

Your team is always putting out fires. There's no time for process improvement because you're always reacting to problems. The same issues keep happening because you never fix root causes.

How to identify it:

• Ask: "When was the last time we improved a process proactively?"

• Look for: Same problems happening repeatedly

• Track: Time spent on reactive work vs proactive improvement

Typical cost: 30-50% of time spent on reactive work = €60,000-€100,000 per year in lost capacity for a 20-person team. Plus opportunity cost of not improving.

How to fix it:

1. Schedule time for process improvement (block 2-4 hours/week for proactive work)

2. Fix root causes, not symptoms (use "5 Whys" technique)

3. Run quarterly operations audits (identify bottlenecks before they become fires)

4. Create improvement backlog (list of processes to improve, prioritize by ROI)

5. Celebrate improvements (recognize when team fixes something proactively)

Time to fix: 4-8 weeks (culture change takes time)

Typical ROI: 300-500% in first year (saves €60,000-€100,000/year in reactive work, enables scaling)

How to Identify Which Bottlenecks Are Costing You the Most

You probably have 3-5 of these bottlenecks. Use this approach to identify which ones are costing you the most money.

Quick assessment (30 minutes):

1. For each bottleneck, ask your team:

•    "Do we have this problem?" (Yes/No)

•    "How many hours per week does this waste?" (Estimate)

•    "What's the cost per hour?" (Salary + benefits + overhead / hours worked)

2. Calculate annual cost:

•    Hours per week × cost per hour × 52 weeks = annual cost

3. Rank by impact:

•    Highest cost = Fix first

•    Medium cost = Fix second

•    Lowest cost = Fix third

Your 90-Day Bottleneck Elimination Plan

Follow this 90-day plan to eliminate your top 3 bottlenecks.

Month 1: Identify and Prioritize

• Run the quick assessment above (30 minutes)

• Rank bottlenecks by annual cost

• Pick your top 3 bottlenecks to fix

• For each bottleneck, quantify the cost (hours × cost per hour × frequency)

Deliverable: Ranked list of bottlenecks with quantified costs, top 3 selected

Month 2: Fix Bottleneck #1

• Follow the "How to fix it" steps for your #1 bottleneck

• Set up the solution (automation, documentation, workflows, etc.)

• Test with your team for 2 weeks

• Track time saved and quality metrics

Deliverable: Bottleneck #1 fixed, time savings measured

Month 3: Fix Bottlenecks #2 and #3

• Fix bottleneck #2 (follow "How to fix it" steps)

• Fix bottleneck #3 (follow "How to fix it" steps)

• Test both solutions

• Track aggregate time savings

Deliverable: Top 3 bottlenecks fixed, aggregate ROI measured

Common Mistakes (And How to Avoid Them)

I've seen these mistakes kill bottleneck elimination projects. Avoid them with these approaches.

Mistake 1: Trying to Fix Everything at Once

❌ Why it fails: You'll get overwhelmed, nothing will get done, and you'll abandon the project.

✅ What to do instead: Fix one bottleneck at a time. Prove value, then move to the next. Start with your highest-cost bottleneck.

Mistake 2: Not Quantifying Costs

❌ Why it fails: You can't prioritize without numbers. "This feels inefficient" isn't enough.

✅ What to do instead: Calculate the actual cost of every bottleneck (hours × cost per hour × frequency). Rank by impact, not by gut feeling.

Mistake 3: Fixing Symptoms, Not Root Causes

❌ Why it fails: The bottleneck will come back in a different form. You'll waste time fixing symptoms.

✅ What to do instead: Use the "5 Whys" technique. Don't implement solutions until you understand why the bottleneck exists.

Mistake 4: Not Involving Your Team

❌ Why it fails: Your team knows where time is wasted—you just need to ask. If you don't involve them, you'll miss real bottlenecks.

✅ What to do instead: Interview the people who do the work. They know where time is wasted—you just need to ask.

Conclusion

These 7 bottlenecks are predictable and fixable. Most 10-100 person B2B teams have 3-5 of them, and they're costing €50,000-€150,000 per year in wasted time and lost capacity.

Fixing your top 3 bottlenecks takes 2-3 months of focused work. The ROI is significant. Most companies I work with save €50,000-€100,000 per year by eliminating these bottlenecks.

These bottlenecks are natural byproducts of growth. They're not your fault. They're what happens when you're too big to wing it but too small to have dedicated ops resources. They're fixable. Once you identify them, you can eliminate them systematically.

Frequently Asked Questions