One home for your team's work, decisions, and contributions.
Heirloom helps small teams, co-ops, programs, and mission-driven organizations coordinate work, discuss decisions, and keep contribution history visible as they build.
Currently onboarding a small number of early teams
Early teams get direct support setting up their workspace around real coordination work.
Clarity
Roles, goals, and ownership become visible without adding hierarchy.
Fairness
Contribution history stays visible over time, not trapped in memory.
Momentum
Move asynchronously with enough context to keep shipping.
Community Studio Loom
Today's pulse across people, decisions, and work
Adopt the new member onboarding loop
A proposal, task board, discussion, and contribution trail stay attached to the same Loom context.
86%
for
12
Updates
7
Tasks
3
Docs
Loom update
Weekly pulse: onboarding loop is ready
Brooke posted 12m ago
Task
Draft intake checklist
claimed by Maya · +18 contribution pts
Proposal
Decision notes attached to the work
vote closes tomorrow
Contribution visibility
Next useful thing
3 unclaimed tasks
Mobile companion
Members can check updates, tasks, and messages on the go.
Small teams do not fail because people do not care.
They fail because the work has no home and hard conversations get delayed until it is too late.
Everything is scattered
Notes, docs, tasks, and decisions spread across tools, so nobody can see the whole picture.
Ownership is unclear
Who owns what? Who did what? The question gets avoided instead of answered.
Talk replaces shipping
Great discussions, weak follow-through, because execution is not anchored anywhere.
Recognition breaks down
People do not feel seen. Effort becomes invisible, and motivation drops.
Before Heirloom
The work exists, but the shape of it is hard to see.
Chat
decision buried
Docs
context drifting
Tasks
ownership unclear
Calendar
follow-up missing
Shared Loom
one home for context and follow-through
Proposal
Decision record + vote
Tasks
Owners, status, next steps
Updates
What changed and why
History
Visible contribution trail
Product
The operating loop for collaborative teams
Every Loom connects the conversation, decision, task, and contribution history behind the work.
- Discussion stays attached to the work it creates
- Proposals become decisions with clear next steps
- Contribution history stays visible as the team builds
A Loom is not another place to file work. It is the path from question to decision to owned work, with the record preserved.
Inside a Loom
One thread becomes owned work
Discussion / Thread
Let's Improve our Landing Page
Discuss changes, share feedback, and build together in the open.
5 replies · 3 members active
Proposal / Decision
Landing Page Update Proposal
Turn the discussion into a decision record.
vote closes tomorrow
Task / Ownership
Implement Landing Page changes
Make the next step visible and claimed.
claimed by Maya
Contribution history
+18 contribution pts
The work stays attached to the member who moved it forward.
visible in Loom history
What stays connected
How we think
Build organizations around the people inside them
Heirloom is built for teams that believe good ideas should not get buried, contribution should not be invisible, and coordination should not require more hierarchy.
Surface ideas
Give members a place to propose, discuss, and shape work before decisions disappear into meetings or chat threads.
Make participation easier
Help people see what is happening, where help is needed, and how to contribute without needing to be in every conversation.
Protect contribution history
Keep a visible record of who helped move the work forward, so recognition and ownership can be grounded in reality.
Who it is for
Built for teams where coordination is part of the work
Product proof
What a Loom looks like in practice
Screenshots from the workspace: feed, task board, and proposal view.
Workspace overview
A live view of current focus, member activity, and progress.
Task board
Owners, statuses, and accepted work in a practical board.
Proposal view
Decision details, voting, and context in one place.
Mobile companion
TestFlight / internal betaHeirloom now follows your team onto mobile.
The mobile companion is in TestFlight/internal beta for existing Loom members, so people can check updates, tasks, proposals, messages, and notifications on the go
Today
2 Loom updates
Proposal comments, new task claim
Next
Review proposal
Member vote closes tomorrow
Quietly
Stay aligned
Check context without opening every tool
How it works
Start simple. Add structure when your team is ready.
- 1
Map your current workflow
In setup, we shape a Loom around your team, programs, members, and active work.
- 2
Start with the loop
Bring one real discussion, decision, or project into Heirloom and connect it to tasks.
- 3
Add structure when it helps
Layer in contribution visibility, roles, and shared ownership pathways as the team matures.
Ownership
Shared ownership when you are ready
Start with collaboration and fairness. Formalize later if you want to.
Start now
- Use Heirloom as your shared workspace
- Track contributions over time
- Build trust through transparency and follow-through
Formalize later (optional)
- Connect to legal pathways when the team is ready
- Incorporation and compliance support can be layered in over time
- Shared ownership structures remain available without blocking day one
Ownership is not required to start. But if you want to build a co-owned organization, Heirloom is designed to support that path.
Pricing
Early access pricing
Heirloom is currently working closely with a small number of early teams before opening public pricing.
Founder-led setup while pricing is still being shaped
We're still shaping pricing, request early access to learn more. Early teams get founder-led setup and direct support as we learn what works.
Early teams get:
- Founder-led setup
- Workspace setup support
- Feedback-driven product shaping
- Pricing discussed based on team needs
- Best for co-ops, programs, mission-driven teams, and small teams exploring shared ownership
Pricing is discussed based on team needs, setup scope, and what Heirloom is actually helping your team coordinate.
“If you want to create something made up of the best expertise and parts of everyone involved, use Heirloom. The way to get the most out of your team is by using Heirloom.”
- Early Heirloom user
Frequently asked
No. Heirloom is a shared operating system where ideas, decisions, execution, and contribution history live together for collaborative-first teams.
No. Early teams and nonprofits use it too. If you are building collaboratively and want clarity plus fairness, it is a fit.
No. Shared ownership is optional. You can start by building together and formalize later if needed.
Request early access or book a short founder call. We will help map your current workflow into Heirloom.
Ready to build together?
Request early access, or book a short founder call.