Skip to main content

Spiceworks Marketing

Some of the founders of Motive have started a new company in Austin, Spiceworks. From their web site, it appears that the company is working on some sort of IT product or service.

Several things about the web site impressed me:

  1. Almost every page on the site had the same call to action.
  2. The call to action was to sign up to be a co-creator of the product, which is powerful for generating word of mouth.
  3. For the most part, the content of the site is simple, direct, and avoids meaningless marketing jargon.
  4. The 'about' page succinctly states the problem the product is supposed to solve.
Here is an excerpt from the 'about' page:

"After talking with dozens of IT pros in small businesses, a team of systems management pioneers had their suspicions confirmed: these pros don't like the complex and expensive IT management solutions they're forced to choose from today. But no one has been listening to them... until now.
We listened carefully to what these weary IT warriors said. And now together, we're creating a simple, easy to use, yet powerful solution -- one that will help them win their daily IT battles."
The one criticism I have is that they do not state what their product does. I suppose they don't want to divulge much before the product debuts. It may also enhance the "whisper" campaign to be somewhat secretive. But I'm not sure how many serious prospects are going to enroll in their alpha program if the web site doesn't give them a bit more information.

Comments

Jay Hallberg said…
Thanks for the kudos. We're trying to avoid the overload of three letter acronyms and jargon that have grown like kudzu in the IT market.

We intentionally haven't stated what the product does yet -- that will come when we launch this summer. Participants in the alpha program will find out when they get their invitation e-mail.

So far we're doing great on registrations. I think this is because we are saying that we will have an alternative to complex and expensive IT solutions. These IT pros are really unhappy with the products they have today.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the