Know

Always know what's happening

Progress turns your team's activity into a clear picture of what actually happened — an executive-ready recap on your schedule, a forward-looking briefing every morning, and meeting notes that become decisions and action items.

Connected to your stack

Every tool your work lives in.

Progress plugs into the tools your team already uses and turns that activity into one clear picture of what's happening — no extra busywork.

Slack

Slack

Channels, threads & messages.

Teams

Teams

Channels, chats & calls.

Linear

Linear

Issues, projects & status.

GitHub

GitHub

Commits, PRs & reviews.

Asana

Asana

Tasks & project updates.

Figma

Figma

Design files & comments.

Notion

Notion

Docs & page updates.

Meetings

Transcripts & notes from every meeting.

MCP

Ask Progress from any AI assistant.

More coming

Jira, Bitbucket, Trello & more.


What's happening?

Scheduled Summary

A complete, executive-ready narrative of your team's day, generated on your schedule. If you only check once, start here. A briefing to read, not a feed to scroll.

  • The narrative

    What actually happened across the team, in plain English. The threads that mattered, explained like a person would.

  • Completions & decisions

    What shipped and what got decided, with people and tickets attached, including binding commitments from standups.

  • Risks & signals

    What's quietly building before it bites: broken attribution, fixes not yet shipped, dependency chains, validation still pending.

  • Recognition & radar

    Who drove what by real contribution, plus progress against the specific items you're personally tracking.

What this looks like in Progress
Summary for Wed, Jan 7

Generated 1 hour ago from 247 activities

Narrative Overview

The day centered on launch-readiness for payments and getting the new embeddable checkout closer to production, with heavy coordination across Slack, Linear, and GitHub. The team shipped concrete reliability fixes — failed-payment recording and Apple Pay behavior — and merged several design updates into main. By end of day the plan tightened: DEV-391 became the single launch gate, and parallel work was consolidated to cut thrash.

Notable Completions & Wins

Shipped code (merged to main)

  • Sarah merged PR #461DEV-410 — records customers from failed payments
  • Mike merged the Apple Pay batch #458#462 tied to DEV-345
  • Emily merged the rebrand pages #451#455 into main

Linear completions

  • DEV-412Removed redundant DB transaction wrapping
  • DEV-408Spreedly re-init for express checkout
  • DEV-419Loading state to prevent double CTA clicks

Marketing wins

  • Chris shipped the pricing-page refresh — sign-up CTR up 12%
  • Launch FAQ drafted and queued for review

Key Decisions & Meeting Outcomes

Decisions made

  • Make DEV-391 (embeddables) the single launch gate
  • Move the launch to Jan 8 to allow a full QA pass
  • Consolidate Apple Pay work into #391; #337 retired

Action items

Action item Owner
HighFinalize payment-flow error handling Sarah
MedRefresh staging config for the new gateway Emily
NormalSchedule checkout design review Mike

Key discussions

  • Mobile performance regressions on product pages
  • Whether to A/B test the new pricing page

Quantitative Snapshot

247

Total activities

18

Completions

By source: Slack (92), GitHub (78), Linear (57), Meeting notes (20)

Top contributors: Sarah (79), Mike (61), Emily (40), Chris (12)

Risks & Signals Worth Watching

  • Launch-critical work concentrated on #391 — single point of dependency
  • Recurring merge conflicts on staging as rebrand pages land
  • New urgent DEV-414: $4.95 charge in free-trial flows

Individual Recognition

  • Sarah drove the most throughput (79 activities), merging 5 high-impact PRs
  • Mike pushed Apple Pay forward (61 activities), now owner of DEV-391
  • Emily kept launch readiness moving, creating DEV-412, 419, 421
Scroll

How should I start the day?

Morning Briefing

Start every day with full context.

A forward-looking overview generated each morning that recaps yesterday, surfaces week-over-week trends, and highlights watch items for the day.

  • Yesterday, distilled

    Where things landed by end of day, condensed to what carries into this morning. The threads that moved, what shipped, what shifted in priority… so you start with context, not a cold catch-up.

  • Week-over-week trends

    How this week compares to last: merge rate, blocker load, momentum, team vibe, change pressure. The direction you're moving, not just today's snapshot.

  • Watch items for today

    What's likely to need you before it turns urgent. The report awaiting QA, the staging work that needs closure, the dependency about to drift. Flagged while there's still time to act.

What this looks like in Progress
Morning Briefing2 hours ago

Your daily overview for Tue, Jun 2

Yesterday Recap

Yesterday shifted from coordination into shipping. Sarah merged the first pass at Braintree (DEV-965) and moved it into staging testing, while Chris shipped the partner-split registration report (DEV-968). The Apple Pay rage-click issue was confirmed resolved — 85 activities and 2 completions on the day, concentrated on payments reliability.

Week-Over-Week Trends

Momentum: mixed but improving — accelerating again at week's end.
Vibe:caution all week — uneven load and late-hours strain.
Change pressure: frequently elevated around payments and funnel work.

Watch Items for Today

  • QA and promote the partner-split report (DEV-968) — merged to staging, needs a production pass.
  • Close out Braintree staging testing — confirm flows, capture edge cases, and decide what's ready to promote.
  • Scope the payment-failure reporting ask (DEV-966) before it stays "important but undefined."
Scroll

What was decided?

Meeting Notes

Turn meeting transcripts into action.

Paste your meeting notes or transcripts, and AI instantly extracts action items, decisions, and key discussion points.

  • Joins your calls, or takes your paste

    Add Progress to Zoom, Google Meet, or Teams and it captures the meeting for you. No call to record? Paste the transcript or your raw notes and it works the same way.

  • Action items, with owners

    Every commitment pulled out and assigned: who's doing what, by when, ranked by priority. The decisions that turn into work, captured before they get forgotten.

  • Decisions and discussion, on the record

    What got decided and why, plus the topics raised but not resolved. The meeting becomes a searchable record, and it all flows into your activity stream automatically.

What this looks like in Progress
Parsed Meeting Output

Sprint Planning - Jan 6, 2025

Action Items

High
Finalize payment flow error handling before launch — Mark
Medium
Update staging environment with new config — Garrett
Normal
Schedule design review for checkout redesign — Harold

Decisions

Launch target moved to Jan 8 to allow full QA pass
Deprecate legacy checkout path after launch

Discussion Topics

Mobile performance regressions on product pages
Whether to add A/B testing for new pricing page
DEV-391
DEV-287
Scroll

Start your 7-day free trial

Try it on this week's work.

Connect your tools and Progress fills in your last two weeks, so you see what's moving and what's stuck from day one.

7-day free trial · cancel anytime