How B2B SaaS Teams Manage Feature Requests
B2B SaaS teams face a unique challenge with feature requests. A single enterprise customer might push hard for a specific feature, but building it could serve one account at the expense of the broader product. Here's how B2B teams manage this with public boards.
The B2B Feature Request Challenge
In B2B, feature requests come from:
- Enterprise customers with large contracts and strong opinions
- Sales teams relaying prospect requirements
- Support teams seeing patterns in tickets
- Product managers with strategic priorities
Each channel has its own bias. Enterprise customers are loudest. Sales teams push whatever closes the deal. Without a system, prioritization defaults to whoever has the most leverage.
How a Public Board Balances Input
A public Linear board levels the playing field:
- Every user gets a vote — Not just the biggest account
- Demand is visible — 200 votes from small customers outweighs one loud request
- Context is shared — Users see what else is planned, reducing "why not my feature?" frustration
- Submissions are structured — Requests arrive with context, not as Slack messages
This doesn't mean ignoring enterprise customers. It means giving your team data to make better decisions.
Handling Enterprise-Specific Requests
Some B2B features only matter to one customer. These don't belong on a public board. Keep them in private Linear projects and handle them through direct communication.
For features that would benefit multiple customers, add them to the public board and let the community validate the demand. If an enterprise customer's request gets 50 votes from other users, it confirms the investment is worthwhile.
Involving Customer Success Teams
Customer success teams can use the public board as a communication tool:
- Point customers to existing requests instead of filing duplicates
- Show customers that their feedback is being tracked
- Share board activity in QBRs as evidence of responsiveness
Building a Scalable Process
As your B2B SaaS grows, feature requests grow faster. A public board scales without adding headcount. Users self-serve by browsing, voting, and submitting. Your team reviews aggregated data instead of individual messages.