Building Klyft: month 8

Eight months ago I started building an ERP system for a clothing brand I was helping with ops. It's now a completely different product called Klyft, aimed at a completely different audience, and launching in 2 months.

Here's what happened.

The original scope was wrong

ERP v1 had everything: sales, inventory, CRM, marketing, finance, fulfilment, reports. It was built in 6 weeks with Claude Code. It worked. The client used it.

Then they stopped. Not because it broke — because it was too much. They didn't need a CRM. They didn't need marketing analytics. They needed to know: what orders are shipping today, where are yesterday's packages, and why is there a payment shortfall of ₹12,000 in the COD reconciliation?

That's a fulfilment operations problem. Not an ERP problem.

What Klyft actually is

Three things:

1. A single dashboard connecting Shopify, Delhivery, Bluedart, and Shiprocket
2. Automatic COD reconciliation — no spreadsheets, no manual cross-checking
3. Exception alerts: stuck shipments, failed deliveries, address mismatches — found before the customer calls you

That's it. Nothing else. Every feature that doesn't serve those three problems is out.

What month 8 looks like

The core flow is built. Shopify webhook integration is done. Delhivery API is connected. Courier routing logic exists.

What's left: COD reconciliation accuracy (this is hard), onboarding flow for non-technical founders (most of my target market), and a billing system that doesn't make me want to quit.

Launch is June 2026. If you run a Shopify brand shipping with Indian couriers — join the waitlist at aaravshethh.in/klyft.

Everything else is still getting figured out.