Over the past few weeks I've been having honest conversations with SaaS founders about one specific problem: how do you know which features your users actually use?
I wasn't pitching anything. I was just listening. Here's what I found.
Every founder I talked to described the same moment.
They ship a feature. Usage looks decent the first week. Then silence. And they have no idea if that feature is loved, ignored, or somewhere in between.
One founder put it perfectly:
"PostHog tells you what happened but not why. You end up cross-referencing events, funnels, and session recordings to piece together a story. The raw numbers rarely answer the actual question. That gap between 'here's the data' and 'here's what to do' is where most tools leave you."
Another founder building a status page product added:
"That sounds useful, especially if it can surface which features correlate with retention or conversion, not just raw usage."
And a third framed it in a way that stuck with me:
"The product stops feeling like analytics software and starts feeling like part of the decision-making process. That's a very different kind of value."
The data backs this up too.
73% of SaaS founders admit they built features just because competitors had them — not because users needed them. 84% targeted feature-focused messaging instead of outcome-focused messaging. And the average team is maintaining features that less than 2% of their users ever open.
That's not a small problem. That's weeks of engineering time wasted every month across thousands of SaaS products.
The tools exist. PostHog, Mixpanel, Amplitude — they're all powerful. But powerful isn't the same as useful for a small team.
One founder described going through PostHog's onboarding: 9 steps, a terminal command, a pricing decision — and landing on a completely empty dashboard with zero answers.
"Far more machinery than a small team needs" was how another founder described it.
So I'm building Featly.
One line of code. Automatic tracking. Plain English answers about which features your users love and which ones they ignore — and which ones actually correlate with retention and conversion.
No setup maze. No blank dashboards. No data analyst required.
We're building in public and looking for founding members who want to shape the product from day one. First founding members get lifetime 50% off.
Follow the journey on X at @getfeatly or drop a comment if this problem sounds familiar.
Hi Adebayo, Featly is actively recruiting founding members to shape the product, so a measurable 30-day commitment would have immediate meaning. I’m building Build Before 2030: a manually reviewed public record where makers claim a Founding 100 number, set one measurable 30-day milestone, and later add proof of what shipped. The first cohort is free. Featly feels like a strong fit. Interested? https://buildbefore2030.com
This sounds interesting. I'm currently in the final stages of getting Featly's beta ready, so a 30-day public commitment actually fits where I'm at. I'll take a look at Build Before 2030 and see if it's a good fit.
That timing sounds like a very good fit. A clean commitment could be something like “open Featly’s beta to the first X founders by [date]” — specific enough to verify, without exposing private metrics. The first cohort is free and manually reviewed; later proof can simply be a beta link, changelog, or screenshot. If anything on the page is unclear, let me know.
Yeah, the timing actually works out well. I'm finishing the V1 debugging now and then we're opening the beta to a small group of founding members.
I'll take a look at Build Before 2030 too — appreciate you sharing it.Yeah, the timing actually works out well. I'm finishing the V1 debugging now and then we're opening the beta to a small group of founding members.
I'll take a look at Build Before 2030 too — appreciate you sharing it.
That milestone is almost a perfect fit for the format. You could phrase it as: “Finish Featly’s V1 debugging and open the beta to our first founding members within the next 30 days.” Later, the beta announcement or changelog can become the proof—no private metrics required.
If you decide to join, submit it here and I’ll review it personally: https://buildbefore2030.com
This comment was deleted 24 days ago