Skip to main content

Offending Your Customers

Yesterday I received an email from a startup on the west coast. I had informally advised the founder, who seems like a nice guy with a good product and viable startup.

But I was immediately put off by the headline of what was a blog post, which was about, well, I'm not going to get into it because I don't want to call him out publicly for it, but it reflected the poor taste delivered in the headline. So I'll have to be vague because the googles are pretty good.

I immediately responded to the email saying it's terrible messaging. He questioned that; his target market is much younger than I, and the language he used is somewhat accepted among that demographic.

But it still sounded bad to me.

Here's my point: you can effectively position your brand and product without using offensive language. You can get your point across without sending something that reflects poorly on you.

Now maybe that's your gig; plenty of companies have done very well by pissing off a good chunk of the market in order to appeal to another.

But to me (and I have to admit there was a time I pushed the limits, especially with ChiliSoft), startups can really undermine their credibility by alienating people when that's not really their core value and brand.

In this case, the language was not aligned with the mission, brand, or style, and I'd throw this in too: target market. It's a miscalculation to think that just because you have a young audience that it will respond positively to poor taste.

Some will like it, and some won't care, but some will care very deeply, and you'll have a bit of a mess to clean if they let you and don't simply walk away, or worse--stop caring at all.

The blog post is gone, and the Facebook post has been removed. I'm guessing I wasn't the only one who complained.

Good choice--you can do better, and I'm sure you will.


Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

Disqus Digests

This morning my phone dinged with a fresh notification--a new email! What oh what could it be?  I rush over to check while thinking "I need to unsubscribe to a lot of stuff so I get fewer non-urgent dinging notifications." Well shoot, that's disappointing. It's Disqus Digests, one of the biggest wastes of dopamine anticipation ever.  It simply sucks.  Disqus itself is great as a commenting system. I've been there since the beginning and have mostly enjoyed its evolution.  And then they did this interruptive, irrelevant email. Well why does it suck, you say.  Every one of these "Digests" sends a few comments from a blog conversation in which I've already participated. That means it's very, very likely that I've seen the comments before.  So I open the mail, see something I've already read, and curse Daniel and Company for enticing me into wasting my time, and cursing myself for falling for it.  So I unsub