General
p/generalShare and discuss tech, products, business, startups, or product recommendations
trending
•

7mo ago

What are some overpriced SaaS tools packed with features you don’t need but still have to pay for?

Just checking what SaaS tools you think have become overpriced because they are packed with features most users don t actually need.

Not necessarily bad products. More like tools where the core feature is useful, but the product has grown into a much bigger package, and the pricing now reflects all the extra stuff around it. Perhaps most users only need the core features, but the product makes you pay for a full suite with integrations, AI, this and that.
For example, some people think Photoshop is too much and switch to Canva instead.
What do you think? And how can founder create the next Canva from our discussion?

•

2mo ago

81% of our users have never changed a setting.

We tracked settings usage across 12,000 accounts over 6 months.

Never opened settings: 81%
Opened once: 14%
Opened more than once: 5%
Most-changed setting: notification frequency (2.1% of users)
Second: theme (1.8%)
Third: timezone (0.9%)

We had built 47 settings. The median user changed zero. The product was effectively one configuration for almost everyone, and we had spent years adding knobs that 95% of users never touched.

The lesson was not "remove settings." It was that defaults are the product. Every setting we added was a decision we were avoiding making for the user.

•

2mo ago

68% of our support tickets were answered by the user's second message.

We analyzed 9,300 support conversations over 8 months. Median first-response time: 4h 20m.

But 68% of tickets contained a follow-up from the user that included the answer a screenshot, an error code, a version number, or a clarification that made the original question answerable. The user had solved it themselves, or had found the missing detail, while waiting.

Median time between the user's first message and their second: 2h 10m. In other words, the user was doing our triage for us, slowly, because we asked too late.

We added a short intake form with three required fields: what you did, what you expected, what happened. Tickets dropped 18%. First-response time dropped to 1h 40m. The conversations that remained were more answerable on the first try.

•

2mo ago

The part of launching nobody talks about

I used to think the hard part was getting the product ready for launch.

Now I m starting to think the harder part is figuring out what to do after you launch.

You suddenly have feedback, random ideas, things that broke, things people liked, and things nobody cared about.

And it s really easy to start changing everything at once.

•

2mo ago

We hired 4 people. 2 were mistakes.

We made 4 hires between September and January. Two worked out. Two did not. Here is the honest breakdown of what we got wrong.

Hire 1 Senior engineer, referred by a friend. Worked out. Still with us. The referral was based on actual past work, not a resume.

Hire 2 Growth marketer, hired from a job post. Did not work out. Left after 4 months. We had hired for "growth" without defining what growth meant for us at that stage. They ran paid campaigns. We needed content and community. Wrong person for the actual job, and that was our fault for not knowing what we needed.

Hire 3 Customer support, promoted from within. Worked out. Knew the product, knew the users, needed no onboarding.

•

4mo ago

Three launches today shipped the same bug. None of them think it is the same bug.

I read three unrelated launches today. A menu bar monitor for coding agents, a desktop widget that runs scripts, and a mail client. Different teams, different categories, nobody talking to each other. Same bug in all three. The monitor falls back to a cached default when it cannot read the real context window, so it shows eighty percent when you are actually at sixteen. The widget keeps displaying the last value a script returned, so a job that died at 3am still looks healthy at noon. The mail client drew an empty window while it waited on its first query, so "still loading" rendered identically to "no mail". None of these are crashes. Every one is a system with no way to say "I do not know yet", so it asserts something instead, and the thing it asserts is always the confident-looking one. It keeps happening because unknown is expensive to represent. You need a third state in the data model, a third rendering in the UI, and a decision about what someone should do when they see it. Falling back to a default is one line. But the cost does not disappear, it just moves to the person reading the screen. Absent data is visible. Wrong data is invisible and confident, and people act on it. So the test I would run on anything with a display: is there a value your UI can show that means "I could not find out"? If there is not, then somewhere in your product missing already renders identically to real, and you will not find out where until somebody acts on it. Where does absent data currently render as an answer in yours?

🙇‍♂️ Which CRM fields are actually worth keeping?

I have been thinking about the difference between CRM data that helps people work and CRM data that just creates more admin.

A field should either:

  • change what someone does next

  • make reporting meaningfully better

  • be required for a real process

Otherwise, it usually becomes incomplete, outdated or ignored.

•

2mo ago

Does raising seed capital early slow down product-market fit?

When we secured our first small angel round, we immediately expanded our developer team and tried to build three major features simultaneously. Having extra capital made us focus on scale before we had actually validated whether users really needed those features. On our next project, we operated strictly on a lean budget for six months. Because resources were tight, we were forced to talk to customers daily and refine a single core feature until it had real demand.

Does early funding distract teams from finding true customer needs, or is capital essential to compete in crowded markets?

•

2mo ago

Do smooth hover effects actually ruin the user experience?

Spent time adding cool button transitions and modal popups to make our web app look high end. Visually it looked awesome but in actual testing people kept double clicking things thinking the app froze.

Turns out users just want instant feedback when they click something. As soon as we removed those extra visual delays everything felt way snappier even though the backend speed didn't change at all.

Are you guys still using smooth micro animations or do you prefer instant button clicks now?

How do you balance custom client requests with keeping your SaaS product scalable?

We were super excited when a couple of large accounts joined us early, but it quickly turned into a trap. We ended up spending nearly all our engineering cycles building specific workflows tailored just for them.

It started feeling more like running an agency than building a true software product, and our main roadmap got put on pause.

If you ve dealt with demanding early clients, what rules did you set to protect your core product focus?

First
Previous
•••
421422423
•••
Next