---
# System prepended metadata

title: Work with MetaFactory

---

# Work with MetaFactory

**Some preliminary thoughts:**

1. How do we decide which projects we want to do a direct drop with vs wholesale deal? Objective (e.g units produced & cost coverage) or subjective metric (e.g culture fit, community reach)?.
2. We need to further document some parts of the internal process (e.g Shopify preparation).
3. Everything that we believe we need to explain over a call (e.g type of print and Kong-Chips) can be translated into useful content for a resource page.

---

## Intake Form
I've prepared a flowchart to visualize the intake form to create leads for us to follow through with in a streamlined and manageable way. The goal is to increase our efficiency and throughput.

![](https://i.imgur.com/NXrcLMU.jpg)
*[Link to Miro flowchart for better viewing](https://miro.com/app/board/uXjVPx3CVBs=/?share_link_id=350283560733)*


**1. Name / Handle**

**2. Contact information  (Email / Discord / Twitter / Telegram / Other)**
- Ideally we want as many of these as possible, but any of these is okay at least for the first contact.
 
**3. Who's the drop for**
- Individual
- Community
    - Is the drop authorized
        - If it's a DAO, we can ask them to link to a gov proposal
    - Estimated community size
        - Helps us decide whether it should be a wholesale deal or drop.
        - Can be objectively measured through Twitter followers/engagement or Discord members/activity.
    - Links to community places (Discord, Twitter, etc)
        - Other

**4. Brief description of drop idea**
- Can help us get a better sense of what they want to achieve, whether it's culture fit (e.g simple merch vs an innovative project)

**5. Type of garment**
- We can start off with what we know we can make for all the inbound and only work on new products in-house. Of course we can have flexibility if needed.

**6. Type of print**
- We can offer some options, but include the "Don't Know/Not Sure" option for those who can't choose. It's helpful if they know, but not an issue if they don't.

**7. Design Mock-Ups**
- Optional, but helps if they have something ahead of time.

**8. Estimated units of production**
- Can help give us a guesstimate of demand to help determine whether it should be a wholesale deal or a drop.

**9. Kong-Chips integration**
- If they want kong-chips, we need to discuss feasibility and placement.

**10. Preferred drop date**
- Doesn't have to be strict, but it's useful to know if they want to time their drop with something specific. Can help us determing if we can make it in time, and also help us prioritize.
- We can mention a minimum window of time we require as a reference.

**11. Preferred payment method (Crypto or Fiat)**
- Suppose we defer to crypto, but we need to know if a client has a different preference.

## Internal Process

I've prepared a flowchart to visualize the internal process we should implement to handle leads after they've filled in the form. Below you'll find the description of each step along with some notes/thoughts.

![](https://i.imgur.com/37SAAlR.jpg)
*[Link to Miro flowchart for better viewing](https://miro.com/app/board/uXjVPx3CVBs=/?share_link_id=350283560733)*

**1. Receive inbound from the form above.**
- We can start with Google Sheets as a first step, and iron out the process while we're working on integrating on MF.OS. Unless MetaDreamer can help us start in MF.OS directly.

**2. Assign/Claim ownership of a lead.**
- There should be a column/field where admins can claim ownership of or be assigned to a lead.
- An owner should move the lead through the entire process.

**3. If there's sufficient information from the form for the lead owner to categorize the request into something to evolve into a drop or a wholesale deal, we do.**
- If we need more information, lead owner reaches out and schedules a call with the interested party to learn more information so they can categorize. If they still can't, we bring the lead info to the core call.

**4. Once categorized, we need to get back to the interested party with a quote.**
- If it's wholesale, we calculate cost, add mark-up and we reach out.
- If it's a drop, we need to first discuss the options (pre-production vs on-demand) with the interested party and explain the pros and cons of each. Once the party decides, we get back with a quote.

**5. After our invoice has been paid, we begin production and QA.**
- If it's an on-demand drop, we skip to the next steps.
- If it's a wholesale deal, we ship the products when ready.

**6. For drops, while we're working on production, we should be doing the following:**
- Finalize drop date & time.
- Get product title and description from client.
- Prepare Shopify listing.
- Prepare drop announcement materials. Those can include:
    - Accompanying graphics/renders
    - Tweet(s)
    - Email Blast
    - Newsletter Feature



## Review

Here's what the complete flowchart looks like if we go from the very beginning (a client filling out the form) to the very end (a sale).

![](https://i.imgur.com/uizHaw4.jpg)
*[Link to Miro flowchart for better viewing](https://miro.com/app/board/uXjVPx3CVBs=/?share_link_id=350283560733)*

Overall, we can start with something simple and upgrade as we go based on what works and what doesn't. The core goal is to take a step towards a more streamlined system as opposed to having a fully-fledged solution from the first day.

## Feedback
Some feedback from Telegram chat:

1. We shouldn't have the DAO stuff in the beginning to avoid scaring people off.
2. People should be able to upload their design files if they have any, not just let us know they have them.
3. The above workflow doesn't address wearables/digital only collab at all.