Go-to-market checklist
Superteam, media, pre-commits, and launch-week cadence, from two weeks out to live.
6 min read · Updated Aug 2026
On this page
Plan distribution before the raise window opens. This checklist covers company materials, outreach, pre-commitments, launch announcements, and launch-day communication.
Track pre-commitments separately. Record which prospective backers have confirmed an amount and which conversations are still open. A pre-commitment is not an on-chain commitment.
Cadence preference. To maximize attention, Backable prefers new raises to go live at 16:00 UTC on Mondays, and announces the following week's raises at 16:00 UTC on Tuesdays.
Months to weeks before launch
- Take care of the basics, build the business. A functional website that conveys the vision, a demo, MVP or (ideally) a fully working app people can use, and docs they can read to go deeper. Keep an X handle relevant to the business, a professional LinkedIn, and an up-to-date pitch deck.
- Reach the relevant audience. Identify where prospective users already gather, such as industry forums, video platforms, social networks, or in-person events. Share a product demo and the raise terms.
- Ask for pre-commitments early. Contact prospective users, angels, venture firms, and liquid funds before launch week. Record the amount and status of each conversation.
- Contact your regional Superteam and relevant professional contacts. Ask for capital, distribution, media coverage, or introductions as appropriate.
- Build a public face. Reach out to Ownership Media, MCG Live, or any relevant outlet to book appearances. Cut clips from those hits and post them. Keep X active and interact with the Backable handle, they often interact back.
- Use relevant public events: hackathons, an Ownership Roadshow, or a Solana conference can provide product feedback, users, and public evidence of participation.
- Send Backable a blurb and an up-to-date deck with your launch date and raise amount, via Telegram (tg.metadao.fi).
Long-form pitch on X
Your Backable page is fixed at publication. An X thread can provide updates and answer questions. Recommended structure: (1) one-line problem, (2) what is live today with a link, (3) the deal in three numbers (goal, price, monthly budget), (4) your own risk case in two sentences, (5) link back to the raise.
One week before launch
- Initialize the raise on Backable. Create the paid draft by about T−6 days so MetaLeX, domain verification, and review are not a launch-day scramble, then finish create (entity + domain verify + Submit) so the raise is queued.
- Formally announce the ICO with an article that introduces the project and team (credentials and awards), explains the raise goals, and gives a tokenomics breakdown, monthly milestones, and revenue projections. Ordr's announcement is the reference: x.com/ordrtrade/…. Tag the Backable handle so the team sees it.
- You do not need to keep the launch secret before this post. It's the formal announcement with everything a contributor might want to know, meant to generate momentum going in.
- Contact Superteam, relevant publishers, and prospective backers with the announcement. Backable may share the article, a branded launch graphic, and the raise in the MetaDAO community channel.
Inside one week until launch
- Publish the schedule. Keep the X account active, share the raise in the MetaDAO community chat, and contact prospective backers. Include the date and time of the raise.
- Post a product video that explains the project and links to the raise. Ryvo's example: x.com/ryvonetwork/….
- Make the media rounds, Ownership Radio, MCG Live, or any other relevant outlet, and post the clips on X.
- Continue confirming pre-commitments and sharing the opening time.
24 hours prior to launch
- Backable posts a 24-hour warning encouraging early commits.
Launch day
- Post a graphic or video announcing the raise is live, with a direct link to your Backable page, on X and any other social channel where your community lives. Use every connection to amplify it.
- Notify confirmed prospective backers when the window opens. Team members who contribute personally should use their own wallets and review the same terms as every other backer.
Mechanism reminder. Distribution is separate from escrow. If the raise misses its goal, each backer can claim their contribution. The claim requires a transaction from the contributing wallet.