Skip to main content

LiveRem Roadmap - Shape LiveRem's Future Together

The Roadmap feature connects you with the entire LiveRem community to influence product development.

J
Written by Jonathan Morgan
Updated over a week ago

Why use the roadmap?

Your voice matters

Every vote helps the LiveRem team understand which features will have the biggest impact across all users. When you vote for a feature that solves a real problem you're facing, you're helping prioritize development resources toward solutions that matter.

See what's coming

No more wondering "when will feature X be available?" The roadmap shows exactly what's being worked on, what's planned next, and what's been completed. You get transparency into development progress and can plan accordingly.

Connect with the community

Discover what other organisations need and find common ground. When you see a feature with votes from 15+ organisations, you know it addresses a widespread need that could benefit your work too.

Avoid duplicate requests

Before submitting a new idea, see if someone else has already suggested something similar. You can add your vote to existing features rather than splitting support across multiple similar requests.

Getting started

Finding the roadmap

Look for "Roadmap" in your left navigation menu. This takes you to the community hub where all feature development happens transparently.

Understanding what you see

The roadmap shows features from across the entire LiveRem user base. Each feature card displays:

  • How many individual users have voted

  • How many organisations are interested

  • Current development status

  • Brief description of the proposed feature

Making your voice heard

Voting on features

When you see a feature that would help your work, vote for it. Your vote joins others from across the LiveRem community to show collective interest. Popular features with broad support get prioritised for development.

Features that solve real business problems tend to gain momentum quickly when multiple organisations vote for them.

Submitting new ideas

Have an idea that isn't already listed? Submit a new feature request by describing:

  • What you want: A clear, specific description

  • Why it matters: The business value or problem it solves

  • Which area: Select the most relevant category

Your submission becomes visible to the entire community, allowing others to vote if they share your need.

Tracking progress

Development stages

Features move through clear stages so you always know where things stand:

  • Submitted: New ideas awaiting review

  • Under Review: Being evaluated by the product team

  • Planned: Approved and scheduled for development

  • In Progress: Currently being built

  • Testing: Being tested before release

  • Complete: Live and available to use

Stay informed

Features you've voted for or submitted are easy to track. You can filter to see only your contributions or focus on features in specific development stages.

Maximising your impact

Vote Strategically

Focus your votes on features that would genuinely improve your daily work with LiveRem. Well-supported features that solve real problems get built faster.

Be specific when submitting

The clearest, most detailed feature requests tend to get the most votes. Explain not just what you want, but why it would be valuable and how it might work.

Check back regularly

The roadmap updates as development progresses. Features you voted for will move through stages, and new community submissions appear regularly.

Benefits for your organisation

Better planning

Knowing what features are in development helps you plan future processes and training. If a feature you need is "In Progress," you can prepare for its arrival.

Reduced workarounds

Instead of building complex workarounds for missing functionality, see if it's already planned or submit it for community consideration.

Aligned development

When multiple organisations vote for similar features, development resources focus on solutions that benefit the broadest user base, including yours.

Collaborative influence

Your organisation's needs combine with those of others to create a stronger voice for important features. A feature with support from 10+ organisations carries significant weight.

Making the most of community feedback

The roadmap works best when you engage thoughtfully:

  • Vote for features that would genuinely help your work

  • Submit detailed, well-reasoned feature requests

  • Check for existing similar features before submitting new ones

  • Focus on business value when describing why features matter

This collaborative approach ensures development resources go toward features that create the most value for the entire LiveRem community.

Did this answer your question?