The morning brief, built in ten minutes

Most founders start the day the same way: fifteen minutes of tab-hopping to reconstruct what happened overnight, project tool, inbox, calendar, and a nagging feeling something slipped anyway. This is a walkthrough of replacing that with a routine Binee runs for you. Four pieces, about ten minutes to set up, all in plain sentences. Prerequisite: you have connected your tools in Settings, then Integrations, at minimum your email, calendar, and project tool.

Piece 1: the 8:00 scheduled report

A scheduled automation runs daily at a time you choose and delivers a report. Open the Automations page, press New automation, and pick the trigger "On a schedule" (or just tell Binee Assistant what you want; both roads end at the same confirmation). Set the time to 8:00 and write the instruction the way you would brief a chief of staff:

"Every morning, give me my priorities: today's meetings and what I should prepare for each, tasks that are overdue or slipped overnight, and any client emails still waiting on a reply from me."

That wording is the configuration. The report folds your day's meetings in alongside what arrived overnight, so the calendar and the inbox and the project tool stop being three separate morning chores. It lands in your Inbox like any insight, is emailed at your set time, and can also post to Slack, your private Binee channel or a shared one you pick under Deliver to. One honest detail worth knowing: a report that genuinely finds nothing is emailed only, so your Inbox never fills with daily "nothing to report" cards.

If you want the leadership channel to get a version too, point a second scheduled automation at a shared Slack channel. Delivery to a shared channel is what makes an automation a team automation; everyone in the channel sees it.

Piece 2: pre-meeting briefs, on demand

Briefs before calls are not an automation; they are a chat habit, and the habit is one message long. From the web app or, more usefully, a Slack DM to Binee five minutes before a call:

"Prep me for my 2pm with Acme."

Binee lines the meeting up with everything else it knows about Acme: the project status, the open email threads and what was last promised in them, and recent meeting commitments where you have a recording tool connected. You walk in knowing that the deliverable they will ask about slipped two days, and that your teammate already flagged it by email yesterday, which is a briefing no calendar alone could give you. The Slack DM matters more than it sounds: you are usually not at the app when the reminder pops, and Binee answers in Slack from the same brain, your own connections included.

Piece 3: the promise-keeper watcher

Now the always-on part. Watcher automations react to incoming activity in your connected tools. The first one to build is the founder classic:

"Warn me when a task delay breaks a date we promised a client by email."

Read that sentence again as a systems problem. Your project tool knows the task slipped. Your inbox knows the date was promised. Neither knows about the other, so this is precisely the failure that gets caught by a client instead of by you. As a Binee automation, it is one sentence in the builder under "What should Binee watch for and tell you about?". When it fires, the insight cites the actual events, the task change and the email with the promise, so you act on evidence, not a hunch. You can test a watcher against your recent activity before saving it, which is worth doing on this one to see the shape of a finding.

Mark this automation urgent. The urgent flag routes it through your urgent notification channels and also speeds up checking: urgent automations get new email checked the moment it arrives where your provider supports instant notifications, while regular automations catch up on the next 15-minute pass. A broken client promise qualifies.

Piece 4: the unhappy-client watcher, with an action step

The second watcher covers the mornings you skim too fast:

"Warn me when a client email sounds unhappy, and open a ClickUp task for it."

The first half is judgment no rule engine can express: unhappy is a tone, not a field. The second half is an action step, "Then Binee does". Binee turns your text into clearly worded action items you review, and saving shows a popup naming exactly what Binee may do; nothing acts until you allow it, and actions run only on your own connections. From then on, when the automation fires, the insight tells you what it found and carries a "What Binee did" line, and the ClickUp task is already sitting in your list, so the follow-up exists even on a morning you only read headlines.

What the routine costs and how it behaves

Watching is free; you pay per investigation. Each firing costs a flat 1.3 credits, a completed action adds 1 credit, and your daily budget, 50 paid firings by default, caps a wild day. Realistically, this whole routine is the daily report plus a handful of watcher firings a week.

Two closing habits make it compound. First, feedback: when a finding is not useful, say so with the reason. Mark two "task slightly delayed" findings as not urgent and that automation stops flagging small slips while still catching the delay that breaks a promised date. Second, iterate from chat: "change my morning report to also include overdue invoices" stages a confirmation card, and the automation updates. The routine you build in ten minutes is the worst version of it you will ever have.