How it works

Relay. Grow. Book. Route. Keep the context connected.

RelayLocal connects the moments that usually split across separate tools: pass work you cannot take, make genuine capacity visible, turn a customer's yes into a booking, or route organisation demand through approved private contractor networks.

Start relaying free

Private handoff

Customer enquiry

You cannot take it

Select trusted Circle

Customer approves

Business accepts

Warm introduction

Two tradespeople reviewing a job together at the doorstep of a red-brick house
01

Relay work you cannot take

A local business can record a legitimate enquiry and route it through selected private relationships rather than posting it publicly.

02

Grow with real capacity

Businesses can state when they want suitable work and record service, area and job preferences for authorised private workflows.

03

Book the customer when they are ready

A service business can publish real appointment availability, show versioned booking terms and take an optional deposit or full payment through its connected Stripe account.

04

Route organisation demand

Demand Partners can move structured service requests through approved private contractor pools, eligibility checks and sequential offers.

05

Keep trust cross-cutting

Customer information remains inside the applicable permission, booking or organisation-authority boundary rather than becoming public routing data.

06

Let businesses respond

Selected or eligible businesses can accept, decline or request more information where the applicable workflow supports it.

07

Record the outcome

RelayLocal keeps the relevant enquiry, offer, assignment, introduction and outcome history visible to authorised participants.

Three perspectives on one handover

What the customer experiences

The customer contacts a business they trust. If that business cannot take the work, the customer receives a clear, private link explaining that a trusted referral is possible. They decide whether their details can be shared, see their options on a simple handoff page, and remain free to choose how to proceed. No accounts, no jargon, no being passed around without warning.

What the receiving business sees

A selected Circle member sees the relevant opportunity information available to them — the type of work, the area and the context they need to decide. They can accept, decline or ask for more information. Customer contact details arrive only through the consent workflow, not in the initial relay.

What the original business can track

The referring business keeps visibility throughout: which businesses were selected, who viewed and responded, the customer's consent status, and what happened after the introduction. That history lives on the relay board and in the activity record, so no handover disappears into a group chat.

After the handover

The introduction is not the end of the journey.

Where the workflow fits, the service business can keep the next factual stage visible, including a RelayLocal booking, without forcing the customer into a public sales funnel.

Contacted

Booked

Quote arranged

Job won

Completed

Café owner warmly handing a written recommendation to a happy customer across the counter

Trust and privacy across every path

Nothing is posted to a public marketplace. An ordinary Relay uses the applicable customer-permission workflow; Demand Partner uses a distinct organisation-authority process and controlled contact release.

How it works — questions

No. Initial routing can use privacy-safe operational information. Identifying or contact details follow the applicable permission or organisation-authority process.

Cookies on RelayLocal

Essential cookies keep RelayLocal working. Analytics run only if you allow them. Cookie Policy