Apprentice → Solo Tech → Team Owner → Scalable Trades Business One system. Every stage. Every trade.

Three tiers.
One architecture.

Most field management tools are built for one type of user, usually the business owner. TOS is built differently. The same relational structure powers all three tiers, with role-based views controlling what each user sees and can do. And because the architecture isn't trade-specific, the same tiers apply whether you're running an HVAC crew, an electrical team, or a plumbing operation.

01
Tier One
TOS Solo

For the independent tech who wants to run their work like a professional from day one. Personal tracking, clean records, real earnings visibility.

  • Personal job tracking
  • Time logging with real labor cost
  • Diagnosis logs (CCC framework)
  • Parts used per job
  • Earnings visibility
  • Personal productivity dashboard
02
Tier Two
TOS Team

When you're ready to bring on other techs. Multi-technician job management, workload balancing, and performance visibility across your whole crew.

  • Everything in Solo, plus:
  • Multiple technician records
  • Job assignment and scheduling
  • Team workload tracking
  • Technician performance rollups
  • Per-tech earnings breakdown
  • Capacity and utilization indicators
03
Tier Three
TOS Owner

Full business intelligence. This is where TOS becomes a decision engine, turning operational data into the insights that actually run a growing HVAC company.

  • Everything in Team, plus:
  • Profitability dashboards
  • KPI reporting (revenue, callbacks, margin)
  • Technician analytics
  • Capacity planning
  • Invoice and payment tracking
  • PM-to-repair conversion analytics
  • Financial reporting layer

11 databases.
All relational.

Every part of TOS is connected. Jobs link to time entries. Time entries link to technicians. Parts link to jobs. Invoices link to payments. Nothing lives in isolation.

Central Hub
Jobs Database
The central record of all service work. Every job carries its type, operational status, financial status, assigned technician, diagnosis logs, parts used, time entries, and invoice. The entire system radiates from here.
Labor
Time Entries
Tracks labor per technician per visit. Supports multiple entries, multi-day jobs, and dynamic labor cost calculation via Settings.
People
Technicians
Every tech has their own record, dashboard, and performance metrics. Scales from 1 to a full crew without structural changes.
Diagnosis
CCC Logs
Complaint → Cause → Correction. Applies to all job types including PM visits (with context-adjusted meaning).
Visits
Service Visits
Represents a single on-site visit. Enables multi-day jobs, multiple techs per visit, and PM + Repair under one site event.
Parts
Parts & Materials
Tracks cost, markup, sale price, supplier, and profit per part, with markup rules pulled dynamically from Settings.
Clients
Clients / Locations
Customer and site records with full service history rollup, equipment units, and PM contract flags for future use.
Finance
Invoices & Payments
Structured billing with deposit support for installations, partial payment tracking, and outstanding balance visibility.
Brain
Settings Database
Centralizes all dynamic values, labor rates, markup %, callback windows, tax rates. No hard-coded values anywhere in the system.

Why it's built
this way.

01
Architecture First

Most field software is built feature-first, adding tools as they're requested. TOS is built architecture-first. Every decision about what to add starts with whether it fits the relational structure cleanly. That discipline is what makes the system scalable rather than just functional.

02
Mobile-First UX

Techs are in the field. They're on their phones. A system that's hard to use on mobile gets abandoned on mobile, and then it stops getting used at all. Every technician-facing view in TOS is designed for a phone screen first, minimal clicks, fast inputs, clear next actions.

03
One Unified Framework

Service calls, PM visits, installations, repairs, they all run through the same CCC diagnostic structure and the same job record. There's no separate "PM system" or "inspection module." One architecture handles everything, which means data stays consistent and analytics actually mean something.

04
Data That Earns Its Keep

Every field in TOS exists because it feeds something, a report, a rollup, a decision. If logging data doesn't ultimately make you money or save you time, it shouldn't be there. The goal is a system that creates intelligence, not one that just stores records.

Starting with HVAC.
Built for every trade.

TOS is launching with HVAC and refrigeration because that's where we know the problem most intimately. But the system architecture was intentionally designed to be trade-agnostic from day one. Here's how the expansion is planned.

Phase 1, Now
HVAC & Refrigeration

The founding trade. Full system, jobs, time, diagnosis, parts, invoicing, PM workflows, KPI dashboard. Built and launching first.

Phase 2, Coming
Electrical

Panel work, service calls, circuit diagnostics, permit tracking. Same core architecture with electrical-specific job types and CCC logic.

Phase 3, Planned
Plumbing

Service calls, installations, emergency dispatch, fixture and pipe job types. Full field ops management adapted for plumbing operations.

Phase 4, Future
Welding & Beyond

Fabrication, structural, pipe welding. And wherever skilled field professionals need a system that actually understands how they work.

TOS is in active
development.

The system is being built right now. Sign up to be notified when it launches, and to get early access when it does.

Get Early Access Read Field Notes