100Startups Challenge

Docs

Delivery System

The delivery checklist and distribution system for each startup launched during the 100 Startups Challenge.

Delivery System

This page defines what needs to be delivered for each startup beyond just building the product.

A startup is not complete when the code works.

It is complete when the full delivery system exists around it:

  • the product is usable
  • the landing page explains the value clearly
  • the audience is identified
  • the content is published
  • the launch is distributed across the right channels
  • the follow-up system is ready

The goal is to make every startup launch repeatable.

Delivery principle

Each project should produce more than one output.

Every startup should create a small launch system made of:

  • a product
  • a landing page
  • a message for the target audience
  • long-form content
  • short-form content
  • scheduled posts
  • documented follow-up steps

This helps ensure that shipping is not isolated to development only.

Core delivery categories

Each startup should be reviewed through these delivery categories.

1. Research

Before launching, each startup needs a minimum research pass.

The goal is not deep market analysis. The goal is enough signal to make the product direction and messaging clearer.

Required research outputs

  • the problem being solved
  • the audience most likely to care first
  • the language that audience uses
  • existing competitors or substitutes
  • the reason this idea is worth testing now
  • the most likely distribution channels

Questions to answer

  • Who is this for?
  • What problem hurts enough to matter?
  • How are people solving it today?
  • Why would someone try this version?
  • What message should lead the launch?

2. Target audience

Each startup should define a clear first audience.

Do not launch to everyone.

Define:

  • primary audience
  • secondary audience
  • user intent
  • likely use case
  • desired outcome for the user

Minimum audience format

For each startup, write:

  • who the first user is
  • what they are trying to achieve
  • what frustration or inefficiency exists today
  • what promise the product makes to them

3. Product delivery

The actual product still needs a minimum delivery standard.

Product checklist

  • core workflow works end to end
  • there is one clear use case
  • the UI is usable enough to demonstrate value
  • major blockers are removed
  • the product can be shown publicly

This does not mean fully polished.

It means launchable enough to test.

4. Landing page

Every startup should have a landing page, even if it is small.

The landing page is the first explanation layer for the product.

Landing page checklist

  • clear headline
  • clear subheadline
  • explanation of the product
  • visual or product screenshot
  • CTA
  • target audience relevance
  • proof, reasoning, or benefits

Landing page goal

A visitor should understand in a few seconds:

  • what the product is
  • who it is for
  • why it matters
  • what to do next

5. SaaS or product packaging

If the startup is a SaaS product or software tool, the product should be packaged clearly enough for real use.

Packaging checklist

  • define the core offer
  • define the first version scope
  • define pricing approach if applicable
  • define signup or access flow
  • define the onboarding expectation

The product does not need a full business model on day one, but it should have a clear shape.

6. YouTube delivery

Each startup should produce one long-form YouTube output as part of the challenge.

YouTube output

  • one main episode documenting the build
  • one clear product story for the episode
  • one visible result by the end of the video

This connects the build process to the public narrative of the challenge.

7. Shorts and short-form clips

Each startup should also create short-form assets from the main work.

Short-form checklist

  • extract 1 to 3 strong moments from the main episode
  • create clips around one idea only
  • focus on payoff, not explanation overload
  • optionally point back to the full video or product

Possible channels:

  • YouTube Shorts
  • Instagram Reels
  • TikTok
  • X clips or short demos

8. Social distribution

Each startup should have a simple social distribution plan.

The idea is not to spam. The idea is to make sure the project is actually delivered into channels where attention can exist.

Core channels to consider

  • YouTube
  • Instagram
  • X
  • TikTok
  • LinkedIn
  • relevant communities
  • direct outreach if useful

Not every startup must use every channel equally, but each launch should define its best-fit channels.

9. Scheduled posts

A launch should include scheduled distribution, not only same-day posting.

You mentioned the idea of having 14 scheduled posts for each day or for each project cycle. That makes sense as a strong operating standard if it is structured properly.

Example scheduled post system

For one startup launch, prepare:

  • 1 launch announcement
  • 1 product demo post
  • 1 short lesson from the build
  • 1 audience pain-point post
  • 1 founder insight post
  • 1 progress or milestone post
  • 1 direct CTA post
  • 1 behind-the-scenes post
  • 1 clip from the YouTube episode
  • 1 clip from the product walkthrough
  • 1 quote or takeaway post
  • 1 feature spotlight post
  • 1 reminder or follow-up post
  • 1 recap post

This gives a structured distribution backlog instead of improvising every day.

10. Community and feedback loop

Each launch should make room for feedback.

Feedback checklist

  • comments monitored
  • notes captured from reactions
  • recurring questions documented
  • objections or confusion points recorded
  • next iteration opportunities identified

Distribution should feed learning, not only visibility.

11. Internal documentation

Every startup needs internal delivery notes.

Document:

  • what was delivered
  • where it was published
  • what assets were created
  • what performed well
  • what underperformed
  • what should improve next time

This is how the delivery system becomes reusable.

Suggested delivery checklist per project

Use this as the minimum delivery checklist for each startup.

Research

  • define problem
  • define target audience
  • identify competitors or substitutes
  • write the core launch message

Product

  • product is usable enough to demo
  • one clear workflow works
  • key blockers removed

Landing page

  • landing page exists
  • value proposition is clear
  • CTA is present

Content

  • one YouTube episode recorded
  • one final episode edited and published
  • one to three short-form clips created

Social

  • core channels selected
  • post copy drafted
  • 14 scheduled posts prepared if the startup is worth a full push

Follow-up

  • responses monitored
  • notes logged
  • lessons captured

Delivery operating model

The ideal operating model for the challenge is:

  1. research the startup quickly
  2. build the product fast
  3. document the process
  4. package the offer clearly
  5. distribute through multiple channels
  6. capture feedback and lessons

That is the full loop.

Rule of completion

A startup should not be marked complete just because the product exists.

A startup is meaningfully delivered when:

  • the product is visible
  • the message is clear
  • the audience is defined
  • the content is published
  • the distribution plan is active
  • the feedback loop is running

Next step

Over time, this page should evolve into a real delivery SOP with templates for:

  • launch messaging
  • landing page sections
  • social post variations
  • scheduled post calendars
  • follow-up review checklists