← Fivetran
Complex day at Fivetran

Price an unrestricted ELA before its assumptions become binding

Published Nov 8, 2026

You’re the finance & operations lead. Your team is in the room.

Run your first brief, free

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 ELA price meets an unrestricted promise about future usage.

Finance protects three years of contribution margin while Product protects the buyer's freedom to expand without another purchase.

Who you’d be doing this for

“Procurement booked the signature meeting for five. Now I'm being asked how much every department will run next year.”

Kamau Ngugi · Director of Analytics Engineering · a character in this brief

Leads the buyer's rollout across business units and needs a purchase structure that will accommodate production adoption.

What is at stake

A $6 million enterprise agreement could lock in three years of unpriced usage. You must weigh a binding expansion promise against disputed costs and a buyer who needs an answer by 5 p.m.

Why it isn’t already fixed

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

  • committed value vs bounded usage exposure
  • unrestricted adoption vs contribution margin
  • signature deadline vs defensible underwriting
  • reported profitability vs available cash

Why Fivetran

AWS delivery costs and a Snowflake marketplace purchase sit inside one ELA whose usage promise outlasts the evidence supporting its price.

Written with these in mind

Finance business partnersCommercial finance operatorsUnit economics specialists

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)
    • Partner with Finance and Revenue Accounting to ensure sound revenue recognition, revenue predictability, deal hygiene, and commercial compliance as consumption, ELA, and marketplace structures scale.
    • The role sets the strategy for how deals get structured, priced, routed, reviewed, and approved, and acts as a key commercial advisor to GTM leadership on the structures that drive growth, including ELA and commercial strategy, cross-sell, and new product launches.

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.

Run your first brief, free

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.

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.