Qualify Service Businesses by Delivery Model
Compare employee delivery, subcontractor networks and platforms through request, scheduling and acceptance responsibilities before assessing fit.
10/24/20263 min read
Two service businesses can use the same industry label while delivering work in very different ways. One may perform projects with employees, another may coordinate subcontractors, and a third may sell a platform that customers operate themselves. Qualification should reflect the delivery model your offer must support.
Imagine a fictional scheduling-tool provider researching three maintenance businesses. All describe themselves as service providers. The software, however, depends on who assigns technicians, controls availability, and accepts completed work. A generic company profile will not answer those questions.
Describe the delivery chain
Start with the unit of service: a site visit, recurring inspection, remote support session, or project milestone. Then trace how a request becomes delivered work and how completion is accepted.
Use current service pages, customer terms where public, operational descriptions, and permitted clarification. A company’s stated capabilities are evidence of its offering, not proof of actual staffing, utilisation, or performance.
Relevant official filings can help verify legal identity and reported business activities. They do not establish the day-to-day dispatch model or the authority of an individual employee.
Compare three fictional models
The research worksheet records these cases:
Alder Maintenance: describes employing its own field team and scheduling visits centrally. Fit question: who controls the dispatch workflow and which exceptions require customer approval?
Harbor Service Network: describes coordinating independent local providers. Fit question: can the network assign work, or do providers accept requests independently?
Moss Support Platform: provides software through which customers find service providers. Fit question: is the company itself delivering maintenance or facilitating another party’s service?
The worksheet does not rank one model as inherently better. It identifies which assumptions the scheduling offer must satisfy and which remain unresolved.
Map control rather than headcount
For each business, record who receives the request, commits capacity, assigns work, communicates changes, invoices, and accepts completion. Those responsibilities may sit with different parties.
A large employee count does not prove a large field-delivery team. A small company may coordinate substantial work through partners. Neither observation establishes revenue, service quality, or a current need for new software.
In the fictional example, Harbor cannot guarantee that every provider will use a central calendar. That limitation changes the proposed scope. The team explores whether a request-status tool would fit better, but it does not claim that the original dispatch product can control independent providers.
Separate delivery model from commercial model
Recurring billing does not necessarily mean recurring field work, and a project contract may include ongoing support. Record how the service is delivered separately from how it is priced.
This distinction helps avoid unsuitable assumptions about implementation. A tool designed for repeat visits may not fit a business whose work consists of bespoke projects with long planning cycles. A subscription fee may cover access to a marketplace rather than any committed service capacity.
Where public information is ambiguous, preserve the ambiguity and ask a targeted question through an appropriate business route.
Make the fit test falsifiable
Write the condition that would make the account unsuitable for the proposed offer. For example: “The tool requires a central team authorized to assign technician schedules.” If that condition is absent, do not keep the account qualified merely because it uses the word maintenance.
Also identify what evidence could change the conclusion. A separate operating subsidiary might run an employee-based service team even when the group’s main model is a network. Keep that exception tied to the relevant entity and service line.
Handoff the operating question
The final brief names the service unit, delivery parties, control points, commercial model, and unresolved fit condition. It should not diagnose inefficiency or promise savings from a website description.
This method turns a broad industry match into a practical operating-model assessment. The result may be a suitable account, a narrower use case, or a respectful decision not to pursue. Each outcome is useful when it follows the way the business actually delivers its service.