Skip to content

Nine tabs per project. Or one thread.

Meeting notesbot
Docswiki
Trackertickets
Drivefiles
Chatthreads
Test sheetQA
.env in chatsecrets
Status docweekly
Spreadsheetcapacity
9 tools · 9 logins · work copied by handmeeting notes → docs → tracker → drive → chat

Add up what your stack costs today.

Open the stack calculator →
How it works

From the call to the sprint. No copying.

Every doc and item keeps the meeting it came from, so the reason travels with the work.

Capture the call

Bot, browser or upload. Decisions and action items come out on their own.

Write it down once

Draft the doc from the call. Every change is tracked; publish when it's agreed.

Plan the work

Stories arrive with their origin attached. Plan them against real capacity.

Ask Spool

Ask the project anything.

Answers come with their sources, and only use what you're allowed to see.

example project · Acme
Service teams

Every client, its own team.

One workspace for all your clients or products. Private teams stay invisible to everyone else, in search and in Spool's answers too.

View as
ACM
Acmecheckout rebuild
private
PSRKAM+36 people
TodoIn progressClient reviewDone
ACM-42Partial refunds
ACM-43Manager approval
Private to Acme
GLB
Globexmobile app
private
JLNT+24 people
TodoIn progressVendor QADone
GLB-18Offline mode
GLB-21Push settings
Private to Globex
INT
Internal toolsopen to the workspace
open
HDSVMOeveryone
TodoIn progressDone
INT-7Onboarding checklist
INT-9Release template
Private
The owner sees every team.
Project graph

The whole project, as one map.

Every meeting, doc, item and file is linked. Hover anything to follow it back to where it started.

drag to move · hover to trace

Agents do the work. People stay in charge.

01
Every run has an owner.

Spool always works for a named person.

02
Nothing lands without you.

New work waits in Triage for a person.

03
Same access as you.

Spool never sees more than the person who asked.

Spool for Priya Shah

Draft stories from Payments requirements v3

✓Read the doc and the kickoff call
✓Wrote 6 stories with acceptance criteria
●Waiting for Priya to review
nothing lands yet
Audit log Acme
  • Spool for Priya read Payments requirements v3
  • Spool for Priya drafted 6 stories
  • Rahul K edited ACM-42
What Spool can seesame as Priya
Acmeyes
Internal toolsyes
Globexno access
Where we are

The whole lifecycle, one module at a time.

What's live, what we're building, and what comes after. No dates we can't keep.

Now livelive

Meetings

Browser extension or upload. Notes, decisions, items.

live

Docs and artifacts

Versions, change history and the project drive.

live

Work items and sprints

Triage, estimates, capacity and burndown.

live

Coding agents over MCP

Claude Code, Cursor or any MCP client works in Spool as you.

Next buildingnext

Meeting bot

Spool joins Google Meet, Zoom or Teams calls and records them.

next

Secrets

A vault for env vars, injected with spool run.

next

Project graph

Everything linked, on one map.

next

Ask and the Spool agent

Answers with sources, drafts and skills.

next

Code and pull requests

Items and pull requests linked both ways.

next

Your coding agent

Hand work to Claude Code, Cursor or Codex, with context.

next

Testing

Cases from acceptance criteria. Failures filed as bugs.

Later plannedlater

Deploys to your cloud

AWS, Azure or GCP, linked to what shipped.

later

Uptime

Know when something breaks, and which change did it.

later

Security and load testing

Checks that run before a release, not after.

  1. MeetingKickoff call with Acme42 min · 3 decisions
  2. DocPayments requirementsv3 published
  3. ItemACM-42 Partial refundsSprint 12 · review
  4. CodePull request linkedcoming next
  5. TestTested against the storycoming next

Bring the whole project. Close the other eight tabs.

Book a call

Free until public launch · onboarding teams in small groups

Type to search…

↑↓ navigate↵ selectEsc close