Last week, a customer paying our highest tier threatened to churn unless we built a custom reporting dashboard that has nothing to do with our core workflow.
Saying no felt terrifying because of the MRR at stake. But saying yes would turn us into a bloated agency instead of a focused product.
for founders past the early stages: where do you draw the line between keeping enterprise revenue happy and protecting your product roadmap?
The users who email you angry or leave detailed feedback are actually doing you a favor even if it hurts. You can learn from them.
The real ghosts are the ones who quietly downgrade, cancel via the billing portal, and ignore every single automated exit survey you send. You're left staring at a dashboard with zero qualitative context on why they left.
for SaaS builders: what creative strategies or prompts actually get silent churners to tell you what went wrong?
When a free user complains, it's easy to ignore. But when a long time paid customer drop a harsh cancellation note or leaves a blunt review, it hits differently even if the overall churn rate is low.
Early on, every churned user feels like a personal failure of your product vision.
As you scale, do you naturally build a thick skin toward churn feedback, or do you just learn to separate product noise from signal?
Today, I read 2 messages that are contradictory in nature, and it seems like one branch is rebelling against the other.
Meta and other big tech companies are replacing human workers with AI.
Heineken, Aerie, Polaroid, and even Cadbury are riding the anti-AI wave, mocking Big Tech and positioning human-made creativity as the ultimate authenticity flex.
How do you think that these pro and anti streams can affect the evolution of AI and our perception of its use?
early on whenever a paying user asked for a specific feature, my immediate reaction was to build it to keep them happy. Our roadmap became a messy patchwork quilt of random requests.
Eventually, I realized those feature requests were often band-aids covering up a confusing core UX or a deeper workflow mismatch. Building what they asked for didn't even stop them from churning later.
for founders managing small teams: how do you filter out the noise of individual feature requests and stick to your core product vision?
We used to think high onboarding ratings meant we built something sticky. Turns out, getting a 5-star review during a test run doesn't mean people will actually open your app next week.
If a tool demands extra mental effort instead of sliding smoothly into a daily routine users just drift away.
How do you design your product to become an automatic part of someone's morning workflow?
I lived outside Japan from 2011 to 2023. The first few years were basically digital nomad life, running my company remotely from wherever I was.
Eventually I figured out that all that traveling mostly just added to my own experience. The world didn't change because I moved around lol. What I really wanted was to make things that change something for other people, so I stopped moving and now I mostly stay home and build.
OP-ED? Recently I've been finding myself actually buying and downloading apps more than before. The common thread? They're all silly things that almost do nothing. I say almost because what they do offer is a bit of joy during my work day. Some of the recent apps I've purchased or downloaded are @Klack, Googly Eyes, @Docko, @Ball,@TabTab, and @NotchNook. Some of these do have productivity or quality of life improvements (looking at the last two) but others are simply about making the computer fun again. For example @Klack has genuinely made me more focused when I type and I've been able to zone in on work. It's like each clickity-clack is driving me closer to where I want to go and idk, the feedback just feels GOOD. The audio is also really nice, not sure how I can explain it, but feels very high-def for something that is mimicking a tactical feeling. All these apps remind me of a time where shareware and P2P ( @Limewire ) was more popular. Where you might be okay buying a CD or floppy and installing something fun on your computer, then telling (sharing) your buddy about it. And with the rise of vibe coding, I think we're going to see vibeware become a thing. Where users will create something fun, quickly, using AI tools like @Cursor, @Replit, or @bolt.new/@Lovable and then put it at a super low cost or have a free-trial (shareware). Those that don't want to pay, will create their own iteration of it and choose their own distribution method (P2P) but it won't eat at the original. It's my genuine feeling that the internet is about to become fun again (it's already started) and I'm curious if I'm the only one feeling this way and/or embracing it? What do you think? Is the era of vibeware a good thing? And if not why should we refute it? This piece was written with FKJ - Just Piano in the background.
