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?
The short video format originated primarily on TikTok as "TikToks." Of course, it was then picked up by Instagram ("Reels"), YouTube ("Shorts"), and later other platforms began to embrace this trend of short, vertical videos (LinkedIn, X).
For these purposes, TikTok created a mobile video editing app and later a desktop version, CapCut. (2019) And guess what...
We gave users 14 days of full access expecting them to explore deeply. Instead, most signed up, used it for 10 minutes on day 1, and never logged back in until the Trial Ending automated email triggered .
When we shortened the window to 7 days (or gated key actions behind reverse trials activation actually went up because urgency forced immediate exploration.
Is the standard 14-day trial dying, or are we just structuring trial onboarding wrong?
when we finally launched our first project, i spent weeks obsessing over backend architecture and minor ui bugs, thinking everyone would notice those technical details instantly.
instead, the very first user feedback we got was about a completely random button placement that took us two seconds to code.
Building a working prototype with AI can feel like the hardest part is over. Then you come back a week later to change one small thing, and suddenly you re dealing with unfamiliar code, broken dependencies, or a feature that affects three other parts of the app.
I m starting to think the real test of an AI-built app isn t whether it works on day one, but whether you can understand and maintain it on day thirty.
For those building with AI, what do you do to make sure you actually understand what you ve shipped?
For two quarters our content team chased click-through rates by writing sensational headlines for our weekly email newsletter. Traffic spiked every Tuesday. Our downstream product signups remained completely flat.
We looked at our analytics. Discovered that those catchy headlines were meant to increase click-through rates but actually attracted curious casual readers who bounced within thirty seconds. They were looking for entertainment, not software solutions.
We rewrote our titles to be boringly specific about the technical problem the article solved. Traffic dropped by thirty percent. Our trial signups from those same emails doubled.
Optimizing for attention attracts the audience. Optimize for qualification instead. Let traffic numbers reflect your actual target market.
It's crazy how easy building something from scratch has become, but one thing I ve noticed lately is that more and more products look fresh on the surface, yet feel almost identical underneath.
I see this every day scrolling the PH daily dashboard, struggling to spot the real difference between dozens of products claiming to be the next Lovable with a twist, another distraction-free productivity app, or yet another AI voice assistant.
Just like with copywriting or design, product concepts are starting to feel homogeneous.
Me? Oh, for me it was definitely never a number. When I got my first job, I made my own lunch and used to eat it all by myself on the office rooftop. Partly because I didn't much like all the baseball talk at lunch, but mainly, of course, to save money. Then, about a year and a half later, I opened my own company. It has already been 22 years since then, and I still run the company myself.
So my conclusion is: it was about having enough money set aside to get me through the low seasons, rather than reaching a certain level of profit.
For the first year of our startup, it was just me and two co-founders writing code. We finally raised a small pre-seed round and decided to make our first big hire: a Senior Software Engineer.
We were thrilled when we snagged someone from a major tech company (think Google/Meta). On paper, they were a rockstar. The resume was flawless, they passed our technical interview easily, and we paid a premium salary to get them.
