The Instructions Were Flawed. I Built It Anyway. Then I Fixed It.

The Ask

A best-in-class dashboard suite with historical close rate probability.

Leadership wanted full pipeline visibility — quota attainment, historical close rates, rep-level performance. The instructions called for a scheduled Flow that would loop over every opportunity ever created, calculate historical win/loss rates per rep, and write those rates back to a field used in the dashboards. Run it daily. Keep it current.

I built it exactly as specified.

The Failure

It ran. It hit a wall. Every single time.

The flow triggered on schedule. It looped through open opportunities, got won opps, got lost opps, nested loop through won opps, nested loop through lost opps, calculated the rate, reset the counters, wrote back to the record. The architecture was correct. The logic was sound.

Then it hit Salesforce's Apex CPU time governor limit and failed.

Trimming the dataset to opportunities from 2017 onward — since the last seller was hired in 2019 — didn't help. Still failed. The loop-over-loop architecture was the problem. It wasn't a data issue. It was a structural one. I flagged this clearly to the Salesforce lead and RevOps lead. No response came back.

The Pivot

Stop asking how to fix the flow. Start asking what leadership actually needs to see.

The underlying ask was quota attainment visibility — where each AE stands relative to their number, in real time. The historical close rate was a means to that end, not the end itself.

So I put quarterly quota directly on the User object. Nobody does this. Salesforce doesn't surface it there by default and most orgs don't think to use it. But it meant the quota lived where the rep lived — and any formula field on Opportunity could reference it through the Owner relationship.

• Added Quarterly Quota as a currency field on the User object — one field per rep, updated each quarter
• Built a Projected Amount formula field on Opportunity: Customer_Amount__c × Probability — auto-calculating, no flow required
• Built a custom fiscal quarter formula field to work around Salesforce's fiscal year date filter bug
• No scheduled flow. No loops. No governor limits. No developer required.

The Build

Seven dashboards. 42 reports. Six AEs plus one Sales Leadership master view.

Once the data foundation was right, the reporting layer came together cleanly. Each AE got their own dashboard — pipeline by stage, projected amount vs quota, close rate by quarter, open opportunities by age. The Sales Leadership dashboard rolled everything up into one view.

• 6 individual AE dashboards — pipeline health, quota attainment, projected close, activity tracking
• 1 Sales Leadership master dashboard — full team rollup, comparative attainment, pipeline by rep
• 6 reports cloned and configured per AE dashboard — 36 AE-level reports total
• 6 additional shared reports for the leadership view
• 42 reports total, all filtered and scoped correctly using the custom fiscal quarter field

The Result

Real-time quota attainment visibility. No Apex. No timeouts. No developer.

Leadership got what they actually needed — a live view of where each rep stood against their number, updated automatically on every opportunity change. The original ask (historical close rate via a scheduled flow) was a proxy for this. The delivered solution was more reliable, more maintainable, and required no ongoing intervention.

The broken flow is deactivated. The dashboards are live. The quota field on User gets updated quarterly in under five minutes. The formula does the rest.