Product
MeetingsDocs and artifactsWork items and sprintsSpool agentCompany
PricingBook a callResources
BlogChangelogStack calculatorDocs ↗Compare
Spool vs LinearSpool vs JiraSpool vs NotionSpool vs Jira + Confluence
Jira is built for deep workflow control at scale. Spool puts the calls, the requirements and the work in one product, linked.
Last checked November 2026
The doc and the tickets, in one place.
Decisions in the requirements become items that link back to the doc, and through it to the call where they were made.
Payments requirements v3 · §2 Refunds
- Partial refunds on bundles.
- Manager approval after 30 days.
- Full refunds stay the default for single items.
- Payments requirements v3Stories from §2
- ACM-42Partial refundsOrigin · §2
- ACM-43Manager approval after 30 daysOrigin · §2
Kickoff call with Acme · 14:02
Priya Shah Bundle customers churn when refunds are all or nothing. Partial refunds ship first.
Where Spool goes further.
Every Atlassian fact is from Atlassian's own pages, checked November 2026.
| Feature | Spool | Jira + Confluence |
|---|---|---|
| One linked chain | ||
| Meeting recording and notes | Yes: Built in: bot, extension or upload | Partly: Loom AI for Meetings, separately |
| Requirements docs | Yes: Built in, with versions | Partly: Confluence, a separate product |
| Products to buy | Yes: One | Partly: Jira, Confluence and Loom, or a bundle |
| Client work | ||
| Keeping clients apart | Yes: A private team per client | Yes: Permission schemes or private spaces |
| Files in the client's brand | Yes: Reports in each client's brand | No: Not built in |
| Price per user per month | Yes: Free during early access | Yes: Free to 10 users · Standard $14.26 for both |
| Build and test | ||
| Secrets vault | Yes: Env vars, injected with spool run | No: Not offered |
| Test cases | Yes: Written from acceptance criteria | No: Not built in; Marketplace apps |
| Project graph | Yes: Calls, docs and items on one map | No: No linked map |
Sources
Wrong about something? Tell us and we'll fix it.
Less to run. More of the story.
One product, one bill
Calls, docs, files, work and the agent in one plan.
Origin on every item
Items keep the call and the doc section they came from.
A team per client
Each client gets a private team. Guests see only theirs.
Publish to the client
Clients see the latest published doc, by link or email.
Moving over? Jira exports work items as CSV. Book a call and we'll plan the move with you.
Book a call01Atlassian records meetings too. What's different?
In Spool the call, the requirements and the items are one product and one graph, so every item links back to the moment it was decided.
02Do we still need Confluence?
Not for project docs. Requirements live in Spool, with versions, and link to the items made from them.
03Can Spool match Jira's custom workflows?
Not fully, and on purpose. Teams add statuses on top of a shared base, and estimates can be points, sizes, hours or none.
04Can we self-host Spool?
Not today. Tell us if you need it.
05What does Spool cost?
Spool is free during early access. See the plans at launch.
- 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