---
tags: v3, product, rfp
---

# RFP - Magesmiths (Sept 22 and beyond)

Discussion context:
- Current product RFP is too bulky
- There isn't enough product definition to guide the team well

## Some Possible RFP Options
### Post-Beta Button Up
- SDK team
- App team

Goal
- Fill in areas that need features still
- Make it flawless and Bug free

### Product Definition Team
- Determine what would take the team from beta > v1
- Define with user stories, product defintion documenation, etc. to help organize and guide developement
- Provide roadmap for v0.5, v0.6, v0.7 etc to get us to v1
- Stay around 4 to 6 weeks ahead of developers, but flexible enough to shift direction going forward
- Define process for how to make product decisions and have DAO approval
- Examples of decisions to make:
- Is the transaction builder the next thing to concentrate on?
- What are other first bolt ons we need?
- Are things like a Discord Notification bot integral enough that we as a team need to prioritize for a full v1 release?
- Defines projects for dev teams to circle around

### Project-Based RFPs
- Ex. Transaction builder - team of devs focused on this
- Bugs and refactor
- Core UI inhancements

Possibly devs can only be on 2 at a time to keep focus.

---

### RFPs

- How can we break work into smaller projects?

#### Contracts

- Updates from audit results
- Documentation

#### SDK

- Developer experience
- Features
- Testing
- Bugs
- Documentation

#### Design System

#### Apps

- User experience
- Features
- Testing
- Bugs
- Documentation

##### Transaction Builder

- Multi-step proposals
- Save configurations
- Share with other DAOs
- Needs design, development, testing and documentation

##### Admin

##### Hub

##### Summon

##### Other Apps

- Notifications
- Marketplace (boosts)
- Bolt-ons
- Explore
- Feed

#### Product

- Goto market strategy
- Migration plan
- Stay ahead of the project teams prioritizing what needs to be done next
- Should have an IRL jam at MCON

### Other

- DAOstillery
- DAO Bootcamp