A growing service company wants to hire another coordinator. The phones are busy, invoices are late, and the operations manager is spending evenings updating customer records. Another person might help. But before the job description goes online, leadership should answer a less comfortable question: how much of the workload is work that should not exist?
Separate demand from avoidable effort
A growing workload can reflect healthy demand, broken processes, or both. Treating every backlog as a staffing shortage makes it harder to see the difference.
What to do: Track one week of activity by category: customer-facing work, approvals, data entry, rework, and waiting. This gives leadership a more useful starting point than anecdotal busyness.
Begin by separating work created by customer demand from work created by broken handoffs. Answering more customer calls may justify staffing. Copying the same order into three applications does not automatically justify another position. For one week, have the team record recurring tasks, approximate time spent, and the reason each step exists. The point is not to monitor individual productivity. It is to understand where the business consumes capacity without creating customer value.
Find the steps nobody would design today
Employees often inherit procedures that made sense years ago. A paper approval, a repeated data entry step, or a status email may exist only because it always has.
What to do: Map the workflow from the original request to completion. Ask which steps add value, which protect against risk, and which are historical habits.
Look for steps that would be hard to defend if you designed the business today. Does a manager approve routine requests because nobody changed a policy? Does someone retype information already captured in a form? Are employees chasing signatures by email when a tracked approval would do? These are strong candidates for process redesign. Removing an unnecessary approval may be more effective than automating it, and less expensive to maintain.
Check whether current tools can do the job
A business may already own automated notifications, intake forms, routing rules, or simple integrations that were never configured.
What to do: Ask IT and operations to review capabilities in the systems already paid for. Avoid adding another platform until the gap is understood.
Many organizations own software with useful workflow capabilities they have never configured. Start with what is already licensed, but do not assume every feature is ready for production. Consider who will administer the workflow, how exceptions are handled, and whether data moves securely between systems. A simple demonstration can show possibility; a controlled pilot shows whether it works under real business conditions.
Keep human judgment where it matters
Automation can route routine requests or validate required fields. It should not silently make sensitive decisions without appropriate oversight.
What to do: Define exceptions, approvals, accountability, and what happens when an automated process fails. A good workflow makes responsibility clearer, not murkier.
Automation is a poor substitute for judgment when decisions involve unusual customer circumstances, employee concerns, contractual commitments, or financial exceptions. Define the routine cases a system can handle and the conditions that require a person. A process that silently makes the wrong decision faster is not an efficiency gain. The design should include review, escalation, and a clear way to reverse or correct an action.
Compare the full economics
A new hire brings judgment, relationships, and capacity that software cannot always replace. Automation has implementation, maintenance, and training costs of its own.
What to do: Compare scenarios: hire, improve the process, automate a narrow step, or combine approaches. Use actual workload and quality measures rather than a generic savings claim.
Compare more than salary against software cost. Hiring includes recruiting, training, supervision, coverage, and future capacity. Automation includes design, integration, testing, monitoring, and ongoing support. Some companies need both: automation to remove avoidable steps and a new employee to serve more customers. The useful measure is whether the combination improves service, reduces errors, and creates sustainable capacity.
Hiring solves capacity only when the work deserves to exist
A growing service business may believe it needs another coordinator because its current staff cannot keep up with incoming requests. But a closer look shows the coordinator spends much of the day copying information from customer emails into a scheduling system and then retyping it into an invoice. Hiring another person will increase throughput temporarily, while preserving the inefficiency. The first question should be which parts of the role require judgment, empathy, or customer relationships and which are predictable administrative steps. Automation is not a substitute for capable employees. It is a way to give those employees more time for work that genuinely needs them. Leadership should measure the process before choosing either a new hire or a new tool.
Follow one transaction instead of debating automation in the abstract
Select a high-volume process such as employee onboarding, invoice approvals, service scheduling, or customer intake. Map the trigger, each handoff, every application touched, and the final result. Record how often the process occurs, how long it takes, and where mistakes happen. Ask what exceptions require human approval. A workflow that occurs twice a month may not justify a complex integration, while a simple task repeated hundreds of times may offer meaningful relief. Calculate potential time savings conservatively and include the effort needed to maintain the automation. The business case should survive without assuming every saved minute becomes a dollar of immediate payroll reduction.
Know where automation should stop
Some decisions should remain with a person even when software can make a recommendation. Customer complaints, exceptions involving sensitive data, unusual financial approvals, and situations with contractual consequences may require human review. Define what information the workflow may use, who can override it, and how errors will be detected. Test the most common cases and the messy exceptions before declaring success. A reliable process needs monitoring and an owner after launch. Otherwise the company replaces an obvious manual bottleneck with an invisible automated one that fails quietly until a customer notices.
Make the hiring decision with better evidence
After mapping the workflow, leadership may still decide to hire. That can be the correct outcome when demand requires more relationship management, specialized expertise, or judgment. The advantage is that the job description will reflect the work the company actually needs rather than the administrative burden it inherited. Ask the MSP or automation partner to assess whether existing applications can exchange information securely, whether the proposed workflow is practical, and what support it will need. Then compare the options: redesign the process, automate a portion, train current staff, or add a role. A thoughtful decision often combines more than one of those approaches.
The Decision Worth Making Before Year-End
This is not an argument against hiring. It is an argument for making sure the next employee spends time on work that matters. A better process can make a new hire more effective from day one instead of asking that person to inherit the same bottlenecks.
Before approving the next position, map the process that position would inherit. Ask which steps should disappear, which can be supported by existing tools, and where a human being will make the biggest difference.
For additional perspective, NIST offers a risk-management framework for organizations evaluating AI-enabled systems. Use that guidance alongside the actual needs and constraints of your organization.
Frequently Asked Questions
What business tasks are good candidates for automation?
Repetitive, rules-based tasks with consistent inputs and clear exceptions are often good candidates, such as routing requests, sending reminders, and transferring approved information between systems.
Should businesses automate before hiring?
They should examine avoidable work before deciding on headcount, but the answer depends on demand, service expectations, and the economics of each option. Automation and hiring can be complementary.
How do you estimate the return on workflow automation?
Measure current labor time, errors, delays, and rework; then include implementation, training, and maintenance costs. Compare those results after a limited pilot.
What processes should remain human-led?
High-stakes decisions, ambiguous exceptions, sensitive customer situations, and work requiring professional judgment should retain clear human oversight.
How can an MSP support process automation?
An MSP can assess systems, access, integration, security, and operational support, and coordinate with automation specialists where deeper process development is required.
