When every customer wants a different dashboard before they buy. I will not promote

One B2B SaaS problem that sneaks up on you is reporting. The first dashboard feels obvious. You pick the metrics, add the filters, make the charts readable, and it works for the first few customers. Then bigger customers start asking for their version of the same screen: can we split this by country and city? can the account manager see only the accounts they own? can this customer get a saved view for their weekly meeting? can the export include the fields finance cares about? can we hide the stuff their team will never use? None of these is a huge new feature by itself. But the default dashboard slowly turns into what the product team guessed most customers wanted six months ago. The bad version is letting every request become a one-off report. That works for a while, then CS is buried in tiny changes and product has no idea which asks are repeating. The other bad version is saying “wait for the dashboard roadmap” to every customer. That keeps the product clean, but it also means the buyer never gets the view they need to run the workflow. I think the better line is: let CS, implementation, or SE create saved customer-specific views, but track the request underneath it. If five customers keep asking for the same split, filter, or export, that should feed product. If one customer has a weird internal meeting format, it can stay as their saved view. For founders selling B2B SaaS, when did you stop treating customer-specific dashboards as support work and start treating them as part of the product?