When a picklist rename silently broke a dozen pipeline reports

The problem

The play

1. 1
   BDR attribution and reconciliation reporting

   Built inbound and outbound BDR attribution reporting and a revenue-generation reconciliation dashboard, so sourced-meeting counts could be tied back to pipeline instead of argued about in a meeting.

2. 2
   A full report audit after the picklist rename

   Audited roughly 200 saved reports named for the sales-accepted-lead stage, isolated the ones whose status filters had been silently broken by the picklist rename, repointed each to the current value and re-verified the output, treating a rename as a reporting migration rather than a field edit.

3. 3
   Territory routing rebuilt on the real coverage model

   Rebuilt territory routing on new round-robin objects keyed to territory region and account size, replacing rules that no longer reflected how the team was actually covering the market.

4. 4
   Consistent meeting source across two booking tools

   Fixed meeting-type mapping across two inbound scheduling tools so booked meetings landed with a consistent type and source, and remediated the downstream reporting fallout from the earlier stage rename.

5. 5
   Ownership backfilled across the whole book

   Ran a temporary flow to backfill the account-manager field on roughly 3,000 existing-business, cross-sell and renewal opportunities, so ownership reporting worked across the installed base and not just new business.

6. 6
   Post-sale handoff automationSlack

   Wired provisioning-complete signals into onboarding round-robin assignment with Slack alerts, plus a sales-to-post-sale handoff template and 60-day trial check-in reminders, so the lifecycle did not go dark at closed-won.

What it moved

From a LeanScale case studyRead the full case study →