... that they've simply accepted as "normal"? Those conversations have been far more valuable than any feature request I've received. I'm curious how other makers approach this. What's the single best question you've asked a customer that changed the direction of your product? Comment from Ghost Kitty(@ghost-kitty-9641558): Comment Deleted Comment from Shahroz Siddique(@shahroz_siddique): @stacywycof83995  That's exactly the direction we're moving in with Trackly. Managers still value having ... ... every single week?" Almost no one answered with "attendance" or "time tracking." Instead, they talked

... code, they talk to customers

... Same queue, totally different urgency. Telling those two apart automatically is the piece I don't have clean yet. In your setup, how are you deciding which of the 20 percent is allowed to wait for a window versus which should break into your focus? Comment from Aadil Ghani(@aadilghani): @virko_kask   This made my day, partly because you actually went and rebuilt the thing, and partly because "a file cannot tap my shoulder" is the cleanest one-line ... ... Same queue, totally different urgency. Telling those two apart automatically is the piece I don't have clean yet. In your setup, how are you deciding which of the 20 percent is allowed to wait for a window versus

... keep it around as the second pair of hands for bigger implementation passes. But if I could only keep one, it's Claude Code every time. Also pro tip, i connected codex via my own custom built MCP so claude code and codex talks

... hear the same advice: "build in public," "launch on Product Hunt," "find your niche," "talk to customers

... point, there are more users, and their expectations start to differ. So how do you decide which features will, or won t, be implemented? The most common approaches I ve personally seen are: Whether the request comes from paying vs. non-paying users Whether the feature aligns with the product vision (and isn t just fluff) How demanding the feature will be to build How many people are asking for it (size of demand) I worked in technical support ... ... figured other users could benefit. Whether or not I am correct will ultimately be determined by 1. Good marketing (for which I need help ... did I say HELP), and 2. User adoption. There's also a Users "needs vs

... your pricing model? Is it the fear factor? Are you worried about picking the "wrong" price and scaring customers away? Stressed about not having enough customer

... product-market fit Product-market fit is one of the overused terms in SaaS entrepreneurship. I read it in every book and blog post regarding growing a SaaS company yet I never really understood it till I started talking to my customers