# Account-wide request rollup on the public roadmap

> Show every request tied to a customer company under the roadmap form so one buyer can see what teammates already asked for before opening a duplicate thread.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/account-wide-request-rollup-on-public-roadmap/
- Source: [productlane.com](https://productlane.com/changelog/2025-04-30-customer-support-portal)
- GrowthDex source hub: [Productlane Changelog](/sources/productlane-changelog-productlane-com/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: medium
- Channels: Website, Customer Success, Product
- Stages: support-led growth, expansion, feedback loop, roadmap


## Why this can grow

A request portal gets more believable when it reflects the account instead of a single contact. Seeing the company's existing requests reduces duplicate submissions, gives the buyer a clearer picture of momentum, and turns the roadmap into shared memory rather than a suggestion box. It also helps expansion because more people inside the account can recognize their own problem already on the page.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where account-wide request rollup on the public roadmap can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Website and Customer Success channel.
3. Use the evidence from productlane.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Productlane's Support Portal adds the customer's and their teammates' requests below the public roadmap form whenever the linked requests share the same company email domain in Linear.

## Adjacent tactics in the same lane

- [Customer-adjustable request importance with added context](/growth-ideas/customer-adjustable-request-importance-with-context/) - same source, 2 shared channels, 2 shared stages
- [Request trend view separating weekly demand from spikes](/growth-ideas/request-trend-view-separating-weekly-demand-from-spikes/) - same source, 2 shared channels, 2 shared stages
- [Private roadmap portal with domain-based access](/growth-ideas/private-roadmap-portal-with-domain-based-access/) - same source, 2 shared channels, 1 shared stage
- [Embedded support portal in the product widget](/growth-ideas/embedded-support-portal-in-product-widget/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The roadmap starts working when it answers back](/blog/the-roadmap-starts-working-when-it-answers-back/) - support-led growth, roadmap strategy, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.