The forecast needs one renewal relationship per account without erasing legitimate multi-contract customers.
Finance needs a number it can close on, while billing data must retain every valid contract relationship.
Who you’d be doing this for
“I had three account owners ask why their renewal total doubled overnight.”
Dzifa Adekunle · Revenue Operations Manager
Owns the renewal pipeline views used by account teams and Finance during the weekly forecast.
What is at stake
Duplicate account-to-contract relationships are overstating renewal pipeline in Looker. You must weigh a fast correction against preserving valid multi-contract billing records.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- forecast speed vs billing relationship integrity
- narrow correction vs durable prevention
- row-level cleanup vs business-rule fidelity
Why Fivetran
Salesforce billing data and BigQuery reporting shape the renewal forecast that business partners use each week.
Written with these in mind
Not your kind of problem? 43 more at Fivetran, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.