StandupStandup
Seven tools in, one morning out

Open Standup.
Understand what matters.
Start building.

Your pull requests, issues, threads and meetings arrive from seven tools in seven shapes. Standup normalizes them into one stream of work events, then tells you which three deserve the next hour.

Under two minutes to your first ranked morning. Read-only, no setup meeting.

NormalizesGitHubLinearSlackCalendarJiraNotionTrello
today · tuesday

Two things are blocking other people. Everything else can wait until after your 14:00.

01
Review Auth OAuth flow · PR #42
Ana has waited 2 days. DEV-18 is blocked behind it.
github
02
DEV-18 mobile release is blocked
Sprint 1 ends Friday. Only your merge unblocks it.
linear
03
Connector retries thread needs your call
Rafa asked 4h ago. Two engineers paused on the answer.
slack

Not a dashboard. A decision about the next hour.

everything you already use

Your work is already everywhere. It just has no center.

Seven tools, each convinced it is the main one. Standup does not ask you to leave any of them — it pulls what happened into a single stream and gives the day a middle.

GitHub
Linear
SlSlack
Notion
Calendar
Jira
Trello
1,284 work eventsOne stream

01 · the primitive

Seven APIs. Seven vocabularies. One event.

A review request, a blocked issue, an unanswered thread and a meeting that eats your afternoon are the same kind of thing: something happened, and it may need you.

Standup normalizes every source into a single WorkEvent before any feature touches it.

1,284
events in a typical week
41
actually involve you
3
need you this morning
work-event.ts
type WorkEvent = {
  service: "github" | "slack" | "linear" | ...
  type: "pull_request.review_requested"
  title: "Review requested · Auth OAuth flow"
  actor: "Guilherme"
  source: "guibersi7/dev-os-orchestrator"
  priority: "high"
  metadata: { prNumber: 42, blocks: ["DEV-18"] }
}

02 · the first ninety seconds

Three answers, before your first coffee cools.

Every surface exists to answer one question. If a card cannot say why it is on your screen, it is not on your screen.

Ranked, with a reason

Never a wall of notifications. Three items, each carrying the sentence that justifies its position.

Review · Auth OAuth flow #42
Ana has waited 2 days. DEV-18 sits behind it.
Checks failing · retry-backoff #118
Your branch. Nobody else is touching it.

Blocked chains, end to end

The link between a stalled review and a slipping release lives across three tools. We draw it in one.

PR #42 · waiting on your review
DEV-18 · blocked 2 days
Mobile release · Friday

Ask, in plain language

Answers cite the events they came from. No summary you have to take on faith.

What slipped this week and why?
Two items. Both trace back to review latency on the connectors repo.
14 eventsDEV-18

03 · setup

Two minutes from authorize to answer.

20s

Authorize

OAuth in a popup. Read-only scopes, shown before you approve.

30s

Choose resources

Pick the repositories, projects or channels you actually work in.

40s

First sync

30 days of history pulled and translated into work events.

now

Value

Your queue re-ranks the moment the new source lands.

What Standup will never put on your screen.

Velocity and story-point charts

They measure estimation habits, not progress.

Developer leaderboards

Ranking people breaks the trust the product depends on.

A notification firehose

You already have six of those. This one has to be shorter.

Dashboards nobody acts on

If a number does not change a decision, it is decoration.

Sources from day zero.

gh

GitHub

Live

li

Linear

Next

sl

Slack

Next

ji

Jira

Queued

ca

Calendar

Queued

no

Notion

Queued

tr

Trello

Queued

Tomorrow morning, open one thing.

Understand what matters. Then start building.