Customer-Revealed Product Roadmap
Distill repeated customer signals into products buyers already want
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
The Customer-Revealed Product Roadmap treats customer contact as a continuous product-discovery system. Founders, salespeople, and product leaders collect observations from many customers and prospects, then distill recurring problems instead of implementing every requested feature. The team combines those patterns with its own vision and point of view, converts the strongest signals into roadmap priorities, and returns to customers to validate whether the resulting product solves the underlying need. The mechanism is repetition and synthesis: one request may be noise, but similar pain expressed across organizations becomes credible evidence. ExactTarget benefited because its sales-driven culture kept founders and employees close to marketers, allowing the company to evolve its software around real workflows while retaining a coherent platform vision.
Origin
Scott Dorsey described this as one of ExactTarget's strong suits, rooted in a founder-led culture where everybody sold, spent time with customers, and listened closely.
Core principles
- 01Stay close to customers and prospects
- 02Listen for recurring needs rather than isolated requests
- 03Balance market evidence with a clear product vision
- 04Convert distilled feedback into concrete product action
How to run it
- 1
Create direct customer contact
Ensure founders and product decision-makers regularly participate in sales, implementation, support, or research conversations. Do not let all market knowledge become filtered through internal reports.
Pro tip Include both current customers and prospects so the sample covers present satisfaction and unmet demand.
Watch out A small number of unusually vocal customers can distort priorities.
- 2
Capture underlying problems
Record the job, constraint, and desired outcome behind each request. Treat a requested feature as evidence rather than an instruction.
Pro tip Ask what the customer would accomplish if the requested capability existed.
Watch out Building literal requests can create a fragmented product without solving the real problem.
- 3
Distill repeated signals
Compare feedback across many individuals and organizations. Identify patterns that recur across customer types or reveal an especially valuable segment.
Pro tip Track frequency, severity, willingness to pay, and strategic fit separately.
Watch out Do not mistake repetition within one account for broad market demand.
- 4
Apply product vision
Combine the market evidence with the team's informed point of view about where the category is going. Choose solutions that serve the recurring need while preserving product coherence.
Pro tip Frame roadmap items as customer outcomes, not lists of requested features.
Watch out Customer listening without strategic judgment can turn the roadmap into a collection of compromises.
- 5
Ship and validate
Deliver the smallest coherent solution and test it with the customers whose feedback informed it. Use adoption and outcome evidence to decide whether to expand, revise, or stop.
Pro tip Invite early participants into structured pilots before broad release.
Watch out Positive comments alone do not prove that the solution changed behavior or created value.
In the wild
ExactTarget's founders sold directly and spent time with marketers. They gathered feedback across customers and prospects, distilled common needs, and used those patterns to shape a SaaS platform that clients wanted rather than relying only on an internally imagined roadmap.
→ Customer proximity helped ExactTarget develop relevant capabilities and sustain a sales- and customer-driven organization.
Common mistakes
Building every requested feature
Individual customers propose solutions suited to their own environment. Implementing each request literally fragments the product and obscures the common problem.
Listening without taking action
Collecting feedback creates no advantage unless the team synthesizes it, makes a decision, and changes the product.
Abandoning the founder's point of view
Market evidence should inform a coherent vision, not replace strategic judgment entirely.
Is it for you?
Best for
It is best for B2B SaaS teams with frequent access to customers, prospects, and usage feedback.
Not ideal for
It is not ideal when customers cannot articulate needs, feedback is sparse, or the product requires a major technology-led leap.
From the transcript
“if you you know are a good listener and you work closely with customers, they will reveal your product roadmap for you.”
“you're really distilling feedback from many, many uh individuals and and organizations, your customers and your prospects in the marketplace.”
“if you can distill that feedback in the right way and take action upon it, uh you can build an amazing solution that clients really…”
From the episode
ExactTarget (acquired by Salesforce) with Scott Dorsey
Scott Dorsey