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
-
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
-
Any advice on starting up small businesses in two countries at the same time?
Please realize that my suggestion would be slightly different if I knew which two countries. However, without knowing that here's what I'd suggestion: 1. Since you're just getting started figure out which country provides the best legal benefits for starting a company. This should include tax benefits, legal protection, and ease when it comes to filing paperwork (incorporating, managing payroll, taxes, etc.). This will undoubtedly save you time and money moving forward, and staying lean. 2. Once you've established your home base country, you'll still need to hire people in the other country as you scale. You may want to think about using a service like oDesk or Elance, not necessarily to recruit people but to manage ALL the paperwork associated with hiring international people. They will of course be given contract status. If you are going to be providing employees equity then I'd suggest consulting a lawyer for how people in the non-home base country will be treated. 3. Reporting revenue. You need to be very careful about whether you are providing goods and services. If it's goods keep in mind that you might be subject to tariffs. If you're providing services then I think you might be in the clear, but please double check. Finally, some countries might have an issue with where the revenue was actually made i.e. are you sitting in your office in your home based country while servicing clients in the non-home base country, or are you actually in the non-home base country. 4. No matter what you'll need to setup a remote working environment for yourself. Invest in the best technology you can, and find clients who are willing to utilize your services on a remote basis. Here are a few additional posts on running a remote team that I've written: http://femgineer.com/2013/09/running-remote-and-making-progress/ http://femgineer.com/2013/03/how-to-transition-to-a-remote-team/PV
-
What is the best method for presenting minimum viable products to potential customers?
Whoa, start by reading the Lean book again; you're questions suggest you are making a classical mistake made by too many entrepreneurs who live and breath Lean Startup. An MVP is not the least you can show someone to evaluate whether or not building it is a good idea; an MVP is, by it's very definition, the Minimum Viable Product - not less than that. What is the minimum viable version of a professional collaboration network in which users create a professional profile visible to others? A website on which users can register, have a profile, and in some way collaborate with others: via QA, chat, content, etc. No? A minimum viable product is used not to validate if something is a good idea but that you can make it work; that you can acquire users through the means you think viable, you can monetize the business, and that you can learn from the users' experience and optimize that experience by improving the MVP. Now, that doesn't mean you just go build your MVP. I get the point of your question, but we should distinguish where you're at in the business and if you're ready for an MVP or you need to have more conversations with potential users. Worth noting, MOST entrepreneurs are ready to go right to an MVP. It's a bit of a misleading convention to think that entrepreneurs don't have a clue about the industry in which they work and what customers want; that is to say, you shouldn't be an entrepreneur trying to create this professional collaboration network if you don't know the market, have done some homework, talked to peers and friends, have some experience, etc. and already know that people DO want such a thing. Presuming you've done that, what would you present to potential users BEFORE actually building the MVP? For what do you need nothing more than some slides? It's not a trick question, you should show potential users slides and validate that what you intend to build is the best it can be. I call it "coffee shop testing" - build a slide of the homepage and the main screen used by registered users; sit in a coffee shop, and buy coffee for anyone who will give you 15 minutes. Show them the two slides and listen; don't explain, ONLY ask.... - For what is this a website? - Would you sign up for it? Why? - Would you tell your friends? Why? - What would you pay for it? Don't explain ANYTHING. If you have to explain something, verbally, you aren't ready to build your MVP - potential customers don't get it. Keep working with that slide alone until you get enough people who say they will sign up and know, roughly, what people will pay. THEN build your MVP and introduce it first to friends, family, peers, etc. to get your earliest adopters. At some point you're going to explore investors. There is no "ready" as the reaction from investors will entirely depend on who you're talking to, why, how much you need, etc. If you want to talk to investors with only the slides as you need capital to build the MVP, your investors are going to be banks, grants, crowdfunding, incubators, and MAYBE angels (banks are investors?! of course they are, don't think that startups only get money from people with cash to give you for equity). Know that it's VERY hard to raise money at this stage; why would I invest in your idea when all you've done is validate that people probably want it - you haven't built anything. A bank will give you a loan to do that, not many investors will take the risk. Still, know not that your MVP is "ready" but that at THAT stage, you have certain sources of capital with which you could have a conversation. When you build the MVP, those choices change. Now that you have something, don't talk to a bank, but a grant might still be viable. Certainly: angels, crowdfunding, accelerators, and maybe even VCs become interested. The extent to which they are depends on the traction you have relative to THEIR expectations - VCs are likely to want some significant adoption or revenue whereas Angels should be excited for your early adoption and validation and interested in helping you scale.PO
-
How do you get a product prototype developed in China sitting in the US?
It varies and it's very very specific to what you want to develop. The concrete design of your circuit matters. Also prototype building costs are usually a factor 10-100 higher than series. If you already have your prototype then you can shop around various manufacturing companies. To do that, you need Gerber files (your PCB design) and a bill of materials. You also need to think about casing: designing it and creating the mold is expensive. If you don't have your prototype yet, I recommend having it engineered in eastern Europe. Custom engineering is cheap there and high quality. IP protection is a problem. One thing to do is to distribute the work to different manufacturers. For the design phase you are safer if you design your prototype in Europe or the US where international patent laws apply. I could give you more specific advise in a phone call, getting to know a bit better what you are trying to build.GF
-
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
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.