Planned

Short build challenges that end in shipped work

We plan to run short challenges where you build something small, deploy it, and show it. Each one will end with work you can point to: a live URL, a repo, and a note on what you did.

None of these has run yet. There are no dates, badges, bots or leaderboards. When the first one is ready we will say so here and on WhatsApp.

How it will work

Three steps, once the first challenge opens

1. Say you are in

Message us on WhatsApp with the challenge you want. We will reply when a group is forming.

2. Build and post

Follow the plan for that challenge. Post what you shipped in the group, with the live link.

3. Finish with proof

You leave with the deliverables listed below and honest feedback from the people who built alongside you.

Beginner · Two days

Weekend first-build sprint

The entry point. Pick a small idea, build it with AI tools, deploy it, and write a short note on what you built and what you checked yourself.

What you would ship

  • One deployed project with a live URL
  • A public repo with a README and an AI-use note
  • A mobile screenshot
  • A proof note: what shipped, what AI did, what you verified
Beginner to intermediate · One week, about an hour a day

Seven days of deploys

Deploy one small thing every day for a week. A landing page, a form, a widget, a bug fix. The point is fluency with domains, hosting, env vars and launch checklists.

What you would ship

  • Seven live URLs, one per day
  • Seven repos with READMEs
  • One page that lists all seven
Intermediate · One month, five to eight hours a week

Five projects in thirty days

Ship five real projects in a month, each with a live URL, a repo, and a short write-up. Choose work that shows what you want to be known for.

What you would ship

  • Five deployed projects
  • Five repos with READMEs and AI-use notes
  • A portfolio page and one written case study
Intermediate · One month, about thirty minutes a day

Thirty days of visible proof

Post one piece of real work every day for a month: code shipped, a deploy, a message sent, a lesson learned. The habit is the product.

What you would ship

  • Thirty daily proof posts
  • A compiled proof log
  • Your best three proofs picked out for a portfolio
Intermediate, after at least one shipped project · Two weeks, one to two hours a day

Two-week outreach sprint

Take work you have already shipped and put it in front of real people. Pick a niche, write your scripts, send ten messages, track every reply. Where it leads is yours.

What you would ship

  • A niche statement and one niche-specific project
  • Three outreach scripts and a list of twenty qualified people
  • Ten messages sent and every reply tracked
  • At least one scope note or proposal sent
Advanced, after several shipped projects · Three months, about thirty minutes a day

Ninety days of building in public

Post daily about what you are building on X or LinkedIn: screenshots, numbers, failures, lessons. Consistency over a quarter builds a record people can find.

What you would ship

  • Ninety public posts
  • A content plan you can reuse
  • A retrospective with real numbers
Principles

What every challenge will hold to

Proof over promises

Every challenge will require shipped work. Attendance and good intentions will not count.

Small ships, often

Daily or weekly output, not one big submission at the end.

Peer accountability

You build for yourself, but you post for the group.