# Feature requests for SaaS teams that want to build the right thing

> Collect feature requests inside your SaaS app, weigh them by customer revenue and tell users when they ship. One flat price, unlimited voters.

URL: https://office.greatwork.company/engage/for/saas
Last updated: 2026-11-21

In a SaaS company, requests arrive from everywhere: support tickets, sales calls, the app itself. The loudest ones aren't always from customers who pay the most. Office Engage puts every request in one list with the revenue behind it, and tells customers when you ship.

## What gets in the way

- Requests scattered across support, sales notes and chat
- No way to tell a $9 customer's request from a $900 one
- Customers never hear that the thing they asked for shipped
- Feedback tools that bill more as more customers vote

## The workflow

1. **Widget in the app.** Add the widget with a signed token, so logged-in users vote in one click and every vote carries their company and plan.
2. **Support and sales add votes.** When a request comes in by ticket or call, the agent adds the customer as a voter with a note.
3. **Sort by revenue.** Before planning, sort ideas by revenue asking and by must-have votes.
4. **Ship and close the loop.** Publish an update linked to the ideas it covers; voters get an email and the in-app badge lights up.

## Example: A 6-person B2B SaaS team

A scheduling SaaS with 1,400 paying accounts adds the widget with company revenue in the token. In the first month 310 customers vote on 90 ideas. Sorted by revenue, "Team reports" (24 votes, $5,100/mo asking) beats "Emoji reactions" (61 votes, $700/mo). They ship reports in six weeks, and all 24 accounts hear about it the same morning.

---

Office by Great Work. Questions or corrections: hello@greatwork.company
