Year our newsletter open rates dropped below 15% even though we had great content. I spent three weeks testing subject lines and send times but nothing seemed to help. The numbers stayed low.

The real issue was that Gmail and Apple Mail started marking our emails as spam. Why? Because many people were ignoring them. We had thousands of subscribers who hadn t opened a single email in over six months. These were accounts ghosts in our database.

I decided to run a re- campaign. It was simple: a text-based email asking if they still wanted to hear from us. I gave them a choice click "yes" if they wanted to stay or let us know if they were done.

Only a handful responded with a yes. So I deleted over 4,000 contacts the next morning. It was genuinely terrifying to see our subscriber count drop so much overnight.. I didn t look back.

AI is becoming a major part of software development, but there's a challenge I don't hear discussed enough: how do independent founders get access to AI if they don't yet have the resources to integrate it into their products?

I'm an independent founder from Pakistan. I've already built and launched a SaaS platform, and my next goal is to introduce AI tools and agents that help creators, freelancers, and small businesses save time and grow.

I've explored startup programs from major AI companies, but I haven't secured support yet. Building independently means making difficult choices about what I can afford to develop next.

People always say that Tuesday or Wednesday is the day to release something to get the most attention. We chose to go against that advice and launched on a Sunday when there was less competition. We got way total upvotes than, during our last launch but the number of people who became paid users went up by two times. The number of visitors was smaller. The people who came had a much clearer interest. Has anyone else chosen to use a day with traffic in favor of a day with more interested people?

I've noticed that coming up with ideas is the easy part. Starting a new project is exciting, picking the tech stack is fun, and the first few days fly by.

Then you hit the boring parts, start doubting the idea, and suddenly you're already thinking about the next project.

I've definitely been guilty of this. Lately, I've been trying to focus more on finishing things than coming up with new ideas.

Curious how other indie makers deal with this. Do you have a system for staying focused, or do you just force yourself to ship?

I keep relearning the same lesson: the first version I am proud of is usually two or three weeks later than the version I should have shown people. What works for me now is a short checklist. Can a new user finish the one core task without me explaining it? Does it fail gracefully when they do something unexpected? Can I see what they did afterwards? If those three are true, I ship it to a small group even if the design is rough. Where do you draw the line between too early and too late?

Before vibe coding I would spend a lot of time just getting started

Now I can test an idea build a small prototype and see if it actually works much faster

The biggest change for me is not writing less code

It s being able to experiment with more ideas

I spent 3 weeks over-engineering a dashboard feature because I was terrified of launching a "clunky" product. I wanted every pixel to look clean, every transition to feel smooth, and every detail to represent my best work before letting real users see it.

When I finally shipped it, 0 people used that specific feature I spent days polishing. Instead, 5 users immediately emailed me complaining about a basic login bug I had completely ignored while focusing on aesthetics.

Felt like a complete waste of time to polish things nobody asked for. That s when I realized that perfectionism isn t high standards; it's often just fear of judgment. Pride doesn't validate your startup, traction does. Shipping fast gives you real feedback, while shipping late only protects your ego.

How do you mentally detach yourself from perfectionism when shipping your first version? Do you push raw code out early, or do you delay until it feels right?

It s kind of frustrating to set up cookie banners, especially when you re just trying to get people to sign up. Having visitors constantly see cookie popups adds a lot of friction.

How do you guys handle this? I still want to track where most of my visitors are coming from, but with GDPR, it feels like I have no choice but to add these annoying cookie banners.

How do you handle marketing when you're a developer?

I've noticed that for me, building the product is actually the easy part. I can spend hours working on features, fixing bugs, improving the UX, etc. But once I have something I'm happy with, I have to switch gears and start thinking about marketing, content, social media, getting users, etc. And honestly, that's the part I struggle with the most.

I'm curious how other developers/solo makers handle this.

Do you start thinking about marketing while you're building, or only once you have something ready?