Something new at Fivetran

Choose between a balance workflow and a flat fee ahead of invitations

Published Nov 8, 2026

You’re the finance & operations lead. Your 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.

A fixed LakeCompute evaluation budget leaves the treatment of unused money unsettled.

Participants want freedom to experiment, while Finance needs a clear obligation for every remaining balance.

Who you’d be doing this for

“My director approved twenty thousand for the test. Procurement sent it back asking what happens to the money if we finish early.”

Francois Smith · Enterprise Analytics Engineering Lead · a character in this brief

Has approval for a limited LakeCompute evaluation but must explain the financial commitment to departmental finance.

What is at stake

Seven prospective LakeCompute customers want a fixed budget before joining a paid evaluation. You weigh a reusable balance arrangement against marketplace limits and obligations that outlast the test.

Why it isn’t already fixed

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

  • customer flexibility vs continuing financial obligations
  • one customer promise vs different marketplace constraints
  • launch learning vs servicing complexity
  • funded consumption vs a simple participation fee

Why Fivetran

LakeCompute evaluations connect transformation consumption to AWS and Snowflake purchasing routes before customers choose an ongoing commitment.

Written with these in mind

Product finance partnersFinance and operations buildersCommercial finance practitioners

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)
    • It leads a global team across the Americas, EMEA, and APAC and partners closely with Sales, Finance, Legal, Product, Systems, Pricing, and Partner Marketplace to keep decisions fast, consistent, and scalable.
    • Conceptualize and launch new, high-impact commercial strategies and deal constructs (e.g. multi-year deals, shift to consumption-based pricing, and product-specific ELAs) that grow revenue and move the business forward.

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.

Similar problems at other organizations

Like this one, each of these turns on committing to a deal before it checks out.

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.

Other problems with a similar purpose

In each of these, as in this one, the aim is to turn a moment of financial hesitation into something that feels calm, clear, and manageable.