How to add a feature request form to your website

A form or a board?

A form is private: each request goes to you and nobody else sees it. A board is public: requests are listed, visitors vote on the ones they want, and you mark them as planned or done.

Start with a form if only you need to read the requests, you expect a handful a month, or they often include private details. Use a board once the same requests keep arriving, or when you want customers to see that you listen.

Option 1: a simple feature request form

Ask three things, and keep only the first one required:

• What would you like us to add? One line, so requests are easy to scan.
• What would it help you do? This is the useful part: the problem behind the request often has a simpler answer than the feature asked for.
• Email, optional. Only if they’d like a reply or to hear when it ships.

If your site has no server (a static site, Webflow, Framer or most AI-built sites), point the form at a form service. Formspree, Web3Forms and Netlify Forms (for sites hosted on Netlify) all have free plans; each filters spam and emails submissions to you. Replace YOUR_FORM_SERVICE_URL with the address it gives you:

<form action="YOUR_FORM_SERVICE_URL" method="POST">
  <label>What would you like us to add?
    <input name="request" required maxlength="120">
  </label>
  <label>What would it help you do?
    <textarea name="details" rows="4"></textarea>
  </label>
  <label>Your email (optional, if you'd like a reply)
    <input name="email" type="email">
  </label>
  <!-- Honeypot: hidden from people, filled in by bots.
       Use the field name your form service's docs give. -->
  <input name="website" type="text" tabindex="-1" autocomplete="off" style="display:none">
  <button type="submit">Send request</button>
</form>

Put the form on its own page, such as /feature-requests, and link to it from your footer or help menu. Reply to people who leave an email; a short “thanks, it’s on the list” makes them far more likely to send the next idea.

Signs a form is no longer enough

• You keep getting the same request and can’t tell how many people asked.
• You copy requests into a spreadsheet to count and sort them.
• Customers ask “is this on your roadmap?” and you have nowhere to send them.
• You ship something and can’t easily tell the people who asked for it.

That’s what a voting board is for. It also changes who does the sorting: visitors find an existing idea and vote, instead of sending it again.

• Six ways to collect feature requests →

Option 2: a feature voting board

A hosted board gives you the list, the voting, an approval step for new ideas and a public roadmap, without a database or admin screens of your own. Canny, Featurebase, UserNote and several others do this; they differ mostly in price and in whether voters have to sign up.

With UserNote, it’s one script tag on every page. It adds a Feedback button that opens the board, and visitors can suggest and vote without creating an account:

<script src="https://getusernote.com/widget.js" data-workspace="ws_YOUR_BOARD_ID" defer></script>

You get an email for each new idea, approve ideas before they appear (on by default), and mark them Planned, In progress or Completed to update the roadmap. The free plan covers one board and up to 50 ideas.

• Install guides for each platform →
• Canny alternatives compared →

Asking an AI builder for one

Ask Lovable, v0, Bolt or Cursor for “a feature request form” and you’ll most likely get exactly that: a form, saving to a new database table or sending email. That’s fine if a form is what you want. Say so, and ask for the parts it would otherwise leave out:

If you want voting and a public roadmap, the word “form” will lead it astray. Ask for a board instead, and tell it to install a service rather than build one, or it will build its own (I tried this in Lovable: it works in minutes, but leaves out approval, spam limits and notifications). This is the prompt for UserNote; replace the board ID with yours from the dashboard:

• Build it or install it? A test in Lovable →
• Lovable →
• v0 →
• Cursor and Claude Code →

The short version

If only you need to read the requests, add a three-question form and point it at a form service. Once requests repeat and people ask what’s planned, switch to a board, so they can vote and follow your roadmap. And when you ask an AI builder, say which one you want.

Disclosure: I build UserNote, one of the boards mentioned here. It has a free plan with no time limit; Pro is a flat $19/month.