For product and engineering teams

Standups your team reads in four minutes, not thirty

Everyone writes a two-minute check-in when it suits them. Tidewell sends one digest at 9:30 with blockers first, so the meeting only happens when something needs a decision.

Free for teams of up to 8. No card needed.

Platform team digest

Tue, 14 Oct · 6 of 7 checked in · 2 blockers

Blocked

Maya Okafor

Blocked

Billing webhook retries need a decision on idempotency keys before I can merge.

Lena Kraus

Blocked

Waiting on staging DB credentials from IT, ticket opened Monday.

Moving

Diego Ramos

Shipped the new rate limiter to 10% of traffic. p95 is flat.

Jun Park

Migrated 41 of 52 cron jobs to the queue. Rest by Thursday.

4 min

Median digest read

3.2 h

Meetings cut weekly

91%

Check-ins on time

How it works

Write it once, read it once, meet only when it matters

  • Before the digest

    Everyone checks in when it suits them

    Three prompts take two minutes: what moved, what is next and what is in the way. A single reminder goes out 30 minutes before the digest, and only to people who have not written yet.

    Your check-in

    Due 09:30

    What moved

    Shipped the rate limiter to 10% of traffic. p95 flat.

    What is next

    Roll out to 50% and add the dashboard alert.

    What is in the way

    Need sign-off on the retry budget from Maya.

  • As soon as it is written

    Blockers go straight to the person who can fix them

    Mark an item blocked and Tidewell pings its owner directly, with the context attached. If it sits for a day, it moves to the top of the team lead's digest.

    Blocker raised

    2 min ago

    Diego Ramos

    Blocked

    Need sign-off on the retry budget before the 50% rollout.

    Sent to Maya Okafor, owner of billing-service

    now

    Maya opened it with the context attached

    +3 min

    Moves to the lead's digest if still open

    +24 h

  • Every morning

    One digest per team, in everyone's own morning

    Each team picks a time. The digest lands at that hour in each person's time zone and skips weekends and public holidays.

    Digest schedule

    Mon–Fri

    Platform

    7 people · Lisbon

    09:30

    Growth

    5 people · New York

    09:00

    Mobile

    6 people · Berlin

    10:00

Product

The details that make the habit stick

Five things teams ask for in the first month, already built in.

Shipped the rate limiter to 10% of traffic

PR #482

Merged

Roll out to 50% and add the dashboard alert

ENG-211

In review

Retry budget needs sign-off

ENG-198

Blocked

Linked to the work

Paste a pull request or ticket link and its status shows inline, so nobody re-types what the tracker knows.

idempotency keys

Maya, 12 Sep

Decided on idempotency keys per webhook

Lena, 3 Oct

Retries wait on the keys decision

Search every update

Find who worked on what, across months of check-ins, from one box.

Your history

Visible to you only

Private by default

People see their own history. Leads see the team digest, never an activity log.

Check in from anywhere

Web, desktop, email or chat. It all lands in one digest.

Reminder to 2 people

09:00

Digest sent to the team

09:30

One reminder, only if needed

A single nudge 30 minutes before the digest, and only to people who have not written.

“Six of us across four time zones joined a 9am call for updates nobody remembered. Now the digest is waiting when I open my laptop, and we meet twice a week to decide things.”

Priya Nair

Engineering manager, Northbeam

FAQ

Questions teams ask before switching

Something else on your mind? Write to us and a person replies within one business day.

No. It replaces the status round. Teams usually keep a short weekly planning meeting and use the digest to decide when else to meet.

Send your first digest tomorrow morning

Free for teams of up to 8, with no time limit. Upgrade when you add a ninth person.