Field service that lives on the same record as the rest of the business.

The phone rings, and one record carries the work all the way to the deposit.

Six steps from the service provider’s perspective. No swivel-chair between systems. No re-typing.

1. 1. The call comes in.

   A property manager calls about an annual fire alarm inspection. Office staff opens the customer record — no spreadsheet hunt, no shared inbox to grep — and sees the prior inspection, last invoice, open deficiencies, and the building’s adopted NFPA edition. The CRM has the contact, the pipeline stage, and the renewal history on the same screen. The lead becomes a job in two clicks.

2. 2. The inspection is scheduled.

   Dispatch drops the job onto the day-board for the right tech. Recurring schedules surface the rest of the year automatically — annual, semi-annual, quarterly, monthly — so the renewal does not depend on someone remembering. The customer portal shows the appointment to the building owner; the AHJ sees what they are entitled to see.

3. 3. The tech arrives, and the mobile app runs the inspection.

   The tech opens today’s board on the phone. Picks the inspection type from the library of 617+ across 32 trades. The checklist walks each step, captures photos, records readings, and cites the jurisdiction’s adopted NFPA edition — not whatever was published last. Offline-first; resyncs when signal returns. No second app for the office to keep aligned.

4. 4. A deficiency is found.

   The tech logs a finding — a tagged extinguisher overdue for hydro, a sprinkler riser with a corroded gauge, a backflow that failed test. Photo, citation, and recommended remediation attach to the deficiency. The deficiency is not a sticky note; it is a record on the same row as the inspection and the customer.

5. 5. The proposal generates from the deficiency.

   A proposal draft writes itself with line items, takeoff references, and approval routing. The customer reads it in the portal, asks one clarifying question in the comment thread, and approves with one click. The approved proposal becomes a work order on next week’s schedule — the same record the tech captured on, now scheduled for the office to dispatch.

6. 6. The customer pays through the portal.

   Time, expenses, parts, and signatures from the repair work attach to the same record. The invoice generates from the work order, not from a re-key into a separate billing tool. The customer pays with ACH or card from the portal — same login they used to approve the proposal — and the deposit lands in the books without a sync job. The AHJ sees the closed deficiency on their slice of the same record.

Six steps. One record. Office, field, customer, and AHJ each saw the slice they needed without anyone re-typing the work into a second system.

Your customer list, your inspection history, your books — they belong to you.

We took the trade-contractor playbook seriously and built around the systems you actually run, not around a closed ecosystem we wish you ran.

Plain answers to the questions every contractor asks first.

Can I license multiple technicians?

Yes. Pricing scales by seat for office, dispatch, and tech roles. Dispatchers and admins are priced separately from field-only seats; a tech who only opens the mobile app is not priced like a full office user. There is no minimum-tech surcharge and no per-truck fee. Pricing details on the pricing page.

Is on-prem or self-hosted possible?

Standard deployment is multi-tenant SaaS on AWS, with tenant data isolated at the row-level by tenant id and at the storage layer by per-tenant prefix. Single-tenant and dedicated-environment deployments are available for customers with a regulatory or procurement requirement that names them; talk to us before signing a contract that requires it so we can scope it correctly.

I already use ServiceTitan / BuildOps / Inspect Point / Jobber. What changes?

Service is built to run the same trade-contractor workflow those tools run — inspections, dispatch, work orders, proposals, invoicing — on a single record that also carries the customer portal, the AHJ submission, and the marketing engine. Most customers who switch are consolidating two or three tools, not just swapping one. We will not pretend the migration is zero work; we will tell you which records port cleanly and which need a re-key, before you sign.

Does the mobile app work without signal?

Yes. The mobile app captures photos, readings, signatures, and checklist responses while offline and syncs when signal returns. It is honest, working software — we do not claim it is the prettiest mobile app on the market without proof, but it does the job a field tech needs done in a basement, on a roof, or in a sprinkler riser closet with no bars.

How long does pricebook setup take?

Most customers are running on a usable pricebook in the first week and tuning it for the first month. The deepest pricebook tooling is on our roadmap, but most operators land fully operational without a multi-month consulting engagement. If you have an existing pricebook in CSV or in another system, we can usually import it.

How does payroll integration work?

Payroll, W-2s, and direct deposit stay with your existing payroll provider — ADP, Gusto, Paychex, or whoever you already use. Guspora exports a CSV of approved hours, jobs, and rates that imports cleanly into the major payroll systems. We are not replacing your payroll provider, and we are not asking you to.

How does the AHJ side work?

The fire department running the jurisdiction can read the inspection reports you submit through the customer portal. Three-party trust: contractor, building owner, and AHJ each see the right slice of the same record. If the AHJ runs Guspora Compliance, the loop closes natively — your submission lands in their queue. If they do not, the report is still a clean PDF and a structured submission, not a fax.

Do you support multiple branches or service areas?

Yes. Multiple branches share one tenant with branch-scoped dispatch boards, branch-scoped customer lists, and branch-scoped reporting. The owner sees consolidated margin; the branch manager sees their branch. The customer record is canonical across branches so a customer with sites in two service areas does not become two records.