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

5d ago

My launch went out unfeatured and got 0 upvotes. What should I check before the next one?

I'm a solo developer. In August I launched a small side project here, and it was never featured, so it couldn't rank at all. It finished with 0 upvotes and 1 comment. My earlier launch, a job-search tool, got only a few upvotes back in July.

Looking back, I think I made two mistakes. I launched without checking whether it would be featured, and I didn't spend any time in the community beforehand. Since then I've been active here daily for about three months.

For makers whose launches were featured: what did you change in your listing (tagline, gallery, first comment, topics) that you think made the difference? I'm especially curious whether anything specific helps a niche or experimental product get featured.

•

2d ago

When does adding more features start hurting your product instead of improving it?

We kept listening to customer feedback and adding features to make our product more useful. Every request seemed reasonable and shipping new functionality felt like progress. But over time the product became harder to navigate. New users struggled to understand where to start while existing users only relied on a small portion of what we had built. It made us question whether we were solving more problems or simply making the product more complicated.

For founders building SaaS products how do you decide which feature requests deserve attention and when is saying no better for the product?

•

3yr ago

From $0 to $5k after a year Indie Hacking. The biggest takeaways.

After over a year of Indie hacking, we've finally hit my first Indie Hacking goal for http://senja.io... $5K MRR Biggest learnings: ##1. Ship fast, fail fast Since we released Senja, I've updated the app over 2,000 times. We're working in a very competitive market with a very low moat, so instead of building just another product, we decided to create the best product in our space. That meant: listening and building customer requests trying things nobody else is doing shipping fast and failing even faster Now we have a product that is one of the best tools in the market, and because our users love the product so much, word of mouth has started to take off. Focusing on product primarily instead of marketing meant that it would take much longer for growth to kick in. But because we have 100s of happy customers and they keep on recommending us, growth is starting to ramp up. We're also constantly experimenting with our marketing. We've tried dozens of things, from shitposting on Twitter to partnering with website builders. A lot of the things we've tried have failed horribly, but the few that worked have worked really well. ## 2. Separate Engineering and Marketing The biggest mistake we've made marketing wise is probably building our marketing site from scratch with code. That meant every change to our marketing site would lead to a back and forth between me and my cofounder. He'd need to change something but couldn't till I was free. Because of this, we couldn't add marketing pages and other resources as quickly as we needed to. Our SEO and content marketing have suffered. Adding a headless CMS didn't help either. Whenever we wanted to try something new, we'd have to build it twice. Once in code, then in our cms. Now we're rebuilding our entire marketing site with Framer (releasing this week!) so that all marketing can be done independently from dev work. ## 3. Start Reporting Up until two months ago, I didn't understand just how powerful reporting is. For most of Senja's life, we tracked signups + customers per day and also asked people where they came from (search, social, ads etc). But we never had concrete reporting in place. To prepare for the road ahead, last week my cofounder and I sat down and spent a day creating reports and my mind has already been blown. Now we know: which marketing channels are working best for us. how long it takes the average user to go from signup upgrade. how many users go from paywall to upgrade how many users we can upsell who our top personas are And much more. If I could go back and do one thing differently, it would be have concrete reporting in from day 1. # Next steps I'm feeling extremely optimistic about the future. SEO is still one of our best performing channels, so we're going to be shipping a lot more help guides, resources and blog posts in the upcoming weeks. We now get over 500 signups per month but less than 10% of them upgrade. So we'll be focusing more on customer success too. We're going to get much more aggressive with our marketing. We'll be: going toe to toe with our competitors reaching out to twice as many people through social media, cold outreach et cetera launching new things every month running many more experiments collaborating with many more awesome creators. As always, we'll be sharing every interesting thing we learn and try in public The support from the build in public community so far has been overwhelming. We'd never have gotten started without Twitter and Indie Hackers. The inspiration, motivation and critique from the community is what's kept us going for a year. Now I'm feeling better than ever, and I'm ready to take our little business to the next level.
•

2d ago

At what stage did manual founder-led support start slowing down your actual product development?

Answering every support ticket directly as a founder gave us incredible insights into real user bugs and UX confusions early on. but now that active accounts are growing, spending three to four hours a day answering repetitive onboarding questions is completely pulling focus away from core development.

for small teams, how did you transition from answering every query manually to building scalable self-serve help centers without losing that personal human touch?

I Tracked Every "Quick Question" for a Month. 74% Took Over 10 Minutes.

I started timing every interruption I labeled a "quick question." Slack messages, DMs, taps on the shoulder.

The average was 11 minutes. The longest was 40. Most of them required context I had to rebuild from scratch because I had been in the middle of something else.

I took 14 freelance projects in one year. Tax season showed I'd worked twice as hard for less money.

Every project felt like an opportunity small ones underpriced ones ones outside my expertise. My calendar was full and I felt important. Then the numbers came in. I started declining anything below a rate I set in advance. Income went up hours went down.

The opportunities weren't bad. I was using busyness to avoid the scary work of pricing myself properly.

For those who've started saying no: was it the requests' fault or your inability to prioritize? And what are you doing right now that you'd drop immediately if you were honest about its value?

•

9d ago

Why do coding agents always try to be over helpful instead of just doing exact task you assigned?

You ask for a quick script addition, and suddenly background logic, helper functions and folder structures are completely rearranged without permission.


It feels less like a coding assistant and more like a coworker who won't stop uninvited cleanups.


How do you lock down your agent workflows so they only touch what you explicitly point to?

•

2d ago

how much of your product roadmap do you share publicly before actually shipping?

sharing weekly progress and feature roadmaps on public forums creates incredible community excitement and gives us early validation before writing complex code. however, last month a larger competitor built a toned down version of a feature we teased publicly weeks before our own release was ready for beta testing.

how do you balance the momentum of building in public with protecting unique feature concepts until they are fully polished?

•

2d ago

I Asked the Agent to Plan Before It Coded and Saved Three Days

I used to describe a feature and let the agent build immediately. It felt fast. It wasn't. The architecture got decided implicitly by whatever the agent tried first.

When that first approach was wrong, everything built on top of it was wrong too.

First
Previous
•••
138139140
•••
Next