Live data from Hacker News

Diary of a programmer with no clue about marketing

neat.io

41–50 of 152 posts

Re: Diary of a programmer with no clue about marketing

#41
post #34

Your website is a perfect demonstration of your title. A nice funky starfield with a pretty logo taking up half of the page, and a partial screen shot taking up to the rest of my screen space (1920x1080). Nothing about what it does instantly pops out. Then I realise there's more, so I scroll - Something, something, JIRA, GitHUB, FogBUGZ, something something. Hmm, ok, based on that probably not something I'd need. Clo…

And now, the download finishes and I run it, and it turns out it won't run on Lion. It would have been nice to mention somewhere what versions of OSX it runs on.

Re: Diary of a programmer with no clue about marketing

#42
post #6

Nice. So one of the things that happened to me when I came to the Bay Area was I was working at Intel and I had to talk to a lot of marketing folks (who were talking to 'the public' about Intel's chips). I realized I didn't have a clue what they did. I set out to correct that before I started my own company and looked for a job that would let me work closely with marketing but still be engineering based. I found one…

Marketing done wrong is advertising an already conceived product.

Marketing done right is strategic. It's about segmenting a market, targeting the right niche, and looking for the right positioning within the niche. It's about guiding the product towards both stated and unstated needs. It should happen before, during and after development. And yes it should also involve generating demand.

Starting marketing after the fact is like building quality into an already created product. Quality is designed in.

Re: Diary of a programmer with no clue about marketing

#43
This is exactly why I've been writing "The Hacker's Guide to User Acquisition" (first chapter: http://www.austenallred.com/the-hackers-guide-to-the-first-1..., next chapter will be about getting press). I would point out a few things.

1. The notion that you "build a better mousetrap" and people will beat their way to your door is true maybe 1% of the time. Many more companies have had to fight a little to become successful than just said, "This is so awesome that everyone loves it." That being said, no amount of marketing can make up for a crappy product.

2. Marketing should be baked into the product itself. If you're figuring out "now how do I get this out to people" after everything is finished, except in some rare circumstances it's too late. Explosive growth almost never happens by virtue of a product being so good that everybody shares it and it goes viral. Yours might, but you can't count on that happening. So how can you leverage your existing user base to create more users?

3. Getting press is more than emailing a couple of bloggers. And emailing bloggers has to be done in a very specific way to get their attention. It's difficult, because you only have one shot: Think about having to run some code and if there are any errors it all falls to pieces. That's what emailing bloggers feels like. But when it works, it works. And when one place picks you up, the others jump on board really quickly (they're kind of like investors in that way).

4. A lot of the "marketers" you've talked to might suck. It's a lot easier to pretend to be a marketer than it would be to pretend to be a programmer. And just as a non-technical person would have a difficult time trying to figure out if a programmer is any good, it will be hard for you to tell the difference between a good marketer and someone who has no idea what they're doing

5. You need a critical mass of users to determine if your product sucks. When I started marketing my first product, I couldn't pay people to use it. It wasn't that people were saying, "I don't like this," but I couldn't get anyone to try it to say whether they liked it or not. Then after months of grinding and trying to figure things out, we found the sweet spot. Thousands of users per day jumped on board, to the point that our biggest problem became scaling. (A good problem to have, but certainly a problem). If I had given up one day earlier I would have thought that no one cared, but really there was no one to care. There's a difference.

6. 99.99% of the time doing marketing is spent figuring out what works. Once you know (and it's different for each client/customer/app), it's really easy. Don't discount it when someone says "Oh you just do this and this, and boom, users." The same as you wouldn't look at a designer and say "Well you just designed that really simple logo, that can't be hard," you can't just look at the work they're doing -- you have to consider the work they have done. And getting to simple is hard.

So the moral of the story: Don't give up yet. It's too early to know if anyone will care about what you built; you have to get it out to more people.

And the next time I hear someone say, "You don't need a marketer, it's all about the quality of the product," I'll point them to this post. Thank you for your honesty, and best of luck to you.

Re: Diary of a programmer with no clue about marketing

#45
I'm one of those people who downloaded the trial, ran it for a few days, and then deleted it. I liked a lot of things about the app, but there were a few bits that I found unintuitive—particularly around managing multiple projects from different sources.

I decided to pass, but I bookmarked it so that I'll be able to find it again in the future if I ever find that I really need a quick way to access my Jira issues from the desktop.

The $49 price is entirely reasonable considering the breadth of the feature set and the target audience, but it does put it outside the impulse purchase comfort zone. It might have been helpful to put it on sale at launch with a discounted price in order to build some traction and lower the barrier to adoption for people who are on the fence.

Re: Diary of a programmer with no clue about marketing

#46
Hrm... random impressions I had:

1) The above the fold stuff sort of showed me what it describes itself as, but not what it really is. A looping animation or video would have been really helpful.

2) The below the fold stuff originally came across as separate products. Like I thought it was your catch-all page for a few other products you've made. So maybe you could make it clearer that they are all components of Bee.

3) Just my own reaction that I noticed - when you demonstrate compatibility with several outside services, there might be a weird disincentive to try it out if the potential customer doesn't use all of those services. Like I immediately had a suspicion that since I use Jira but not Github or Fogbugz, that the other focuses of the tool would get in the way or make it feel unwieldy. (I didn't download it to disprove that feeling.)

4) Time/task tracking is a REALLY crowded space, and I imagine it is really difficult to convince someone to try out a new tool, partly because of switching costs. For instance, for me, I use Quickbooks on the Mac, and I'm pretty married to Intuit's "My Time" since it's the only tool I know of on the Mac that will automatically transfer time records to Quickbooks, which I then use to make invoices. And then if someone asks me why I create my invoices from time records in Quickbooks, then... heck, I dunno, I made the decision at one point and it works for me. I could do a whole first-principles analysis I guess that might lead me to a completely different way of working that might lead me to being able to using a different time-tracking app like Bee, but... I don't like going that low on my e-Maslow's hierarchy very often.

5) No obvious mention of price on the front page... no obvious indicator of what clicking the "Buy" button will do or where it will take me. I moused over it, looked for an info tip, and didn't click. (I'm one to just buy rather than deal with download/try/maybe-buy.)

Re: Diary of a programmer with no clue about marketing

#47
I recently read the book "Cashvertising". It's very good at breaking down how to sell in print. I recommend you read it. For example, your headline "Better task tracking on your Mac" offers no real benefit. What is good about task tracking? What is the benefit it offers? Make that answer your headline.

Read the book. It helped me immensely.

Re: Diary of a programmer with no clue about marketing

#49
post #18

Nice! Great to read your experience from creating a product to launching it. Also glad to win over another developer to not thinking that all marketing is BS ;-) Some tips from a marketer: +Get analytics set up! I see that you've only mentioned the top of the funnel (traffic) and the bottom of the funnel (downloads). I'm assuming you don't have tracking for the full flow (traffic > install > activation > day 1-30 ret…

Extremely great advice here. Most people might think this is second nature, but there really is a list of boxes to check and these are all necessary.

Re: Diary of a programmer with no clue about marketing

#50
post #9

Nice work. I've also recently released my first Mac app [0] and I'm working on getting the word out about it by making it free, the idea being that if it's known by people, it can be spread through word-of-mouth, especially if it becomes indispensable. GitHub's API currently reports 600 users, and I'm working on increasing that to 1000 before making it a paid app and marketing it. Nice to see both approaches here; I…

That intro video says it all. Beautifully done.
Post reply on HN