Ship 28 Projects in 2026

Hey you, thanks for stopping by. I've set myself a challenge to design, build and ship 28 projects in 2026 in the search for product-market fit. That's it, that's the plot.

Figure 1. Here's my perspective looking at this article.

I used to get stuck on one idea for years. Maybe you have too. It feels safe—like you’re making progress—but really, it’s just procrastination disguised as focus.

So for 2026, I decided to try the opposite.

Design, build and ship 28 Projects in 2026 is made as a public experiment in volume, accuntability, and transparency.

Three simple rules:

1. Ship, don’t perfect. Done is better than polished. If it works, it goes live.
2. Public by default. Failures, discoveries, everything documented. No hiding.
3. Iterate quickly. Feedback is data. Use it to pivot, adjust, or double down.

What counts as "shipped"?

Not everything has to be huge. But every project needs to meet some criteria:

• Live at a public URL (subdomain or standalone)
• Does something useful (even if small)
• Has a clear value proposition
• Someone other than me has seen it

Why 28?

Because constraints matter.

I have over a dozen of half-baked projects sitting locally. That’s enough to drown in options. I needed something radical to push myself.

28 is ambitious. Enough to force velocity, but not obviously impossible. Enough that patterns can emerge. If project 14 has the same problem as project 7, that’s data. If project 3 takes off, I can study why. Volume creates insight.