Use Case

Founder brief on demand today — scheduled to your Slack DM once the morning DM ships (in development).

These pages exist for real buying and rollout decisions, not generic demo traffic. Each one states the pain, the workflow, the outputs, the commercial fit, and the self-host versus Cloud tradeoff explicitly.

Pain

Founders lose time reconstructing priorities, chasing context, and checking multiple channels before responding or deciding.

Workflow

Run slack_find_decisions and slack_channel_summary over your founder + product + ops channels for an on-demand brief. The scheduled morning catch-up DM (Pro/Team — in development) will land the same brief at 8am workspace time once it ships.

Signals this page is relevant

  • Important decisions are getting buried across founder, product, and support channels
  • You regularly need a same-day brief before replying or deciding
  • You'd benefit from a structured morning DM that lands before you open Slack manually

Repeatable workflow steps

  • Pick your founder + product + ops channels.
  • Run slack_find_decisions + slack_channel_summary for the last 24 hours — a structured brief on demand.
  • When the scheduled morning DM ships (in development), the brief lands at 8am workspace time automatically. Decide; don't archaeologize.

Named outputs

  • On-demand founder brief (daily 8am DM in development)
  • Decisions + asks + action items
  • Risks + open questions surfaced
  • Workflow profile: exec_brief
  • Target brief shape: exec_brief target shape: {summary, decisions, risks, asks, action_items}
  • Claude-first, Gemini CLI supported

What good looks like

  • A founder starts the day with one structured brief in their DM instead of channel hopping.
  • Decisions are explicit and reusable by an operator or EA.
  • Once the scheduled DM ships (in development), the workflow runs every morning automatically — no asking required. Today, run slack_channel_summary at the same time every morning for the same shape.

Prompt starter

Use this as the initial request in Claude or Gemini CLI after the endpoint is connected.

Run slack_find_decisions and slack_channel_summary on my exec channels for the last 24 hours.

Anonymized example output

Summary: current state compressed for the next operator. Action items: owner + deadline when available. Decisions: commitments already made in Slack. Handoff: what the next person needs before they open the raw channel.

Plan fit

Pro at $19/mo is the fit — unlimited AI calls today, and the scheduled morning catch-up DM (in development) is the lever that turns it into a daily founder habit.

Self-host vs Cloud

Self-host if you want to define exec_brief profiles locally and don't need the AI brain. Pro is the fit when the daily brief becomes a habit you depend on.

Premium fit

Pro at $19/mo gives you unlimited AI tools today; the scheduled morning DM is in development and is the lever that makes it a daily habit. Until then, Pro buys unlimited calls and permanent OAuth.

Trust and buyer review

  • Use /status for the live hosted status contract.
  • Use the Ops engagement page for SLA, custom retention, or SOC2 questions.
  • Use the security page for buyer-facing controls, storage, and analytics disclosure.
  • Use official vs managed when the team is still deciding between Slack's official path and the managed commercial path.
Security Ops engagement Official vs managed