Everyone Wants to See the Pipeline Differently. That's the Problem.
The CRO wants to see the pipeline by region. The VP wants it by rep. The director wants it grouped by stage with only late-stage deals. The new manager wants it by product line. And every single one of them asked RevOps for a custom report last Tuesday.
This is the pipeline visibility tax. Everyone on the revenue team needs to see the same data, but nobody needs to see it the same way. And the gap between “what I want to see” and “what’s available” is filled by report requests, spreadsheet exports, and meetings where half the time is spent finding the right view.
The report request treadmill
In most Salesforce orgs, pipeline visibility is a RevOps service. Someone needs a new cut of the data, they ask RevOps. RevOps builds a report or dashboard, shares it, and moves on to the next request.
The problem isn’t that RevOps can’t build reports — they can. The problem is that the requests never stop:
- “Can you add a filter for enterprise deals only?”
- “Can I get this grouped by close month instead of stage?”
- “Can you build a version of this for my team’s territory?”
- “I need this same view but for next quarter.”
Each request is small. In aggregate, they consume hours every week and keep RevOps in a service-desk role instead of a strategic one.
What “see the pipeline your way” actually means
The alternative isn’t “give everyone report builder access.” Most managers don’t want to learn Salesforce report builder, and even if they did, reports don’t give you change tracking, inline editing, or real-time team drill-down.
The alternative is a pipeline view where the end user controls the lens:
Groupings you build yourself. Want to see deals by forecast category? One click. By stage? One click. By account type, then by rep within each type? Two clicks. By a custom field that’s specific to your business? Same — pick the field, apply it, done. No report request needed.
Filters you apply, not request. Need to see only deals above $100K closing this quarter owned by your team? Apply the filters yourself. They persist across views. Remove them when you’re done.
Saved views you own. Built the perfect configuration for your Tuesday pipeline call? Save it. Name it “Tuesday Pipeline Call.” Open it next week in two seconds. Share it with your co-managers so everyone runs the same meeting.
Team drill-down built in. Click through the org hierarchy — from the full org, into a region, into a manager’s team, into a single rep. The groupings, filters, and view stay the same. You’re just changing the scope.
What this replaces
When users can configure their own pipeline views, specific things stop happening:
- The “can you build me a report” request. Gone. The manager builds the view themselves in 30 seconds.
- The Monday morning spreadsheet. Gone. The view is live. It updates as deals move. No export needed.
- The “which report are we using” meeting confusion. Gone. Everyone opens the same saved view. The meeting starts with the data, not a search for the data.
- The RevOps report maintenance backlog. Gone. Views are self-service. RevOps builds the important shared views once, and individual managers build their own.
How this plays out in practice
Monday morning: The VP opens their saved “Team Pipeline” view. It’s grouped by rep, filtered to this quarter, showing open deals only. They scan the subtotals, spot that one rep’s pipeline dropped, and drill into that rep’s deals.
Tuesday pipeline call: The team opens the shared “Pipeline Review” view. Grouped by forecast category. Flow View shows what changed. The manager clicks into Commit to check the deals. No prep was needed — the view is always ready.
Wednesday 1:1: The manager scopes to a single rep. Same view, same groupings, but filtered to one person. They walk through the rep’s deals, flag two for follow-up, edit a close date inline.
Thursday director check-in: The director opens their saved view — grouped by manager, then by stage. They see which managers have enough late-stage pipeline and which don’t. Two clicks to drill into a specific team.
None of these required a report request. None required a spreadsheet. None required RevOps to build or maintain anything. The power is in the hands of the people who need the data.
The RevOps shift
When pipeline visibility is self-service, RevOps gets something back: time. The hours spent building and maintaining individual reports become hours spent on process improvement, forecast accuracy, and strategic analysis.
RevOps still owns the shared views — the standard pipeline review configuration, the forecast call view, the board-level summary. But they’re not building custom views for every manager who wants a slightly different slice. That work is now zero.
Akoonu’s Pipeline Reviews gives every manager the ability to group, filter, drill down, and save their own pipeline views — without report requests, spreadsheet exports, or RevOps involvement. See it in action.
