How I Ship an MVP in 2 Weeks - Part 3 From Code to First User

Disclosure: I work on OpenNomos, building developer tools and tracking my indie journey.

This is Part 3 of my 01MVP series. In Part 1 and 2, I covered why MVPs matter and how to pick the right first feature. This time, let's talk about actually shipping — the part where most projects die.

The 2-Week Rule

After spending 3 months on a project nobody used, I made a rule: if I can't ship something usable in 2 weeks, I'm building too much.

Here's the reality check: your first users don't need a polished product. They need one thing that works. One feature. One workflow. One problem solved.

My current project, 's observation that "bad writing becomes more valuable in a world of AI-assisted writing." The same applies to software: rough, real, working software stands out in a sea of polished AI-generated landing pages.

What I'm Building Next

With 01MVP, I'm following this same 2-week rule. Next tool, next weekend. Each tool ships when it's useful, not when it's perfect.

The hardest part isn't the code. It's resisting the urge to add "just one more feature" before showing it to anyone.

Ship it ugly. Ship it Monday. Ship it now.

This is Part 3 of my 01MVP series. Catch Part 1 and 2 on the OpenNomos blog.