Daily brief

The daily brief is your morning check-in: once a day 1mn writes a short, warm, first-person note — "Yesterday I worked on…" — recapping what happened on your Tasks board and folding in whatever business data you've connected. It's emailed to every workspace member and does nothing else — it never changes a campaign, touches your site, or draws a conclusion from the numbers.

It works with zero integrations: even a brand-new workspace gets a brief, because the core of it is a recap of your own Tasks board. Connecting revenue and advertising just adds a line or two.

Prerequisites

None are required — the brief always recaps your Tasks-board activity. Two optional connections enrich it, and each is folded in silently when present and omitted silently when absent:

• Revenue — Polar.sh adds a one-line revenue read (week-over-week).
• Advertising — a provisioned Meta ad account adds a one-line ad-spend read for yesterday. An account is provisioned the first time you add advertising budget; there's no separate connect step.

The brief never mentions a source that isn't connected — it just leaves that line out.

What it covers

Every brief is built from your Tasks board first, then enriched:

• Done yesterday — tickets that moved to completed or done in the trailing ~24 hours, described in the agent's own words. Routine runs (an SEO audit, a docs sync, and the like) are included but labeled as routines so you can tell them from tickets you filed.
• Waiting for your review — every ticket currently in awaiting review, so you know what's sitting on you. Each ticket with a number is deep-linked as TKT-<number> straight to /dashboard/tasks/<id>.
• Revenue (when Polar is connected) — one short line comparing the last 7 days to the prior 7 (week-over-week), in your Polar organization's currency, with orders when notable. With fewer than 14 days of data it states the latest revenue without a WoW figure.
• Ad spend (when a Meta ad account is provisioned and had spend yesterday) — one line with yesterday's spend plus results or link clicks, in the account's currency. No spend yesterday → the line is omitted entirely.

Every number is read straight from a tool's response — the brief never estimates, joins, or fabricates a figure. It's a check-in, not an analytics report: no tables, no channel mix, no funnels, no recommendations.

Voice

The brief reads like a diligent PM checking in, not a report generator:

• First person, warm, present tense. It opens with "Yesterday I worked on…" (or a close variant when literally nothing shipped).
• Short — a subject line plus a few sentences or tight bullets, with at most a couple of groupings.
• Honest. It never invents activity or numbers to fill space, and never calls out what's missing — a source that isn't connected is simply left out.

When it runs

The loop wakes once a day, at your workspace's delivery hour (set from Cadence), and always sends. A manually triggered run emails too. It doesn't re-check the hour or dedupe against an earlier brief — the daily wake is the only cadence gate.

Example

A brief for a day with real movement reads like this:

# Your 1mn brief — 2 shipped, 1 waiting on you

**Yesterday I worked on** getting two things over the line for you.

## ✅ Done yesterday
- Shipped the **pricing-page redesign** — [TKT-142](https://1mn.ai/dashboard/tasks/abc123)
- The **SEO routine** finished its weekly audit and filed the fixes

## 👀 Waiting for your review
- **New launch ad set** is drafted and ready to deploy — [TKT-145](https://1mn.ai/dashboard/tasks/def456)

## 💰 Business
Revenue was **$5,930 last week, up 9%** on 38 orders, and yesterday's ads spent
**$120 for 84 link clicks**. Nothing here needs a decision from you.

A quiet day is honest about it:

# Your 1mn brief — quiet day

Quiet day yesterday — nothing shipped and nothing waiting on you. I'll keep watch.

What you get back

• An email to every workspace member, sent via Resend as plain text plus light HTML. A small Markdown subset renders: #/## headings, - bullets, **bold**, and [text](url) links.
• A Telegram push of the same brief, automatically, when Telegram is connected.
• A report on your Tasks timeline — the brief is also emitted as a report artifact, so it's there whether or not you open the email.
• A saved record in the business_digest entity (headline, revenue, orders, WoW, MRR, and the note itself), while the underlying revenue and ad-spend trends stay visible on the dashboard's Business tab regardless of whether a brief ran.

Notes & limits

• Recommend-only. The brief observes and reports; it never changes a campaign, a budget, or your site, and never recommends a marketing move off revenue or spend alone.
• No analytics, traffic, or attribution. It doesn't read web analytics, doesn't join revenue to a source, and does no funnel or retention analysis. Product usage and errors live on the Users tab via the 1mn SDK; organic-search performance lives on the SEO tab via Search Console.
• Deep links need a ticket number. Routine runs without a TKT-<number> are mentioned but not linked.
• Delivery is best-effort. If email isn't configured on the server or your workspace has no member emails, the send is a silent no-op — the Telegram push and the timeline report still land.
• Set the delivery hour and how often it runs from Cadence.