Dear ph, am i a robot?
I connected everything you asked me to connect. I post here regularly. I comment on other people's threads like it's my part time job. I've upvoted, supported, replied, shown up on days i had nothing to say.
And still, 3 verification requests later, i'm sitting here unverified like a guest at my own party.
At this point i'm starting to run theories.
Maybe i'm too active and it looks suspicious. Maybe my account is being held to a secret standard nobody told me about.
Or maybe i'm actually a robot and nobody had the heart to tell me .
How do you get early users to give feedback?
Hey Product Hunt,
I just launched the closed beta of CoLaunchly for waitlisted users. It s a marketing co-pilot for indie devs that creates personalized launch plans, content templates, and channel strategies based on your app and target audience.
Now that it s out in the wild, I m realizing how hard it is to actually get feedback from early users. Even the ones who signed up seem quiet.
Seeking advice for customer acquisition
How is everyone keeping up with all the AI products?
I maintain 20+ open-source projects across 4 ecosystems. Should I have focused on just one?
I look at my GitHub profile and sometimes wonder if I'm doing this wrong
Here's what I currently maintain, solo:
WP Bones a Laravel-like framework for WordPress plugins. PHP, Composer, Blade templates. 169 stars, v2.0.3, active since 2018.
20+ Mantine UI Extensions React components for Mantine: Parallax (Apple TV card effect), Split Pane, Window (draggable/resizable), Rings Progress (Apple Watch style), QR Code, Onboarding Tour, and more. TypeScript, published on npm.
FinderGit a native macOS app that turns Finder into a Git-aware file browser. SwiftUI, no Electron, with inline diffs, Git actions, and AI commit messages. Free, in public beta.
octoscope a terminal dashboard for GitHub. Go + BubbleTea, with 7 themes (including a CRT phosphor mode), single binary via Homebrew.
Four languages. Four ecosystems. Four very different user bases. One person.
Why is it so hard to just say no to early customers?
When you're running a small project, every single user feels precious so saying no to a request feels like you're actively pushing them away. I remember keeping a user waiting for ages on a custom integration because I didn't want to admit I wasn't going to build it.
They eventually stopped replying and moved to another tool. Once I started giving fast, blunt answers even when it meant losing someone my workflow got so much cleaner.
Do you try to please every early user or do you draw a hard line early on?
Customer Who Left and Then Came Back
Someone cancelled last year. No drama, no complaint. Just gone.
They came back eight months later. I asked why they left and why they returned. The answer was the same thing both times. They needed something I did not have, then they did not need it anymore, then they needed it again.
The Spreadsheet That Ran My Business for Two Years
I had a spreadsheet with every customer, every payment, every conversation. It was messy and manual and I complained about it constantly.
Then I moved everything to a proper tool. It took three weeks. And I lost something I did not expect.
The Feature That Only Worked Because Nobody Used It
I built something that worked perfectly. Fast, reliable, handled every case.
It also fell apart the moment two people used it at the same time. A race condition I had never hit because I was always the only person testing it.