Skip to content

Know what matters across your business.

When performance changes, the explanation rarely lives in one report. HQ helps teams frame an operating question, inspect related evidence and review the next decision.

Request an HQ walkthroughExplore the example

Ri’SERVE’s Operating Intelligence application. Sources and capabilities are confirmed for each deployment.

SIGNAL → EVIDENCE → OWNER REVIEW
An illustrative operating question, its source evidence and a proposal for a named owner. Concept workspace; no live metrics or completed action.
Read diagram details
  • Selected signal: Illustrative location
  • HQ investigation: Context to inspect
  • Source evidence: References retained
  • Owner review: Decision stays here
  • Selected signal → HQ investigation: operating question
  • Source evidence → HQ investigation: source evidence
  • HQ investigation → Owner review: proposal for review (possible, subject to review)

A change at one outlet.
Where would you look next?

Imagine repeat visits changing at Outlet A. HQ’s investigation model connects the question to comparable locations, surrounding evidence and a named reviewer.

Follow the reasoning below. A pattern is a starting point for investigation; it does not establish a cause.

Guided operating example · fictional Outlet A

Four steps, at your pace

HQ / MULTI-OUTLET JOURNEY
Concept workspace, not a product screenshot or customer result.
Read diagram details
  • Outlet A: Illustrative signal
  • Feedback + visits: Source references
  • Feedback + visits → Outlet A: observed at

Step 1 of 4

Notice one outlet exception

An illustrative change in repeat visits starts an investigation at Outlet A. It is a question to inspect, not a measured customer result.

What to check
Example: Outlet A · repeat-visit signal · source period to confirm.
What this establishes
Keep the signal attached to a named location.

Illustration of an investigation, not a live product workspace. No customer results, connected data or completed actions are shown.

Have an operating question of your own?

Request an HQ walkthrough

Follow the question across the business.

Location performance and supply-chain exceptions need different evidence. HQ’s application model is horizontal; the operating context is specific.

ILLUSTRATIVE EXPLAINER · 4 STEPS

Skip explainer
HQ / MULTI-OUTLET JOURNEY
Keep the signal attached to a named location.Concept workspace, not a product screenshot or customer result.
━ Source / typed relationship┄ Possible / requires review

From one outlet signal to an accountable decision.

  1. STEP 01

    Notice one outlet exception

    An illustrative change in repeat visits starts an investigation at Outlet A. It is a question to inspect, not a measured customer result.

    Keep the signal attached to a named location.

    Read diagram details
    • Outlet A: Illustrative signal
    • Feedback + visits: Source references
    • Feedback + visits → Outlet A: observed at

    Evidence / boundaryExample: Outlet A · repeat-visit signal · source period to confirm.

  2. STEP 02

    Choose an appropriate comparison

    Compare locations with compatible periods, services and definitions. A different operating mix can make an apparent difference misleading.

    The comparison set is part of the evidence.

    Read diagram details
    • Outlet A: Illustrative signal
    • Comparable outlets: Like-for-like scope
    • Feedback + visits: Source references
    • Outlet A → Comparable outlets: compare like-for-like
    • Feedback + visits → Outlet A: observed at

    Evidence / boundaryConfirm comparable location definitions and the time window.

  3. STEP 03

    Inspect the surrounding evidence

    Bring feedback themes, visits, service mix and staffing records into view. Co-occurring patterns do not establish what caused the change.

    Add context without assigning a cause.

    Read diagram details
    • Outlet A: Illustrative signal
    • Comparable outlets: Like-for-like scope
    • Feedback + visits: Source references
    • Service + staffing: Context, not a cause
    • Outlet A → Comparable outlets: comparison set
    • Feedback + visits → Outlet A: describes
    • Service + staffing → Comparable outlets: context only (possible, subject to review)

    Evidence / boundaryRetain record pointers, freshness and unresolved questions.

  4. STEP 04

    Name the reviewer and the next question

    An owner reviews the comparison and source evidence before choosing a supported next step. No external write or completed outcome is implied.

    A proposal remains a proposal until reviewed.

    Read diagram details
    • Outlet A: Illustrative signal
    • Comparable outlets: Like-for-like scope
    • Feedback + visits: Source references
    • Service + staffing: Context, not a cause
    • Decision owner: Review required
    • Outlet A → Comparable outlets: comparison set
    • Feedback + visits → Service + staffing: inspect together
    • Comparable outlets → Decision owner: review proposal (possible, subject to review)

    Evidence / boundaryConfirm the owner, permissions and supported workflow before action.

Concept workspace, not a product screenshot or customer result.

From a batch exception to an approval boundary.

  1. STEP 01

    Identify the delayed batch

    Start with an illustrative batch exception. Keep the batch identity explicit so later relationships can be checked against the same record.

    One exception, one traceable starting point.

    Read diagram details
    • Batch B-17: Illustrative delay

    Evidence / boundaryExample: Batch B-17 · schedule exception, not live output.

  2. STEP 02

    Connect inventory and order evidence

    A linked order is potentially exposed to the delay. The relationship warrants investigation; it does not prove that delivery will be missed.

    Distinguish a known link from a possible impact.

    Read diagram details
    • Batch B-17: Illustrative delay
    • ERP / MES record: Source + timestamp
    • Warehouse: Stock / allocation
    • Shipment: Delivery relationship
    • Linked orders: Potential exposure
    • ERP / MES record → Batch B-17: source reference
    • Batch B-17 → Warehouse: allocated to
    • Warehouse → Linked orders: may affect (possible, subject to review)
    • Shipment → Linked orders: linked delivery

    Evidence / boundarySolid: source relationship. Dashed: possible downstream impact.

  3. STEP 03

    Develop a response proposal

    Bring the evidence and possible order exposure to an operations owner. Replenishment or rescheduling options need a supported integration and an agreed approval gate.

    Context supports a decision; it does not authorize a write.

    Read diagram details
    • Batch B-17: Illustrative delay
    • Warehouse: Stock / allocation
    • Linked orders: Potential exposure
    • Decision owner: Review required
    • Batch B-17 → Warehouse: allocated to
    • Warehouse → Linked orders: may affect (possible, subject to review)
    • Linked orders → Decision owner: proposed response (possible, subject to review)

    Evidence / boundaryNo autonomous execution, regulatory readiness or replacement of ERP/MES/WMS is asserted.

  4. STEP 04

    Stop at the approval boundary

    Bring the evidence and possible order exposure to an operations owner. Replenishment or rescheduling options need a supported integration and an agreed approval gate.

    Context supports a decision; it does not authorize a write.

    Read diagram details
    • Batch B-17: Illustrative delay
    • Warehouse: Stock / allocation
    • Linked orders: Potential exposure
    • Shipment: Delivery relationship
    • Decision owner: Review required
    • Batch B-17 → Warehouse: allocated to
    • Warehouse → Linked orders: may affect (possible, subject to review)
    • Shipment → Decision owner: options for review (possible, subject to review)

    Evidence / boundaryNo autonomous execution, regulatory readiness or replacement of ERP/MES/WMS is asserted.

Concept workspace · external writes require supported integrations and review.

Why are similar locations diverging?

Review comparable periods, service mix, repeat visits and staffing context. Differences suggest questions to investigate, not an automatic explanation.

Explore the multi-location example

What could a batch exception affect?

Trace the proposed relationship between supplier records, stock movements and downstream orders within the sources available to the evaluation.

Explore Source-to-Sale context

A demonstration is a starting point.

Separate what you can explore here from what needs agreement for your deployment.

Demonstrated here
A fictional, manually guided investigation: notice a signal, compare records, inspect evidence and review a next step. This is an illustration, not a live connected HQ workspace.
Confirm deployment scope
Source coverage, metrics, investigation workflows, decision proposals and approval boundaries. Feasibility and implementation scope are agreed for the organization.
Planned extensions
Generalized autonomous execution, outcome follow-through and institutional learning. Historical replay and causal reasoning remain roadmap directions.

Start with one
operational problem.

The HQ Value Sprint

A scoped evaluation of how HQ could help your team investigate one measurable operating challenge. Begin with discovery, then agree the evidence, capabilities and evaluation criteria in writing.

  1. Choose one question

    Agree the operating problem, the decision owner and what a useful evaluation would establish.

  2. Check the evidence

    Review candidate records, definitions, access permissions and integration feasibility together.

  3. Evaluate the agreed scope

    Inspect the agreed capabilities against that question. Keep data gaps and limitations visible.

  4. Review the findings

    Document what was learned, what remains unresolved and whether a broader scope makes sense.

What we scope together

Candidate inputs
Relevant records or exports, location definitions, source periods and an agreed access route.
Your team
A decision owner, a source-system contact and permission to evaluate the agreed data.
Written deliverables
A question and success criteria, a feasibility assessment, evaluation findings and a next-step recommendation, as agreed in the proposal.

A clear boundary from the start.

No assumed connector coverage, production rollout or autonomous action. Timing, source refresh, capabilities and responsibilities are agreed following discovery.

Scoped proposal following discovery.

Discuss an HQ Value Sprint

Scope the evidence before the connection.

Start with the records you already have.

Transaction history, location definitions, staffing context and authorized feedback may help frame an investigation. The question determines the useful evidence.

Connection method, field coverage, mapping and refresh cadence require source-by-source assessment. A category in an example is not a confirmed connector.

Review data readinessRead common data questions

The application is horizontal. The context is specific.

Motif is the Graph Compiler foundation being developed. Domain packs supply business meaning; HQ is the application for working with that context.

THREE-PART MODEL / MOTIF
Illustrative architecture · Motif is a working name / design direction.
Read diagram details
  • Source record: ERP / CRM / POS
  • Business identity: References linked
  • Selected context: Meaning + evidence
  • Source record → Business identity: identifies
  • Business identity → Selected context: domain semantics

Sources, identities, relationships and evidence describe the proposed foundation. This conceptual model does not assert that every component is production-ready.

Read the Motif overviewExplore domain packsReview HQ pricing options

Make the deployment boundaries explicit.

Production and staging hosting

HQ production and staging are hosted in AWS us-east-1 (Northern Virginia, United States).

This identifies the production and staging hosting region. Confirm the locations and handling of backups, logs, AI processing and other subprocessors during technical discovery.

Agree the boundaries before rollout.

Review source permissions, data handling, operating responsibilities and the approval boundary for any supported action.

Review security and deployment

Bring one question. Find a useful first scope.

Tell us what changed, which systems hold the records and who owns the next decision. Include your time zone and preferred times if you would like a walkthrough.

Request an HQ walkthrough

An enquiry starts a conversation. It does not reserve a meeting.