tech
Operations Management
Running the day-to-day systems and processes that deliver the product or service.
Definition
Operations management is the function that makes the business actually run: workflows, SOPs, quality control, vendor management, capacity planning, scheduling. In a small service business, the founder is the operations manager. As the business scales, a dedicated ops lead becomes the first non-revenue hire that pays for itself - they free up founder bandwidth, install discipline, and prevent the silent leakage of bad processes. Strong ops is invisible from the outside but felt in every interaction.
When to hire the first operations lead
The signal to hire a dedicated operations person in a US service business is rarely revenue - it is founder bandwidth and process leakage. Hire when: you have more than 5 to 8 employees, founder is spending more than 15 hours per week on operational coordination (scheduling, vendor management, quality review), you have repeated quality misses or missed deadlines, or you are about to scale headcount and current processes will not absorb new hires. Typical first hire in US small business: Operations Manager at 80 to 130K base salary, reporting to the founder. For sub-2M-revenue businesses, a fractional COO (1099, 5 to 15 hours per week, 5 to 15K per month) often makes more sense than full-time hire.
The operations tech stack
Modern US operations runs on a stack of 6 to 10 tools. Project and task management: Asana, Monday, ClickUp, or Linear. Documentation: Notion, Confluence, or Coda. Communication: Slack plus email. Time tracking: Harvest, Toggl, or Clockify. CRM: HubSpot, Pipedrive, or Salesforce depending on stage. Customer support: Zendesk, Intercom, or HubSpot Service Hub. Accounting: QuickBooks Online or Xero. HR and payroll: Rippling, Gusto, or Justworks. Specialized: PSA tools (Mavenlink, Kantata) for service businesses, ERP (NetSuite, Acumatica) for product businesses above 10M revenue. Total stack cost typically 0.5 to 1.5 percent of revenue. Audit the stack quarterly; tools rot and overlap accumulates.
Cycle time as the master operations metric
Cycle time is the single highest-leverage operations metric for most US service businesses: how long does a unit of work take to flow from start to finish? Measure cycle time per major workflow (proposal to signed contract, contract to first delivery, ticket open to resolution). Once you measure it, two patterns emerge: most cycle time is wait time (work sitting in queues), not work time. And cycle-time reduction usually requires removing handoffs, not making people work faster. US lean manufacturing principles apply directly to service businesses: smaller batch sizes, fewer handoffs, parallel rather than sequential work, and visible WIP limits. Cutting cycle time by 30 percent typically lifts capacity 30 to 50 percent at zero added cost.
Operations during scaling and during downturn
Operations needs change with business cycle. During scaling (revenue growing 30 percent plus annually): focus on documenting current processes, hiring and ramping new team members, increasing capacity, defending quality. The risk is process collapse under volume. During downturn or flat growth: focus on margin protection, vendor renegotiation, automation of repeated tasks, capacity flexibility (shift from full-time to fractional or contractor structure). The risk is cutting too deep and damaging delivery capability. Best US practice: maintain a 'capacity flexibility ratio' - what percentage of capacity can you flex up or down in 30 days. Above 30 percent flexibility is healthy; below 15 percent means you are over-fixed and exposed in a downturn.
FAQ
What is the difference between operations and project management?
Operations runs recurring work; project management runs unique time-bounded initiatives. A US service business has operations (customer onboarding, monthly delivery, support tickets, billing) running every day, and projects (launch a new service line, migrate CRM, implement new SOP) running with start and end dates. Both functions can be in the same person at small scale; they separate at 30 to 50 employees. Operations measures cycle time and error rate; project management measures on-time and on-budget delivery against scope. Confusing the two leads to projects that never end (treated as ops) and operations that constantly disrupt (treated as projects).
Should operations sit under the COO, CFO, or CEO?
Depends on stage. Small US business under 5M revenue: operations sits under the founder/CEO, often combined with a fractional COO. Mid-market 5M to 50M revenue: dedicated COO who owns operations, customer success, and sometimes finance and HR. Past 50M: COO owns operations specifically; finance reports to CFO; people reports to CPO. The wrong structure: operations under CFO usually creates a cost-cutting bias that damages customer experience. Operations under CEO with no dedicated leader creates founder bottleneck.
How do I prevent operations from becoming bureaucratic?
Three rules. One, the SOP serves the work, not the reverse: if an SOP slows the work without improving quality, kill the SOP. Two, every operational process has an owner with authority to change it within 24 hours; no committee approvals for process tweaks. Three, measure outputs and customer outcomes, not adherence to process. The risk of mature ops teams is process worship - everyone follows the SOP and quality is fine but the team has stopped thinking. Combat this with quarterly process audits: every SOP gets a 'still needed, simplify, or kill' decision.
What ops investments have the highest ROI?
Ranked by US small business ROI data. One, automation of repeated administrative tasks (billing, reminders, status updates) via Zapier, Make, or custom automations - 5 to 20x ROI within 6 months. Two, project-level profitability tracking - reveals 20 to 40 percent of unprofitable work that can be repriced or declined. Three, SOPs for the top 10 recurring workflows - cuts onboarding new hires from 6 months to 6 weeks. Four, customer health scoring and proactive intervention - lifts retention 5 to 15 percent. Five, capacity flexibility (mix of W-2 and contractor) - protects margin in downturn. Avoid: ops tools without process discipline (tool without SOP = chaos with a dashboard).
What does world-class operations look like in a US small business?
Five signals. One, the founder takes a 2-week vacation and nothing breaks. Two, new hires reach 80 percent productivity in under 8 weeks because the SOPs are good. Three, customer onboarding produces measurable first value in under 14 days. Four, cycle time and error rate metrics are visible on a shared dashboard reviewed weekly. Five, the team can name the top 3 ops priorities for the quarter and the metrics that prove progress. Most US small businesses hit zero of these five; world-class operations hits all five. Each one is achievable; the discipline is sustaining them simultaneously.
In your business
- →Document the 10 most-repeated workflows as SOPs before hiring an ops lead - otherwise they spend 6 months figuring out what you do
- →Track ops metrics: cycle time, error rate, on-time delivery %
- →Ops investments pay off in margin - process improvements compound