Customer – to listen or not to listen

 

If I had asked people what they wanted, they would have said faster horses

There is a pretty high chance you have heard the quote and an equally good probability that you yourself have used it to support or demolish an argument on “customer knows best”. It is quite interesting to note how quotes by well known people become the base to support an argument without any need to understand the true import of what has been said.

While we do not know if Henry Ford really said those lines, there is ample evidence that he thought along those lines. To the extent that his company suffered. Steve Jobs also showed similar inclinations (in terms of the customer not always knowing what s/he wants) when he said

It’s really hard to design products by focus groups. A lot of times, people don’t know what they want until you show it to them

Now, there are brilliant companies that have been built on innovation and creativity that is attributed to the capacity to think independent of public opinion/noise. On the other hand, frameworks like the Lean Startup recommend listening to your customers at regular intervals to get feedback on your product. In fact, Eric Ries even recommends

Frequency is more important than talking to the “right” customers, especially early on.

 

So, as a startup, how do you build your product – basing it on your experience & intuition or by constantly going back to your (potential) customers regularly for feedback?

For us, at RobusTest, the answer is not a choice between the former or latter. It is a combination of both approaches. Having an insight into what the customer wants can be a matter of creative thinking that comes about without the need to talk to any customer. It can also come about from a deep understanding of customer’s problems. Of course, the latter is not as sexy.

We, the founders and our early employees have worked extensively in the app testing and test tooling space. We relied on this experience to arrive at the feature set of the early version of RobusTest. As we met more customers to pitch our product, we realized that customers are not looking for a product, they are looking for solutions to business problems. And these problems are unique to each customer. We, therefore, focus a lot on listening to the customer. When we say, “listening to the customer”, it is not the mere act of hearing what the customer says. It includes observing the customer’s business and business practices. Asking questions without having the answer already set. My earlier post on product design touched upon this aspect of discovering the usefulness of your offering.

How did you go about creating your product? Was it gut feel to start with and then market research? What do you think about talking/listening to the customer to create your product?

Forget the Product, Obsess about Customer (Problems)

Attending a #PNCamp is like going to an amusement park. You know you are going to have a great time. But everything that happens still manages to amaze you in a way you do not expect.

Seth Godin

In this post, I will share my experience at the recently held #PNCamp3 at ISB, Hyderabad. This was the first Product Nation Camp held at Hyderabad and focused on early-stage B2B startups.

A bit about my startup, RobusTest. RobusTest is a software platform that helps enterprises test mobile apps better and release them faster at a significantly lesser cost. We are currently 2 years old and work with 2 leading enterprises. I came into #PNCamp3 with a burning question – how do I do sales? In the last few months, my understanding of sales has improved through reading and through real experience. At #PNCamp I was looking forward to understanding enterprise sales in a structured manner. I did get some answers and I hope you too get a few takeaways from this post.

Building a Global Product Business

The day started with Jay Pullur of Pramati Technologies exploring the topic of building a global product business from his experience of building multiple enterprise products and successfully exiting a few. Incidentally I worked with Pramati Technologies for 8 years and closely with Jay on an enterprise product.

Jay Pullur of Pramati talking about building a global product
Jay Pullur of Pramati talking about building a global product

Chefs would tell you that when making a dish, not only is it important to have the right ingredients, it is equally important that the ingredients be added at the right time and in the right mix. Jay explored both these facets – the appropriate constituents and appropriate team constitution – when building a product business.

To start with, in the building phase, you need to get the technology and the product right. Once your product is ready, you will be selling and for that you need to identify your market and your customers. In the third phase, you will be looking at scaling for which you need to focus on people and capital. It is important to remember that as a startup grows through these phases, the focus on relevant ingredients increases but it does not imply the absence of other ingredients e.g. you will need people even when you are scaling, you will need the technology even when you are selling – just that when selling your focus should be on identifying the right market and customers and when scaling your focus should be on getting the right people and having enough capital.

Jay also touched upon the different types of exits startups may have – an exit at the build stage is most probably an acquihire, an acquisition at the sell stage is most probably for the acquirer to get a foothold in the market that the product caters to. When you exit at scale, it is for the acquirer to gain a position in the market.

Product Teardown

Product Teardown is always a much awaited session because of the open and forthright feedback given by experts on existing startups and their working. Hats off to every startup which chooses to participate in this exercise. It is an acknowledgement of their willingness to confront their shortcomings and work on them.

Participants presenting at the Product Teardown
Participants presenting at the Product Teardown

5 startups presented their product – UrbanPiper, EngineerBabu, Vaave, KnightTracker, DataKatalyst  – while a crack team which spent considerable time and effort in researching the startup – right from its market space down to the minutest detail – gave feedback. As I heard the feedback given to each startup, I could see many mistakes/oversights in our own marketing and selling strategy. Following are some highlights from the product teardown.

Are customers clear about what you are offering?

Does your website clearly communicate what you are offering – to put it the right way which problem of theirs are you solving, how can a customer sign up or get more information, what they will need to pay, and many other such questions that go into “converting” a customer.

Wait, are you clear about what you are offering?

As engineers and technical geeks, most product startup founders have immense clarity about what they are building. However, most of the times we are found wanting when it comes to clarity on “which problem are we solving”, “whose problem are we solving” & “how are we solving it”. It goes without saying, that a product without customers is a hobby project at best.

Is your website communicating your value proposition or confusing your potential customer?

A rookie mistake most founders make when creating their website (or any other marketing channel) is to explain all features of their products with painstaking detail forgetting the one important part – the customer and how we intend to make his/her life better. In fact, it is not at all a bad idea to look at websites of the competition and learn a few things from them (or even copy the entire site, of course in a smart manner).

Are you selecting your customer(s) or are you catering to everyone?

When we are starting up, there is a great desire to include everyone in our customer set. This propensity, of course, ends up confusing every potential customer. It is, therefore, important to put in some thought into which customer segment to address.As is often recommended, identify your least resistant customers and go after them.

One example that was cited was nature of business ownership. As a startup when the challenge is to close a deal as fast as possible, it makes sense to target businesses which are still run by the owner rather than corporates where decision making is spread out across teams and is, shall we say, bureaucratic.

When identifying the target customer segment, it is helpful to pick as narrow a segment as possible. This helps a startup focus its efforts which is very essential considering that startups need to be very judicious with their resources.

Selling to Enterprise Customers Globally

While Jay’s session focussed on building global enterprise products, Zenoti’s Sudheer Koneru delved into selling to enterprise customers across the globe. Zenoti is a cloud-based software for spas and salons and is a successful SaaS product from India.

Sudheer Koneru talking about selling to enterprise customers globally
Sudheer Koneru talking about selling to enterprise customers globally

One of the first things that Sudheer emphasised on is that if we are targeting the global market (and we better know if we are), then all the messaging including website, language, photographs & product demos should be geared towards creating the impression that we are an international player.

On the topic of Customer Development, Sudheer narrated an impressive anecdote on how he and his team went about studying their customers’ problems. They literally got themselves massaged and manicured into customer development! They took services from different spas and salons and simulated multiple real-life scenarios. This exercise provided important insights into issues that the current offerings posed. It empowered them to talk to their customers in a language they spoke and hence, connected instantly with the customer.

An important piece of advice that Sudheer gave was to avoid selling to customers and rather focus on asking the right questions to understand their problems. Of course, it is important to ask the right questions. So instead of asking “would you like a product which does this and this”, one could ask “how do you currently do ….”, “how much times does … take ”, “how often do you create reports”, “how do you decide if you need to ….”. The answers to these questions will help one understand how to solve the customer’s problems.

The one thing

If there was one thing that I took back from #PNCamp3, it would be

forget about your product, rather obsess over your customer – rather obsess over the customer’s problems

Thanks

Last but not the least, I am grateful to the entire team behind #PNCamp3.

Thanks a lot to the team at iSPIRT – Avinash, Chaitanya and Sainath, to Sudheer and his team from Zenoti (Mrityunjay, Anand, Bharath) which was present in full force and helped organize the camp,  to Jay Pullur & Raunak (Now Floats) for their presence and guidance. Of course, thanks to ISB for being an amazing venue.

Guest Post by Aishwarya Mishra, RobusTest