Bringing AI in at Fivetran

Decide when AI may draft causes for seven disputed expense movements

Published Nov 8, 2026

You’re a forward deployed engineer working with Fivetran’s finance team. The team is in the room.

The setting

's is software for building, transforming, governing and validating data workflows. It runs in the browser and from a command line, and data analysts and engineers use it every day.

Product’s expense totals agree, while the reasons behind seven movements remain disputed.

Product needs a view of continuing spend, while Accounting protects the distinction between timing effects and underlying cost changes.

Who you’d be doing this for

“Yesterday I was asked whether we could renew the vendor, and I still had two different explanations for the same increase.”

Radha Bose · Product Director · a character in this brief

Uses the monthly expense review to decide whether vendor commitments leave room for planned product work.

What is at stake

Finance reviewers disagree on why seven of eighteen large Product expense movements occurred. You decide when AI can draft a cause from Snowflake and AWS evidence, and when Finance must supply the explanation.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • consistent categories vs explanations of novel movements
  • current spending signals vs close timing effects
  • broad coverage vs focus on consequential movements
  • cross-source context vs restricted financial access

Why Fivetran

Product operating expense decisions connect vendor commitments and roadmap funding across the combined product portfolio.

Written with these in mind

Finance-focused forward deployed engineersSolutions engineers building governed AI workflowsIntegration engineers who enjoy outcome-based pilots

Not your kind of problem? 62 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.

  • Global Head of Deal Strategy and Operations (opens in a new tab)
    • Shape policies and operational standards for our marketplace presence, and drive cross-functional alignment with Finance, Product, and vendor partners to optimize transaction efficiency and financial accuracy.
    • Fivetran helps organizations automate data movement across the systems, clouds, engines, and tools they rely on. dbt Labs pioneered analytics engineering, helping teams transform data into reliable, governed insights.

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.

Other live briefs connected to this one, and what connects them.

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.