All features
Collect

Public Feedback Boards

Request Mark public feedback boards give SaaS teams one place to collect product ideas, feature requests, votes, and comments. Each board has a secure public URL, its own branding, live/offline controls, and a clear path from user signal to founder dashboard.

When it helps

Why teams use this

Feature requests disappear in private channels

Startups and micro-SaaS builders often hear useful ideas in support replies, DMs, Discord, Slack, and calls. A public board gives every request a durable place to live.

Users cannot see whether anyone is listening

Without visible statuses and updates, customers keep asking about the same features. Request Mark turns the request page into a lightweight progress record.

Internal tools are too heavy for public feedback

Linear, Trello, and Jira are useful for delivery, but they are not designed as customer-facing request portals. Request Mark sits before those tools.

What this helps you do

Create separate boards for products, segments, launches, or communities.
Share secure board URLs in emails, support replies, chat threads, and help docs.
Keep each request attached to comments, vote counts, status, and owner updates.
Pause a board by taking it offline without deleting the underlying feedback.

After setup

What improves after setup

One link for every feedback channel

Share a board from onboarding emails, support replies, product menus, docs, chat communities, or founder updates.

Clear signal before roadmap commitment

Votes and comments help you see whether a request is repeated demand or a loud one-off ask.

A customer-facing history of decisions

Statuses and admin updates show users what is new, planned, in progress, shipped, or closed.

Examples

Real ways to use it

Micro-SaaS changelog follow-up

After shipping a feature, link users back to the request so they can see the shipped status and the reasoning behind the decision.

Beta feedback board

Create a board for a beta cohort, collect launch feedback for two weeks, then take the board offline when the beta window ends.

Founder support reply

When a customer asks for a feature in email, send the board link with their refId so the ask becomes trackable demand.

How it works

  1. 1Create a board and set the product context.
  2. 2Share the secure board URL with a refId for each user.
  3. 3Collect requests, votes, and comments in one dashboard.
  4. 4Publish updates when a request moves to planned, in progress, shipped, or closed.

Best for

  • Startups that need feedback signal before adding a full product operations suite.
  • Indie hackers who want one public link instead of a spreadsheet.
  • SaaS and micro-SaaS teams that already use Linear, Trello, or another delivery tool internally.

Not the best fit for

  • Enterprise teams that need complex roles, approval chains, or procurement workflows from day one.
  • Teams looking for a full product management suite with strategy, discovery, and portfolio planning.
  • Support teams that only need private ticketing and do not want public request visibility.

Recommended plan

Starter

Most founders can start with Starter because 5 boards is enough for one product, one beta, or a few customer segments.

  • 5 public boards
  • Unlimited requests, votes, and comments
  • Admin updates and secure public links

FAQ

What is a public feedback board?+

A public feedback board is a shared page where users can suggest features, vote on requests, leave comments, and see product updates without entering your internal roadmap tool.

Do users need an account to submit feedback?+

No. Request Mark identifies users through the public board link so they can vote and comment without creating another account.