The setting
's lets data teams build, transform, govern and validate their data workflows, either in a web browser or with command-line tools.
A year of supported reporting rests on savings that a monthly close has not yet tested.
Keeping three business units in scope protects reporting continuity, while the customer's cost ceiling leaves no room for an open-ended recovery.
Who you’d be doing this for
“Finance asked me which six reports disappear if we cut the other units, and I couldn't give them an agreed list.”
Mikkel Hakkinen · Customer Analytics Engineering Lead · a character in this brief
Supports the ten critical workloads and must explain the proposed renewal scope to three business units.
What is at stake
An enterprise customer may remove two business units from its annual renewal today. You must weigh preserving ten reporting workloads against committing to savings that a full monthly close has not tested.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- three-unit retention vs a fixed operating ceiling
- successful jobs vs accepted reporting value
- binding annual scope vs an untested monthly close
- distributed adoption vs centralized accountability
Why Fivetran
dbt Cloud adoption across three business units must translate into accepted reporting outcomes, not merely successful jobs.
Written with these in mind
Not your kind of problem? 54 more at Fivetran, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Fivetran. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Sr. Customer Solutions Architect (opens in a new tab)
- Own Mutual Success Plans and shape Mutual Account Plans with the AE, mapping whitespace across business units, subsidiaries, and use cases
- Shape the account plan and own the technical side of the expansion pipeline, translating executive-level customer initiatives into scalable data workloads and solutions
- Customer Solutions Architect (Denver) (opens in a new tab)
- Senior Technical Instructor (US East) (opens in a new tab)
- Fivetran and dbt Labs are bringing together two industry-leading companies with a shared mission: helping organizations unlock the full value of their data.
- As we bring our teams and technology together, we’re building on the strengths of both companies while continuing to deliver the products and experiences our customers know and trust.
- Customer Solutions Architect (Austin) (opens in a new tab)
- Customer Solutions Architect (NYC) (opens in a new tab)
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about betting growth on an outside partner or launch.
An investment firm's $480,000 renewal rests on savings that reviewers dispute.
You must weigh a defensible outcome commitment against eight weeks of delivery capacity that signature locks in.
A financial research customer will renew $600,000 tonight only with a firm acceptance date, but its reviewers dispute readiness.
You must weigh a binding success commitment against switching the customer to a supported workflow with a different path to value.
A renewal is frozen because DevOps, security, and procurement disagree on the value of broader telemetry.
You must weigh incident visibility against a commitment the customer cannot easily unwind.
The same setting, from another role
Each is set around Fivetran’s dbt platform, written for a different role. They’re separate briefs, not the same scenario.
Generated dbt changes can pass a quick diff review while missing a downstream contract or lineage dependency.
You must weigh faster review flow against the evidence reviewers need to trust a promotion.
Plausible AISQL answers are reaching warehouses without a dependable link to approved metric definitions.
You must weigh fast containment against preserving useful answers for ambiguous analyst questions.
Changed metric definitions are reaching the catalog while AISQL answers from stale context.
You must weigh faster refreshes against query latency and needless rebuilds.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make an ambitious commitment financially and operationally sound enough to hold up under later scrutiny.
Two weeks before the committed control date, 14% of export events in scope cannot be classified either way.
You have to weigh broken analytics against the promise you made to a regulator and a customer.
A signed contract exposes up to $4.8M in annual service credits, and the reserve is due before the customer goes live.
You weigh machine-generated evidence against a wider scenario range, and the terms hold for the year.
Fourteen of 180 reviewed benefit-change contacts did not match the current eligibility record.
You have to weigh a four-week go-live against an architecture that cannot cheaply be reversed.
