Start with the complete loop. Pay when the work expands.
Community lets a team create a real Decision Contract, collect ballots, publish its response, and record the outcome now. Paid plans add explicit capacity and connected operation; they do not sell the right to participate.
One free path proves the product. Paid paths remove a named constraint.
There is no popularity badge and no invented urgency. The page names the limit or capability that creates a reason to upgrade.
Community, free
Reach the first useful outcome before a commercial conversation: one live question carried from contract to published outcome.
- ✓1 open decision, hard limit
- ✓500 ballots, hard limit
- ✓All three ballot methods
- ✓Response and outcome record
Close one complete loop
The first conversion event is not a page view. It is a team publishing the answer it promised and preserving what happened next.
Capacity or connected operation
Move to paid only when the current work crosses a declared boundary.
- ↗A second open decision on Community, or a fourth on Indie
- ↗More than 500 ballots on one decision
- ↗Custom domain, API, webhooks, or connected identity
- ↗A non-recurring three-decision pack
Compare what changes, not a stack of vague feature names.
Every plan shows open-decision capacity, ballot capacity, the value available before upgrade, and the next boundary. Free is self-serve; paid plans use assisted setup.
Community
Best for: A team proving the complete loop on one live question.
Value before upgrade: Create the contract, collect ballots, publish the response, and record the outcome before paying.
- ✓Open capacity: 1 open decision, hard limit
- ✓Ballot capacity: 500 ballots, hard limit
- ✓Included operator allowance: not yet published; operator count is not the primary commercial unit
- ✓Approval, ranked Borda, and pairwise
- ✓Email one-time-code verification
- ✓Hidden live scores
- ✓Public result, response, and outcome
- ✓CSV export and audit log
Upgrade when: A second decision must stay open, the audience exceeds 500 ballots, or connected operation becomes necessary.
Start freeIndie
Best for: One product running occasional decisions with a larger audience.
Value before upgrade: Keep three decisions open at once, preserve the complete response loop, and add product presentation.
- ✓Open capacity: 3 open decisions, hard limit
- ✓Ballot capacity: 5,000 ballots, soft limit
- ✓Included operator allowance: not yet published; operator count is not the primary commercial unit
- ✓Brand colour and logo
- ✓CSV and audit export
- ○Remove the player.vote badge
- ○Discord and Slack notifications
Upgrade when: Open work must be unlimited, or the product needs a custom domain, API access, or signed webhooks.
Arrange IndieStudio
Best for: One active product using accountable decisions as an ongoing operating loop.
Value before upgrade: Run unlimited simultaneous decisions with allowlists, a custom public record, API access, and signed webhooks.
- ✓Open capacity: Unlimited open decisions
- ✓Ballot capacity: 25,000 ballots, soft limit
- ✓Included operator allowance: not yet published; operator count is not the primary commercial unit
- ✓Invite allowlists
- ✓Custom public-record domain
- ✓Host API and signed webhooks
- ✓Published outcome record
Upgrade when: Ballot volume or connected identity needs the higher Scale profile.
Arrange StudioScale
Best for: A high-volume product operation that needs connected identity.
Value before upgrade: Keep unlimited decisions open, raise the soft ballot threshold, and use partner voter assertions.
- ✓Open capacity: Unlimited open decisions
- ✓Ballot capacity: 100,000 ballots, soft limit
- ✓Included operator allowance: not yet published; operator count is not the primary commercial unit
- ✓Everything in Studio
- ✓Partner voter assertions
- ✓Connected identity path
- ○Defined operator-role allowances
- ○Higher API limits
Upgrade when: The work needs negotiated enterprise controls, a maintained connector, or managed delivery.
Arrange ScaleRuns in the product now.
A real manual buying or provisioning path.
Accepted work that is not built.
Hard blocks new work. Soft accepts it, warns, and creates no automatic charge.
Commercial terms 2026-07-21. Published prices are commercial hypotheses until behaviour confirms them; this page does not claim validated demand.
Decision Pack
For a team that needs a few consequential decisions but does not need a recurring product subscription.
- Each successful Decision Contract creation consumes one use. A failed creation consumes none.
- When the count or validity window ends, new pack creations stop; existing ballots, results, responses, outcomes, and public records remain.
- The pack stays separate from the recurring product grant and never turns into a subscription.
Add evidence or service. Never buy the right to be counted.
Baseline identity, hidden live scores, audit history, public results, and the response loop remain part of the core product.
Integrity+
$249Add review evidence to one consequential decision without changing baseline participation rights.
Discuss Integrity+Identity Connector
$2,400Maintain one external identity assertion path and its evidence pipeline.
Discuss Identity ConnectorManaged Decision
$1,500Add a contract workshop, dry run, and facilitation when the decision itself needs delivery support.
Discuss Managed DecisionFree is self-serve. Paid entry is assisted.
Self-serve checkout is not live. The page therefore offers no purchase button and makes no claim that payment can complete online.
Why the model is shaped this way.
Why not charge for participation?
The bill should not rise mainly because more affected people submit feedback, vote, or read the answer.
Why not make operator count the main bill?
Product work crosses several roles. The recurring value unit is the product or workspace, with capacity and connected operation stated directly.
What happens when paid access ends?
Already published decisions and outcomes remain part of the public record. New paid operations depend on the agreed plan; existing evidence is not retracted.