---
tags: Kleros
---
# Kleros Community Design V1
```
Author: Frothy
09/21/2021
```
:::danger
Needs:
1. Jurors to stay busy on solving cases and earning PNK
2. There is a communication gap, we want DAOS/B2B to think of Kleros when they need something resolved, like how I think of Amazon when I need to buy something
:::
# Macro Level - The Big Picture
### Want Created:
How do re-engage existing accounts and attract net-new accounts?
Similar to a B2B pipeline, how do we build MVPs or representatives from each org? Does each DAO have a legal team or someone responsible for disputes?
**Re-engagement and Acquisition**
| Goal | Metric |
| ----------------- |:----------------------- |
| Community satisfaction through community experiences| Establish customer lifetime value (CLV) |
| Funnel through a pipeline | Conversion Rate %|
| Retention | # of engagement |
## Where Are We Starting
- Jurors
- token participants
- Democracy or dispute enthusiasts
## What do we want DAOs to do?
- Kleros first to mind for resolution needs
- Recommend Kleros to other DAOs
- DAO onboarding pipeline
## How do we get there?
- Incentivize to help each other
- Moving them along the "commitment curve"
- identify and collect all the partcipants who have gone through the funnel
```
Hook event:
"Conflict resolution, monetary settlements"
```
## Community Design Process
Design Question: **HOW CAN Kleros BE THE CHOICE OF ARBITRATION RESOLUTION?**
- ***Community-first UX Design Sprint*:**
* Recruit, interview + deliver UX research into current and potential arbitration participants
* Synthesize findings and lay out community strategy
* Community Strategy ⇒ de-risk the launch
- **Community Strategy**
⇒ community distribution channels
⇒ partnerships
⇒ relationship building + cultivation
⇒ new arbitration market opportunities
- **Metaverse Vibe:**
Community froth for distribution through online events / twitter spaces / discord jams
Strong metaverse presence + viral memes across main metaverse channels.
- **Memetic Desire around liquidity events**
Identify the moat to create
Get into the subculture of DAO conflict resolution and know how their behavior is influenced by their fellow sub-group community
Creating the right context + conditions for social signaling to take off
- **First users Contribution Flywheel**
How to incentivize early community to be natural ambassadors + ecosystem allies of Kleros? How to create 100 true Kleros fans in the first 30 days?
Find ways to enable collective co-creation of Kleros events and iterate on community feedback.
- **Focus on the *fingerspitzengefühl (that 'fingertip feeling')***
Know what differentiates the different collectable personas, how they're thinking, behaving and know what will light them up.
Execute content that taps in precisely to the crypto culture that Kleros wants to appeal to.

Move Kleros's active members into Power Members

Engage existing active members to increase volume of transacitons.
---
**Community Thesis V1**
**Incentive**: Ease of transaction and onboarding
**Purpose**: Accessible court of community law
**Gather**: Conduct decisions together
---
# Micro Level - The Specific Details
## Proposal
1. Increase activity and volume of current users
2. Create pipeline and retaining wall of new participants
:::success
Identify resolution events and onboard/engage
:::
Ideas:
- onboarding DAOs
- Rewards for acquisition
- accounts flow through the pipeline
- B2B play, need an institutional community
- "hook" event
---
### Initial Timeline
**Kick-off: October 05, 2021**
Week 1: Onboarding and Initial Strategy Assessment
Kleros shares relevant information for Frothy to map out proposal
Consistent communication for any additional, missing, and follow-up information
Week 2: Incentive Creation vertically for roles, horizontally across roles
Drafting community proposal
Outreach to internal customers to approve or counter strategic direction
Week 3: Create logistics
Managing existing and building net-new assets and programming
Collaborating with the marketing team on a shared message
Week 4: Outreach to current Lead arbitration providers
Distributing bandwidth constraints
Delegating program owners
Week 5: Onboarding roles with objectives and metrics
Scheduling deliverables and assigning points-of-contact
Fixing and preventing churn in the user journey
Week 6: Launch logistics and announcements
Directing distribution channels to orbit
---
### Next Steps
- Meeting with Kleros for Proposal review
- Submit budget
- Start onboarding and knowledge download
---
# Review and Decision:
Tuesday, Oct 5, 2021
## Background
typically the project leader would be the direct user here
DAOs, other influential keystake holders, founders when there is a proposal, how when a votes go, having Vitalik's support is to get this to pass
Not criminal cases, neutral disagreement of DAO governance, this is not what we agreed upon as a DAO, insurance - and someone is asking for reimbursements
MakerDAO - has an onboarding process to include more assets as collateral for DAI, and use Kleros for decision making process, needs to have formal proposal, and who are the influential stakeholders, many cases it's the founders. In MakerDAO, it's the team on the collateral onboarding.
"Community litigators"
## Objectives
1. Helping identify the keystakes holders who facilitates proposals, guidelines, community expectations: collateral onboarding, Founders, Community Leads
2. Building the BD onboarding pipelines
3. Narrative shift for Community: Shifting the narrative thinking of Kleros as default option for governance services
4. keep Jurors earning PNK
5. Setting metrics
**Optionals:**
Kleros big on game theory, and thus misunderstanding how Kleros would work
Anti-FUD (Fear/Uncertainty/Doubt) - how to fight misconception of "I" can sway the courts, courts can be gamed (if i'm a whale i can sway) - building legit that Kleros is the option
"not outsource" - integration tool msg
Main: Projects building their own dispute mechanisms, with over simplified
## Goals
Unknown:
conversion rate of DAOs to adopt Kleros
number of DAOs/Teams needed to onboard
Would like:
Have teams to bring on to us
Need to "have as many as possible" into the first stage of the pipeline
Minimize bandwidth constraints
## Scope
1. Is helping Kleros calculate how many teams are needed to onboard
2. Find teams with most pain/high value (in the dozens)
High value distributes, willing to pay ETH fee, but smaller distributes does not want smaller transactions
3. larger volume, smaller scale
decentralized marketplaces
4. Community Narrative design
## Future Considerations
Anti-FUD
Potential, recruit Community Lead
## Out of Scope
1. being responsible for conversion rate
2. Juror responsibilities
3. already knows who their team are, they don't really need exact recommendations
## Project Exit
1. clear est. of a BD pipeline - handover
2. Clear target list and outreach executed
3. Clear narrative to present to the community as a package
## Key Stakeholdrs
1. Jimmy is the BD owner
2. Community Lead is the role actively looking to fill
## Constrains/Assumptions/Risks/Dependencies
Has communication team needs help
---
# What Will be Delivered:
## Deliverables
1. Establishing Metrics - calculate how many teams are needed to onboard
2. Building the BD onboarding pipelines
3. Sales outreach to BD
4. Community Narrative Shift
## Financial Resources
44,000 DAI per month at 3-4 months
- 10,000 B2B Sales Funnel Design
- 12,000 Sales Outreach
- 22,000 Community Design
Payment options open for discussion (ETH / DAI)
- An option is to be left open for token based completion bonus on governance tokens if scope is changed
- ETH price will be established at the beginning of each monthly pay period
- 50/50 split between with PNK