I publish every day and I check my numbers every few days. Right now those two rhythms are out of sync the last figures I actually read are five days old, and I've shipped four batches against them.

The uncomfortable part is what I opened in those four batches. Three tests, all still running, none of them readable. So I've spent four days making decisions from a snapshot instead of from results, and the snapshot is the thing I was trying to move.

Two options and I don't love either. Keep publishing on schedule and accept that a chunk of it is guesswork. Or hold until I can read the last batch, and lose the cadence I've built.

I've been picking the first one, mostly out of habit rather than because I worked it out.

In the course of six weeks of the launch i handled all support communications for an invoicing application i developed for freelance photographers personally. No automation, not templates. I was expecting bug reports. Instead I was provided with a blueprint where my product confuses its customers.
Three emails deserve mentioning. One of them was asking about the location of the "send reminder" button it was on a page where users never logged in.Another email made assumptions that deposits and the final payment were interchangeable as my label system had the word to describe these notions.. Finally there was a brief "thank you note" from the wedding photographer, from Cebu stating that the PDF document he received looks exactly like it was generated by his studio. This one was immediately. Hanged to my desk.
The analytical tools showed that users were leaving the dashboard. The emails explained the reasons of doing. As a result I ve repositioned the "reminder" button. Separated these two labels. Repeat questions disappeared within a week.

Now I am curious how far this signal goes. When did you stop answering every communication and what replaced it?

15 days into product hunt, still figuring things out and already found a bug.
Refresh your own post enough times and watch the view count go up. that's not a new viewer. that's just me hitting refresh.

Feels like PH could use a sharper QA pass tbh. if anyone from the team's reading this, happy to point out more stuff i've noticed.
NOT COMPLAINING, just genuinely nerdy about this kind of thing lol

I often see founders wondering:

Do kitty points matter for ranking? Should makers have high kitty points before launching?

If you're pairing an expensive AI model with a cheap one to save money, Anthropic's cost guide has a sentence worth reading twice: in their measurements, "a second model paid off in two shapes".

Shape one, the advisor: the low-cost model runs the whole loop and phones a frontier model only when stuck. Advice comes back short, roughly 400 700 tokens, so you pay top rates only for judgment, never for the bulk generation. Their data says the advisor closed 50 90% of the capability gap to the stronger model with a catch I'll get to.

Shape two, the orchestrator: the frontier model plans and delegates, cheap workers absorb the token-heavy exploration, and most of the bill lands at worker rates. This is the shape we run daily, though we arrived at it for context-window reasons and the billing benefit came along free.

The catch in shape one deserves a name: the executor has to know it's stuck, and that self-knowledge is itself a capability. In their measurements, a pairing that consulted happily at default effort dropped to almost never consulting when the executor's effort was lowered and then scored below the executor running alone. You saved money on the worker, and the worker stopped raising its hand.

When I started I thought every problem needed an immediate fix. If users complained about something I d jump on it. If growth slowed down I d try something new. If a process felt messy I d try to rebuild it. But sometimes the better move was to leave it alone for a while. A few problems fixed themselves as the product changed while others turned out to be problems I was creating by overthinking them. How do you decide when a problem actually needs your attention and when it s better to just leave it alone?

I went through my credit card statement last weekend and finally canceled a software I ve been paying for over a year. I felt bad doing it because the product was great, but I only used it a few times all year.

It was a good reminder that churn isn't always caused by bugs or bad features sometimes people just outgrow the need for the tool.

If you run a SaaS how do you learn from users who leave politely without filling out cancellation surveys?

When we started, our app was super simple. People logged in did what they came for in seconds and signups were high.

Then we tried to make everyone happy by adding tons of settings and custom options. instead of making the app better it just confused new users and brought in endless bugs.

In the early days, our product had a single, crystal-clear value proposition. Users logged in, knew exactly what to click, and achieved their goal in seconds. Because the core experience was focused, conversion rates were high and onboarding was practically effortless.

Then came the desire to expand. We started building every feature users requested, adding customizable settings, and creating multiple workflow options. Instead of delighting people, the experience deteriorated. More options split user attention, clutter ruined the clean interface, and new features introduced unexpected edge-case bugs. We added value on paper, but in reality, we just added friction.

How do you strategically say "no" to feature requests so your product stays lean, intuitive, and effective as it scales?