@eliadele@builtshelf The main problem is that devs keep forgetting that most people don't give a fuck about animations or fancy websites, they just want their problem solved
This month's learning:
Spent $300 on a wedding newsletter placement for SeatPlanning, my seating chart tool.
Signups: ~0.
What actually works: someone googles “seating chart”, lands on a tool that works instantly, and pays within minutes.
My buyers aren’t nurtured leads. They’re people with a deadline.
@abhay8769 Support was one of the things that I automated first. Most questions are already answered by your docs so I got tired answering the same thing over and over. Marketing on the other hand still takes most of my time.
@oderajoseph Before letting either act, I’d want it to say “I don’t know” and hand off cleanly. Do you see more damage from wrong answers or from wrong actions?
Small things Brumi does in my habit app that nobody asked for:
- sleeps at night, grumpy if you wake him
- drowsy in the morning
- turns into a ball if you hold him. Yes, you can throw him
- his antenna catches fire at a 3-day streak
@Chandan_blaster Guilty on the AI customer support one. The demo is the easy part; the more challenging part is getting it to say “I don’t know” instead of making things up.
While building SeatPlanning I noticed I kept answering the same support questions and the existing tools were not working as I wanted.. So, I'm building MivoChat: AI support chat that answers from your docs and turns every conversation into a Telegram topic for your team. https://t.co/VmrpSHakN4
@usama_shaX Support is the sneaky line. Per-seat or per-resolution pricing means the bill grows with every signup, which is why I priced MivoChat flat. Which cost hides best in your view?