---
# System prepended metadata

title: Boost Market Feature UX
tags: [Product]

---

---
tags: Product
---

# Boost Market Feature UX

#### Links
[Figma Prototype - Boosts v1](https://www.figma.com/proto/8eBBDVPuJPfntNfHq7nWdS/Specs-Boost-Market?page-id=0%3A1&node-id=12%3A598&viewport=3062%2C427%2C0.1584220826625824&scaling=scale-down-width)
[Boost submission form data](https://hackmd.io/fJcp8NWrRAqTU3FRbWdQ1w)
[Figma File](https://www.figma.com/file/8eBBDVPuJPfntNfHq7nWdS/Specs-Boost-Market?node-id=0%3A1) - has full specs (including empty states, etc.)

## Overview 
The boost marketplace will be similar to an app store for the DAOs. It will provide a variety of Boosts that can augment your DAO as well as Services that can help with a variety of things like web3 skills, legal consultation, etc. 

Definitions:
* Boosts: code-based, expand on the functionality of a DAO
* Service: human-based, adds an ally connection between two DAOs to provide a service
* Target DAO: DAO that will receive a Service or install a Boost
* Service DAO: DAO that is providing the Service

## Outline of Feature Roadmap
*(outlined by Adrienne, opened to all changes)*

### Pre-v1
* Information out into community, getting boost developers interested in participating? Or wait till feature is built out fully?
### v1 
* Basic Marketplace into navigation in the app 
  * Access points from hub and in DAO navigation
  * Market landing page
    * Search 
    * Tags
    * Filters 
    * Categories
* Allow for paid Boosts - one-time, name your price 
* Installation workflow
* Updates for Boost page in DAO
* Form for community members to submit boosts
    * Workflow for submissions:
        * Code vetting
        * Communication with boost dev
        * UberHaus proposal submission and followup
        * Boost into marketplace

### v2 
* Full Boost payment options / funding proposal vs. personal wallet workflow
    * Subscription/streaming
    * one-time, base or more
    * Free 
* Allow for paid Services - buy service workflow
  * One-time payments
  * Free 
  * Update to Allies page in DAO
* Update to marketplace for Services
* Report Boost - maybe just into a discord channel to review? 
  * This may depend on when gatekeeping for new Boost is lifted, first Boosts will be likely trusted enough this won’t be needed

### v3+ 
* TBD - path for less gatekeeping of Boosts/Services into market? 
* Services streaming/subscription 
* Boost creation workflow 
* Service creation workflow
* List will depend highly on feedback 
    * Curated/paid Boost/Service space 
    * Boost/Service management page for boost builders 
    * Boost/Service usage info

# Feature Overviews & Workflows
## Boosts
Here is the workflow so far for Boost installation on a DAO, feedback open on any part. This can also be found on the ‘boost/revenue sprint’ figjam board (images in here look terrible). 

https://www.figma.com/file/9tr0r9qscTOTLL3Q2ZSF1g/Boost-Market?node-id=0%3A1

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

The most notable thing to think about with Boosts is considering support as the market expands. The more Boosts, the more support will be needed. Is the dev responsible? Could Boost Foundry be used to help with this? 

## Services

Services will be provided in future version of the marketplace. Considerations around how they will fit into the Allies page and the future of DAO to DAO communiation will be considered. 

https://www.figma.com/file/9tr0r9qscTOTLL3Q2ZSF1g/Boost-Market?node-id=0%3A1 

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

### Notes on this Direction/Workflow
* Choose/buy Service will create a funding proposal in Target DAO
* After proposal passes > proposal created in Service DAO 
  * This allows DAOs to pick up only the work they want to
  * Gives the asking DAO the ability to get their funds back if there is no response from the Service DAO 
* The explore page could also allow for filtering on DAOs that supply Services
* To think about: point-of-contact information only available to see to members or publicly shown in the Ally space?

### Cons to this Direction
* More complexity in code to support the Boosts vs. Services
* Longer lead time to actually start working together 

## Other Possibilities
* From the jobboard project over in Raid Guild season 1 projects - this forum post came up that might make sense to think about in the Market ecosystem (and possibly include the jobboard s1 devs in on):
  * https://forum.daohaus.club/t/dao-tasks-a-better-way-to-show-how-much-work-there-is-to-do-and-money-on-the-table-for-those-willing-to-contribute-to-daos/1151
  * Job or Gig postings seem like a natural step from the Service model, although will likely need to break from the DAO to DAO model, allowing an individual to apply for a gig (ex. ‘we are looking for a front end dev to join our DAO’) 



