By the time we sat down to count, Kaarya’s navigation had fifteen top-level destinations. My Work. Projects. Portfolio. Import. Goals. Teams. Workload. Dashboards. AI. Clients. Templates. Settings. WhatsApp. Users. Platform.
Fifteen. Every one of them was real. Every one was built, wired up, and working. None was a stub, a half-finished experiment, or dead weight we’d forgotten to remove. That’s what made the decision hard. If half of those had been broken, cutting them would have been janitorial work. Instead we were staring at fifteen finished rooms and trying to explain why a new user should only be allowed to see one door.
That’s the part worth naming plainly: a product with fifteen front doors doesn’t have a front door. It has a directory. Someone opening Kaarya for the first time doesn’t read “Goals,” “Workload,” and “Portfolio” and think “ah, a coherent tool.” They think “which of these do I need,” find no answer, and pick none of them. Fifteen options isn’t fifteen chances to hook someone — it’s one moment of paralysis, dressed up as choice.
So we needed to cut, and we needed a reason better than taste. Taste gets you an opinion; it doesn’t get you conviction when someone spent three weeks building the Workload view and watches it disappear from the nav. What we used instead was a straight competitive comparison: put Kaarya next to Asana, Monday, and Zoho, feature by feature, and ask where Kaarya was the only “yes” in the room.
Two places. WhatsApp-native working — updating tasks and projects from a WhatsApp thread instead of logging into a dashboard — and India-specific billing, GST-compliant invoicing and UPI. Everything else on the list, all fifteen destinations’ worth of capability, existed somewhere in Asana or Monday or Zoho too. We weren’t uniquely good at Dashboards or AI or Portfolio views. We were uniquely good at exactly two things.
Then we cut one of the two. This is being built as a free public test that takes no money from anyone, so billing has nothing to prove yet — GST and UPI matter enormously to an Indian SMB signing a contract, but they’re invisible to someone just trying the product for free. That left one differentiator standing: the project tracker your team updates from WhatsApp. Not a tagline we picked because it sounded good. The one claim left after we tried to falsify all the others.
The nav follows the claim. Four items: My Work, Projects, WhatsApp, Settings. Everything a new user needs to understand what Kaarya is and try the one thing it does that nothing else does.
The eleven that came off the nav — Portfolio, Import, Goals, Teams, Workload, Dashboards, AI, Clients, Templates, Users, Platform — didn’t get deleted. They got hidden. Every route still resolves if you type the URL. Every feature still runs underneath. One environment variable puts the entire fifteen-item nav back exactly as it was. We made this decision reversible on purpose, because deleting is an argument you only get to have once — you can’t easily un-delete three weeks of someone’s work to see if you were wrong. Hiding costs us nothing to reconsider next quarter. Deleting would have cost us the eleven things and the willingness to admit the cut was too aggressive if it turns out that way.
None of this makes the eleven free. Real time went into building Workload views and a Portfolio rollup and an AI feature, and as of this test, none of it is visible to anyone who lands on the product for the first time. That’s an honest cost, not a hidden one. Work that shipped is now work nobody sees. We think a product that says one true thing clearly is worth more right now than a product that says fifteen true things at once — but “worth more” doesn’t mean the eleven cost nothing. It means we decided, deliberately, what the front door should say, and left the rest of the building standing behind it, lights on, waiting.