standupai
Start free

Documentation

StandupAI docs

Practical setup notes for async standups, integrations, notifications, billing, and API access.

Getting started

Quick start guide

Create an account, choose your workspace, and review the first generated standup.

Start setup
  • Start from signup and create or join your workspace.
  • Connect one source of work activity before inviting the full team.
  • Review the generated draft before anything is sent to the team digest.

Invite team members

Bring in developers and managers after the workspace defaults are set.

Open demo workspace
  • Invite only the people who participate in standup or review the digest.
  • Managers can review team summaries without changing developer drafts.
  • New members can submit manually until their integrations are connected.

Connect your first integration

Start with GitHub, Linear, Jira, or Slack so drafts have useful source context.

See integrations
  • Use one integration first to validate the workflow.
  • StandupAI keeps source labels attached so developers can verify the draft.
  • Add additional integrations once the team trusts the daily review loop.

Submit a standup

Edit the draft, add missing context, and send it when it sounds like you.

Try the demo
  • The draft is never the final word until the developer reviews it.
  • Blockers should stay plain and specific.
  • Managers receive the team digest after updates are submitted.

Integrations

GitHub setup

Use pull requests, reviews, and merged work as source signals for the standup draft.

  • Connect the GitHub workspace from integration settings.
  • Start with repositories owned by the active engineering team.
  • Review generated summaries for source accuracy before rollout.

Linear OAuth

Use issue movement, comments, and blockers as planning context.

  • Authorize the Linear workspace from settings.
  • Map active teams to the StandupAI workspace.
  • Keep issue titles clear, since they appear in draft source labels.

Jira setup

Bring sprint and ticket movement into the same daily review flow.

  • Connect Jira after the workspace exists.
  • Limit access to the projects your standup team actually uses.
  • Use Jira status changes as context, not individual productivity scores.

Slack workspace install

Use channel context and blocker threads without turning Slack into another standup bot.

  • Connect Slack only for the channels that carry work updates.
  • Keep digest channels visible to managers and team leads.
  • Avoid private-message scraping. Shared team context is the trust boundary.

Notifications

Reminder schedule

Set one daily reminder window that fits the team rhythm.

  • Use a single morning reminder for most teams.
  • Avoid repeated pings unless the team explicitly asks for them.
  • Let developers submit before the reminder if their draft is ready.

Manager digest emails

Give managers a compact summary after the team has reviewed updates.

  • Digest content should focus on blockers, decisions, and progress.
  • Do not frame the digest as surveillance or productivity scoring.
  • Keep individual source links available for review.

Slack notifications

Send useful nudges and digests without recreating a daily meeting in chat.

  • Use Slack for reminders and summary delivery.
  • Keep the edit and review loop inside StandupAI.
  • Route blockers to the channel where the team can act on them.

Quiet hours

Protect focus time by limiting when reminders and digests can send.

  • Set quiet hours around local evening and early morning time.
  • Use workspace defaults first, then adjust for distributed teams.
  • Never force a developer to submit outside their working window.

Billing & plans

Plan comparison

Choose the smallest plan that covers your team size and retention needs.

View pricing
  • Free is best for testing the workflow with a small team.
  • Team plans unlock collaboration and longer history.
  • Upgrade only when the team has proven the daily review loop works.

Upgrade or downgrade

Change plans from billing settings when your team size changes.

  • Plan changes should preserve workspace data within the plan retention window.
  • Seat count follows active workspace members.
  • Billing actions should be handled by a workspace admin.

Cancel subscription

Cancel from billing settings and export anything you need before retention ends.

  • Cancellation stops future renewal.
  • Workspace data remains available through the retention window.
  • Contact support if you need export help before cancellation.

Invoices & receipts

Access billing records from the customer portal.

  • Admins can open the billing portal from settings.
  • Receipts are sent to the billing contact.
  • Update billing details before the next invoice period.

API reference

Authentication

Use workspace-scoped API keys for server-side access.

  • Create and rotate API keys from API settings.
  • Never expose API keys in browser code or public repositories.
  • Use the minimum scope needed for your integration.

Standups API

Read submitted standups and create internal reporting workflows.

  • Fetch reviewed submissions, not raw private activity streams.
  • Filter by workspace, date, or member where supported.
  • Use source links to preserve auditability in downstream tools.

Team members API

Sync member lists with internal directories or onboarding tools.

  • Keep member identity tied to workspace membership.
  • Deactivate members who no longer participate in standup.
  • Avoid using member activity volume as a performance metric.

Webhooks

Subscribe to submitted updates, blockers, and digest-ready events.

  • Verify webhook signatures before processing events.
  • Retry failed deliveries with idempotent handlers.
  • Send blockers to systems where the team already works.

Guides

Running async standups

Replace the meeting with a short daily review habit.

  • Keep the daily update under one minute.
  • Ask for context only when the generated draft misses something important.
  • Use blockers as the reason to talk, not the meeting itself.

Manager dashboard guide

Review team status without interrupting developers.

  • Start with blockers and missing updates.
  • Use trends to improve process, not to rank people.
  • Follow up only where a decision or unblock is needed.

Onboarding your team

Roll out StandupAI by proving trust with a small group first.

  • Pilot with one team for a week.
  • Explain which sources are used and what is never published automatically.
  • Collect feedback before replacing the recurring meeting.

AI summary tips

Make generated updates easier to trust and faster to edit.

  • Use clear ticket titles and PR descriptions.
  • Add human context for blockers, decisions, and handoffs.
  • Keep the final update in the developer voice.