Mission Control

Analytics

Last 30 days. The primary outcome is held ICP calls; traffic stays below the funnel so it cannot obscure conversion.

Outbound to held call

Build an ICP list, publish proof, run controlled outreach and trace held calls back to the touch that caused them.

Funnel to held ICP calls

Read top to bottom. Everything above the last row exists to produce the last row.
  • 0

    Touches out

    Published posts, newsletters, messages and other recorded outbound touches.

  • 1

    Clicks

    Only clicks on links minted through /r/<slug> are visible here.

  • 0

    Replies

    Inbound replies and DMs, not clicks.

  • 0

    Booked

    Calls on the calendar.

  • 0

    Held

    Calls that actually happened.

  • 0

    Held with an ICP-fit contact

    The north-star metric. Everything above exists to produce this row.

100% of held ICP calls trace back to a touch.

By angle

Which argument produced held ICP calls. Use this to set next week's content and outreach plan.
AngleTouches outHeld, ICP fit
the commercial case for narrowing scope11

Search Console opportunity finder

Turn search demand into proof-led angles that can support outbound and organic discovery.

No Search Console snapshots yet

Attach a Search Console rail account with the site URL in its external reference, then run a snapshot. Nothing is queried live — the screens read stored rows.
Rail accounts

Traffic

Traffic is supporting evidence. Held ICP calls remain the outcome that decides whether the funnel works.

No GA4 snapshots yet

Attach a GA4 rail account with the property id in its external reference, then run a snapshot.
Rail accounts

Everything here reads stored snapshots. Nothing re-queries Google on render, which is why the page is fast and why history survives a credential expiring. The health strip shows whether the nightly job is still running.

Jump to

Search brands, flows, people and control panel sections