---
# System prepended metadata

title: The MetaXelerator

---

# The MetaXelerator

The MetaXelerator is designed to onboard new projects into the Ethereum web3 ecosystem with the goal of adding new DAOs/communities to the DAOhaus platform. By enabling individuals or groups to start **'micro-event' local meetups** via funding from UberHAUS, a local-area recruiting machine can be created that incorporates the entire Meta-Ecosystem (DAOhaus, Raid Guild, MetaCartel) and help to spread awareness of the incorporated brands.

### Why Local Events?
Local events have great potential to build strong in-person communities around DAOs and can be foundational in scaling up much larger events around the world. Forming local communities around DAOs, or more specifically DAOhaus, can also lead to IRL DAOhauses, which can support contributor co-working spaces and streamline both contributor and project onboarding. Ultimately the live events should be seen as a tool for promoting the MX program and creating more legitimacy in the space.

## MetaXelerator Flow
The MetaXelerator flow consists of clear and concise steps that create a highly efficient process for new projects to deploy fully functional products and communities.

While the process highlighted below outlines steps that incorporate full funding and development rounds utilizing the Meta-Ecosystem, not all steps will be relevant for all projects. Some projects may have developers to build the product, funding to hire Raid Guild on their own, or both and just looking to supplement their processes.

**MetaXelerator process:**

![](https://i.imgur.com/DiiaLcn.png)


**Step 1:** A MetaXelerator Meetup is held in a MetaXelerator Host's local area and a new startup is looking for assistance.

**Step 2:** The MetaXelerator Host connects the project in the DAOhaus Discord and introduces them to UberHAUS. The project then applies for a UberHAUS grant to cover the costs of a Raid Guild consultation and maybe for the specs to be built(?).

**Step 3:** The Raid Guild consultation goes well and specs are built for an MVP.

**Step 4:** With the specs built, the project applies for a MetaCartel grant. 

**Step 5:** The project is approved for a grant and should then create a DAO on the DAOhaus platform in order for the core team to manage the grant.

**Step 6:** Once the grant is secured in the project's DAO, Raid Guild is hired to build the MVP.

**Step 7:** After the MVP is built, the project can launch its own token - giving a portion of it as a membership tribute to UberHAUS.

**Step 8:** With the project's DAO established and MVP built, it then applies for a MetaCartel Ventures pre-seed round.

**Step 9:** Once pre-seed is secured in the project's DAO, it then hires Raid Guild to build the beta version of the product.

**Step 10:** The project now has a DAO, beta product, token, and UberHAUS membership, so the project launches a PoolHAUS in order to build liquidity and community around the token.

**Step 11:** With PoolHaus built, the project leverages its partnerships with MetaCartel, DAOhaus and Raid Guild to promote the project and its PoolHAUS, to ultimately build liquidity for its token and a strong community around the project.

**Step 12:** Once the PoolHAUS and community building is a success, the project now has the necessary support to deploy and scale the full release of its product.

## Extracting Value
Each project that comes through the MetaXelerator process would be leveraging services provided by Raid Guild, making use of MetaCartel Grants and Ventures, joining UberHAUS and giving a portion of their native tokens to the UberHAUS treasury, and bringing more value and users to the DAOhaus platform.


## Starting a MetaXelerator Meetup Event

Anyone can start a local MetaXelerator meetup by creating a proposal and requesting funding from UberHAUS. The meetups can be hosted on the Meetup app, Eventbrite and/or using Kickback.

**Spin up a MetaXelerator DAO for the MetaXelerator Hosts.**
*Full-time jobs have the potential of forming from this venture.*

Offering proper incentive with long term benefits will be vital to the MetaXelerator's success.


### Incentive Model for MetaXelerator Hosts

- Offer grants to cover the costs of the meetups and pay to cover the time spent organizing and hosting the meetups.
- Create a MetaXelerator DAO that can join UberHAUS and request funding to compensate the MetaXelerator Hosts.
- Give a special role for MetaXelerator Hosts.
- Incorporate POAPs (for both the Hosts and attendees) for each event organized by the MetaXelerator Hosts.
- Bonuses for MetaXelerator Hosts based on KPIs


### Meetup Event Template / Standardized Process
Meetups should be standardized to an extent where successful process flows are implemented based on collected KPIs. Each MetaXelerator Host or Host Group can still use the opportunity to market their own projects and/or recruit into their DAOs, which still adds value to the Meta-Ecosystem. Although, if the MetaXelerator Hosts do not perform well or meet the required minimum of projects onboarded, they will lose their ability to host these events.

**Each MetaXelerator event should have:**

- An official MetaXelerator banner (Need designs - Adrienne maybe)
- Basic guidlines for the event flow (coming soon - from Jeremy)
- A POAP to distribute to the Attendees (Need POAPGOD)
- Complimentary food and/or drinks (UberHAUS Grant/MetaXelerator treasury)


### Pitch Template
A template for pitching these events is required, something that can be used for advertising it and displaying it within event apps.


## Tracking KPIs

**For the MetaXelerator**

- how many make it through the process
- what kind of projects make it through
- at what point do projects fall off
- average funding received for initial MC grant
- average funding received for MC ventures
- how is the funding spent


**For the projects**
- community/user growth
- native token distribution
- native token value
- value flow throughout the project

## Scaling Ideas

### IRL DAOhauses
Local community owned or rented co-working spaces that make it easy to recruit more contributors and onboard new projects into the MetaXelerator.

### Digital MetaXelerator
Digital MetaXelerator events can easily be incorporated into the program flow and will be a major driver for acquiring more participants.


--- 

# Appendix 

### Why go IRL, when Web3 is online?  
**The DAO and Web3 space lives and thrives online (IRL vs URL), enabling people from all over the world to learn, participate and build. Won't IRL events be limited in the scope of communities we can reach?**

Yes, DAOs & Web3 enable anyone to participate from everywhere due to its online nature, but we want to reach out to people who aren't already aware of this movement online. 

Our hypothesis here is: 
1. Despite its small reach, IRL events are high-quality interaction points that can effectively explain and convince people about the Web3/DAO movement
2. We can scale these small-reach, high-quality IRL events globally in a operationally-light manner. 

Our efforts in the first few pilots should aim to measure: 
1. What is the quality of MX IRL Events? 
    - % / # of attendees who were not in Web3/DAOs before MX
    - % / # of attendees who understand Web3/DAOs after MX 
    - % / # of attendees who became active in Web3/DAOs after MX 
3. Does the operational overhead outweigh the benefits of running MX IRL Events? 
    - Man-hours involved in starting a "Chapter"
    - Budget involved in starting a "Chapter"
    - Man-hours involved in organising an Event
    - Budget involved in organising an Event
    - Man-hours involved in retaining / keeping alive a "Chapter"
    - Budget involved in retaining / keeping alive a "Chapter"

### How do we make Hyper-localisation work?
**If we go hyper-local into each community and each community is different, how do we make hyper-localisation work for us?**

Some communities that are more well-versed in DAOs & Web3 (e.g. Denver) and some will be less well-versed (e.g. Asia). We will need different 'syllabuses' or content modules for communities with different competencies and interests. 

For instance, perhaps when a new Chapter is set up, we have a standard flow of events. 
1. Presentation on Web3 & DAOs
2. Fireside Chat of Members in a DAO (e.g. RaidGuild, MetaCartel, etc.)
3. Workshop on Forming a DAO 
4. ...

This list is just for illustration, but can be worked on further. As communities get off the ground, we can leave it to "Chapter" leaders  (Meta Guides) to plan as they see fit. 

### 'Investment' Thesis
**As an Accelerator, what is our investment thesis?**

We want to accelarate and help projects that are 
1. In Web3 or looking to enter Web3
2. Building tools for communities OR have community as part of their product/solution 

For these projects, there will be a good fit as: 
1. Expertise: We know how DAOs work, how to set up one, what issues they face, what problems they are looking to solve. We can advise them on what makes sense and what doesn't. 
2. Connections: We are the people in the space. If they need to build something, raise funds, find users, we can help them find their way. 
3. User Adoption: We are the users.
4. Fundraising (Community-owned): There are many avenues to raise money from people that are aligned to your cause (such as Grants, MCV, DAO angels, etc.)