the startups.com platform about startups.comCheck out the new Startups.com - A Comprehensive Startup University
Education
Planning
Mentors
Funding
Customers
Assistants
Clarity
Categories
Business
Sales & Marketing
Funding
Product & Design
Technology
Skills & Management
Industries
Other
Business
Career Advice
Branding
Financial Consulting
Customer Engagement
Strategy
Sectors
Getting Started
Human Resources
Business Development
Legal
Other
Sales & Marketing
Social Media Marketing
Search Engine Optimization
Public Relations
Branding
Publishing
Inbound Marketing
Email Marketing
Copywriting
Growth Strategy
Search Engine Marketing
Sales & Lead Generation
Advertising
Other
Funding
Crowdfunding
Kickstarter
Venture Capital
Finance
Bootstrapping
Nonprofit
Other
Product & Design
Identity
User Experience
Lean Startup
Product Management
Metrics & Analytics
Other
Technology
WordPress
Software Development
Mobile
Ruby
CRM
Innovation
Cloud
Other
Skills & Management
Productivity
Entrepreneurship
Public Speaking
Leadership
Coaching
Other
Industries
SaaS
E-commerce
Education
Real Estate
Restaurant & Retail
Marketplaces
Nonprofit
Other
Dashboard
Browse Search
Answers
Calls
Inbox
Sign Up Log In

Loading...

Share Answer

Menu
Product Development: In the context of an already established software product, should I give what my customers want or what they need?
SC
SC
Scott Colenutt answered:

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.

Talk to Scott Upvote • Share
•••
Share Report

Answer URL

Share Question

  • Share on Twitter
  • Share on LinkedIn
  • Share on Facebook
  • Share on Google+
  • Share by email
About
  • How it Works
  • Success Stories
Experts
  • Become an Expert
  • Find an Expert
Answers
  • Ask a Question
  • Recent Answers
Support
  • Help
  • Terms of Service
Follow

the startups.com platform

Startups Education
Startup Planning
Access Mentors
Secure Funding
Reach Customers
Virtual Assistants

Copyright © 2025 Startups.com. All rights reserved.