Partner walkthrough.
A step-by-step demo script.

1. 1

   Phase 1

   Open with the live signal

   Goal

   Show the partner that Streamwake’s signal is real-time, second-resolution, and theirs — not a synthetic demo.

   Actions

   1. 1Open the agents dashboard in your shared browser.
   2. 2Filter to the partner’s sandbox account and the test stream you registered.
   3. 3Trigger a synthetic playback stall in the demo viewer (pause network for 8 seconds).

   What to say · what to listen for

   • Say: “Every row on this chart is a probe that ran on the actual player event — not a canned dataset.”
   • Listen for: “How fast does this update?” — the answer is the second-resolution refresh you can see on the chart.
   • If the partner asks about scale: pivot to per-probe cost on the Scale plan, not platform-scale abstractions.

   Observable at the end of this phase

   ›A rebuffer ratio ticks up on the chart while the network is paused, and the anomaly class surfaces in the right rail within one second of the stall clearing
2. 2

   Phase 2

   Walk the data plane, hop by hop

   Goal

   Make the wire format tangible — the partner should leave with a mental model of the five hops and which ones they own.

   Actions

   1. 1Switch to the API reference page (/docs/api-reference).
   2. 2Walk the five hops: player → SDK → telemetry endpoint → agents dashboard → stream registration.
   3. 3Highlight the two auth models: bearer (telemetry) vs cookie session (stream registration, agent reads).

   What to say · what to listen for

   • Say: “You own hops one and three; we own hops two, four, and five. The boundary is the bearer key.”
   • Listen for: “Do we need your SDK?” — answer: no, the REST surface stands on its own; SDK is the faster path when you control the player.
   • If the partner pushes on field drift: reference /docs/api-reference as the single source of truth.

   Observable at the end of this phase

   ›Partner can name the two auth models and the five hops from memory

   ›They have the API reference URL written down
3. 3

   Phase 3

   Surface the MTTR story

   Goal

   Translate the technical signal into a support-team outcome the partner can champion internally.

   Actions

   1. 1Trigger an alert in the demo viewer by exceeding the 3-second rebuffer threshold.
   2. 2Open the incidents panel and walk the audit trail: probe timestamp, anomaly class, agent classification.
   3. 3Compare to the partner’s current incident triage loop (time-to-first-signal, time-to-classify).

   What to say · what to listen for

   • Say: “The first signal here is the probe — not the customer ticket. Your support team reads the trail instead of reproducing.”
   • Listen for: “What does the audit trail look like in our environment?” — walk them through the export endpoint.
   • If the partner asks about post-mortems: the trail makes post-mortems write themselves; specific format lives at /docs/api-reference.

   Observable at the end of this phase

   ›A classified anomaly with an agent-attributed root cause appears in the right rail within 30 seconds of the threshold breach

   ›The incidents panel shows the full probe-to-classification trail
4. 4

   Phase 4

   Land the commercial shape

   Goal

   Make the revenue-share and co-marketing rhythm concrete enough that the partner can take it to their CFO.

   Actions

   1. 1Switch to the partner program page (/partners/streaming).
   2. 2Walk the three co-commercial axes: revenue-share on self-serve and Scale, co-marketing on blog + changelog, co-sell on enterprise.
   3. 3Reference the five-step onboarding cadence: apply → discovery → sandbox → build → co-launch.

   What to say · what to listen for

   • Say: “Specific percentages are scoped during the discovery call below. This page stays informational — we don’t publish standard numbers.”
   • Listen for: “How long until we go live?” — answer: a few weeks, not months; the cadence is visible end-to-end.
   • If the partner asks about launch control: the bearer key works against the dev sandbox from day one, so your integration ships on your schedule.

   Observable at the end of this phase

   ›Partner has the apply form URL and the partner-team email written down

   ›They can name the five-step onboarding cadence from memory
5. 5

   Phase 5

   Close on the next action

   Goal

   End the call with a single, concrete action the partner can take this week — not “let’s circle back next quarter.”

   Actions

   1. 1Ask the partner to send one engineer through the SDK quickstart before the next call.
   2. 2Confirm the next-step slot on the calendar before you hang up.
   3. 3Send the partner-team intro email within two hours of the call ending.

   What to say · what to listen for

   • Say: “The single thing that unblocks us both is one of your engineers running through the SDK quickstart this week. That’s the action item.”
   • Listen for: “We need to loop in our security team” — offer the security page (/security) and a security-team direct line.
   • If the partner demurs on the next step: ask what would have to be true for them to say yes — then book the follow-up around that.

   Observable at the end of this phase

   ›A next-step slot is on the calendar before the call ends

   ›The partner-team intro email is drafted, ready to send within the two-hour reply window

Adjacent pages on the partner program.