Emily Carter

Last month a paying user asked for a feature that would directly contradict the main use case of a product I work on. Not a small addition a change that would make it worse for every other user. I said no politely. He didn't cancel but he also stopped giving feedback and I've been second guessing that decision since.

The part nobody talks about is that "sticking to your vision" sounds clean in theory but in practice it means watching a paying user go quiet and not knowing if you were right.

So for those who've been in this exact spot: when a paying user asks for something that goes against a product's core do you say no and risk losing them or add it and risk the product? And the harder question: what did you actually do the last time it happened not what you think you should have done?

Launch day gets all the attention. The day after is the part nobody writes about, and it's the part I'm least prepared for.

The upvotes stop, the notifications dry up, and you're left with a product, some new signups, and a very quiet inbox. The temptation is to immediately start planning the next launch. I think that's a mistake the week after is when you actually learn whether the launch meant anything.

What I'm planning to do with those seven days: personally email every signup from launch day, ask one question ("what made you click?"), and read the answers before touching the product again. No new features that week. Just listening.

For people who've launched: what did you actually do in that week, and did it change what you built next? I'm especially interested in anyone who ignored the post-launch week and regretted it.