The conversation

Business & incomeExperience excerpt · English

I've done exactly one legit "SaaS startup" type venture around 2012-2015

I've done exactly one legit "SaaS startup" type venture around 2012-2015. I still think about the absolutely insane customer service requests we'd get. It was a very niched down Eventbrite competitor, so we did things like PDF ticket generation, QR code generation, attendance tracking, there was a big fundraising component as well so lots of payment infrastructure. We charged a percentage of ticket sales so any one event or even customer was not worth very much (a positive IMO). I still remember someone emailing me directly with the "oh we'd love to give you money but you have to add these features for us first" so they could use this event ticketing and fundraising platform to ... run their dog grooming business. As many have learned, the people actually paying you money are usually pretty reasonable. It's the people who haven't paid you a cent who have all these crazy demands.

Original discussionI've built my first successful side project, and I hate it419 source comments · at import
5

What was this responding to?

Parent context · original excerpt

BT

This was a fascinating read, really. The potential customer base being basically suckers waving wads of cash to be taken from them. The wild contrast of how nice the author tries to be to every single person that interacts with the project -- despite majority being the equivalent of single-celled organisms poking the fb markeplace "is it available" button. Reading some of the messages from potential users is so eye-opening. I don't know if there's a sane way to deal with the entitlement, other than just plain ignoring those interactions. How would one handle this type of project in 2024? Route most of the rote communication via an LLM, automate as much as possible, ignore all feature requests, dogfood everything as you continue to use the project yourself? I really like the learnings the autor took from this experience. Seems like most of them came from adopting "I give up" attitude when…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 5

Direct replies available in this import. Original-language excerpts.

AU

Yup yup yup. Big reason for avoiding free users is avoiding those requests. This is the kind of thing no startup puts in their year one budget and (alongside supplier cashflow issues) is why those projections don't work for

Full original
HE

A collected a few crazy support requests here: https://successfulsoftware.net/2010/11/21/problem-exists-bet...

Full original
TH

> As many have learned, the people actually paying you money are usually pretty reasonable. It's the people who haven't paid you a cent who have all these crazy demands. Real question: I wonder if this phenom has been part of a case study for MBAs. It makes sense to me. If you are paying customer, you have already convinced yourself it is a valuable product. Deeper: Is it every worth trying to convert the "crazies" using sales strategies? Example: Well, if you sign-up for our enterprise package, we promise your needs in X months.

Full original
HI

Unfortunately the IBMs of the world have taught a lot of entrepreneurs a very valuable lesson: Companies only pay attention to you as a customer when they think the checkbook is coming out, or going away. Big companies have different reasons, but the behavior is similar. The people who understand this start making everything sound like a quid pro quo situation even if it's not very sensible. The more clever and slightly pessimistic entrepreneur might go so far as suggest the problematic customer talk to one of their competitors. But that sort of biological warfare really should be covered by the Geneva Convention.

Full original
CR

It’s hard, but my best advice for Saas builders who get crazy feature requests from non-customers is simple: Don’t reply. You have to judge which requests are “crazy” of course, which isn’t always easy. “If you could just do this one thing, I would gladly pay for a subscription” has to be weighed with how much work it would be, and whether you think it would apply to other potential or existing customers. But a reply explaining your rationale for politely saying “no” simply gives the potential customer a reason to stay engaged, often leading to indignation when the inevitably feel dissatisfied with your reasoning. After all, they don’t care about your other customers, they just want their problem solved. Many, many prospective customer inquiries don’t deserve answers, and you’ll find yourself buried in unproductive back-and-forth if you don’t do the simplest thing of ignoring them.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.