A service call arrives. Is it covered by the agreement, still under manufacturer warranty, explicitly excluded, or billable? In most contracting businesses that question is answered by whoever has been there longest — and answered wrong often enough to matter, in both directions: work given away that should have been billed, and customers billed for work that was covered.
Status: product concept, in active development. This is something we are building, not something you can buy today. We publish our roadmap because the engineering thinking behind it is the useful part — and because we would rather show you the design than imply a finished product.
Designed Capabilities
- Agreement and warranty repository — the obligations in one system rather than a filing cabinet.
- Covered assets and service frequencies — exactly what is under contract, per site.
- Entitlements and exclusions engine — the fine print, made operational.
- Response commitments and scheduling rules — SLAs that actually drive dispatch.
- Covered-versus-billable determination — answered at intake, consistently.
- Renewal pipeline and notifications — renewals surfaced before they lapse.
- Labor and material profitability — per agreement, not just per job.
- Customer and service-system integration — connected to dispatch and invoicing.
The Money Is in the Determination
Getting covered-versus-billable right on every call is worth more than most efficiency features, because it corrects a leak that runs continuously in both directions. It also removes an argument with the customer, which is worth something on its own.
Tell us if this matches a problem you have — early input shapes what we build first, and we will give you an honest view of where it stands.