For the Chief of Staff who currently spends 45 minutes every morning sifting email, news, and a stack of dashboards to compile what the principal needs to know. Bureau replaces that. By 6 AM, every day.
Mark, Chief of Staff to a public-company CEO, used to spend 7-to-7:45 AM every weekday building a brief: Gmail from key senders, the calendar for today and tomorrow, the deal-pipeline status webhooks, the customer-incident feed. Three weeks after switching to Bureau he stopped doing that.
Now Bureau pulls Mark's sources at 5:30, hands them to a briefer LLM, then to a scriptwriter, then to two co-host journalists' voices. By 6:08 AM the episode is in two tokenized podcast feeds — one for the CEO, one for the COO. Mark gets back 3.75 hours a week.
Add OAuth integrations from Desk in two clicks. POST any custom system to the universal webhook source — no plugin marketplace, no developer needed.
Important senders, last-N-hours filter, label-scoped reads. OAuth, refresh-handled.
Today + tomorrow + same time next week. Surfaces conflicts and prep windows.
POST /v1/sources/{slug}/ingest. Anything that can POST JSON — a CRM, a status page, a custom cron — becomes a beat. No code on our side.
Public news, vendor blogs, regulator feeds, daily web-search briefs. Same as the Operator tier sources.
Post JSON, get a beat. Your CRM custom-deal-stage-update webhook, your portfolio P&L cron, your status-page event stream — anything that can fire an HTTP request becomes a Bureau source with no code on our side.
POST https://api.bureau.news/v1/sources/acme-deals/ingest
Authorization: Bearer bureau_src_a1b2...
Content-Type: application/json
{
"items": [
{
"title": "Acme Industries moved to Closed-Won",
"summary": "$240k ARR · 3-year term · CRO sponsor",
"url": "https://your-crm.example.com/deals/12345",
"metadata": {"stage": "closed_won", "amount": 240000}
}
]
}
When sources land, the briefer LLM produces a 1-2 paragraph summary in the segment's beat shape. The brief gets stored. The raw payload (your colleague's email body, the webhook JSON, the calendar attendee list) is dropped after the brief is composed — unless your tenant explicitly opts into payload retention per source.
last_listened_at