The setting
's lets data teams build, transform, govern and validate their data workflows, either in a web browser or with command-line tools.
An onboarding reply needs a clear next step without turning disputed completion into a promise.
Account notes preserve customer context, while implementation records preserve evidence of completed setup.
Who you’d be doing this for
“I told six colleagues they could start Monday, then found out their access still needed approval.”
Bereket Okello · Analytics Engineering Lead · a character in this brief
Coordinates Enterprise onboarding and needs to tell colleagues what still prevents them from accessing dbt Cloud.
What is at stake
Enterprise CSMs must reconcile conflicting records in 17 of 40 onboarding questions. You decide whether AI may infer a remaining step from conflicting notes, or must leave that part of the reply for the CSM.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- account context vs consistent milestone definitions
- clear next steps vs disputed completion
- broad question coverage vs a bounded integration
- current status vs historical commitments
Why Fivetran
Guided Setup spans warehouse configuration, SSO, RBAC/SCIM, and user access, so a completed milestone does not establish that colleagues can start using dbt Cloud.
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)
- Anticipate churn or contraction risks well before they surface, and lead recovery plans for at-risk strategic accounts, including implementation reviews and healthcheck sessions
- Align customer technical strategy with business objectives and commercial plans, and represent the technical view in account strategy discussions
- Customer Solutions Architect (Denver) (opens in a new tab)
- Senior Technical Instructor (US East) (opens in a new tab)
- Adjust instruction on the fly while focusing on learner outcomes
- Deliver live, world-class instruction to train and onboard dbt - Fivetran customers, partners, and GSIs in small (~10), large groups (up to ~30) and webinar audiences (50 - 200)
- 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 people starting something and never quite finishing it.
CSMs checked multiple records for 18 of 30 onboarding replies about next steps.
You decide when AI may draft a next step from Salesforce notes and when the CSM must settle whether a proposal became an agreement.
CSMs reopened account histories for 26 of 40 routine onboarding questions.
Where will you let AI draft the next step, and where must it hold for a CSM because the answer would promise someone’s work?
Enterprise support leaders are waiting on launch answers while account evidence sits across several records.
You must decide whether the AI drafts only from approved guidance or also surfaces tentative working-session details for review.
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 the background systems nobody sees behave dependably even under heavy, high-volume real-world load.
Eleven of the 18 committed workflows still need manual follow-up to provision accounts or hand over equipment, and hiring dates are fixed.
You have to weigh a faster launch against the risk of wrong access or a dropped handoff.
Deal managers are opening dozens of document views to infer which reviewers are engaged.
You have to weigh a faster deal signal against permission-safe visibility.
Incorrect confirmations are sending patients into clinic callbacks and invalid appointment slots.
You have to weigh rapid restoration against the proof needed before changing a live scheduling workflow.