Built for guilds
Independent, together.
Onboarding, verification and cases in shared queues. Every consequential decision keeps a record of who acted and why.
The operator's desk.
Member onboarding
Invite members, see who has finished setup, and help the ones who are stuck.
Verification queue
Review submitted evidence and record a decision. Rejections carry a reason and a way to resubmit.
Cases and appeals
Assign a reviewer with no link to either party. Outcomes need a written reason.
Activity history
Consequential actions record who acted, when and why, so decisions can be explained later.
How a case moves.
- Opened
- Evidence added
- Independent review
- Written outcome
- Appeal if needed
An appeal opens a separate review stage. The first outcome is never erased, so everyone can see how the decision changed and why.
CASE-0031
Unpaid milestone
Case opened
Milestone payment overdue by 21 days
Evidence added
Signed scope, delivery files, messages
Reviewer assigned
No link to either party
Decision
No decision yet
Either party can appeal the decision. The first outcome stays on record.
Product concept. Sample data
Membership is not access.
Joining a guild does not open every member's records. Each request checks the person's role and their relationship to the specific record. Support staff get limited diagnostic access by default, and any exception is time-limited, needs a reason and is logged.
Run your guild's pilot with us.
Tell us about your guild, roughly how many members you have and what you want to organise first.