Skip to content
Signal Grid

Manifesto Nº01 — for whoever holds the pager tonight

AI incident triage · concept

The pager should bring you a story, not a siren.

Signal Grid is a fictional triage layer for on-call teams. It reads the alerts, gathers what changed and hands the responder a short account of the incident, so the first minutes go on fixing rather than searching.

  1. 01Group the noise before it reaches a human.
  2. 02Show what changed, where, and who owns it.
  3. 03Draft the next step. Let the engineer decide.

Signed — the Signal Grid team (fictional)

What changes

01 — Before / with

What changes when the pager has context.

The same incident, handled two ways. Signal Grid does not fix anything on its own: it prepares the ground so the person on call can.

  1. 01Alert intake

    BeforeEvery alert pages someone, duplicates and echoes included.

    With Signal GridRelated alerts are grouped into one incident before anyone is paged.

  2. 02The first minutes

    BeforeOpen a row of dashboards to work out what is actually broken.

    With Signal GridA short triage summary: affected services, recent changes, likely owners.

  3. 03Ownership

    BeforeGuess who owns the failing service from an old wiki page.

    With Signal GridRouting follows your service catalogue and on-call schedule.

  4. 04Runbooks

    BeforeSearch for the runbook and hope it is still current.

    With Signal GridRelevant steps drafted inline, marked as suggestions for a person to approve.

  5. 05Handoff

    BeforeContext lives in one tired head and a very long chat thread.

    With Signal GridA running timeline the next responder can read before taking over.

  6. 06Review

    BeforeRebuild the timeline from memory for the post-incident review.

    With Signal GridTimeline, decisions and changes exported as a review draft.

02 — Sample pricing

Priced per responder, not per alert.

Billing

Updates the sample estimates on each plan.

Sample pricing for a fictional product. Nothing is for sale.

Shift

$20/ responder / month

Sample · 8 responders = $1,920 billed yearly

For a single rotation that wants calmer nights.

  • Alert grouping into incidents
  • Triage summary on every page
  • Incident timeline
  • Chat and email notifications
Compare tiers

Rotation

Recommended

$36/ responder / month

Sample · 8 responders = $3,456 billed yearly

For teams with several services and handoffs between shifts.

  • Everything in Shift
  • Change context from deploys
  • Runbook drafts for approval
  • Shift handoff summaries
  • Post-incident review drafts
Request a walkthrough

Command

Custompriced with you

Sample tier · no published price

For organisations running many rotations and a review practice.

  • Everything in Rotation
  • Cross-team escalation policies
  • Custom retention settings
  • Single sign-on
  • A named contact for rollout
Ask about Command

Compare tiers

What is in each plan.

The tiers differ in how much of the incident they help coordinate. Shift handles the page; Rotation handles the handoff; Command handles many teams at once. Limits shown are samples.

Features included in each sample Signal Grid plan
FeatureShiftRotationCommand
Triage
Alert grouping into incidentsIncludedIncludedIncluded
Triage summary on each pageIncludedIncludedIncluded
Change context from deploysNot includedIncludedIncluded
Runbook drafts for approvalNot includedIncludedIncluded
Coordination
Incident timelineIncludedIncludedIncluded
Shift handoff summariesNot includedIncludedIncluded
Post-incident review draftsNot includedIncludedIncluded
Cross-team escalation policiesNot includedNot includedIncluded
Administration
Rotations1Up to 10Unlimited
Timeline retention (sample)30 days1 yearConfigurable
Single sign-onNot includedNot includedIncluded
Named rollout contactNot includedNot includedIncluded

03 — Questions

Asked before the first page.

  • Is Signal Grid a real product?

    No. Signal Grid is a fictional brand, and this is a landing page example designed and built by CraftLayer Studio. There is no product, trial or sales team behind it.

  • Does it fix incidents on its own?

    Not in this concept. It groups alerts, gathers context and drafts suggested steps. Every action that touches a system is left for a person on call to approve and run.

  • What does it connect to?

    The concept assumes the usual on-call sources: alerting, metrics, logs, deploy history, a service catalogue and team chat. No specific vendors are implied.

  • How does it decide what is related?

    It looks at timing, the services involved and recent changes, then shows its reasoning next to the grouping so responders can split or merge incidents themselves.

  • Are the prices real?

    No. Every price, limit and discount on this page is a sample used to show how a three-tier plan and comparison table can be laid out.

  • Can our team get a walkthrough?

    Not of Signal Grid, since it does not exist. If you want a page like this for a real product, CraftLayer Studio is linked in the footer.

Concept demo · nothing is sent

Make the next page arrive with context.

Request a walkthrough

walkthrough@example.com is a fictional address. No one will reply.