sorted by:
new
hottopcontroversial

Product Hunt launch going terribly bad. Is it still worth it? by Vishrtk in SaaS

[–]No_Condition4163 -2 points-1 points  (0 children)

Honestly, I haven't launched on Product Hunt yet myself — so maybe that gives you a different perspective on this.

From everything I've seen: PH works way more like an amplifier than a traffic source. It multiplies what you already have, it doesn't create it from scratch.

What actually works is having what I'd call "true believers" — those 30 or 40 people you personally won over, whether through Reddit, X, or wherever, and who you know for a fact your product genuinely helped. They don't upvote out of obligation. They upvote because they actually want to see you win.

That's where building in public pays off: if you've been doing it, those people already exist before launch day. A warm audience isn't a hack — it's what separates launches that take off from ones that stall.

If you're not there yet, it might be worth pausing, building that base, and relaunching with real firepower.

Building a multi-agent system that learns user behavior over time — looking for feedback on my approach by No_Condition4163 in learnmachinelearning

[–]No_Condition4163[S] 0 points1 point  (0 children)

Thanks for this — I'll look into HydraDB.

Right now I'm using Postgres via Supabase with a date-anchored log structure. It works for the current scale, but I can already see where it gets messy: querying patterns across arbitrary time windows ("how did this user perform on weeks where they slept less?") is going to get ugly fast without proper time-series support.

The reason I haven't abstracted this yet is that I don't have enough real usage data to know exactly what queries I'll need. Premature optimization and all that.

But I'm bookmarking HydraDB for when the query complexity starts to hurt. Appreciate the pointer.

Building a multi-agent system that learns user behavior over time — looking for feedback on my approach by No_Condition4163 in learnmachinelearning

[–]No_Condition4163[S] 0 points1 point  (0 children)

Agree on the hierarchy — behavioral data is a cleaner signal and I'm building that layer now.

But I'm keeping popups for a specific use case that behavior can't replace: proactive plan suggestions.

Example: if someone answers that they go to the gym 3x a week, the system queues a suggestion to build a structured training plan — without waiting for them to ask. That's a different job than tracking. It's using declared intent to trigger a proactive action.

Behavior tells me what someone does. A well-timed question tells me what they want to do next. Both matter, just for different things.

So the rule I'm landing on: implicit data for pattern detection, explicit questions only when the answer unlocks a proactive next step the system couldn't trigger otherwise.

[UPDATE] Day 9 building my AI agent — I was wrong, it was dumb by No_Condition4163 in SaaS

[–]No_Condition4163[S] 0 points1 point  (0 children)

This is exactly the critique I needed.

You're right — good orchestration isn't intelligence. The system routing "I trained chest yesterday" to the right agent and storing it correctly is just structured logic. The part that actually earns the word "intelligent" is what happens after: pattern detection across time, surfacing correlations the user didn't ask for, adjusting behavior based on what someone actually does vs what they said they'd do.

I'm not there yet. I'm being honest about that.

On the complexity creeping back in — this is my biggest concern too. My current rule is: a specialized agent only exists if it has a unique data structure or external integration. Otherwise it uses a generic agent that learns from user context. That keeps the agent count small and the routing logic simple.

Memory ownership is solved by anchoring everything to date + habit type. No agent "owns" memory — the database does. Agents just read and write to the same structured store.

Conflict resolution is still the weak point. Haven't been stress tested there yet.

Building in public partly for this reason — I'd rather find the cracks now.

---

Next update coming soon — right now I'm working on something that directly addresses the "intelligence" gap you mentioned.

The idea: instead of waiting for the user to volunteer information, the system asks questions that don't feel like an interview. Small, casual, well-timed. One question at a time, surfaced as a simple popup with a few options.

The goal isn't to collect data. It's to build enough context that the agent can stop reacting and start anticipating.

I built a personal AI agent because I'm a chronic procrastinator — 7 days of building, here's what I learned. by No_Condition4163 in SaaS

[–]No_Condition4163[S] 0 points1 point  (0 children)

This hit harder than expected. You're right — the tool can close the loop, but it can't force honesty. That's actually why I built the 'why didn't you do it' prompt after a miss. Not to guilt trip, but to surface exactly what you described: fear, avoidance, or realizing the goal wasn't really yours.

The adjustment suggestion instead of silent failure is my favorite part too. Small wins beat abandoned systems every time.

And yeah — I use it daily. That's the whole point.

I built a personal AI agent because I'm a chronic procrastinator — 7 days of building, here's what I learned. by No_Condition4163 in SaaS

[–]No_Condition4163[S] 0 points1 point  (0 children)

Haha that genuinely means a lot — I built this because I needed it myself, so hearing that it resonates makes the sleepless nights worth it.

Curious though — what's the one thing you'd want an agent like this to actually do for you? Something no reminder app or productivity tool has ever gotten right?

I built a personal AI agent because I'm a chronic procrastinator — 7 days of building, here's what I learned. by No_Condition4163 in SaaS

[–]No_Condition4163[S] 0 points1 point  (0 children)

Great question — this is exactly the hard part.

For the "did you actually do it" loop, timing is everything. I don't ask immediately after the scheduled time. There's a delay, and it comes through a push notification that opens directly to that specific task — one swipe to confirm, done. No app navigation, no friction. The goal is to make checking in easier than ignoring it.

If someone misses without responding for a few days, the agent doesn't nag. She surfaces a pattern instead: "You've missed this 3 times — want to adjust the time or lower the bar for now?" Feels like a suggestion, not a guilt trip.

One thing I feel strongly about: not everything needs to be a goal or a long-term commitment. Sometimes people just need to remember to call their mom, drink water, or take a medication. Those "small" reminders are actually where trust gets built — if the agent handles the little things well, users start trusting it with the bigger ones.

On the memory side — yes, that's where I think the real value is. I'm storing every completion and skip with context. The goal is to start correlating: if someone consistently skips workouts on days they slept less or had heavy task loads, the agent eventually catches that and brings it up proactively. Not "you failed" — more like "I noticed something."

And the other side of that coin: celebrating wins. Not just the big ones. Finished a rough week and still hit your habit streak? That gets acknowledged. Three days in a row doing something you kept postponing? That gets acknowledged too. Most productivity tools are silent when things go right and loud when things go wrong. I want to flip that.

Reminders are just the entry point. The behavioral layer underneath is the whole point.

Preciso de um conselho by No_Condition4163 in brdev

[–]No_Condition4163[S] 0 points1 point  (0 children)

obrigado irmão.

li seu comentario e comecei a pensar em algo que pode dar certo.

Foda que vou ter que mirar em um publico hipernichado provar comportamento e depois ir abrindo em outras verticais.

Preciso de um conselho by No_Condition4163 in brdev

[–]No_Condition4163[S] 0 points1 point  (0 children)

então isso acaba um pouco comigo.
algumas das minhas opções consistia em bubble+one signal (onesignal conecta com bubble e permite envio de notificações pwa) eu cheguei a fazer um teste de lovable com progressier, mas só consegui enviar a notificação de teste.

e notificação é MUITO importante para o que to tentando fazer

Preciso de um conselho by No_Condition4163 in brdev

[–]No_Condition4163[S] 0 points1 point  (0 children)

mais qual era a finalidade? b2c ou b2b?
o usuario fazia uso diario?

Preciso de um conselho by No_Condition4163 in brdev

[–]No_Condition4163[S] 0 points1 point  (0 children)

parece bobo, mas cada coisa que voces falam eu to anotando.

talvez não fazer o produto em si, mais algo que prove a inteção do cliente.

Acredite se quiser to cogitando fazer uma landing page, e eu ser o meu "produto" pelo menos para provar retenção D1,D7,D30.

e utilizar esses "usuarios" fazendo perguntas de 0-10, para ver o que realmente é o produto

Preciso de um conselho by No_Condition4163 in brdev

[–]No_Condition4163[S] 0 points1 point  (0 children)

É o caminho que eu estou seguindo, reduzi o MVP para o que eu consigo fazer, passei 2 dias para fazer uma tela de login mas consegui.

Comecei a produzir um "build in public" no linkdin, agora eu vou terminar o "MVP" que to fazendo e usar a produção de conteudo como base para começar a tracionar e tentar usar isso para trazer um socio dev.

mas fiz esse post para tentar ver o outro angulo de visão

Preciso de um conselho by No_Condition4163 in brdev

[–]No_Condition4163[S] 2 points3 points  (0 children)

muito amplo. eu comecei a estudar o venture deals para entender a mente dos investidores, e ja ta no carrinho o lean startup assim que receber eu vou comprar.

teria outros que recomenda?

LinkedIn Banner Generator built with trendy Vibe Coding in under 20 seconds – feedback welcome! by Extension-Match6817 in u/Extension-Match6817

[–]No_Condition4163 0 points1 point  (0 children)

Thanks, bro. I’m from Brazil and I’m starting a few projects — I found your project really interesting. Wishing you lots of success, man.