Rather than reject techniques like this because they're not technically products, I think we should expand the concept of MVP to include things like this because they serve the same purpose: learning about your market, reducing risk, validating ideas.
One drawback to this approach is that it may give you false negatives. What if you landing page copy doesn't work or your AdWords copy is wrong? As with all lean/custdev hacks ymmv. Bottom line is you need to find customers to talk to, otherwise everything is an assumption.
Some other articles that touch on this approach:
http://startupbound.com/how-i-quickly-test-and-validate-star...
http://www.startuplessonslearned.com/2008/11/using-adwords-t...
http://www.cindyalvarez.com/best-practices/customer-developm...
there should be another name for this. MVI maybe? minimum viable idea?
>The canonical MVP strategy for a web application is to create a mock website for the product and purchase online advertising to direct traffic to the site. The mock website may consist of a marketing landing page with a link for more information or purchase. The link is not connected to a purchasing system, instead clicks are recorded and measure customer interest.
from: [wikipedia](http://en.wikipedia.org/wiki/Minimum_viable_product#Techniqu...)
That seems to directly contradict the implication of 'mvp' that you're using, which is that it MUST be a viable product that customers can use.
EDIT: The best part of markdown is when it isn't supported, the code is very readable. I say leave it!
i can agree with that, on some level, but i still feel that to have a complete MVP (process), you necessarily have to have a P at the end of it.
This?
> We did everything possible to not show that we hadn't even started the back-end yet.
Is testing marketing and UI design. Which is great. But it's not an MVP.