0→1 in Enterprise: Why It's Harder Than Startups

I've done 0→1 in both worlds: early-stage startup (Kashmakash) and enterprise organization (Keka's BGV module). They're both hard. But enterprise 0→1 is harder in ways nobody talks about.

The unique challenges of enterprise 0→1

1. You're selling internally first: Before building anything, you need budget, headcount, and executive sponsorship. My BGV pitch deck went through 4 iterations before engineering resources were approved. In a startup, you just... start building.

2. Legacy systems constrain your architecture: We couldn't build the "ideal" BGV module because it had to integrate with Keka's existing databases, authentication, and UI patterns. Every architectural decision carried legacy baggage.

3. Existing customers have expectations: Enterprise customers expect new features to work with what they already have. You can't break backwards compatibility. You can't "move fast and break things" when the things are production systems generating revenue.

4. Internal politics are real: The existing product teams didn't always want a new module competing for resources and attention. I spent as much time managing internal relationships as I did on the actual product.

5. Success criteria are messier: In startups, you know if you succeed—you get users and revenue. In enterprise, "success" might mean enabling a strategic account, even if the module itself isn't profitable yet.

What enterprise 0→1 taught me

• Patience is a product skill. You can't rush internal buy-in.
• Constraints breed creativity. Working within legacy systems forced better solutions.
• Relationships compound. The trust I built on the BGV module opened doors for later projects.
• Success is a longer game. It took 18 months to call BGV a "success." In startup terms, that's forever.

If you're doing 0→1 inside an enterprise: respect the context. It's not slower because people are dumb. It's slower because the stakes are higher.