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, OpenNomos Json, started as exactly two tools: a Timestamp Converter and a JSON Parser. That's it. Two tools, zero bloat, one weekend of work. And people started using it immediately because it solved actual pain points.

What "Ship" Actually Means

Shipping isn't just pushing code. It means:

1. The thing is live. Someone can type a URL and use it.
2. It does exactly one thing. Not "it could do X, Y, Z eventually." One thing, right now.
3. You can measure if it works. Did someone actually complete the core workflow?

Everything else — analytics dashboards, user onboarding, dark mode — is noise for week 3+.

The Feedback Loop

The real value of shipping fast isn't speed itself. It's the feedback loop:

• Week 1: Ship → 0 users → "nobody knows it exists"
• Week 2: Share on Twitter/Build in Public → 5 users → "the JSON error messages are confusing"
• Week 3: Fix error messages → 15 users → "can you add a minify toggle?"

This is infinitely better than:

• Month 1-6: Build everything in silence → launch → crickets

The Scariest Part

The scariest part of shipping in 2 weeks is that people will see the ugly version. But here's what I learned: nobody cares about your messy V1 as much as you do. The people who do notice are usually other builders who appreciate the honesty.

In fact, I recently quoted @arvidkahl'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.