Loading...
Answers
MenuIn the context of an already established software product, should I give what my customers want or what they need?
Answers
Always take into consideration what your customers want, even when building "what they really need", because it will give you insight into how best to implement it.
On whether to "give them what they want", it comes down to what % of your customers want something. If 99% of your customers want something, it would probably be best to give it to them. If 5% of your customers want it, don't bother.
If you're just reading posts to a "things I want" forum, then what you may be seeing is the opinion of a loud minority, which will make it look like 99% want something, when really only 2% do.
To accurately assess the % you could actively send out an email poll to all your users asking which of several options they would most want (allow them to choose 1). Embed the poll in the email itself to make it as easy as possible to respond to. Also, if possible embed in the email a screenshot of what each new feature would look like, so that it will be easier for them to see your side of the story about why you think a feature would be "what they actually need". Just have your designer make the screenshots, you don't need to actually have them be programmed and functional.
If you want to discuss this in relation to the unique details of the actual features you're thinking about implementing, let me know,
best,
Lee
I would suggest market research to ensure you have the most accurate data.
When we launch an update to our existing products or even a new line at Vital Consulting, I always make it a point to sell the experience and influence the customer of what they want.
Help them discover for themselves what their needs are and turn them into wants.
There are a few conflicting statements in your question that make this a little tricky to answer - but I am gonna give it a go anyway.
Firstly, it seems like when you're saying "what they really need" perhaps you have strong opinions on what they need and are frustrated that they don't see things the same way as you? If this is the case, you are definitely going to be facing the uphill battle that you reference.
My suggestion is to talk to your customers (actual face to face, or telephone calls) and find the trends in the features or specifications they are requesting. If you are already established (which I am taking to mean - you have loyal, paying customers and are financially stable) then take an 80/20 approach to improving your product.
Spend 80% of your time/resources by adding the feature requests that you know people are asking for and likely to pay for and spend 20% of your time/resources on those experimental features that you think people need even if they don't realise it yet.
Also, this will probably keep you motivated to continuously test and improve your own product because you'll have a 20% "side project" budget. Those are always fun.
Related Questions
-
I've been working on an app concept for 6 months and built an MVP. Is it better to pay a development firm to build or hire a developer as a cofounder?
I have built two software companies by hiring out the development work. I sold one for a decent sum during the dot com era (circa 1999). I remain a shareholder in the other one. I currently work with amazing development company on behalf of one of my clients. Here are some things to consider. 1. Do you really want to give up equity? If not outsource. 2. How fast do you want to get to market? If sooner than later, outsource. 3. How capitalized are you? If undercapitalized, either outsource offshore (which runs about 20% of US rates), or bring on an equity development partner. I offer a free call to first time clients. Let's chat and I'll give you some great advice from three decades of experience. Just use this link to schedule the free call: https://clarity.fm/kevinmccarthy/FreeConsult Best regards, Kevin McCarthy Www.kevinmccarthy.comKM
-
Is there any typical questions for customers' pain points discovery or it's impossible to standardise?
I have built several multi-million dollar businesses using (2) very simple questions: "What makes you say that...." and "Tell me more...." No matter what someone says to you, you just keep asking one (or both) of the questions. If you do it 4 or 5 times in a row you'll learn everything you ever wanted to know.DW
-
What are ways to find and engage B2B beta users for a brand new application?
Find apps that are B2B and go to the review sections. Specifically going to Google's play or Chrome store and look at reviews and follow them to Google+ to engage. I took that same angle for B2C app I was building last year. Check it out. http://blendah.com/post/37331434653/lean-startup-hackTM
-
What are the key accomplishments for the first year of a startup?
A generalized question can only get a generalized answer. The most significant accomplishment is validating that the product you have built is a fit with your target market. This is demonstrated primarily by engagement (the people who sign-up or who previously visited, continue to return) and secondarily by growth, ideally based on word-of-mouth or viral growth but effectively converting paid traffic is a great second prize. Other significant accomplishments include: Not running out of money Recruiting and retaining great talent who believe in the founders' vision. Your loved ones not thinking you're as crazy as they thought you were a year ago. I'm happy to talk to you in a call to give you more specifics about what you want to set as your goals more specific to your startup.TW
-
How can I smoothly transition from full time worker to self-employment?
The ways I've done this in the past are 1) Find some customers that are willing to hire you (or your product) but know that you'll only be free nights & weekends to support/work with them. 2) Find a "partner" (co-founder or other) that's got a flexible schedule that can help build the business while you're at work. 3) Block out nights, mornings and weekends to build the business till you have enough orders to cover 50% of your salary. This might mean 7pm-11pm most nights, and 4 hours each day Sat & Sun. Make progress (sales $$$) and momentum. All that being said, it's risk reward. Sounds like you want to avoid taken the risk, and I get that .. but the upside is always smaller. Unless you put yourself in a position to have to succeed (ex: quitting your job) then you may never make the scary decisions that are required to build a company (like cold calling, going in debt, making a presentation, etc). I'm on company #5 with many other side projects started nights & weekends .. so I get it - but don't be afraid to bet on yourself and go all in.DM
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.