Stop adding features: talk to users instead
When growth stalls, the reflex is almost always the same: ship another feature. It rarely works, because the problem was never a missing feature - it was a missing conversation.
Feature-creep is a coping mechanism
Adding a feature is something you can do alone, on your own schedule, with a guaranteed outcome: the feature will exist. Talking to users requires someone else to show up, and their answer might be uncomfortable. So SaaS founders default to the option that feels productive and does not require anyone else's cooperation.
The result is a product that grows in complexity without growing in usage - more surface area to maintain, with no clearer signal about why people are not converting or sticking around.
Two very different responses to a stall
Adding features
- Guesses at what users want
- Increases maintenance and complexity
- Delays the uncomfortable conversation
- No new signal generated
Talking to users
- Surfaces the actual objection
- Costs nothing to build
- Creates a relationship, not just a data point
- Tells you what NOT to build
"If you cannot explain why a user churned without guessing, you have a conversation problem, not a feature problem."
What to do instead this week
Before writing another line of code, book five short calls with users who signed up but did not convert, or who converted but stopped using the product. Ask what they expected, what confused them, and what almost made them leave. You will learn more in those five conversations than in a month of speculative feature work.
Want to turn this into a daily habit? Join the GTM Gate beta.