Why RelayLocal · Relay. Grow. Book. Route.
Local work already moves. RelayLocal keeps the handover, capacity, booking and routing context connected.
The problem is not a lack of apps. It is that the important moments between enquiry, trusted handover, capacity, appointment, payment and organisation assignment usually live in different places.
Local work already moves through relationships
Service businesses already pass work to people they trust, call around when they have spare capacity, arrange appointments in separate calendars and chase payment in another tool. RelayLocal does not invent those behaviours. It gives them one operating memory.
A good enquiry should not become a dead end
When a business cannot take suitable work, the customer should not have to restart from zero. Relay provides a private, recorded handover through selected relationships while customer information stays inside the appropriate permission boundary.
Capacity should be useful before the phone rings
Grow turns Open, Limited or Paused capacity, availability windows and work preferences into private operating signals. Suitable routing can use those facts without creating a public lead-buying feed or promising work.
The customer’s yes needs an operational next step
Bookings lets a service business publish real availability, show versioned terms and use supported Stripe checkout for a deposit or full payment. If the service later goes wrong, the customer concern, business response, refund and external dispute evidence can stay attached to the booking instead of vanishing into email.
Organisation demand needs different controls
Demand Partner does not pretend to be an ordinary referral. It uses approved contractor pools, deterministic eligibility, private offers, recorded assignments, assignment-linked appointments and explicit payment responsibility for organisation-routed work.
Trust means keeping boundaries visible
RelayLocal separates public marketing from protected operations, separates privacy-safe routing context from customer contact data, and separates business subscription billing from customer payments and organisation settlement records.
Better routing should not weaken the rules
Opportunity Graph v1 is deliberately guarded. It may reorder already-eligible contractors for a small 5% beta cohort when enough contextual evidence exists, but it cannot bypass the hard eligibility rules or turn a business into a universal quality score.
Start with the part of the workflow you need today.
A business can begin with Relay, then use Growth, Bookings or organisation-routed opportunities when those capabilities fit its operation.