Skip to content
Requirements to work

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.

  1. Payments requirements v3 · §2 Refunds

    • Partial refunds on bundles.
    • Manager approval after 30 days.
    • Full refunds stay the default for single items.
  2. Payments requirements v3Stories from §2
    • ACM-42Partial refundsOrigin · §2
    • ACM-43Manager approval after 30 daysOrigin · §2
  3. Kickoff call with Acme · 14:02

    Priya Shah Bundle customers churn when refunds are all or nothing. Partial refunds ship first.

Side by side

Where Spool goes further.

Every Atlassian fact is from Atlassian's own pages, checked November 2026.

Spool and Jira + Confluence, feature by feature
FeatureSpoolJira + Confluence
One linked chain
Meeting recording and notesYes: Built in: bot, extension or uploadPartly: Loom AI for Meetings, separately
Requirements docsYes: Built in, with versionsPartly: Confluence, a separate product
Products to buyYes: OnePartly: Jira, Confluence and Loom, or a bundle
Client work
Keeping clients apartYes: A private team per clientYes: Permission schemes or private spaces
Files in the client's brandYes: Reports in each client's brandNo: Not built in
Price per user per monthYes: Free during early accessYes: Free to 10 users · Standard $14.26 for both
Build and test
Secrets vaultYes: Env vars, injected with spool runNo: Not offered
Test casesYes: Written from acceptance criteriaNo: Not built in; Marketplace apps
Project graphYes: Calls, docs and items on one mapNo: No linked map
In Spool

Less to run. More of the story.

  1. One product, one bill

    Calls, docs, files, work and the agent in one plan.

  2. Origin on every item

    Items keep the call and the doc section they came from.

  3. A team per client

    Each client gets a private team. Guests see only theirs.

  4. 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 call
Questions

Fair questions.

Still unsure? Book a call or write to us.

01Atlassian 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.

  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