S3 budget update for Eagle Ops
Since Eagle Ops is the first experiment of clustering multiple Squads into a guild, there are some lessons learned that we would like to share:
- A guild should revising its budget in a timely manner, in order to provide transparency to stakeholders (short reasoning why a budget should remain the same or should be adjusted, should be enough)
- We have learned that squads should start with the bare minimum of contributors for the work, as it is easier to expand than to reduce.
- Having fewer contributors in a team will have (in general) a positive influence on accountability and performance
Based on the aforementioned learnings, the guild revised S2 internally and would like to propose a significant budget reduction of 49% (from $53.5k to $27.5k per month) for S3, according the following changes:
Ops Squad: As the focus shifts from facilitating day-to-day operations towards facilitating the DAO transition, we would like to reduce the budget significantly with 79% (from $12k to $2.5k per month)
Finance Squad: As the Squad managed to stay below 50% of the budget in S2 and it is not planning to expand in S3, we would like to reduce the S3 budget with 57% (from $18.5k to $8k per month)
Data Squad: As the product is not expected to launch in S3, we would like to reduce the budget with 30% (from $14.35k to 10k per month), and let the squad focus explicitly on the good work of the data dashboard.
Legal Squad: Based on S2’s experience, we are able to legal squad is able to reduce the budget with 36% (from $11k to $7k per month)
The guild is expected to only require $5k of funding in S3, as the Eagle Ops’s multisig still has $78k left from the S2 due to proper budget management (remaining funds of S3 will be transferred back to the Aragon treasury).
S3 Proposed KPIs for Eagle Ops
The KPI’s for S3 per squad are outline below:
Recurring Deliverables (Rick):
- 100% timeliness to compile AN DAO payments: prepare, sign and execute routine financial transactions within 10 days after voting is done
- 100% timeliness to compile core contributor payments: prepare, sign and execute routine financial transactions by the last Thursday of every month
- 100% timeliness to compile creator payments (bounties): prepare, sign and execute on a weekly basis
- 100% timeliness of monthly income/expense report & contributor rewards report posted on the forum before the 5th of next month
Concrete Deliverables (Rick):
- Compose a Finance Operating Model that functions as a best practice for the new DAO
- Providing an updated DEX liquidity position for Aragon
- Build a budget expense overview for new the DAO
- Build a proposal tracker that provides a real time overview for delegates on the already approved funding & funding pending in vote
- Having a working on-chain and off-chain accounting solution in place for the new DAO
- Provide an end of the season financial transparency report
Additional deliverables (Rick):
As learned from S2, Finance Squad should be flexible in additional deliverables. During the last season, approx. 10 additional deliverables required attention from the Finance Squad.
*Finance squad does not provide financial or investment advice in any jurisdiction. Finance squad has not provided such advice in the past, it does not intend to provide such advice in the future. It only provides operational support for financial aspects.
Recurring Deliverables (Rick):
- Navigating the transition from AN DAO towards the new Aragon DAO by being the point of contact for the current guilds
- Updating guilds on the relevant DAO transitioning
- Maintaining the DeWork board for AN DAO, responsible for organising & updating the board and being the point of contact for questions regarding the tool
- Facilitating the daily operations within the current AN DAO, in terms of tooling and bots
- Meta-governance point of contact for Balancer (based on the Wildfire proposal)
Concrete deliverables (iFun):
There are no concrete deliverables defined at the start of S3. Learnings from S2 were that Ops Squad provides the most value in navigating and solving complications that pop-up during the Season.
Recurring Deliverables (Lion):
- Amending Necessary Contributor Agreements in order to provide Forward Compatibility with DAO Transition
- Assisting HR in reviewing and issuing letters for different purposes to contributors
- Assisted in reviewing and Negotiating multiple Agreements with Aragon Vendors (AMMs, Exchanges, Smart Contact Auditors, External Advisors, Clients etc.)
- Aragon Branding and Intellectual Asset Review and Strategy for DAO Transition
- Assisting the Ops Guild in General Compliance Research and Implementation
Concrete Deliverables (Lion):
- Risk Analysis of Publicly Available Documentation of Aragon
- Review of Policy/Proposal Drafts prepared by Finance Squad
- Legal Wrapper Research/Support and DAO Structuring
- Data Management and Privacy Standards Implementation
- Contract Management Software Implementation
- Assisting with compliance and legal requirements of Ops wrapper
Additional deliverables (Lion):
As learned from S2, Legal Squad should be flexible in additional deliverables. During the last season, approx. 10 additional deliverables required attention of Legal Squad.
**Legal squad does not provide legal advice in any jurisdiction. Legal squad has not provided such advice in the past, it does not intend to provide such advice in the future. It only provides operational support for legal/regulatory aspects.
- Deliverable 1, Led by Fabs and supported by nocibambi End of Year Survey and Quarterly survey thereafter – understanding the satisfaction and needs of contributors to the new DAO
- Deliverable 2, Led by Henrystats and Supported by Fabs Product Dashboard – continue development, refinement and update of the competitor dashboard and creation of data for articles:
- Articles: Objective is to position Aragon as a Thought Leader on DAO creation. Therefore we will create articles to showcase:
- Article 1 [WIP], Led by Fabs Supported by Henrystats: Delivery of Dashboard containing DAO creation vs. DAO Activity vs. Chain creation & activity. — currently being worked on with COMMS
- Article 2 Led by Fabs Supported by Henrystats: Nuance of DAO Activity, limitations and opportunities
- Article 3 Led by nocibambi and Supported by Henrystats: How does DAO creation look like on-chain in different ecosystems? What does this tell us about the technical aspects of DAOs under different platforms? What does this imply for the concept of “DAO”?
- Article 4 Led by Fabs and Supported by Henrystats: The values of DAO activity, exploring what the data can show us for values of DAO activity across ecosystems and chains
- Article 5 Led by nocibambi and Supported by Henrystats: Frequency of DAO activity: exploring how often DAOs execute transactions, trends, seasonalities, and special events.
- Article 6 Led by Fabs and Supported by Henrystats: DAO Value, how valuable are transactions? Where are the most valuable active DAOs?n
- Article 7 Led by Sammie: Product overview, feature comparisons, roadmap analysis on DAO platforms in current competitor analysis scope, i.e., Syndicate, Colony, DAO Haus, Zodiac vs. Aragon
- Deliverable 3, Led by Fabs and supported by team, Data for other Squads – supporting other guilds and squads with their reporting and data needs.
- Deliverable 4, led by Sammie, Payment data – combining Dework and Parcel data to gain deep insight into the expenses of Aragon.