The Crowd Supply Guide: The Life Cycle of a Crowd Supply Campaign
Most of a Crowd Supply campaign takes place via a private git repo on GitHub. We use project repos as a simple way to manage content and collaborate on project details, so there’s no need to already be a professional git or GitHub user. A project manager will shepherd the creator through batches of issues which are the tasks that must be completed before, during, and after a campaign.
Crowd Supply will review the submission and ask any questions needed to determine suitability. If the submission is accepted, Crowd Supply will return a Statement of Work (SoW) for your signature.
Once the SoW is signed, Crowd Supply will assign a Project Manager (PM) who will create and subsequently manage a private GitHub repo for your project. Those PMs will be your main points of contact for the duration of the campaign, and that repo will be your primary means of communication, organization, file storage, and content staging.
When your GitHub repo is up, you’ll start creating your pre-launch page and preparing the foundation for a crowdfunding campaign by working your way through a first batch of GitHub issues:
Mouser setup: provide basic company documentation so we can begin the process of getting you set up as a Mouser supplier
Images and prototypes: provide images for the pre-launch page, if possible, and send a prototype that Crowd Supply can photograph, film, and possibly share with reviewers
Pre-launch page: provide basic information so Crowd Supply can populate a "coming soon" page
Outreach plan: gather information and engage resources for your campaign's outreach effort
Once your pre-launch page is accessible to the public and gathering email subscribers, it’s time to begin working toward your campaign launch:
Pledge levels: detail each of the products that will be available through your campaign
Funding goal: determine how much your campaign must earn to be successful
Comparison table: generate a table comparing your project with its competitors
Campaign page draft: prepare a draft of the content that will appear on your campaign page, including value propositions, features & specs, images & videos, documentation resources, etc.
Video: write an outline for your campaign video or, if Crowd Supply is producing your video, provide specific project details that the video should cover
Export compliance: provide details that our compliance team can use to classify your product for export (country of origin, encryption functionality, part numbers, etc.)
CE guidance: determine European certification requirements, if any
Plan weekly project updates: make a list of weekly updates you plan to post during the campaign, outline the first few updates, and draft a launch-announcement update that we can post as soon as your campaign goes live
Wholesale order: work with Crowd Supply to prepare for post-campaign sales through your project page and through Mouser's website
Coordinate with your PM to launch your campaign on an agreed-upon date. During the campaign, you will work through the next batch of GitHub issues:
Field reports: reach out to your backers, identify those who have used your project in particularly interesting ways, and ask them to produce a field report (or introduce us so we can ask them)
Orders Are Filled
As orders ship to backers, we will prepare for long-term sales:
Prepare your project page for stock status: turn your crowdfunding page into an informational page for items that ship from stock
What's next: just because crowdfunding is done doesn't mean the project has to be. You can continue creating relevant updates, garnering Field Reports, answering technical questions from potential customers, tracking stock sales, filling additional stock orders from Crowd Supply (or Mouser), and, of course, launching new projects!
Question not answered here? Contact us to see how we can help.