Why I Sometimes Ship Before the Feature Is Ready

Shipping incomplete work sounds crazy. But in enterprise B2B, controlled imperfection can be your biggest competitive advantage. Here's when and how to do it.

There's a feature in Keka's exit management module that launched at 60% complete. No polish. Missing edge cases. Documentation was a Google Doc.

It became one of our highest-adoption features.

The counterintuitive logic of shipping early

In enterprise B2B, you're not competing for App Store ratings. You're solving specific problems for specific customers who have specific needs—right now.

Speed signals partnership: When a key customer says "we need X by next quarter," building in 6 weeks says "we're partners." Building in 6 months says "get in line."

Early users shape the product: That 60% version was shaped by 3 anchor customers who told us what the other 40% should be. If we'd guessed, we would have gotten it wrong.

Competition waits for no one: While you're polishing, someone else is shipping. In our market, being "good enough" first often beats being "perfect" second.

When NOT to ship early

This isn't about shipping garbage. It's about strategic incompleteness. Some things must be right from day 1:

  • Core value proposition: If the main job-to-be-done doesn't work, nothing else matters.
  • Data integrity: You cannot have bugs that corrupt or lose customer data.
  • Security: Non-negotiable. Even for early MVPs.
  • Trust moments: Transactions, confirmations, anything where users expect certainty.

How to ship early responsibly

1. Choose the right customers: Early adopters who understand the trade-off. Customers who say "I'd rather have something imperfect now than something perfect later."

2. Be transparent: "Here's what works, here's what doesn't yet, here's when it will." Honesty builds trust even when the feature doesn't.

3. Close the loop fast: If you ship 60%, have a plan to hit 80% within 4-6 weeks. Early shipping without fast follow-up is just disappointing people.

4. Collect feedback aggressively: Weekly calls with early users. Watch them use it. Understand what's actually blocking value vs. what's just not polished yet.

Shipping early isn't about cutting corners. It's about optimizing for learning velocity over immediate perfection.