Feature Request Template: Free Copy/Paste Form + Examples

Need a simple way to collect better product ideas from customers, teammates, or stakeholders? Use the feature request template below to turn vague suggestions into clear, actionable feedback your product team can evaluate and prioritize.

You can copy the template as-is, customize the fields for your team, or use Featurebase to collect, organize, prioritize, and close the loop on feature requests automatically.👇

Free feature request template

Copy and paste this template into your feedback form, product portal, support process, or internal request workflow.

Here’s the same template in a copyable format:

Feature title:
Submitted by:
User role:
Company or account:
Problem to solve:
Use case:
Proposed solution:
Business impact:
Priority:
Current workaround:
Supporting evidence:
Status:
Internal notes:

What is a feature request template?

A feature request template is a structured form used to collect suggestions for new product features or improvements. Instead of receiving vague feedback like “it would be nice if this worked better,” a template helps users explain what they need, why they need it, and how the request would help them.

For SaaS and software teams, feature request templates make product feedback easier to collect, compare, and prioritize. They also help product managers, customer support teams, and customer success teams avoid missing important context when users submit ideas.

A good feature request template standardizes the feedback process so every request includes the information your team needs to decide what to build next.

✨ Start collecting & managing feature requests with Featurebase for free →

Why should you use a feature request form?

The biggest benefit of using a template is standardization.

With a tried-and-tested format, you make sure that you never miss out on critical information. An effective feature request template lets you capture detailed feature requests and your customers can submit all the info without you missing a beat.

A feature request template helps you:

• Collect consistent information from every requester
• Understand the problem behind the requested feature
• Compare requests more fairly
• Reduce back-and-forth with customers
• Give product teams enough context to prioritize
• Track requests from submission to release
• Keep customers updated when something changes

Using a feature request form also ensures a better understanding and prioritization of user needs. By analyzing structured feedback, you can identify common patterns and urgent enhancements, making aligning your development efforts with user expectations and market demands easier.

The goal is not just to collect more ideas. The goal is to collect better feedback that your team can actually use.

Who can use a feature request template?

A feature request template benefits different departments of your business, including your users!

• Startups and SaaS: Templates encourage consistent feedback, boost customer loyalty, and support informed decisions by structuring user suggestions. They also help validate new features for market feasibility.
• Product managers: Structured templates help prioritize and track feature requests, identify trends, and clearly communicate customer ideas, helping align the product roadmap with user actual needs and your business goals.
• Customer support teams: Templates streamline the follow-up process and help collect feature requests and other feedback in one place for the product team to prioritize.
• End users: Effective feature request templates simplify the submission process, enhance transparency, and show you're actively listening to them to build better products.

5 feature request template examples

Different teams collect feature requests in different ways. A small startup may only need a basic form, while a larger SaaS company may need account data, revenue impact, user segments, and prioritization fields.

Here are five feature request templates you can copy and adapt.

1. Basic feature request template

Use this simple template when you want a lightweight way to collect product ideas without overwhelming users.

Feature title:
What feature would you like to request?

Description:
Describe the feature in more detail. What should it do?

Problem:
What problem would this feature solve for you?

Use case:
When would you use this feature?

Priority:
How important is this to you? Low / Medium / High

Screenshots or attachments (optional): Attach relevant screenshots, documents, or additional resources that can help illustrate your request.

When to use this template

This template works well for early-stage SaaS products, simple feedback portals, community forums, or support teams that want a fast way to capture ideas.

It keeps the process easy for users while still giving your team enough information to understand the request.

2. Customer-facing feature request form template

Use this version when customers submit requests through your website, app, feedback portal, or support center.

What would you like us to build or improve?

Tell us about the problem:
What are you trying to do, and what is stopping you today?

How would this feature help you?
Explain the outcome you want to achieve.

How often would you use this?
Daily / Weekly / Monthly / Occasionally

How important is this to your workflow?
Nice to have / Important / Critical

Are you using a workaround today?
If yes, tell us what you currently do instead.

Can we follow up with you about this request?
Yes / No

Attachments or examples:
Upload screenshots, links, videos, or notes that help explain your request.

When to use this template

This template is best for public feedback portals, in-app widgets, help centers, and customer-facing forms.

It focuses on the customer’s problem instead of forcing them to define the exact solution. That distinction matters because customers often know their pain point better than they know the best product implementation.

3. Internal stakeholder feature request template

Use this template when sales, support, customer success, marketing, leadership, or other internal teams submit feature ideas to the product team.

Feature request:
What feature or improvement is being requested?

Requested by:
Who is submitting this request?

Team:
Sales / Support / Customer Success / Marketing / Leadership / Other

Customer or account impacted:
Which customer, segment, or account is this related to?

Problem:
What customer or business problem does this solve?

Evidence:
Include customer quotes, tickets, call notes, recordings, or lost deal context.

Business impact:
Revenue impact / Retention risk / Expansion opportunity / Support reduction / Strategic need

Urgency:
Low / Medium / High / Time-sensitive

Number of customers affected:
How many customers or accounts have requested this?

Current workaround:
How is the customer or team handling this today?

Suggested next step:
Review / Research / Add to roadmap / Discuss with customer / Decline

When to use this template

This template is useful when internal teams regularly pass customer feedback to product managers.

It helps separate one-off opinions from evidence-backed requests. Instead of “a customer asked for this,” the product team gets the account context, impact, urgency, and supporting evidence needed to make a better decision.

4. SaaS product feature request template

Use this template when you need more product and business context before deciding whether to prioritize a request.

Feature title:

Customer segment:
Free / Trial / SMB / Mid-market / Enterprise / Internal user

Requester role:
Admin / End user / Buyer / Developer / Support / Other

Problem statement:
What problem does this request solve?

Desired outcome:
What should the user be able to do after this feature exists?

Use case:
Describe a real scenario where this feature would be used.

Frequency:
How often does this problem occur?

Impact:
Revenue / Retention / Activation / Engagement / Support volume / Compliance / Other

Affected accounts:
List relevant customers, accounts, or user groups.

Existing workaround:
What do users do today instead?

Related requests:
Link similar requests, duplicates, tickets, or discussions.

Priority score:
Optional: use RICE, ICE, value vs. effort, or another prioritization framework.

Product team decision:
New / Reviewing / Planned / Not planned / Shipped

When to use this template

This is the best option for SaaS teams that collect a lot of product feedback and need to compare requests across customers, plans, segments, and revenue impact.

It gives product teams the context they need to prioritize requests without relying only on the loudest customer or the most recent conversation.

5. GitHub issue feature request template

Use this template if your team collects feature requests through GitHub Issues or another developer-focused issue tracker.

## Feature request

### Summary
A short description of the feature you would like to see.

### Problem
What problem does this solve?

### Proposed solution
Describe the solution you would like.

### Alternatives considered
Have you tried any workarounds or alternative approaches?

### Use case
Describe how you would use this feature in a real workflow.

### Additional context
Add screenshots, examples, links, or related issues.

### Priority
Low / Medium / High

When to use this template

This format works well for open-source projects, developer tools, APIs, infrastructure products, and technical communities.

It is especially useful when requesters need to describe technical workflows, alternatives, expected behavior, or implementation context.

Feature request vs. bug report: what’s the difference?

A feature request is a suggestion for new functionality or an improvement to existing functionality. A bug report describes something that is broken, not working as expected, or behaving incorrectly.

The line can sometimes blur. A customer may describe a bug in the form of a feature request, or they may request a new feature because an existing workflow feels broken.

That is why it helps to ask for the problem, use case, expected outcome, and screenshots. These fields help your team understand whether the submission is a bug, a feature request, or a broader product idea.

5 ways to collect better feature requests

A copyable feature request template is a great starting point, but it is not the only way to collect product feedback.

In real SaaS teams, feature requests can come from forms, in-app widgets, support conversations, bug reports, public roadmaps, and surveys. The best setup depends on where your users naturally share feedback and how your product team wants to manage it afterward.

Here are five ways to collect and manage feature requests more effectively.

1. Use the simple feature request template

A simple form is the easiest way to start collecting feature requests. Add it to your product, help center, emails, or surveys, and ask for the basics: title, description, use case, priority, and screenshots.

It’s a good starting point, but once requests grow, you’ll need better ways to organize, deduplicate, and prioritize them.

2. In-app feature request widgets

Featurebase allows you to add in-app widgets for feedback collection. Their biggest advantage is convenience for the customer, as they don’t have to leave the app.

In-app feedback widget (live demo)

Customers can simply open the form and select the feedback type they want - be it a feature request, bug report, or a question about an integration.

The best part is that it suggests existing feature requests, which they can upvote. This reduces duplicate requests while still making everyone's voice count.

In short, users see other's feature requests as they're about to submit their own. If they see something similar (or a duplicate of their request), they can simply visit that original request and upvote it.

Plus, there's a handy screenshot tool that lets them add screenshots for further context to their feedback. Since submitting feedback and feature requests can be done in your app, you increase user engagement and make sure that they submit items such as bug fixes immediately when they see them.

The Ultimate Guide for Collecting In-App Feedback →

3. Bug report template

Bugs can often lead to opportunities that not only fix them but also give you ideas for improving the product further. If your customers encounter a bug, they should have an easy way to report it.

In Featurebase’s bug report template, the first thing that stands out is the custom placeholders. They help guide users through a structured report and give them all of the necessary information. 👇

Custom fields require users to include necessary information when reporting a bug.

This can be super helpful in speeding up bug reports and fixing them. Just imagine the mess you'd have with all users reporting bugs without any structure, app version, etc.

4. Public product roadmap

A public product roadmap is an excellent way to build customer trust and loyalty and keep users informed about what is coming. It makes product improvement and feedback transparent for the end-user, which helps manage expectations and increases loyalty.

Public roadmap made with Featurebase.

The roadmap template's collaborative interface makes it easy to monitor the development process. Users can upvote feature requests and comment on them, which lets you see how popular certain feature requests are, so you can build them first.

Featurebase also allows you to filter based on different user segments when looking at feature requests. This way, you can see potentially which feature negatively affects your business and which one can be incredibly valuable.

For example, if companies with a high monthly recurring revenue desire a specific feature, building it can be highly beneficial. On the other hand, if free trial or low-tier users keep sending new requests for features, they may not be so beneficial for your revenue and bottom line.

The best public roadmap examples for SaaS companies →

5. User experience surveys

Surveys are an excellent way to collect qualitative and quantitative feedback. You can encourage users to take them by placing them on your website, in your app, in emails or anywhere you can add a link.

In-app survey created with Featurebase

Many survey tools offer different survey templates that you can run inside your app or send via email. Be it open-ended surveys, NPS, or other types, your life is much easier with a ready-made template that you can simply activate.

What does a good feature request include?

1. A clear and concise title for the feature request. The title should provide a brief and clear summary of the customer’s requested feature. It also helps categorize similar requests for the future.
2. A detailed description of the feature. The description should provide a thorough understanding of the feature. It should include what the feature does and how it works.
3. Urgency or level of importance. A phrase indicating the urgency of a feature request. This component helps the product team prioritize the requests so they can complete all tasks effectively.
4. A specific scenario where the feature will be useful. This is where customers describe the use case for their feature. It helps in understanding the practical application and relevance of the request.
5. What the user expects to achieve with this feature. The expected outcome of the requested feature helps the team understand the customer’s goals.

Best practices for collecting feature requests

Even with a feature request template in place, there are good practices for effective feedback collection.

1. Make it easy for users

The best way to encourage user feedback is to remove obstacles for them. Give them specific instructions on how to make their feedback impactful for you. Enable different feedback-sharing channels, from public portals to in-app widgets.

The idea is to make everything seamless and smooth for the customer. For instance, even if you’re using email for feedback collection, make it short and sweet. Include a clickable CTA button that takes the customer directly to your feedback form.

Another way Featurebase helps is that it lets you implement Single Sign On. This means customers can authenticate themselves with one click, so you can connect users with their feature requests, letting you paint a complete picture of your user feedback.

2. Ask the right questions

The feedback you get will be as good as the questions you ask your customer. If you ask specific, easy-to-understand questions, you will get the relevant information you seek.

A great practice is to create required fields to guide users in giving you the answers you need. With Featurebase, you can create many different kinds of required fields for your feature request form:

✨ Start collecting & managing feedback with Featurebase for free →

3. Prioritize requests effectively

In an ideal world, you’d be able to implement each and every piece of feedback.

However, the reality is that you can’t stray too far from your specific product vision. Moreover, packing your product with every feature under the sun will make it downright unusable.

In other words, you must decide which feature requests to prioritize. You can do that by creating user segments, focusing on the groups most valuable to your business.

Similarly, you can evaluate the need for a request by looking at its demand. Upvotes offer a super intuitive way to determine the popularity of a feature request.

With a feature request tool like Featurebase, you can use a range of analytical tools to prioritize requests effectively. From feature voting to filtering requests by metrics like customer revenue, you can make data-driven decisions on what ideas to implement.

Finally, to aid your decision-making process further, you can rely on feature prioritization frameworks like RICE. Such frameworks help you determine the impact-effort payoff of a feature request.

4. Always close the feedback loop

You should keep your customers informed throughout the feedback collection process. If you’re turning down their feature request, explain your decision or suggest alternatives.

Similarly, if you’re working on their request, inform them of your plan moving forward. A great way to accomplish this is through a public changelog and release notes.

What is a customer feedback loop and how to create a good one →

Wrapping up

A feature request template helps you collect user feedback consistently and in an organized. It also ensures that customer feedback gets implemented, as you have a structured way of collecting and processing their ideas.

Featurebase helps you collect, manage, and act on feedback effectively with neat feature request forms. You can collect in-app feedback, run surveys, prioritize ideas by customer revenue, and much more.

The onboarding is amazingly quick, and it comes with a Free plan that allows unlimited feedback, so there's no downside to trying it.

✨ Start collecting & managing feedback with Featurebase for free →

FAQs

How do you write a feature request?

To write a good feature request, describe the problem, explain the desired outcome, include a real use case, and add any supporting evidence such as screenshots, examples, or customer quotes. A strong feature request focuses on why the feature is needed, not just what the requester wants built.

What should a feature request template include?

A feature request template should include a title, description, problem statement, use case, priority, expected outcome, supporting evidence, requester details, and status. For SaaS teams, it can also include customer segment, account value, current workaround, and internal notes.

What is the difference between a feature request and a bug report?

A feature request asks for new functionality or an improvement to existing functionality. A bug report describes something that is broken or not working as expected. If the user wants the product to do something new, it is usually a feature request. If the product is failing to do something it already should do, it is usually a bug report.

What is a feature request form?

A feature request form is a structured way for users, customers, or internal teams to submit product ideas. It usually asks for the requested feature, the problem it solves, the use case, the priority, and any supporting context.

How do product teams prioritize feature requests?

Product teams prioritize feature requests by looking at customer demand, business impact, user segment, revenue potential, strategic fit, confidence, and development effort. Many teams use frameworks like RICE, ICE, or value vs. effort to compare requests more consistently.