GTM Flight Recorder

Public demo · read-only

Operating company: RelayBridge (fictional)

Observability for automated revenue decisions

See why an automated decision was made, and what newer rules would have done.

Flight Recorder keeps the evidence and the exact rules behind automated account-prioritization decisions, so the person who owns that workflow can inspect a past decision and replay it under different rules without rewriting history.

For GTM engineers, technical RevOps operators and revenue-systems owners responsible for automated prioritization logic.

Three questions the demo answers

Each answer below is read from the demo's own synthetic data on this request, and each links into the page that shows it in full.

  1. Why was this account prioritized?

    NovaSignal AI scored 86 against a threshold of 75 under rules v3.2, so the output was PRIORITIZE.

    Open the recorded decision

  2. What was available but ignored?

    head_of_platform_start_date was recorded as 2026-03-05. It was available at the decision boundary, but the rules did not use it: its recorded state is available but ignored.

    verified_integration_pressure was recorded as LOW. It was available at the decision boundary, but the rules did not use it: its recorded state is available but ignored.

    website_intent was explicitly unavailable, which is a different thing: the system did not have it.

    See the preserved context

  3. Would newer rules decide the same?

    Replayed under v5.2 on the same preserved evidence, the score is 72 against threshold 75: DO_NOT_PRIORITIZE. The recorded decision stays 86, PRIORITIZE.

    That second result is a counterfactual: computed on demand for this request, never stored, exactly as on the decision page. No present-day evidence entered it.

    Open the replay comparison

How it works

  1. Record. Each decision enters through one collector with the evidence it could see and the exact rules it ran.
  2. Preserve. That context is kept exactly as it was at the decision boundary. Later evidence never rewrites it.
  3. Replay. The same preserved context is evaluated under other rules, and the two results are compared side by side.

The walkthrough

Elias Skora walks through one decision: its preserved evidence, the rules it ran, and a replay under newer rules.

Download the video · The video file is served from media.flight-recorder.app.

Contact

Sending goes through Web3Forms, which processes and keeps your name, email and message under its own terms; this site does not receive or store it.

What this is, and is not

Every account, event and outcome here is synthetic; RelayBridge and its prospects are fictional. The demo is read-only. No real customers, live integrations or results are claimed. The project fully replays one decision class, account prioritization, deterministically, on synthetic data.

How it was built · Source code