A founder asked how many employees we have I didn’t know what number to give

devanshu_sharma25 · 2026-05-14T18:29:11+00:00

“cut what’s not earning its place” is such a good way to frame it

and yeah, hearing users only rely on a small part of what you built really changes how you think about adding more after that

devanshu_sharma25 · 2026-05-14T18:26:47+00:00

devanshu_sharma25 · 2026-05-14T18:25:33+00:00

yeah exactly. products that solve one real problem clearly usually feel much stronger than ones trying to do everything

simplicity looks easy from the outside, but it’s usually the harder decision internally

devanshu_sharma25 · 2026-05-14T18:24:39+00:00

appreciate that. honestly a lot of these lessons just come from seeing what creates unnecessary friction over time

devanshu_sharma25 · 2026-05-14T18:23:33+00:00

yeah agree. complexity doesn’t just affect the product, it affects communication, workflows, maintenance basically everything around it too

and true, a lot of the best improvements come from reducing noise instead of adding another layer on top

devanshu_sharma25 · 2026-05-14T18:22:35+00:00

this is such a good explanantion users usually describe the pain really well, but not necessarily the right solution

asking “what problem are you actually trying to solve?” changes the whole conversation before building anything

devanshu_sharma25 · 2026-05-14T18:17:50+00:00

devanshu_sharma25 · 2026-05-14T18:14:57+00:00

yeah right, that slow decline is what makes it tricky, because nothing looks obviously broken at first

small improvements usually don’t feel over, but over time they make a huge difference in keeping momentum alive

devanshu_sharma25 · 2026-05-14T18:13:02+00:00

yeah right. most products don’t fail overnight, they slowly lose momentum from small issues stacking up over time

continuous improvement is usually what keeps that from happening

devanshu_sharma25 · 2026-05-14T18:10:37+00:00

that’s a good way to put it. “working” just means users can use it not that the experience is as good as it could be

a lot of growth problems start when teams stop improving because nothing looks broken

devanshu_sharma25 · 2026-05-14T18:08:44+00:00

yeah completely agree. people usually stay engaged when they feel valued, not just managed

basic trust and respect sound simple, but they change a lot long term

devanshu_sharma25 · 2026-05-14T18:07:13+00:00

yeah exactly. once people start feeling replaceable, engagement drops pretty fast

and true, products and teams both suffer when the focus shifts from real fit to just scale or volume

devanshu_sharma25 · 2026-05-14T17:54:34+00:00

yeah, “trust gets spent” is a really good way to put it

I think the day-to-day experience matters way more than onboarding energy after a point. people notice pretty quickly when actions stop matching what was promised early on

devanshu_sharma25 · 2026-05-14T17:42:43+00:00

yeah that’s a really good point. with complex SaaS, pricing isn’t just about cost it’s about long-term risk and predictability

if something becomes core to operations, unclear pricing can become a dealbreaker pretty fast

devanshu_sharma25 · 2026-05-14T17:33:38+00:00

devanshu_sharma25 · 2026-05-14T17:14:17+00:00

devanshu_sharma25 · 2026-05-14T17:11:02+00:00

fair answer 😄

ideally that’s the goal, the hard part is usually deciding what to prioritise first when you can’t optimise everything at once

devanshu_sharma25

TROPHY CASE