Release Notes That Close the Loop

Most release notes are a list of changes nobody asked to see. VoteFirst release notes are different because they connect directly to your voting board. Each feature in a release links to the voters who requested it. Customers do not just see what changed, they see that their input drove the change.

Categorized and Structured

Tag each item in a release as a feature, improvement, bugfix, security update, or breaking change. Customers can scan release notes and focus on what matters to them. Breaking changes stand out. Bug fixes are visible but do not clutter the headline features.

Automatic Notifications

When you publish a release, every voter who voted for a feature in that release gets notified. They see that the thing they asked for shipped. No manual follow up emails. No tracking spreadsheet of who asked for what. The notification happens because the data already exists in your voting board.

What You Get

Connected to your voting board

Every release item links to the feature request it fulfilled. Voters see the direct path from their feedback to your release.

Auto notification to voters

Voters who requested shipped features get notified automatically. No manual tracking or email campaigns needed.

Release categorization

Tag items as feature, improvement, bugfix, security, or breaking change. Structured categories help customers scan quickly.

Voter count per feature

Each release item shows how many customers requested it. Social proof that you build what customers want.

Public release history

A chronological page of all releases on your branded page. Customers browse your shipping history anytime.

Custom domain support

Your release notes page lives at releases.yourapp.com. Your branding, your domain, no third party badges.

Frequently Asked Questions

A release notes tool helps you publish structured product updates that customers can browse. VoteFirst goes beyond simple release notes by connecting each entry to the voters who requested the feature, automatically notifying those voters when the release publishes.

When you mark a feature as shipped on your voting board, you can add it to a release. The release note entry links back to the original feature request, showing vote count and the voters who asked for it. This creates a visible path from customer feedback to delivered product.

The release notes feature works best when connected to the voting board, since that is what enables auto notifications to voters. You can also create standalone release entries, but the voter connection and auto notification require the voting board link.

You can create releases and add features to them before publishing. When you are ready, publish the release and notifications go out. Currently, publishing is manual, but you control exactly when it happens.

Each release item can be tagged as: feature (new capability), improvement (enhancement to existing), bugfix (problem fixed), security (security related update), or breaking change (change that requires customer action).

VoteFirst Lite is $4.50/mo and Pro is $19.50/mo. Release notes are included in both plans alongside the voting board, roadmap, and changelog. Flat pricing with no per user charges. Both plans include a 30 day free trial.

Related Use Cases

Start Publishing Release Notes

30 day free trial. Lite starts at $4.50/mo.

Success

Your changes are saved successfully

Error

Something went wrong. Please try again

Warning

Your session will expire in 5 minutes

Info

New update available for download