# Admin Thoughts
As Drew put it, drops are the lifeblood of MetaFactory. They're how we can generate both revenue and attention. However, drops haven't been frequent or consistent as of late, while expenses have kept running.

To me, the main problem is that the DAO is unable to efficiently manage the high volume of inbound interest we receive. This is causing potential projects to be dropped or lost, resulting in missed opportunities and therefore missed revenue.

If we think of MetaFactory as a two-parts entity, with one part being the DAO which is responsible for driving innovation and inspiring creativity, and the LLC which is responsible for handling production and distribution, it becomes clear that we shouldn't have the same approach to both.

One is more about fostering a community and cultivating a culture, while the other is tip-of-the-spear sales. We should act accordingly with each.

## Creating a process to manage inbound interest

We need to develop a streamlined process for managing inbound interest and moving potential projects through the pipeline from initial contact to drop. This could include creating a system for tracking and organizing leads (e.g a CRM), establishing clear communication channels, and setting up regular follow-up procedures.

Also, we need to consider implementing a wholesale program for projects that cannot be turned into a MF drop, but are still of interest to us. Milfdad's production catalogue is a good place to start, but we need to formalize different "options" for projects to choose. This could provide an alternative way for the DAO to work with these projects and generate revenue, while still allowing us to focus on managing our core drops.

## Creating a process for projects to work with MetaFactory

In addition, we need to outline the process a project needs to follow to work with us. That should be crystal clear on our very homepage. A typeform would be ideal, asking relevant questions based on the information we need to decide whether we'll proceed forward as a drop, or counter-offer with a wholesale deal.

We could be asking for info that helps us decide two things:

1. If the project is a culture fit for us.
2. If it meets the requirements (communmity size, brand reach?) to be a MF drop instead of a wholesale deal.

Having that info would help us quickly triage which projects we want to spend some time on a call with to make a drop out of, and which projects we want to get back to with our catalogue for a wholesale deal.

## Scaling
Having a standarized process in place would enable us to 10x our output since anyone can be trained to use it. That means that as we dabble into other things, and as we start working on even more inbound, we can just get more contributors involved with the management of the drops. That resolves bottlenecks and allows people to meaningfully contribute to the growth of MetaFactory.

## Web3 Culture Drops
Apart from working with niche groups within web3 (e.g a specific DAO), we should aim to create drops that appeal to the general web3/crypto twitter audience and are based on all the new developments (news and especially memes) happening in the space.

We're already very in touch with the space on an individual level. However, we do not have sufficient speed when it comes to dropping merch relevant to current affairs of CT. Once we have a standarized process for drops in place, we can actually create "emergency drops" when something new happens and move them through the pipeline as a priority.