They paid more than anyone else. They also demanded more than everyone else combined.

Every week brought a new urgent request. Every feature became a negotiation. Every call ended with a list of things I needed to do for them specifically. I had become their vendor, not my product's founder.

I have developed a few saas. Most of which were AI based saas and they needed AI to produce output. I wanted to run lifetime deals on those saas, but there was a problem that for how long can I sustain those users? I have been through a lot of lifetime deals platform to see if those were good fit for my saas. Then there came another problem for me. All of those platforms were taking a minimum of 40% sale commission while asking me to heavily discount the listing price.
For me, those platforms were charging way more than I expected initially. Then I realized that it would be a disaster for me if I ever launched my saas on these platform. I also came to know that there were people known as power users, and these people tend to exploit your application and its features.
I also was confused whethe providing lifetime deals directly to the users of your saas would be good? But, the question here still arises - For how long can you sustain these users as your api bill will be there for you every month for the rest of your life?

So, did you ever plan for lifetime deals? Or would you ever go with lifetime deals?

Everyone says "give the agent full context so it understands the architecture." But lately, I've noticed that the more files I index or attach, the more distracted the model gets. It starts hallucinating patterns from old legacy modules instead of following the clean patterns in the active file. Where is the sweet spot for context limits?

Numbers can look fantastic on paper while your actual product is driving people crazy behind the scenes. We tracked high usage on a new update and thought we nailed it, but watching just two people try to navigate it live showed me every single flaw we missed. Spreadsheets don't show you the frustrated sighs or the pauses where people get stuck. How much weight do you give to raw data versus actually jumping on a call to watch how someone uses your app?

Our landing page, product pages, design system, even our promo video, all of it came from AI tools plus taste. Five years ago this would have needed at least one designer on payroll and tons of Figma design effort.

Here's the uncomfortable part. The output is genuinely fine. Not award winning, but clean, consistent, and shipped in weeks instead of months. Nobody who visits our site asks if we have a designer.

A. I watch a lot of YouTube to stay updated, but many videos are 1 2 hours long and I only need one specific thing from them.

B. Right now I drag the progress bar back and forth, or open the transcript and press Ctrl+F. It works, but it eats a lot of time.

C. What do you do? Speed up the video, read the transcript, ask an AI, or just skip it? And what has worked best for you?

I discover a lot of tools through Product Hunt, and the upvote count is usually the first thing I look at. But it doesn t always match how useful a tool turns out to be for me.

Last month I signed up for a #1 product of the day because of its huge upvote count. I used it twice and forgot about it. A few weeks earlier I had tried a small launch with barely 50 upvotes, a simple tool for organizing browser tabs, and I still use it every single day.

It made me wonder if I give upvotes too much weight. Maybe the comments and the maker s replies say more about quality than the ranking does.

When you decide what to try, what do you look at first: upvotes, comments, the demo, or something else? Has a low-ranked launch ever surprised you?

During the year of our business I answered all the support emails myself. It was hard. I did not like it. Looking back it was the important thing we did and I almost handed it over too soon.

Analytics showed which buttons were pressed. The inbox showed which actions users wanted. These are two types of information. One day a user wrote: "I expected the export button to send the report to my accountant." Our button saved a file. No one would have ever noticed this difference in the funnel chart;. In the next month three other users had the same issue. We added an email button. The problem went away.

Now I keep a spreadsheet with four columns. The words that the person uses the screen they were on what they were hoping for and what actually happened. Patterns start to appear after forty entries. It is important to write down the words since they will become your landing page copy and button labels.

There is a risk. Support emails are more likely to come from customers and less likely from happy quiet ones. That feature no one ever asks about could be the thing that keeps everyone coming which is why I look at the email box along with the retention numbers not instead of them.

For 15 years I built ecommerce stores for clients at my agency in Italy. Good business, good clients, but always trading time for money. Last year I took a problem I kept solving manually for clients, writing product descriptions, and turned it into a SaaS product.

The transition from agency to product was harder than I expected. A few things I learned the hard way:

1. Your agency clients are NOT your SaaS target market. They want custom work, not self-service tools. Different mindset entirely.

2. Pricing is a completely different game. In agency work you price by the hour or project. In SaaS you price by the value delivered and underpricing is the default mistake.

3. Marketing yourself feels wrong. After 15 years of marketing other people's businesses, promoting your own product feels awkward. You have to get over it fast.

4. The loneliest part is making decisions alone. In agency work the client tells you what to build. In SaaS, you decide and you live with the consequences.

5. Being bootstrapped is a superpower, not a limitation. No investors means no pressure to grow at all costs. You can build what actually matters.

I'm still early in this journey and learning every day.