Product
MeetingsDocs and artifactsWork items and sprintsSpool agentCompany
PricingBook a callResources
BlogChangelogStack calculatorDocs ↗Compare
Spool vs LinearSpool vs JiraSpool vs NotionStories that come with their origin attached.
Items made from a meeting or doc keep it as their origin, so nobody has to ask why we're building this. Plan sprints against real capacity, and let Spool do the grooming.
Press C anywhere to make an item · J K to move · ⌘K for the rest
Work moves. The reason moves with it.
Items from meetings and docs wait in Triage until someone accepts them, then cross the board with their origin attached.
ACM-42 is in Triage
Ask any item why it exists.
Every item keeps its origin and links. Follow them back through the doc to the moment it was decided.
Partial refunds
Linked
- Kickoff call with Acme
- Payments requirements v3
- ACM-43Manager approval after 30 days
- ACM-46Refund emails show the partial amount
Payments requirements v3 · §2
Partial refunds on bundles. Full refunds stay the default for single items.
Kickoff call with Acme · 14:02
Priya Shah Bundle customers churn when refunds are all or nothing. Partial refunds ship first.
Plan to capacity. Spool fills the rest.
Set a goal and a capacity. Fill with Spool adds backlog items by priority until the sprint is full. You adjust.
- ACM-46Refund emails show the partial amount2
- ACM-48Receipt shows refund status3
- ACM-50Refund reasons report5
- ACM-51Bulk refunds from the dashboard8
- ACM-45Apple Pay at checkout3
Goal: refunds anyone can trust
- ACM-43Manager approval after 30 days5
Quick to make. Quicker to move through.
Press C anywhere to make an item; it gets its team's key, like ACM-42. ⌘K for everything else.
- Triage1
- ACM-48Receipt shows refund status
- Todo1
- ACM-43Manager approval after 30 days
- In progress2
- ACM-42Partial refunds
- ACM-47Double refund on retry
- In review1
- ACM-44Refund ledger entries
01Are there sub-tasks?
No. Stories, tasks and bugs have acceptance criteria instead, and ticking them drives progress. Epics group the bigger pieces.
02Can Spool put work into a sprint on its own?
No. Its items wait in Triage until a person accepts them. Fill with Spool proposes; you decide.
03Can a team change the workflow?
Teams can add statuses, like Vendor QA, on top of the workspace's base. Estimates can be points, T-shirt sizes, hours or none.
04What happens to open items when a sprint ends?
You choose where they go: the next sprint or the backlog.
05Do you have roadmaps or initiatives?
Not yet. Epics and projects cover most of it today.
- MeetingKickoff call with Acme42 min · 3 decisions
- DocPayments requirementsv3 published
- ItemACM-42 Partial refundsSprint 12 · review
- CodePull request linkedcoming next
- TestTested against the storycoming next
Bring the whole project. Close the other eight tabs.
Free until public launch · onboarding teams in small groups