Skip to main content

Providing Feedback

Your feedback is essential to making Market Maven better. We actively listen to our users and regularly implement suggestions to improve the platform.

Ways to Provide Feedback

Email Feedback

Send detailed feedback directly to our team:

In-Platform Feedback

Use built-in feedback tools:
  • Feedback widget: Click the feedback button in the platform
  • Quick surveys: Respond to occasional short surveys
  • Feature voting: Vote on proposed features and improvements
  • Usage analytics: Help us understand how you use the platform

Support Context

When reporting an issue or suggestion, include enough context for us to reproduce it:
  • Report details: Market, report name, page, filters, and selected visual
  • Browser details: Browser, device, and screen size
  • Screenshots: Show exactly what you are seeing where possible
  • Timing: Date and time when the issue occurred

Types of Feedback We Value

Feature Requests

Help us prioritize new functionality: Data and Analytics:
  • New data sources or metrics
  • Additional analysis capabilities
  • Enhanced visualization options
  • Advanced filtering and segmentation
User Experience:
  • Interface improvements
  • Navigation enhancements
  • Mobile experience upgrades
  • Accessibility improvements
Integration and Export:
  • New export formats
  • Source coverage requests
  • Third-party integrations
  • Report personalisation features

Bug Reports

Help us maintain platform quality: When reporting bugs, include:
  • Detailed steps to reproduce the issue
  • Browser and device information
  • Screenshots or error messages
  • Expected vs actual behavior
  • Date and time when issue occurred
Types of bugs to report:
  • Data display errors
  • Chart or visualization problems
  • Export or download issues
  • Performance problems
  • Mobile compatibility issues

User Experience Feedback

Share your experience using Market Maven: Usability Insights:
  • Confusing interface elements
  • Difficult-to-find features
  • Time-consuming workflows
  • Learning curve challenges
Content and Documentation:
  • Missing or unclear help content
  • Gaps in training materials
  • Suggestions for better explanations
  • Ideas for tutorial improvements

Feature Request Process

Submission

  1. Submit your idea: Use any of our feedback channels
  2. Provide details: Explain the problem and proposed solution
  3. Include context: Share your use case and business value
  4. Suggest priority: Help us understand urgency and importance

Evaluation

Our team evaluates requests based on:
  • User demand: How many users would benefit
  • Business impact: Value to financial services professionals
  • Technical feasibility: Development complexity and resources
  • Strategic alignment: Fit with platform roadmap

Implementation

For approved features:
  • Roadmap inclusion: Features added to development schedule
  • Progress updates: Regular communication on development status
  • Beta testing: Early access for feedback providers
  • Feature announcement: Notification when feature goes live

Feedback Response and Follow-up

Acknowledgment

We respond to all feedback:
  • Email confirmation: Acknowledgment within 24 hours
  • Ticket creation: Formal tracking for complex requests
  • Initial assessment: Preliminary evaluation within 1 week
  • Regular updates: Progress reports for ongoing items

Status Tracking

Stay informed about your feedback:
  • Feedback portal: Track status of your submissions
  • Email updates: Notifications about progress and decisions
  • Feature announcements: Learn when your suggestions go live
  • Thank you credits: Recognition for valuable contributions

Community Involvement

Join our feedback community:
  • User advisory board: Participate in platform direction
  • Beta testing program: Early access to new features
  • Case studies: Share success stories and use cases
  • Referral program: Help other organizations discover Market Maven

Feedback Best Practices

Effective Feature Requests

Be Specific:
  • Clearly describe the desired functionality
  • Explain the business problem being solved
  • Provide examples of how you’d use the feature
Show Business Value:
  • Quantify time savings or efficiency gains
  • Explain competitive advantages
  • Describe impact on decision-making
Consider Context:
  • Explain your role and typical use cases
  • Provide industry context when relevant
  • Share how others might benefit

Constructive Criticism

Focus on Problems:
  • Identify specific pain points
  • Explain the impact on your workflow
  • Suggest potential solutions
Provide Examples:
  • Use specific scenarios from your experience
  • Include screenshots when helpful
  • Reference similar tools or approaches you’ve seen
Balance Feedback:
  • Acknowledge what works well
  • Prioritize the most important issues
  • Consider implementation complexity

Feedback Impact

Recent Improvements

Examples of user-driven enhancements:
  • Enhanced AI Q&A: Improved natural language understanding
  • Mobile Optimization: Better mobile browser experience
  • Export Options: Improvements to visual data export workflows
  • Report Personalisation: Saved views and favourite report improvements

Upcoming Features

Based on your feedback:
  • Source Coverage: Additional public or regulatory datasets
  • Report Personalisation: More ways to save and return to useful analysis states
  • Report Interactions: Improvements to filtering, drill, focus mode, and source lookup guidance
  • Team Workflows: Better support for organisation-based access
Every piece of feedback is valuable, whether it’s a simple suggestion or detailed feature request. We review all submissions and many user ideas become platform improvements.
The most impactful feedback includes specific use cases and explains how the suggestion would improve your workflow or decision-making process.