Why Relevant — and not an appointment-first CRM.
Most field-service CRMs assume your business is one tech, one truck, one appointment at a time. That works for HVAC tune-ups and plumbing service calls. It breaks the moment your job is a scope of work performed by a crew or a sub over days or weeks.
Optimized for one-truck service calls
- • The core object is an appointment on a tech's calendar.
- • Subcontractors are an afterthought or a paid add-on.
- • "The job" is whatever fits between two appointments.
- • Change orders, materials, and scope live in spreadsheets.
Optimized for crews, subs, and scope-based jobs
- • The core object is a job with a real scope and lifecycle.
- • Internal crews and subs are first-class, side-by-side.
- • Scope Dispatch sends defined work to a crew or sub with a public approve link.
- • Materials, change orders, and invoices live with the job.
Where Relevant earns its keep
If you bid scope and then run it through a mix of your own crews and subs, you have probably tried to make a calendar-first CRM work. It almost does. Until a change order shows up, or a sub needs to see the scope before they accept, or you need to know how much of a job's contracted dollar value is still in progress versus completed.
Relevant treats the job — not the time slot — as the thing the whole system organizes around. The schedule still exists, but it is a view onto the work, not the work itself.