Most people think users choose products based on features or price. In reality, support decides who stays.
A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.
Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.
Most people think users choose products based on features or price. In reality, support decides who stays.
A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.
Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.
I'm Aloke, Engineer #1 at Warp and lead eng on Warp's new coding features.
We're all in on agentic coding at Warp, but we also recognize that even the best agents need some human guidance. We just launched a suite of new features to help you closely iterate with agents code review panel, file editor, file tree, slash commands, WARP.md (or use your existing agent.md file).
At a time when everyone allows themselves to build any solution using AI, it is difficult to differentiate themselves, and makers are betting on more aggressive distribution.
Some differentiate themselves with good tech support, some build their personal brand as a founder, and some pay influencers.
I spent last month testing some assumptions like: founders want to meet others in-person. These assumptions failed as it's not as simple as that. There are some intricacies.
Well, I think will come back to the original asusmption that sort of worked. People liked being on the map, sharing their profile, and getting discovered.
It is a question of choosing between two evils for us now. Neither option is completely free of flaws.
Human: Recruiters with "gut feelings" who harbor unconscious bias. they reject excellent candidates who just didn't go to the "right" school or didn't just "click." Inconsistent, unfair, and un-auditable.
AI: Algorithms whose training datasets are themselves replete with historical biases. They increase the scale of discrimination at light speed, becoming so-called black boxes that end up rejecting qualified candidates for reasons that humans cannot even fathom.
We are truly deciding to exchange messy, subjective human prejudice for cold, ruthlessly efficient algorithmic prejudice. Is that really an upgrade?
I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team? My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product. I'm curious what you all think, would you hire a vibe coder?
I've been pretty impressed at the amount of products people (including myself) have been able to create which got me curious... do vibe coders or AI-primary builders have a place in a company or team? My thinking is the more technically adept would work on the core-focus while vibecoders can assist with other tasks that shouldn't be the main devs focus...like a potential feature add, minor changes, or even exploring different ways of modifying the existing product. I'm curious what you all think, would you hire a vibe coder?
Raycast just shipped a new release introducing Auto Transcribe, powered by @Granola, and two new AI experiments: Auto Models and Bring Your Own Models.
Do you spend 3 hours trying to find a clever .com before writing a single line of code? Or do you ship the MVP and slap on whatever domain wasn t taken at the time?
Do you spend 3 hours trying to find a clever .com before writing a single line of code? Or do you ship the MVP and slap on whatever domain wasn t taken at the time?
I might be missing some but I've been pretty much in love with @Lovable, @Cursor, @bolt.new and have been trying to use @Replit more and I honestly haven't touched @BASE44 too much but have heard good things. @chrismessina has nudged me to use @Windsurf for whenever I build another Raycast Extension! Currently I use: - @bolt.new / @Lovable - @Cursor - @Warp Curious what everyone thinks is the top one so far!
Product Hunt is great for discovery , but sometimes there are concerns about authenticity and trust when products are submitted by people not affiliated with them.
Would verifying domain ownership (e.g., via email or DNS) help ensure that only legitimate makers or teams can submit a product? Or would it add too much friction to the launch process?
I ve seen a lot of makers (myself included) start building with one idea, then pivot completely after talking to users.
I launched Waivify a simple digital waiver tool because I noticed yoga instructors and personal trainers still using paper or clunky PDFs for liability waivers. It started as a weekend build. Now it s used by solo business owners to simplify their client onboarding.
But along the way, I realized I wasn t just solving waivers I was helping service pros feel more legit and reduce admin anxiety.
I read in TechCrunch today that Perplexity is trying to dominate the Indian market, which could potentially increase the number of users (and thus compete with OpenAI).
Perplexity is trying to attract more users by offering a free 12-month Perplexity Pro subscription normally worth $200 to all 360 million Airtel subscribers. (That is the cost for them.)
We're having some internal discussions about what users would prefer - a wide range of niche products (maybe in more of an app-like ecosystem) - or an all in one platform. Interested in learning what the community things - primarily folks who use creator tools and publish / sell / create content!