Product management with Google AdWords

Posted on 4 December 2008 in Business of Software, Resolver Systems

You can't rely on people's response to your advertising to manage your product -- but as one of many inputs, perhaps it could be valuable. Can part of the product management role be taken over by aggregating data from carefully-targeted Google AdWords campaigns?

There have been some interesting recent discussions on the topic of product management. Like most startups, Resolver Systems doesn't have anyone with the job title "Product Manager", but the role is filled, mostly by me and my co-founders. We look at the software, talk to clients and to potential clients, read spreadsheet blogs, and try to synthesize all of this together to work out where development of Resolver One should go over the next weeks, months, and years.

This works surprisingly well; we've produced something solid and reliable that clearly fills a real gap in the market. But the other day I was looking at the first results from a new Google Adwords campaign, and noticed something interesting -- something that may well be standard practice for people who've used this kind of tool for longer than I have, but was a bit of a revelation for me.

The way we'd structured this campaign was to identify the ten things we thought were most interesting about Resolver One, and then to create an Ad Group inside AdWords for each. "Ad Group" is Google's terminology for a set of advertisements that all share the same set of keywords (among other things). So, for example, we had an Ad Group to cover Resolver One's programmability, with keywords like "programmable spreadsheet" and "code in spreadsheet". When Google spotted these keywords in a search, it would know that it could present its user with our ad, which said something like "a new, easy-to-program spreadsheet - download the 14-day trial".

These ten Ad Groups had been running for a day or so, and I checked out the numbers -- and saw something interesting. The number of clicks each ad got often went against my intuition about the product. I would have thought that the ability to convert a spreadsheet to a program would be much more interesting than the fact that you can build spreadsheets that are better protected against layout changes. But the number of clicks says quite the opposite!

To put it another way -- by having an Ad Group per feature, and then ranking the Ad Groups by the number of clicks they received, I was able to get an instant market survey telling me what people thought about our different features. For less than GBP50 (I'd not budgeted more for this phase of the advertising), over 300,000 people looked at pages including our ads, but more importantly 350 clicked through on a specific feature, "voting" for more work on that feature!

I think this is a great new input to the product management process. Obviously building what people know they want is only part of creating something great; it's as, if not more, important to build stuff they don't yet know that they want, even if you then have to spend time and effort persuading them to try it out. But if you have ten ideas and want to know which is most popular, a GBP50 AdWords campaign can tell you an incredible amount very quickly.

So, the question is... if you were starting a new company tomorrow, would you think it ethical to start advertising before you started coding, just to see which features to focus on first?