Introduction

sprintrr is project management for client work — agencies, consultancies and dev shops. A call happens, the plan changes, and by Friday the client wants an update. sprintrr turns that loop into a few approvals:

1. Bring the call in. Connect Fireflies and pick the meeting, or paste a transcript from Zoom, Teams, Meet, Otter or Granola.
2. Approve the changes. sprintrr proposes new tasks, updates to existing ones and removals. Removals start unticked, and nothing changes until you apply.
3. Draft the Friday update. sprintrr writes a status update from what actually happened in the project — shipped, in progress, blockers, next, asks. You edit it.
4. Send it. Publish to Slack or email. Drafts never send themselves.

On day one, describe the project in plain language and sprintrr generates the starting plan — milestones and tasks with estimates — in about a minute.

What you can do

• Turn meetings into task changes — creates, updates and removals, each one approved by you. See Transcripts → tasks.
• Draft and send status updates — from the project's own activity, to Slack or email, on demand or as a scheduled draft. See Status updates.
• Start from a prompt — a plain-language brief becomes milestones and tasks with categories, priorities and estimates. See AI generation.
• Track the work — the same tasks on a board, calendar, Gantt, table and milestones, with time tracking and progress that rolls up from task status.
• Ask your project — plain-language questions answered from the project, with citations. Free. See Ask.
• Collaborate in teams — invite people by email to a shared workspace, assign tasks and follow a team activity feed. On a Teams plan, each person gets a seat and the team shares one AI Credits pool. See Teams.
• Bring your own AI key — connect your own Anthropic, OpenAI or Gemini key on any plan and AI use is unlimited.
• Automate with MCP — drive your projects from Claude Desktop, Cursor or any MCP client, or call the HTTP API directly. See Integrations → MCP.

How it fits together

Day one   brief ──▶ generated plan (milestones + tasks)
 
Each week
  meeting ──▶ proposed changes ──▶ you approve ──▶ plan stays current
  (Fireflies  (create / update /
   or paste)   remove tasks)
 
  plan ──▶ drafted status update ──▶ you edit ──▶ Slack / email
 
Workspace = Personal  OR  Team (shared projects; seats + shared credits on a Teams plan)
Every change ──▶ Activity feed (manual or MCP-attributed)

A project contains milestones and tasks. Tasks belong to a project and can be grouped under a milestone; a milestone's progress is calculated automatically from the status of its tasks. Projects live in either your personal workspace or a team workspace.

Where to go next

• New here? Start with the Quickstart.
• Have a call to process? Read Transcripts → tasks.
• Owe someone an update? Read Status updates.
• Want the model behind projects, tasks and milestones? Read Core concepts.
• Integrating programmatically? Jump to the MCP integration.