Practical worksheet for lean B2B SaaS teams

Prioritize feature requests by customer account

More votes do not always make a request the right choice. Use this worksheet to see which accounts need a change. Check their needs, weigh the work and record your decision.

By WarpixReviewed October 1, 2026For founders and product leads

Start with the decision

See who is behind the votes

Several people may work for the same customer. Count those people, but count their account only once. Then check each account’s plan and payment status. A plan name or revenue value does not prove that an account is paying.

Account data helps you weigh a request. It does not make the choice for you. Keep your goals, the problem, the people affected and the work needed in view.

Use this method whenyour team knows which customers made a request and needs to explain what it chose to build.

A repeatable review

Five checks before you choose a request

  1. 01

    Record the request

    Note the problem, who raised it and when. Keep their own words and how they work around it today.

  2. 02

    Map people to accounts

    Count each person once. Count each account once too. Note how you know a person belongs to that account.

  3. 03

    Check the context

    Keep paying, trial, past due, churned, prospect and unknown states separate. Use a trusted source for each state. Missing data does not mean zero.

  4. 04

    Check freshness and currency

    Note when each value was checked. For revenue, keep the currency and period. Do not add monthly and annual amounts, or mix currencies.

  5. 05

    Make and explain the decision

    Weigh the account data against your goals, reach, urgency and effort. Note how sure you are, what is unknown and who takes the next step.

Fictional worked example

How to prioritize feature requests by revenue

Start with the accounts behind each request. Count each account once, even if several people from it ask for the same feature. Check the revenue data your team supplies. Note its currency, period and date. Then weigh it against your goals and the work needed.

The table uses fictional accounts and values. Warpix does not calculate monthly or lifetime revenue. Your team supplies the values.

Fictional account and revenue data for two feature requests
RequestAccountsReported valueCurrency and periodAs ofStill to check
Export filtersA-101; A-2041,200; 600USD per month, reported plan valueRisk of churn and fit with our goals
Saved report viewsA-101; A-204; A-317; A-4021,200; 600; 450; unavailableUSD per month where suppliedValue for A-402; fit with our goals for all accounts

Each value matches the account in the same position. Scroll the table to see all fields on a small screen.

Count each account once per request

Do not add the two rows together: A-101 and A-204 appear in both. Missing data does not mean zero.

There is no automatic winner

Check which problem matters most, how old the data is and how much work each change needs. Ask what else would have to wait.

Copyable worksheet

Write down the facts and your choice

Copy these fields into a spreadsheet or use the blank CSV. You fill it in yourself. It does not calculate a score or choose a winner.

Fields for your feature request worksheet
FieldWhat to record
RequestName the request. Note the problem, source and date.
Account evidenceCount people and accounts once each. Note how they are linked and where the data came from.
Payment and contextNote the payment state, plan or group. Add a value only if you may use it. Include its currency, period and date. Mark old data.
Decision evidenceNote the reach, urgency and effort. Check the fit with your goals. Write how sure you are and what you still need to know.
Decision recordRecord your choice and why. Name an owner and review date. Add a roadmap link and the next step.
Download CSV template

Where Warpix fits

Keep requests and account data together

The worksheet helps you review requests by hand. Warpix keeps requests, votes and private account data in one place. Link a request to your roadmap, then share an in-app update when work ships.

You supply the account data during founder-assisted setup. Unknown accounts and payment states stay clear. Revenue can inform your choice, but Warpix does not rank requests with AI. Updates appear in the app, with no email or browser push.

Next step

Bring one recent decision to the conversation

We help you set up Warpix. Your 30-day free trial starts when the workspace is ready. Then it is $39/month USD if you choose to continue.

Request your free trial setup