---
# System prepended metadata

title: Untitled

---




- **Challenges with DAO Decisions**:
  - DAOs can be chaotic.
  - Ideas often only get halfway executed.
  - Suggestion to delegate responsibilities to teams for better organization.
- **ETH Denver Experience**:
  - Last year's experience lacked organization.
  - Treasury funds are underutilized.
  - Goal: Present a more organized outline at the next meeting.
- **Hackathon Perspective**:
  - Last year's hackathon was last-minute and lacked organization.
  - Suggestion for an internal hackathon manager.
  - Form teams in advance for better preparation.
  - Consider stipends from the Treasury for hackathon members.
  - Importance of well-organized teams for better chances of winning.
  - Opportunities arise even for teams that don't win.
  - Need for RaidGuild support and coordination.
- **Value Recognition**:
  - Need consensus on how to evaluate and recognize the value of individual categories.
  - Importance of understanding the highest impact areas.
  - Concern about mismatch of skill set to tasks.
  - Need for a vetting mechanism to match skills to tasks.
  - Past experiences had enthusiastic members but lacked execution due to skill mismatch.
- **Budget Considerations**:
  - All activities could fall under a marketing budget.
  - Suggestion: RaidGuild should consider spending up to 20% of the treasury on marketing initiatives.
  - Unclear consensus on budget allocation.
  - Need to account for other marketing efforts throughout the year.
  - Importance of compensating members for high-value initiatives.
  - Need to determine available budget before encouraging proposal submissions.
- **Responsibility**:
    - Concerns about selecting the right skill set for each initiative.
    - Potential for a point person responsible for their budget.
  - **Money Allocation**:
    - Deciding budgets for initiatives.
    - Question of who decides the budget amounts.
- **Hackathon Coordination**:
  - Importance of having a lead or coordinator.
  - Need for a mechanism to ensure qualified individuals take on responsibilities.
- **Prioritizing Tasks**:
  - Importance of consensus on priorities.
  - Need to decide on high-value initiatives first.
- **Process Proposal**:
  - Treat the task allocation like an RFP process.
  - Use signaling sessions to rank tasks.
  - Invite members to submit proposals for prioritized tasks.
  - Use a vetting mechanism on the front end to avoid awkward situations later.
  - Propose a light proposal template for ease of submission.
- **High-Level Strategy**:
  - Need for a broader conversation on marketing strategy.
  - Consideration of whether the strategy needs to be decided before diving into tasks.
- **Sales Funnel Perspective**:
  - RaidGuild operates more like a high-touch sales funnel.
  - Importance of meeting and explaining RaidGuild to potential clients.
  - Potential misalignment with generic marketing strategies.
- **Dashboard for Metrics**:
  - Desire for a dashboard to track metrics like unique page visits and conversion rates.
  - EC Wireless mentioned integrating site analytics.
  - Importance of understanding the entire sales funnel.
- **Marketing Concerns**:
  - Fear of allocating resources to non-impactful areas.
  - Desire to evaluate the effectiveness of marketing strategies.

### Process

- **Process Proposal**:
  - Add marketing evaluation to the list of tasks.
  - Use a TCR signal vote to prioritize tasks.
  - Each member receives an equal allocation of voting tokens.
  - Members can allocate their tokens to the tasks they prioritize.
  - After signal vote, a lightweight proposal template is used to define scope, problem, and approach.
  - Proposals are evaluated and commented on by members.
  - Economic considerations need to be addressed in the following weeks.
- **Signal Vote Details**:
  - Tasks are put up for a signal vote without a well-defined scope or budget.
  - After the vote, tasks with clear signals are further defined.
  - Tasks without signals are disregarded.
- **Proposal Submission**:
  - Interested members fill out a lightweight proposal template.
  - Proposals include goals, strategy, team size, and budget.
  - Multiple proposals can be submitted for the same topic.
  - Proposals are evaluated, possibly through emoji voting or other simple mechanisms.
  - Competition is encouraged, but collaboration on proposals is also possible.

### Budgeting

- **General Budget Considerations**:
  - The group discussed the challenge of determining a budget for the marketing initiatives.
  - The idea is to base the budget on the guild's earnings from the past year, which would be bear market earnings.
  - The group discussed the importance of being conservative with the budget, especially considering the unpredictability of events like eath Denver.
  - The group also discussed the need to avoid subjective magic numbers and instead base decisions on past data and initiatives.
- **Evaluating Past Marketing Efforts**:
  - The group discussed the importance of evaluating past marketing efforts to determine their value and the amount spent.
  - This would involve looking at the efforts of the spring brigade and reviewing the history of rips and treasury payouts.
- **Value of Initiatives**:
  - The group discussed the challenge of determining the value of various initiatives, such as booths at events.
  - They noted that while some initiatives may seem expensive, they can lead to high-value clients or other benefits.
  - The group discussed the importance of allowing sentiment to emerge through a decentralized signaling process rather than relying solely on individual opinions.
- **Reviewing Past Efforts**:
  - The group discussed the importance of reviewing past marketing efforts to provide context for future initiatives.
  - They noted that it's essential to understand what has been funded in the past and what value those efforts have brought to the guild.

