Skip to content
Dash Help
XLinkedIn
Request early access

Set up your morning briefing

A morning briefing is the highest-leverage thing Dash does for a founder or operator. Instead of opening three dashboards before 9 AM, you open Slack and Dash has already DM’d you the read.

What goes in a good briefing

Section titled “What goes in a good briefing”

Pick the 4 to 6 numbers you actually care about, plus one or two flags. Less is more. A useful default for a SaaS team:

  • MRR, this month vs last
  • Pipeline, current value + delta from last week
  • Ad spend + CAC, last 7 days
  • Active trials, count + change
  • Flag: anything Dash thinks you’d want to see (stuck deals, churn risk, a metric that moved more than expected)

Trim or swap based on what your team runs on. An ecommerce team might want revenue + inventory days of cover. An agency might want billable hours + open scope.

Tell Dash what you want

Section titled “Tell Dash what you want”

In your DM with Dash, write the briefing description like a one-shot ask:

@Dash here’s the morning briefing I want, every weekday at 8 AM Eastern:

  1. MRR, this month vs last (from Stripe)
  2. Pipeline total + delta WoW (from HubSpot)
  3. Ad spend last 7 days, Google + Meta combined, with CAC
  4. Active trials count + change
  5. One flag: anything that moved more than usual

DM it to me. Skip weekends. Skip US holidays.

Dash will read this back, confirm the time, the recipients, the data sources, and ask if you want to test-run it once before scheduling. Say yes and you’ll get the briefing within a minute. Say schedule it and Dash will set the recurring job.

See the first one before it goes live

Section titled “See the first one before it goes live”

Always test-run the briefing once before scheduling. The first DM Dash sends will catch any wrong sources or weird formatting in a way that’s much harder to debug after it’s been running for a week. If something looks off, tell Dash and it’ll fix it. See Give Dash feedback so it improves for the practice.

Make changes later

Section titled “Make changes later”

The briefing isn’t locked. You can tell Dash:

@Dash drop the ad spend line from the morning briefing, replace it with a churn risk count.

@Dash move the morning briefing to 7:30 AM.

@Dash pause the morning briefing this week, I’m on PTO.

Dash will confirm the change and apply it to the next run.

Send it to the team, not just you

Section titled “Send it to the team, not just you”

A briefing can go to a channel instead of a DM. Just change the destination:

@Dash send this morning briefing to #leadership at 8 AM instead of DMing me.

Channel briefings count as a publish action, so Dash will ask for your approval on the first run before they start hitting the channel automatically. After approval, subsequent runs go through without re-asking unless the briefing’s content shape changes. See How approvals work for the details.

Common briefings teams set up

Section titled “Common briefings teams set up”
  • Founder briefing: MRR, pipeline, ad spend, active trials, one flag. DM only, weekdays 8 AM.
  • Sales briefing: pipeline by stage, top 5 stuck deals, AE call volume yesterday. Posted to #sales weekday mornings.
  • Growth briefing: ad performance Top 3 / Bottom 3, MQL count, blog traffic delta. Posted to #growth Monday and Thursday.
  • Ops briefing: open invoices over 30 days, support ticket backlog, new hire start dates this week. Posted to #ops Mondays.
  • Agency client briefing: per-client weekly report with branded header. Posted to each client channel Mondays.

What’s next

Section titled “What’s next”