Growth should make your business stronger, not harder to operate. But somewhere between $3 million and $10 million in revenue, many companies discover that every new job creates more coordination, more data entry, more approvals, and more opportunities for something to fall through the cracks.
The work still gets done, but only through follow-up calls, spreadsheet updates, inbox searches, and employees who know how to rescue broken handoffs. That is not a capacity problem alone. It is a process optimization problem.
Process optimization means improving how work moves from one step to the next so your team can deliver faster, with fewer errors and less dependence on individual heroics. The goal is not to make people work harder. It is to remove the friction that keeps capable people from doing their best work.
Why process friction becomes expensive at $3M–$10M
At an earlier stage, the founder may personally approve purchases, answer customer questions, review job margins, and resolve delivery issues. That level of involvement can work when the company has a small number of customers and projects.
As volume increases, the same approach becomes a constraint.
A customer order may move through sales, operations, purchasing, production, finance, and billing. Each department may use a different spreadsheet, application, or version of the customer’s information. A small gap at one handoff becomes a delay somewhere else:
- Sales closes a job, but operations lacks the specifications needed to schedule it.
- Purchasing orders materials without the correct job or cost code.
- Employees enter the same customer or project data into multiple systems.
- An approval waits in one person’s inbox for three days.
- Finance cannot finalize job costing because time and expense data arrives late.
- A billing error sends the work back through several teams for correction.
This is how revenue growth creates operational drag. The company is not necessarily inefficient because people are careless. The process was simply never designed for the volume and complexity the business has reached.
Start with the workflows closest to cash and capacity
Do not begin by trying to optimize every process in the company. Start with three to five workflows that have the greatest effect on revenue, delivery, cash flow, and management visibility.
Common candidates include:
- Quote to job setup to billing
- CRM to operations handoff
- Purchasing to receiving to inventory or job assignment
- Time entry to job costing to payroll
- Change order to approval to invoice
Choose processes that are frequent, error-prone, slow, or difficult for leadership to see without asking someone for an update.
A useful test is to ask:
- Where does work wait?
- Where is information entered more than once?
- Where do employees regularly ask, “Who owns this?”
- Which tasks require the founder or owner to intervene?
- Which delays affect billing, margins, inventory, or customer experience?
- Where does work get sent back for missing information or corrections?
Those questions will usually reveal more than a generic productivity review.
Map the process as it actually happens
A process document often describes the intended workflow. Process optimization requires mapping the real workflow.
Choose one high-impact process and document every step from the initial trigger to the final outcome. For each step, identify:
- The person responsible
- The information required
- The system or spreadsheet used
- The decision being made
- The next owner
- The expected turnaround time
- The most common reason the work stops or gets returned
Include the informal workarounds. If a project manager sends a text message because the formal system does not notify the right person, that belongs on the map. If finance maintains a separate spreadsheet because the accounting system does not provide timely job-cost information, document that too.
The gap between the official process and the real process is where much of the friction lives.
Four friction points that deserve immediate attention
1. Manual handoffs
A manual handoff occurs when someone must forward an email, retype information, attach a document, or explain context that should already be available.
For example, a salesperson may close a job in the CRM and email operations a summary. Operations then creates a project in another system and finance creates a customer record in a third. Each transfer introduces the possibility of missing details, inconsistent names, and incorrect dates.
Improve the handoff by defining:
- The trigger that starts it
- The required information
- The receiving owner
- The next action
- The service-level expectation
- The escalation path if it is late
A clean handoff should make the next step obvious without requiring a meeting or a personal favor.
2. Duplicate data entry
Duplicate entry is not only a time problem. It creates competing versions of the truth.
If a customer address, project value, payment terms, or cost code changes in one system but not another, employees make decisions using different information. Over time, this affects forecasting, purchasing, customer communication, and financial reporting.
Assign each major data type a system of record. Then reduce the number of places where employees need to manually recreate it. Where the process is stable and rules are clear, integration or ERP automation can move information between systems and create an audit trail.
The principle is simple: enter information once, validate it at the source, and make it available to the people who need it.
3. Approval bottlenecks
Approvals are necessary for control, but not every decision needs to reach the owner or CFO.
Review each approval and ask whether it adds meaningful risk protection or simply reflects an old habit. Then create decision rules based on thresholds, risk, margin, or customer impact.
For example:
- Routine purchases below a defined amount can be approved by the department manager.
- Jobs meeting predetermined margin and payment criteria can move forward without executive review.
- Change orders above a threshold require finance or leadership approval.
- Any exception to standard payment terms follows a separate route.
Set an expected response time for each approval. A purchase that waits four days for review may create more cost than the control is worth.
4. Rework loops
Rework occurs when a job, document, order, or invoice must return to an earlier step for correction. It is often treated as an employee performance issue, but recurring rework usually signals a process design issue.
Look for missing fields, unclear standards, poorly timed reviews, and ambiguous ownership. Fix quality at the earliest practical point instead of relying on finance or operations to catch every issue at the end.
A practical example: speeding up job costing
Consider a $6 million specialty contractor. The company completes work consistently, but job profitability is not visible until weeks after completion.
The process looks like this:
- Field employees submit time through a mobile tool.
- Project managers send material receipts by email.
- Purchasing maintains its own order spreadsheet.
- Finance waits for project managers to confirm which costs belong to which job.
- Billing begins only after the information is reconciled.
The result is delayed job costing, late invoices, and month-end uncertainty.
A better process would establish one job ID and standardized cost codes across quoting, purchasing, time entry, and billing. Required fields would be captured when the work occurs, not during month-end cleanup. Receipts and time entries would route to the correct project owner, with exceptions flagged for review.
The improvement is not just faster reporting. Leadership gains earlier visibility into margin, project managers can correct overruns sooner, and finance can invoice with greater confidence.
Process optimization comes before automation
Technology can reinforce a good process, but it cannot rescue a confusing one.
Before automating, decide:
- What should trigger the next step?
- What information must be complete?
- Who owns the decision?
- What exceptions require human judgment?
- What should happen when a deadline is missed?
Once the process is clear, automation can handle repetitive work such as:
- Routing approvals
- Sending reminders and escalations
- Creating a project from an accepted quote
- Syncing customer and job information
- Validating required fields
- Posting approved time and expenses to job costing
- Alerting leaders when cycle times or margins move outside target
This is where ERP becomes essential infrastructure for scaling. ERP is not simply another software purchase. It can provide the common data structure, workflow controls, role-based visibility, and auditability required to operate with consistency as volume increases.
Brown Paper Analytics approaches this work through its Process & Efficiency pillar, which focuses on cleaner handoffs, less rework, higher throughput, and workflows the team can actually use.
Measure the result in business terms
Process optimization should produce measurable operating improvements. Choose a small set of metrics before changing the workflow.
Useful measures include:
- Time from quote acceptance to job setup
- Time from job completion to invoice
- Percentage of jobs fully costed within a defined period
- Approval cycle time
- Number of manual handoffs per job
- Number of invoices returned for correction
- Rework hours by process
- Forecast variance
- Days required to complete month-end close
Start with a baseline, pilot the improved process with a small team or group of jobs, and review the results after four to eight weeks. If the team is bypassing the new workflow, do not assume resistance is the only explanation. The process may still be too complicated, missing information, or disconnected from daily work.
Effective operational excellence and process improvement makes the right behavior easier to follow.
Addressing the three common objections
“We cannot afford to fix this right now.”
The cost of inaction is already present in overtime, delayed billing, rework, missed purchasing opportunities, and management time spent chasing updates. Start with one workflow tied directly to cash or capacity. A focused improvement can create value without launching a company-wide transformation.
“Implementation will disrupt the business.”
A phased rollout is less disruptive than allowing a broken process to continue. Map the current state, redesign the highest-impact handoffs, pilot the change, train the people involved, and expand only after the process works in practice.
“We will do it later.”
Later usually means after another hire, another major customer, or another period-end crisis. Growth rarely makes process friction disappear. It makes the consequences more expensive.
A practical starting point is the ERP roadmap in 90 days: clarify the current state, prioritize the highest-value improvements, and create a phased plan that supports the way your business actually operates.
Your next step: find the constraint before adding more effort
You do not need to optimize everything at once. Identify the workflow that creates the most delay, rework, or uncertainty. Map how it really works, quantify the cost of the friction, and define a simpler future state.
Then connect the process to the right standards, systems, metrics, and accountability.
If your business is between $3 million and $10 million in revenue and growth is exposing gaps in handoffs, approvals, job costing, or reporting, request a process and ERP readiness diagnostic. Brown Paper Analytics will help identify the highest-leverage constraint and outline a practical process-to-system roadmap for improving flow without overwhelming your team.