Sophia

I went through my credit card statement last weekend and finally canceled a software I ve been paying for over a year. I felt bad doing it because the product was great, but I only used it a few times all year.

It was a good reminder that churn isn't always caused by bugs or bad features sometimes people just outgrow the need for the tool.

If you run a SaaS how do you learn from users who leave politely without filling out cancellation surveys?

I used to write changelogs the day after shipping but i d always forget half the details and end up with vague updates.

Now i write a quick line every time a feature gets finished. It keeps everything clear and actually helps me notice if a feature is too confusing before going live.

When do you guys usually prep your update notes and do your users even bother reading them?

Building a real project is way better than copying basic tutorials but i'm not sure if an affiliate setup stands out to hiring managers.

I want to create something that brings actual cash to users, but worry it might look more like a marketing tool than a solid software build.

Would you recommend sticking with a monetization idea like this, or building something more technical?