Opportunity Intelligence · Guarded beta

Build better routing from real relationship evidence, without weakening the rules.

RelayLocal’s Opportunity Graph compares already-eligible businesses using privacy-safe relationship and outcome evidence. A guarded beta can influence ordering for up to 5% of eligible live Demand Partner requests when enough contextual evidence exists; hard eligibility remains authoritative and all other requests fall back to deterministic routing.

Illustrative human context

The people in controlled routing

Demand Partner
RelayLocal
Assigned business

An organisation routes through its approved private pool; approval is not RelayLocal vetting and only one offer is active at a time.

Illustrative roles only, not named RelayLocal customers or live activity.

Why a second routing layer matters

Two businesses can both satisfy the same hard requirements while having different evidence in a specific relationship, service, area and operating context. RelayLocal is testing whether that context can make future routing more useful without creating a public ranking system.

Hard eligibility first

Two-sided approval, service, area and recorded availability/capacity remain the gate. Context cannot rescue an ineligible candidate.

Context instead of a universal score

Evidence belongs to a specific relationship and opportunity context rather than becoming a permanent public reputation number.

Controlled authority

Only a deterministic 5% live cohort can use Graph ordering, and only after hard eligibility and minimum-evidence checks pass. Other requests use deterministic ordering.

Real workflow

The Opportunity Graph controlled-learning loop

  1. 01

    Privacy-safe fingerprint

    Create a context fingerprint from service, outward area, urgency, timing, job/value bands and the approved relationship — without direct customer identity.

  2. 02

    Deterministic eligibility

    Run the existing hard filters first. Only already-eligible candidates enter Graph comparison.

  3. 03

    Contextual evidence

    Look at relationship-specific factual evidence such as prior accepts, declines, expiries and recorded outcomes.

  4. 04

    Confidence and recency

    Weight evidence conservatively so tiny samples and stale history do not dominate.

  5. 05

    Guarded ordering

    For a small deterministic beta cohort with enough evidence, contextual ordering can reorder already-eligible candidates. Otherwise the deterministic baseline is used.

  6. 06

    Outcome learning

    Record privacy-safe factual offer/outcome evidence and update contextual aggregates.

  7. 07

    Graduation gates

    Measure usefulness, concentration, fairness, privacy and failure behaviour before any broader rollout beyond the current 5% beta.

Designed around a privacy boundary

Included

Service, outward area, timing/urgency bands, job/value bands, approved relationship identifiers and factual routing outcomes.

Excluded

Customer name, email, phone, full address, contact notes, attachment contents and private access tokens.

Still treated carefully

Business and organisation identifiers can be personal data in some circumstances, especially for sole traders.

No black-box contractor ranking

Graph v1 is not an AI quality score, public star rating or universal contractor leaderboard. A decline or expiry in one context does not become a permanent judgement about a business.

Failure must not break routing

Graph calculation and learning are isolated from the authoritative eligibility path. If Graph is unavailable or evidence is insufficient, the deterministic routing workflow continues.

What must happen before broader rollout

The current beta is capped at 5%. Broader rollout still requires continuing outcome evidence, fairness and concentration review, retention and legal review, suitable transparency/challenge mechanisms, a proven rollback path and evidence that contextual ordering improves useful operational outcomes without weakening privacy or eligibility controls.

Clear boundaries

Opportunity Graph v1 is not…

  • Universal adaptive routing for every request
  • AI choosing the best contractor
  • A public quality score
  • A customer profiling engine
  • A guarantee of response or completion
  • A way to bypass hard eligibility
  • A claim that software is uncopyable

Opportunity Intelligence · Guarded beta questions

A guarded beta is live for up to 5% of eligible Demand Partner requests. Hard eligibility is still authoritative, and requests outside the cohort or without enough evidence use deterministic routing.

Cookies on RelayLocal

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