Commercial pest control is not residential work with bigger invoices.

A commercial property is rarely one place. A plaza has a dozen tenant units. A condo tower has a parking level, a chute room, a garbage room and hundreds of suites. A restaurant group has the same brand at eight addresses with eight different layouts and eight different problem histories.

When the software can only represent an address, everything below that level becomes free text. Which unit had activity, which building the interior stations sit in, which tenant space keeps recurring — none of it can be queried later, because none of it was ever a field.

• Properties, buildings, units and unit groups model the site the way the technician walks it.
• Service context and device history stay attached to the specific place they belong to.
• Findings at unit level survive as data, not as a sentence in a note field.

Commercial work runs on service agreements. Monthly, bi-weekly, quarterly — the schedule is an obligation that exists whether or not anyone books it. That is a different concept from a customer calling for an appointment, and treating it as a repeated booking creates a quiet, ongoing failure mode: a visit that was never created is a visit nobody notices is missing until the customer does.

Recurring service belongs in the schedule as a standing commitment, with the week and day views the office needs to see coverage, and a visible pool of work that has not been assigned to anyone yet.

Commercial accounts generate an audience for the paperwork. The site contact wants to know what happened today. The property manager wants a service report. A quality manager at a food-handling site wants the trend across the last quarter, the device map, the corrective actions and the details of what was applied.

All of them are asking for the same four facts: what was checked, what was found, what was done about it, and when. If those facts are captured as structure during the visit, the paperwork is a byproduct. If they are captured as prose, someone rebuilds the report by hand every month.

• Device and inspection outcomes recorded per visit, against the device and the location.
• Materials, chemical applications and treatment records tied to the work performed.
• Work orders and service reports generated from the visit rather than retyped after it.
• Issues that stay open and visible until follow-up work closes them.

ServOS is being built and tested inside a working commercial pest control company before it is sold to anyone else, alongside a small group of other operators through the end of 2026. The data model reflects how commercial service is actually run rather than how it looks from the outside.