Technology Stack for a Five-Person Service Business
Why this matters
A five-person service business (one owner, two technicians, one office, one floater) has crossed the threshold where paper, spreadsheets, and a single QuickBooks file no longer scale. The owner is in the truck most days; the office is the only person in the building during business hours; the workflow has to run without the owner's hands on every transaction. Picking the right software stack at this stage prevents two later problems: tearing out an inadequate system at 10 employees (when migration cost is much higher) and selecting an enterprise platform that is heavy for a 5-person workload. This is the working stack and the selection logic.
The five categories
A trade-business stack at this size has five core software categories. Each can be a separate product or bundled in a vertically integrated platform.
- CRM and dispatch (customer database, scheduling, dispatching, work order management)
- Accounting (general ledger, AR, AP, financial reporting)
- Payroll (wage payment, tax filing, benefit administration)
- Communications (phone system, text, email)
- Field tools (mobile app for technicians, photo capture, signature, payment)
A sixth category, project management and field-tools-specific, is often bundled into CRM and dispatch at this size; standalone field tools become relevant at 15+ employees.
The build-vs-buy-vs-bundle decision
Three architectural patterns:
Pattern A. Best of breed. Separate vendor for each category. Strongest individual capabilities; most expensive in total; requires integration work (Zapier, native integrations, or accepting some manual data entry between systems).
Pattern B. Vertical platform. Field-service management (FSM) platform bundles CRM, dispatch, field tools, and sometimes payment processing. Integrates to a separate accounting and payroll. Common pattern at 5 to 50 employees.
Pattern C. Single platform. One platform claims to cover everything. Usually limits in one or more categories. Rare to fit well at five employees.
For a five-person business, Pattern B is the most common fit: a vertical FSM platform plus accounting plus payroll plus communications.
Category 1: CRM and dispatch
What it does: customer record (contact, address, history), job creation, scheduling, dispatch to technicians, work order generation, invoicing.
Vertical FSM platforms in this space include ServiceTitan, Housecall Pro, Jobber, FieldEdge, Workiz, ServiceFusion, and Manuall. Selection criteria for a 5-person business: pricing model (per-user, per-tech, flat-rate; per-user favors smaller shops); mobile app depth and reliability; native integration to QuickBooks Online or Xero; customer portal (online booking, payment, status); out-of-the-box reporting; trade-specific features; implementation time (days vs months); data export capability (lock-in is a real concern). Avoid enterprise platforms aimed at 50+ operations.
Category 2: Accounting
General ledger, AR, AP, bank reconciliation, financial reporting. The two dominant options: QuickBooks Online (market-leading, integrated with most FSM platforms, well-supported by bookkeepers and CPAs; Plus tier is typically right at five employees because it enables class tracking, projects, inventory); Xero (better UI, smaller US trades integration ecosystem, stronger outside US). QuickBooks Desktop is phasing out; new businesses should not start there. Avoid spreadsheet-based accounting at five employees: transaction volume exceeds the practical limit and there is no audit trail.
Category 3: Payroll
Calculate wages, withhold and remit taxes, file quarterly/annual returns, issue W-2s and 1099s, manage benefits enrollments. Options: Gusto (dominant for under-50-employee, includes benefits administration and basic HR), ADP RUN (long-established, more expensive, deeper for complex needs), QuickBooks Payroll (bundled with QBO), Rippling and Justworks (newer entrants with different bundles). For five employees, Gusto or QuickBooks Payroll cover most needs; Gusto leads on HR features. Do not run payroll manually; the risk of tax-deposit errors is not justified by the small savings.
Category 4: Communications
Business phone line, call routing, voicemail, business text, call recording, analytics. VoIP business phones (RingCentral, Dialpad, Vonage, Grasshopper, Ooma, OpenPhone) include call routing, automated attendant, mobile app, business text, and CRM integration. Call tracking (CallRail, CallTrackingMetrics, Invoca) adds tracked numbers per marketing source for attribution. Business email (Google Workspace, Microsoft 365) with domain is required for credibility. At five employees, VoIP plus call tracking plus email complete the communications layer.
Category 5: Field tools, integrations, pricing
Field tools is the technician mobile app for dispatches, photos, signatures, in-field payment, and status updates. In Pattern B this is bundled into the CRM and dispatch platform; the technician works from the FSM platform's mobile app. Standalone field-tools products exist for businesses with un-migratable legacy CRM but are uncommon at five employees.
Integration data flow: CRM and dispatch is the system of record; accounting receives invoice and payment data from CRM (native integration is standard); payroll receives time and wage data from the FSM (if it handles time tracking) or from a separate tracker; communications receives caller ID lookup from CRM and feeds recordings or notes back. Before committing, test the integration in a sandbox; "we integrate with QuickBooks" varies from "every transaction flows automatically with detail" to "manual export and import monthly."
Software pricing scales with employee count and feature tier. At five employees the relative scale is: CRM and dispatch is the largest line item; accounting (QuickBooks Online Plus), payroll, and phone are mid-tier; email is small. Total monthly cost is meaningful but pays for itself many times over against manual alternatives. Negotiate; most platforms discount 10 to 20 percent for annual commitment.
Migration and what to defer
Data lock-in is real: three years of customer records, jobs, invoices, and photos take non-trivial effort to migrate. Before committing, verify export capability (all customers, jobs, invoices, payments, photos in machine-readable format), format (CSV is the standard; proprietary is a red flag), and export cost (some platforms charge).
At five employees defer: enterprise FSM platforms for 50+ operations, standalone field-tools products (bundled is fine), custom-built integrations, advanced analytics platforms (built-in dashboards suffice), marketing automation platforms (CRM basic email plus social schedulers cover the audience size). Revisit the stack at 10 employees to evaluate whether a best-of-breed split is warranted.
References
- IRS Publication 583 - Starting a Business and Keeping Records (recordkeeping requirements supported by software)
- FTC Health Breach Notification Rule and state data-breach notification laws (relevant if storing PII)
- SOC 2 Type II audit reports (each vendor's; verify before contracting)
- PCI DSS v4.0 (relevant for payment processing components of FSM platforms)
- General Data Protection Regulation (relevant if any customer is in the EU, even occasionally)