DCZion
Start freeSign in

Manual

You can make two things in DCZion: a workspace and a decision. They are different objects, they are counted separately, and mixing them up is the main source of confusion. This page draws the line.

1. A workspace is a box. A decision goes inside it.

A workspace holds a team: its people, its decisions, and its invitations. One person creates it, and that person is its owner. A decision is a single question you settle, and it lives inside one workspace — or inside none at all, which makes it solo.

ObjectWhat it isExample nameWho owns it
WorkspaceThe team's box: members, decisions, invites"Acme"The person who created it
DecisionOne question, with its alternatives and criteria"Hire a CTO"The initiator who started it

You will see the word team in a few places in the app. It means the same thing as a workspace.

2. A solo decision and a team decision

It is the same decision-making engine either way. The difference is where the decision lives, and which counter it spends.

  • Solo decision — you start it with no workspace. Nobody else is asked to score. It belongs to your account.
  • Team decision — you start it inside a workspace. Its members are invited to score blind, and the results are shared with the team.

3. Three counters, and what moves each one

CounterGoes up whenFreeTeam
WorkspacesYou create a workspace. Nothing else moves this.5 per account15 / 50 / 100 / 250 per account — the class you pick sets it
Team decisionsYou start a decision inside a workspace. Every member spends from the same count.10 a month per workspace100 a month per workspace
Solo decisionsYou start a decision with no workspace.10 a month per account100 a month per account
SeatsSomeone accepts an invitation and joins. An invitation on its own moves nothing.5 per workspace10 / 50 / 100 / 250 per workspace — the class you pick sets the cap

Team decisions and solo decisions are separate counts. Spending one never touches the other.

4. Worked example

Tom is on the Free plan.

  1. Tom creates a workspace named Acme. Workspaces: 1 of 5. Seats: 1 of 5 (Tom).
  2. Tom starts a decision named "Hire a CTO" inside Acme. Acme's team decisions: 1 of 10. Workspaces: still 1 of 5.
  3. Tom starts a second decision, "Pick the office", in the same Acme. Acme's team decisions: 2 of 10. Workspaces: still 1 of 5. Seats: still 1.
  4. Tom starts a decision with no workspace, "Should I move house". That is solo. Tom's solo decisions: 1 of 10. Acme is untouched: still 2 of 10.

Any number of decisions with the same team is still one workspace. The workspaces count only moves when you create a workspace.

5. Seats: who takes one, and when

A seat is a person who has joined the workspace. An invitation by itself takes no seat, which is why you can invite more people than you have seats — they queue, and the first ones to accept get in.

  • Acme has 5 seats and 5 members joined. Acme is full.
  • Tom invites three more people. Nothing happens yet — invitations are free.
  • Those three click their links. The first one joins: 5 of 5. The other two are told the workspace is full.
  • Tom removes a member who has left the team. One seat is free again the same second, and the next person can join.

6. Whose plan a workspace uses

A workspace uses the plan of the person who created it. Not the plan of whoever is making a decision, and not the plan of the newest member.

  • Acme was created by Tom, who is on Free. So Acme gets Free limits: 5 seats, 10 team decisions a month — even if a member of Acme is on a paid class.
  • When Tom subscribes to a Team class, Acme becomes a Team workspace: 100 team decisions a month, and as many seats as his class allows (10 / 50 / 100 / 250).
  • The class is flat: Team 50 costs the same whether Acme holds 3 people or 50. Members joining later never change the bill — the cap is the only thing the class buys.
  • A member on a paid class still gets their own allowances: 100 solo decisions a month, and the workspace allowance of the class they bought (15 / 50 / 100 / 250, one per seat above Team 10). If they want a bigger seat cap for their own team, they pick the class that fits.

7. When you reach a limit

Limit reachedWhat still worksWhat unblocks it
Workspaces (5)Everything inside the workspaces you already haveDelete a workspace you no longer use
Team decisions this month (10)Everything already created; drafts you are still writing; other workspaces keep their own countWait for the reset on 1 October (UTC), or move to Team for 100
Solo decisions this month (10)Everything already created; draftsWait for the reset on 1 October (UTC), or save the decision into a workspace
Seats (5)The decision-making itself — nothing is lockedRemove a member who has left. Seats do not reset monthly

Amounts only ever cap new decisions and new joins. Nothing you have already made is deleted or locked, on any plan. Drafts cost nothing until you open them for input.

8. The plans

Free

5 workspaces

5 seats per workspace

10 team decisions / month per workspace

10 solo decisions / month

Team

15–250 workspaces (one per seat above Team 10)

50 seats per workspace

100 team decisions / month per workspace

100 solo decisions / month

Enterprise

Custom contract. No caps on workspaces, seats, or decisions.

Compare plansSee my usageFAQ